idnits 2.17.00 (12 Aug 2021) /tmp/idnits63720/draft-ietf-radius-acc-servmib-05.txt: ** The Abstract section seems to be numbered Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** There is 1 instance of too long lines in the document, the longest one being 29 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 28 has weird spacing: '...t>, and expir...' == Line 427 has weird spacing: '...invalid authe...' -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (31 March 1999) is 8445 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- -- Missing reference section? '1' on line 524 looks like a reference -- Missing reference section? '2' on line 529 looks like a reference -- Missing reference section? '3' on line 533 looks like a reference -- Missing reference section? '4' on line 536 looks like a reference -- Missing reference section? '5' on line 539 looks like a reference -- Missing reference section? '6' on line 545 looks like a reference -- Missing reference section? '7' on line 551 looks like a reference -- Missing reference section? '8' on line 557 looks like a reference -- Missing reference section? '9' on line 562 looks like a reference -- Missing reference section? '10' on line 567 looks like a reference -- Missing reference section? '11' on line 573 looks like a reference -- Missing reference section? '12' on line 633 looks like a reference -- Missing reference section? '13' on line 582 looks like a reference -- Missing reference section? '14' on line 588 looks like a reference -- Missing reference section? '15' on line 634 looks like a reference -- Missing reference section? '16' on line 597 looks like a reference Summary: 6 errors (**), 0 flaws (~~), 3 warnings (==), 18 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 RADIUS Working Group Glen Zorn 2 INTERNET-DRAFT Microsoft 3 Category: Informational Bernard Aboba 4 Microsoft 5 31 March 1999 7 RADIUS Accounting Server MIB 9 1. Status of this Memo 11 This document is an Internet-Draft and is in full conformance with all 12 provisions of Section 10 of RFC2026. 14 Internet-Drafts are working documents of the Internet Engineering Task 15 Force (IETF), its areas, and its working groups. Note that other groups 16 may also distribute working documents as Internet-Drafts. Internet- 17 Drafts are draft documents valid for a maximum of six months and may be 18 updated, replaced, or obsoleted by other documents at any time. It is 19 inappropriate to use Internet-Drafts as reference material or to cite 20 them other than as "work in progress." 22 The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt 24 The list of Internet-Draft Shadow Directories can be accessed at 25 http://www.ietf.org/shadow.html. 27 The distribution of this memo is unlimited. It is filed as , and expires October 1, 1999. Please send 29 comments to the authors. 31 2. Copyright Notice 33 Copyright (C) The Internet Society (1999). All Rights Reserved. 35 3. Abstract 37 This memo defines a set of extensions which instrument RADIUS accounting 38 server functions. These extensions represent a portion of the Management 39 Information Base (MIB) for use with network management protocols in the 40 Internet community. Using these extensions IP-based management stations 41 can manage RADIUS accounting servers. 43 4. Introduction 45 This memo defines a portion of the Management Information Base (MIB) for 46 use with network management protocols in the Internet community. In 47 particular, it describes managed objects used for managing RADIUS 48 accounting servers. 50 RADIUS accounting servers are today widely deployed by dialup Internet 51 Service Providers, in order to provide accounting services. As a result, 52 the effective management of RADIUS accounting servers is of considerable 53 importance. 55 5. The SNMP Management Framework 57 The SNMP Management Framework presently consists of five major 58 components: 60 o An overall architecture, described in RFC 2271 [1]. 62 o Mechanisms for describing and naming objects and events for the 63 purpose of management. The first version of this Structure of 64 Management Information (SMI) is called SMIv1 and described in 65 RFC 1155 [2], RFC 1212 [3] and RFC 1215 [4]. The second version, 66 called SMIv2, is described in RFC 1902 [5], RFC 1903 [6] and RFC 67 1904 [7]. 69 o Message protocols for transferring management information. The 70 first version of the SNMP message protocol is called SNMPv1 and 71 described in RFC 1157 [8]. A second version of the SNMP message 72 protocol, which is not an Internet standards track protocol, is 73 called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10]. 74 The third version of the message protocol is called SNMPv3 and 75 described in RFC 1906 [10], RFC 2272 [11] and RFC 2274 [12]. 77 o Protocol operations for accessing management information. The 78 first set of protocol operations and associated PDU formats is 79 described in RFC 1157 [8]. A second set of protocol operations 80 and associated PDU formats is described in RFC 1905 [13]. 82 o A set of fundamental applications described in RFC 2273 [14] and 83 the view-based access control mechanism described in RFC 2275 84 [15]. 86 Managed objects are accessed via a virtual information store, termed the 87 Management Information Base or MIB. Objects in the MIB are defined 88 using the mechanisms defined in the SMI. 90 This memo specifies a MIB module that is compliant to the SMIv2. A MIB 91 conforming to the SMIv1 can be produced through the appropriate 92 translations. The resulting translated MIB must be semantically 93 equivalent, except where objects or events are omitted because no 94 translation is possible (use of Counter64). Some machine readable 95 information in SMIv2 will be converted into textual descriptions in 96 SMIv1 during the translation process. However, this loss of machine 97 readable information is not considered to change the semantics of the 98 MIB. 100 6. Overview 102 The RADIUS accounting protocol, described in [16], distinguishes between 103 the client function and the server function. In RADIUS accounting, 104 clients send Accounting-Requests, and servers reply with Accounting- 105 Responses. Typically NAS devices implement the client function, and 106 thus would be expected to implement the RADIUS accounting client MIB, 107 while RADIUS accounting servers implement the server function, and thus 108 would be expected to implement the RADIUS accounting server MIB. 110 However, it is possible for a RADIUS accounting entity to perform both 111 client and server functions. For example, a RADIUS proxy may act as a 112 server to one or more RADIUS accounting clients, while simultaneously 113 acting as an accounting client to one or more accounting servers. In 114 such situations, it is expected that RADIUS entities combining client 115 and server functionality will support both the client and server MIBs. 117 6.1. Selected objects 119 This MIB module contains thirteen scalars as well as a single table: 121 (1) the RADIUS Accounting Client Table contains one row for each 122 RADIUS accounting client that the server shares a secret with. 124 Each entry in the RADIUS Accounting Client Table includes eleven columns 125 presenting a view of the activity of the RADIUS accounting server. 127 7. Definitions 129 RADIUS-ACC-SERVER-MIB DEFINITIONS ::= BEGIN 131 IMPORTS 132 MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY, 133 Counter32, Integer32, 134 IpAddress, TimeTicks FROM SNMPv2-SMI 135 SnmpAdminString FROM SNMP-FRAMEWORK-MIB 136 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF 137 mib-2 FROM RFC1213-MIB; 139 radiusAccServMIB MODULE-IDENTITY 140 LAST-UPDATED "9901290000Z" -- 29 Jan 1999 141 ORGANIZATION "IETF RADIUS Working Group." 142 CONTACT-INFO 143 " Bernard Aboba 144 Microsoft 145 One Microsoft Way 146 Redmond, WA 98052 147 US 149 Phone: +1 425 936 6605 150 EMail: bernarda@microsoft.com" 151 DESCRIPTION 152 "The MIB module for entities implementing the server 153 side of the Remote Access Dialin User Service (RADIUS) 154 accounting protocol." 155 REVISION "9903290000Z" -- 29 Mar 1999 156 DESCRIPTION "Initial version as published in RFC xxxx" 157 -- RCC xxxx to be assigned by IANA 158 ::= { radiusAccounting 1 } 160 radiusMIB OBJECT-IDENTITY 161 STATUS current 162 DESCRIPTION 163 "The OID assigned to RADIUS MIB work by the IANA." 164 ::= { mib-2 xxx } -- To be assigned by IANA 166 radiusAccounting OBJECT IDENTIFIER ::= {radiusMIB 2} 168 radiusAccServMIBObjects OBJECT IDENTIFIER ::= { radiusAccServMIB 1 } 170 radiusAccServ OBJECT IDENTIFIER ::= { radiusAccServMIBObjects 1 } 172 radiusAccServIdent OBJECT-TYPE 173 SYNTAX SnmpAdminString 174 MAX-ACCESS read-only 175 STATUS current 176 DESCRIPTION 177 "The implementation identification string for the 178 RADIUS accounting server software in use on the 179 system, for example; `FNS-2.1'" 180 ::= {radiusAccServ 1} 182 radiusAccServUpTime OBJECT-TYPE 183 SYNTAX TimeTicks 184 MAX-ACCESS read-only 185 STATUS current 186 DESCRIPTION 187 "If the server has a persistent state (e.g., a process), 188 this value will be the time elapsed (in hundredths of a 189 second) since the server process was started. 190 For software without persistent state, this value will 191 be zero." 192 ::= {radiusAccServ 2} 194 radiusAccServResetTime OBJECT-TYPE 195 SYNTAX TimeTicks 196 MAX-ACCESS read-only 197 STATUS current 198 DESCRIPTION 199 "If the server has a persistent state (e.g., a process) 200 and supports a `reset' operation (e.g., can be told to 201 re-read configuration files), this value will be the 202 time elapsed (in hundredths of a second) since the 203 server was `reset.' For software that does not 204 have persistence or does not support a `reset' operation, 205 this value will be zero." 206 ::= {radiusAccServ 3} 208 radiusAccServConfigReset OBJECT-TYPE 209 SYNTAX INTEGER { other(1), 210 reset(2), 211 initializing(3), 212 running(4)} 213 MAX-ACCESS read-write 214 STATUS current 215 DESCRIPTION 216 "Status/action object to reinitialize any persistent 217 server state. When set to reset(2), any persistent 218 server state (such as a process) is reinitialized as if 219 the server had just been started. This value will 220 never be returned by a read operation. When read, one of 221 the following values will be returned: 222 other(1) - server in some unknown state; 223 initializing(3) - server (re)initializing; 224 running(4) - server currently running." 225 ::= {radiusAccServ 4} 227 -- New Stats proposed by Dale E. Reed Jr (daler@iea.com) 229 radiusAccServTotalRequests OBJECT-TYPE 230 SYNTAX Counter32 231 MAX-ACCESS read-only 232 STATUS current 233 DESCRIPTION 234 "The number of packets received on the 235 accounting port." 236 ::= { radiusAccServ 5 } 238 radiusAccServTotalInvalidRequests OBJECT-TYPE 239 SYNTAX Counter32 240 MAX-ACCESS read-only 241 STATUS current 242 DESCRIPTION 243 "The number of RADIUS Accounting-Request packets 244 received from unknown addresses." 245 ::= { radiusAccServ 6 } 247 radiusAccServTotalDupRequests OBJECT-TYPE 248 SYNTAX Counter32 249 MAX-ACCESS read-only 250 STATUS current 251 DESCRIPTION 252 "The number of duplicate RADIUS Accounting-Request 253 packets received." 254 ::= { radiusAccServ 7 } 256 radiusAccServTotalResponses OBJECT-TYPE 257 SYNTAX Counter32 258 MAX-ACCESS read-only 259 STATUS current 260 DESCRIPTION 261 "The number of RADIUS Accounting-Response packets sent." 262 ::= { radiusAccServ 8 } 264 radiusAccServTotalMalformedRequests OBJECT-TYPE 265 SYNTAX Counter32 266 MAX-ACCESS read-only 267 STATUS current 268 DESCRIPTION 269 "The number of malformed RADIUS Accounting-Request 270 packets received. Bad authenticators or unknown 271 types are not included as malformed Access-Requests." 272 ::= { radiusAccServ 9 } 274 radiusAccServTotalBadAuthenticators OBJECT-TYPE 275 SYNTAX Counter32 276 MAX-ACCESS read-only 277 STATUS current 278 DESCRIPTION 279 "The number of RADIUS Accounting-Request packets 280 which contained invalid Signature attributes." 281 ::= { radiusAccServ 10 } 283 radiusAccServTotalPacketsDropped OBJECT-TYPE 284 SYNTAX Counter32 285 MAX-ACCESS read-only 286 STATUS current 287 DESCRIPTION 288 "The number of incoming packets silently discarded 289 for a reason other than malformed, bad authenticators, 290 or unknown types." 291 ::= { radiusAccServ 11 } 293 radiusAccServTotalNoRecords OBJECT-TYPE 294 SYNTAX Counter32 295 MAX-ACCESS read-only 296 STATUS current 297 DESCRIPTION 298 "The number of RADIUS Accounting-Request packets 299 which were received and responded to but not 300 recorded." 301 ::= { radiusAccServ 12 } 303 radiusAccServTotalUnknownTypes OBJECT-TYPE 304 SYNTAX Counter32 305 MAX-ACCESS read-only 306 STATUS current 307 DESCRIPTION 308 "The number of RADIUS packets of unknowntype which 309 were received." 310 ::= { radiusAccServ 13 } 312 -- End of new 314 radiusAccClientTable OBJECT-TYPE 315 SYNTAX SEQUENCE OF RadiusAccClientEntry 316 MAX-ACCESS not-accessible 317 STATUS current 318 DESCRIPTION 319 "The (conceptual) table listing the RADIUS accounting 320 clients with which the server shares a secret." 321 ::= { radiusAccServ 14 } 323 radiusAccClientEntry OBJECT-TYPE 324 SYNTAX RadiusAccClientEntry 325 MAX-ACCESS not-accessible 326 STATUS current 327 DESCRIPTION 328 "An entry (conceptual row) representing a RADIUS 329 accounting client with which the server shares a secret." 330 INDEX { radiusAccClientIndex } 331 ::= { radiusAccClientTable 1 } 333 RadiusAccClientEntry ::= SEQUENCE { 334 radiusAccClientIndex Integer32, 335 radiusAccClientAddress IpAddress, 336 radiusAccClientID SnmpAdminString, 337 radiusAccServPacketsDropped Counter32, 338 radiusAccServRequests Counter32, 339 radiusAccServDupRequests Counter32, 340 radiusAccServResponses Counter32, 341 radiusAccServBadAuthenticators Counter32, 342 radiusAccServMalformedRequests Counter32, 343 radiusAccServNoRecords Counter32, 344 radiusAccServUnknownTypes Counter32 345 } 347 radiusAccClientIndex OBJECT-TYPE 348 SYNTAX Integer32 349 MAX-ACCESS not-accessible 350 STATUS current 351 DESCRIPTION 352 "A number uniquely identifying each RADIUS accounting 353 client with which this server communicates." 354 ::= { radiusAccClientEntry 1 } 356 radiusAccClientAddress OBJECT-TYPE 357 SYNTAX IpAddress 358 MAX-ACCESS read-only 359 STATUS current 360 DESCRIPTION 361 "The NAS-IP-Address of the RADIUS accounting client 362 referred to in this table entry." 363 ::= { radiusAccClientEntry 2 } 365 radiusAccClientID OBJECT-TYPE 366 SYNTAX SnmpAdminString 367 MAX-ACCESS read-only 368 STATUS current 369 DESCRIPTION 370 "The NAS-Identifier of the RADIUS accounting client 371 referred to in this table entry. This is not necessarily 372 the same as sysName in MIB II." 373 ::= { radiusAccClientEntry 3 } 375 -- Server Counters 376 -- 377 -- Requests - DupRequests - BadAuthenticators - MalformedRequests - 378 -- UnknownTypes - PacketsDropped - Responses = Pending 379 -- 380 -- Requests - DupRequests - BadAuthenticators - MalformedRequests - 381 -- UnknownTypes - PacketsDropped - NoRecords = entries logged 383 radiusAccServPacketsDropped OBJECT-TYPE 384 SYNTAX Counter32 385 MAX-ACCESS read-only 386 STATUS current 387 DESCRIPTION 388 "The number of incoming packets received 389 from this client and silently discarded 390 for a reason other than malformed, bad 391 authenticators, or unknown types." 392 ::= { radiusAccClientEntry 4 } 394 radiusAccServRequests OBJECT-TYPE 395 SYNTAX Counter32 396 MAX-ACCESS read-only 397 STATUS current 398 DESCRIPTION 399 "The number of packets received from this 400 client on the accounting port." 401 ::= { radiusAccClientEntry 5 } 403 radiusAccServDupRequests OBJECT-TYPE 404 SYNTAX Counter32 405 MAX-ACCESS read-only 406 STATUS current 407 DESCRIPTION 408 "The number of duplicate RADIUS Accounting-Request 409 packets received from this client." 410 ::= { radiusAccClientEntry 6 } 412 radiusAccServResponses OBJECT-TYPE 413 SYNTAX Counter32 414 MAX-ACCESS read-only 415 STATUS current 416 DESCRIPTION 417 "The number of RADIUS Accounting-Response packets 418 sent to this client." 419 ::= { radiusAccClientEntry 7 } 421 radiusAccServBadAuthenticators OBJECT-TYPE 422 SYNTAX Counter32 423 MAX-ACCESS read-only 424 STATUS current 425 DESCRIPTION 426 "The number of RADIUS Accounting-Request packets 427 which contained invalid authenticators received 428 from this client." 429 ::= { radiusAccClientEntry 8 } 431 radiusAccServMalformedRequests OBJECT-TYPE 432 SYNTAX Counter32 433 MAX-ACCESS read-only 434 STATUS current 435 DESCRIPTION 436 "The number of malformed RADIUS Accounting-Request 437 packets which were received from this client. 438 Bad authenticators and unknown types 439 are not included as malformed Accounting-Requests." 440 ::= { radiusAccClientEntry 9 } 442 radiusAccServNoRecords OBJECT-TYPE 443 SYNTAX Counter32 444 MAX-ACCESS read-only 445 STATUS current 446 DESCRIPTION 447 "The number of RADIUS Accounting-Request packets 448 which were received and responded to but not 449 recorded." 450 ::= { radiusAccClientEntry 10 } 452 radiusAccServUnknownTypes OBJECT-TYPE 453 SYNTAX Counter32 454 MAX-ACCESS read-only 455 STATUS current 456 DESCRIPTION 457 "The number of RADIUS packets of unknown type which 458 were received from this client." 459 ::= { radiusAccClientEntry 11 } 461 -- conformance information 463 radiusAccServMIBConformance 464 OBJECT IDENTIFIER ::= { radiusAccServMIB 2 } 465 radiusAccServMIBCompliances 466 OBJECT IDENTIFIER ::= { radiusAccServMIBConformance 1 } 467 radiusAccServMIBGroups 468 OBJECT IDENTIFIER ::= { radiusAccServMIBConformance 2 } 470 -- compliance statements 472 radiusAccServMIBCompliance MODULE-COMPLIANCE 473 STATUS current 474 DESCRIPTION 475 "The compliance statement for accounting servers 476 implementing the RADIUS Accounting Server MIB." 477 MODULE -- this module 478 MANDATORY-GROUPS { radiusAccServMIBGroup } 480 OBJECT radiusAccServConfigReset 481 WRITE-SYNTAX INTEGER { reset(2) } 482 DESCRIPTION "The only SETable value is 'reset' (2)." 484 ::= { radiusAccServMIBCompliances 1 } 486 -- units of conformance 488 radiusAccServMIBGroup OBJECT-GROUP 489 OBJECTS {radiusAccServIdent, 490 radiusAccServUpTime, 491 radiusAccServResetTime, 492 radiusAccServConfigReset, 493 radiusAccServTotalRequests, 494 radiusAccServTotalInvalidRequests, 495 radiusAccServTotalDupRequests, 496 radiusAccServTotalResponses, 497 radiusAccServTotalMalformedRequests, 498 radiusAccServTotalBadAuthenticators, 499 radiusAccServTotalPacketsDropped, 500 radiusAccServTotalNoRecords, 501 radiusAccServTotalUnknownTypes, 502 radiusAccClientAddress, 503 radiusAccClientID, 504 radiusAccServPacketsDropped, 505 radiusAccServRequests, 506 radiusAccServDupRequests, 507 radiusAccServResponses, 508 radiusAccServBadAuthenticators, 509 radiusAccServMalformedRequests, 510 radiusAccServNoRecords, 511 radiusAccServUnknownTypes 512 } 513 STATUS current 514 DESCRIPTION 515 "The collection of objects providing management of 516 a RADIUS Accounting Server." 518 ::= { radiusAccServMIBGroups 1 } 520 END 522 8. References 524 [1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for 525 Describing SNMP Management Frameworks", RFC 2271, Cabletron 526 Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, 527 January 1998. 529 [2] Rose, M., and K. McCloghrie, "Structure and Identification of 530 Management Information for TCP/IP-based Internets", RFC 1155, 531 Performance Systems International, Hughes LAN Systems, May 1990. 533 [3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 1212, 534 Performance Systems International, Hughes LAN Systems, March 1991. 536 [4] M. Rose, "A Convention for Defining Traps for use with the SNMP", 537 RFC 1215, Performance Systems International, March 1991. 539 [5] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure 540 of Management Information for Version 2 of the Simple Network 541 Management Protocol (SNMPv2)", RFC 1902, SNMP Research,Inc., Cisco 542 Systems, Inc., Dover Beach Consulting, Inc., International Network 543 Services, January 1996. 545 [6] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Textual 546 Conventions for Version 2 of the Simple Network Management Protocol 547 (SNMPv2)", RFC 1903, SNMP Research, Inc., Cisco Systems, Inc., 548 Dover Beach Consulting, Inc., International Network Services, 549 January 1996. 551 [7] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Conformance 552 Statements for Version 2 of the Simple Network Management Protocol 553 (SNMPv2)", RFC 1904, SNMP Research, Inc., Cisco Systems, Inc., 554 Dover Beach Consulting, Inc., International Network Services, 555 January 1996. 557 [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network 558 Management Protocol", RFC 1157, SNMP Research, Performance Systems 559 International, Performance Systems International, MIT Laboratory 560 for Computer Science, May 1990. 562 [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 563 "Introduction to Community-based SNMPv2", RFC 1901, SNMP Research, 564 Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., 565 International Network Services, January 1996. 567 [10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport 568 Mappings for Version 2 of the Simple Network Management Protocol 569 (SNMPv2)", RFC 1906, SNMP Research, Inc., Cisco Systems, Inc., 570 Dover Beach Consulting, Inc., International Network Services, 571 January 1996. 573 [11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 574 Processing and Dispatching for the Simple Network Management 575 Protocol (SNMP)", RFC 2272, SNMP Research, Inc., Cabletron Systems, 576 Inc., BMC Software, Inc., IBM T. J. Watson Research, January 1998. 578 [12] Blumenthal, U., and B. Wijnen, "User-based Securi Model (USM) for 579 version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 580 2274, IBM T. J. Watson Research, January 1998. 582 [13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol 583 Operations for Version 2 of the Simple Network Management Protocol 584 (SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco Systems, Inc., 585 Dover Beach Consulting, Inc., International Network Services, 586 January 196. 588 [14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC 589 2273, SNMP Research, Inc., Secure Computing Corporation, Cisco 590 Systems, January 1998 592 [15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access 593 Control Model (VACM) for the Simple Network Management Protocol 594 (SNMP)", RFC 2275, IBM T. J. Watson Research, BMC Software, Inc., 595 Cisco Systems, Inc., January 1998 597 [16] Rigney, C., "RADIUS Accounting", RFC 2139, April 1997. 599 9. Security considerations 601 There are management objects (radiusAccServConfigReset) defined in this 602 MIB that have a MAX-ACCESS clause of read-write and/or read-create. 603 Such objects may be considered sensitive or vulnerable in some network 604 environments. The support for SET operations in a non-secure 605 environment without proper protection can have a negative effect on 606 network operations. 608 There are a number of managed objects in this MIB that may contain 609 sensitive information. These are: 611 radiusAccClientAddress 612 This can be used to determine the address of the RADIUS 613 accounting client with which the server is communicating. 614 This information could be useful in impersonating the client. 616 radiusAccClientID 617 This can be used to determine the client ID for the accounting 618 client with which the server is communicating. This 619 information could be useful in impersonating the client. 621 It is thus important to control even GET access to these objects and 622 possibly to even encrypt the values of these object when sending them 623 over the network via SNMP. Not all versions of SNMP provide features 624 for such a secure environment. 626 SNMPv1 by itself is not a secure environment. Even if the network itself 627 is secure (for example by using IPSec), there is no control as to who on 628 the secure network is allowed to access and GET/SET 629 (read/change/create/delete) the objects in this MIB. 631 It is recommended that the implementers consider the security features 632 as provided by the SNMPv3 framework. Specifically, the use of the User- 633 based Security Model RFC 2274 [12] and the View-based Access Control 634 Model RFC 2275 [15] is recommended. Using these security features, 635 customer/users can give access to the objects only to those principals 636 (users) that have legitimate rights to GET or SET (change/create/delete) 637 them. 639 10. Acknowledgments 641 The authors acknowledge the contributions of the RADIUS Working Group in 642 the development of this MIB. Thanks to Narendra Gidwani of Microsoft, 643 Allan C. Rubens of MERIT, Carl Rigney of Livingston and Peter Heitman of 644 American Internet Corporation for useful discussions of this problem 645 space. 647 11. Authors' Addresses 649 Bernard Aboba 650 Microsoft Corporation 651 One Microsoft Way 652 Redmond, WA 98052 654 Phone: 425-936-6605 655 EMail: bernarda@microsoft.com 656 Glen Zorn 657 Microsoft Corporation 658 One Microsoft Way 659 Redmond, WA 98052 661 Phone: 425-703-1559 662 EMail: glennz@microsoft.com 664 12. Full Copyright Statement 666 Copyright (C) The Internet Society (1999). All Rights Reserved. 667 This document and translations of it may be copied and furnished to 668 others, and derivative works that comment on or otherwise explain it or 669 assist in its implmentation may be prepared, copied, published and 670 distributed, in whole or in part, without restriction of any kind, 671 provided that the above copyright notice and this paragraph are included 672 on all such copies and derivative works. However, this document itself 673 may not be modified in any way, such as by removing the copyright notice 674 or references to the Internet Society or other Internet organizations, 675 except as needed for the purpose of developing Internet standards in 676 which case the procedures for copyrights defined in the Internet 677 Standards process must be followed, or as required to translate it into 678 languages other than English. The limited permissions granted above are 679 perpetual and will not be revoked by the Internet Society or its 680 successors or assigns. This document and the information contained 681 herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE 682 INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR 683 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 684 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 685 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE." 687 13. Expiration Date 689 This memo is filed as , and 690 expires October 1, 1999.