idnits 2.17.1 draft-ietf-radius-auth-servmib-01.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): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-26) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. 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. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == The page length should not exceed 58 lines per page, but there was 11 longer pages, the longest (page 2) being 66 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** 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.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 130 instances of too long lines in the document, the longest one being 10 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 12 has weird spacing: '...), its areas...' == Line 13 has weird spacing: '... its worki...' == Line 17 has weird spacing: '... and may ...' == Line 18 has weird spacing: '...afts as refer...' == Line 21 has weird spacing: '... To learn...' == (29 more instances...) -- 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 (12 February 1998) is 9570 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: '2' is defined on line 537, but no explicit reference was found in the text == Unused Reference: '3' is defined on line 540, but no explicit reference was found in the text == Unused Reference: '4' is defined on line 543, but no explicit reference was found in the text == Unused Reference: '5' is defined on line 548, but no explicit reference was found in the text == Unused Reference: '6' is defined on line 553, but no explicit reference was found in the text == Unused Reference: '7' is defined on line 559, but no explicit reference was found in the text == Unused Reference: '8' is defined on line 564, but no explicit reference was found in the text == Unused Reference: '9' is defined on line 570, but no explicit reference was found in the text == Unused Reference: '10' is defined on line 575, but no explicit reference was found in the text == Unused Reference: '11' is defined on line 580, but no explicit reference was found in the text == Unused Reference: '12' is defined on line 585, but no explicit reference was found in the text == Unused Reference: '13' is defined on line 591, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2138 (ref. '1') (Obsoleted by RFC 2865) ** Obsolete normative reference: RFC 2139 (ref. '2') (Obsoleted by RFC 2866) == Outdated reference: A later version (-06) exists of draft-ietf-radius-ext-00 ** Downref: Normative reference to an Informational draft: draft-ietf-radius-ext (ref. '3') -- Possible downref: Non-RFC (?) normative reference: ref. '4' ** Downref: Normative reference to an Historic RFC: RFC 1901 (ref. '5') ** Obsolete normative reference: RFC 1902 (ref. '6') (Obsoleted by RFC 2578) ** Obsolete normative reference: RFC 1903 (ref. '7') (Obsoleted by RFC 2579) ** Obsolete normative reference: RFC 1904 (ref. '8') (Obsoleted by RFC 2580) ** Obsolete normative reference: RFC 1905 (ref. '9') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 1906 (ref. '10') (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 1907 (ref. '11') (Obsoleted by RFC 3418) ** Obsolete normative reference: RFC 1908 (ref. '12') (Obsoleted by RFC 2576) ** Downref: Normative reference to an Historic RFC: RFC 1909 (ref. '13') Summary: 22 errors (**), 0 flaws (~~), 20 warnings (==), 3 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: Standards Track Bernard Aboba 4 Microsoft 5 12 February 1998 7 RADIUS Authentication Server MIB 9 1. Status of this Memo 11 This document is an Internet-Draft. Internet-Drafts are working docu- 12 ments of the Internet Engineering Task Force (IETF), its areas, and 13 its working groups. Note that other groups may also distribute work- 14 ing documents as Internet-Drafts. 16 Internet-Drafts are draft documents valid for a maximum of six months 17 and may be updated, replaced, or obsoleted by other documents at any 18 time. It is inappropriate to use Internet-Drafts as reference mate- 19 rial or to cite them other than as ``work in progress.'' 21 To learn the current status of any Internet-Draft, please check the 22 ``1id-abstracts.txt'' listing contained in the Internet-Drafts Shadow 23 Directories on ds.internic.net (US East Coast), nic.nordu.net 24 (Europe), ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific Rim). 26 The distribution of this memo is unlimited. It is filed as , and expires August 1, 1998. Please 28 send comments to the authors. 30 2. Abstract 32 This memo defines a set of extensions which instrument RADIUS authen- 33 tication server functions. These extensions represent a portion of the 34 Management Information Base (MIB) for use with network management pro- 35 tocols in the Internet community. Using these extensions IP-based 36 management stations can manage RADIUS authentication servers. 38 3. Introduction 40 This memo defines a portion of the Management Information Base (MIB) 41 for use with network management protocols in the Internet community. 42 In particular, it describes managed objects used for managing RADIUS 43 authentication servers. 45 RADIUS authentication servers are today widely deployed by dialup 46 Internet Service Providers, in order to provide authentication ser- 47 vices. As a result, the effective management of RADIUS authentication 48 servers is of considerable importance. 50 4. The SNMPv2 Network Management Framework 52 The SNMPv2 Network Management Framework consists of four major compo- 53 nents. They are: 55 o RFC 1902 which defines the SMI, the mechanisms used for 56 describing and naming objects for the purpose of management. 58 o RFC 1905 which defines the protocol used for network access to 59 managed objects. 61 o RFC 1907 defines the core set of managed objects for the 62 Internet suite of protocols. 64 o RFC 1909 which defines the administrative aspects of the 65 framework. 67 The Framework permits new objects to be defined for the purpose of 68 experimentation and evaluation. 70 4.1. Object Definitions 72 Managed objects are accessed via a virtual information store, termed 73 the Management Information Base or MIB. Objects in the MIB are defined 74 using the subset of Abstract Syntax Notation One (ASN.1) defined in 75 the SMI. In particular, each object object type is named by an OBJECT 76 IDENTIFIER, an administratively assigned name. The object type 77 together with an object instance serves to uniquely identify a spe- 78 cific instantiation of the object. For human convenience, we often use 79 a textual string, termed the descriptor, to refer to the object type. 81 5. Overview 83 The RADIUS authentication protocol, described in [1], distinguishes 84 between the client function and the server function. In RADIUS authen- 85 tication, clients send Access-Requests, and servers reply with Access- 86 Accepts, Access-Rejects, and Access-Challenges. Typically NAS devices 87 implement the client function, and thus would be expected to implement 88 the RADIUS authentication client MIB, while RADIUS authentication 89 servers implement the server function, and thus would be expected to 90 implement the RADIUS authentication server MIB. 92 However, it is possible for a RADIUS authentication entity to perform 93 both client and server functions. For example, a RADIUS proxy may act 94 as a server to one or more RADIUS authentication clients, while simul- 95 taneously acting as an authentication client to one or more authenti- 96 cation servers. In such situations, it is expected that RADIUS enti- 97 ties combining client and server functionality will support both the 98 client and server MIBs. 100 5.1. Selected objects 102 This MIB module contains five scalars as well as a single table: 104 (1) the RADIUS Authentication Client Table contains one row for each 105 RADIUS authentication client that the server shares a secret with. 107 Each entry in the RADIUS Authentication Client Table includes twelve 108 entries presenting a view of the activity of the RADIUS authentication 109 server. 111 6. Definitions 113 RADIUS-AUTH-SERVER-MIB DEFINITIONS ::= BEGIN 115 IMPORTS 116 MODULE-IDENTITY, OBJECT-TYPE, 117 OBJECT-IDENTITY, experimental, 118 Counter32, Gauge32, Integer32, 119 IpAddress FROM SNMPv2-SMI 120 TEXTUAL-CONVENTION, DisplayString FROM SNMPv2-TC 121 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF; 123 radiusAuthServMIB MODULE-IDENTITY 124 LAST-UPDATED "9802121659Z" 125 ORGANIZATION "IETF RADIUS Working Group." 126 CONTACT-INFO 127 " Glen Zorn 128 Microsoft 129 One Microsoft Way 130 Redmond, WA 98052 131 US 133 Phone: +1 425 703 1559 134 EMail: glennz@microsoft.com" 135 DESCRIPTION 136 "The MIB module for entities implementing the server 137 side of the Remote Access Dialin User Service (RADIUS) 138 authentication protocol." 139 ::= { radiusAuthentication 1 } 141 radius OBJECT-IDENTITY 142 STATUS current 143 DESCRIPTION 144 "The OID assigned to RADIUS MIB work by the IANA." 145 ::= { experimental 79 } 147 radiusAuthentication OBJECT IDENTIFIER ::= {radius 1} 149 radiusAuthServMIBObjects OBJECT IDENTIFIER ::= { radiusAuthServMIB 1 } 151 radiusAuthServ OBJECT IDENTIFIER ::= { radiusAuthServMIBObjects 1 } 152 -- Textual conventions 154 RadiusTime ::= TEXTUAL-CONVENTION 155 DISPLAY-HINT "4d" 156 STATUS current 157 DESCRIPTION 158 "RadiusTime values are 32-bit unsigned integers which 159 measure time in seconds." 160 SYNTAX Gauge32 162 radiusAuthServIdent OBJECT-TYPE 163 SYNTAX DisplayString 164 MAX-ACCESS read-only 165 STATUS current 166 DESCRIPTION 167 "The implementation identification string for the 168 RADIUS authentication server software in use on the 169 system, for example; `FNS-2.1'" 170 ::= {radiusAuthServ 1} 172 radiusAuthServUpTime OBJECT-TYPE 173 SYNTAX RadiusTime 174 MAX-ACCESS read-only 175 STATUS current 176 DESCRIPTION 177 "If the server has a persistent state (e.g., a process), 178 this value will be the time elapsed since it started. 179 For software without persistent state, this value will 180 be zero." 181 ::= {radiusAuthServ 2} 183 radiusAuthServResetTime OBJECT-TYPE 184 SYNTAX RadiusTime 185 MAX-ACCESS read-only 186 STATUS current 187 DESCRIPTION 188 "If the server has a persistent state (e.g., a process) 189 and supports a `reset' operation (e.g., can be told to 190 re-read configuration files), this value will be the 191 time elapsed since the last time the name server was 192 `reset.' For software that does not have persistence or 193 does not support a `reset' operation, this value will be 194 zero." 195 ::= {radiusAuthServ 3} 197 radiusAuthServConfigReset OBJECT-TYPE 198 SYNTAX INTEGER { other(1), 199 reset(2), 200 initializing(3), 201 running(4)} 202 MAX-ACCESS read-write 203 STATUS current 204 DESCRIPTION 205 "Status/action object to reinitialize any persistent 206 server state. When set to reset(2), any persistent 207 server state (such as a process) is reinitialized as if 208 the server had just been started. This value will 209 never be returned by a read operation. When read, one of 210 the following values will be returned: 211 other(1) - server in some unknown state; 212 initializing(3) - server (re)initializing; 213 running(4) - server currently running." 214 ::= {radiusAuthServ 4} 216 -- New Stats proposed by Dale E. Reed Jr (daler@iea-software.com) 218 radiusAuthServTotalAccessRequests OBJECT-TYPE 219 SYNTAX Counter32 220 MAX-ACCESS read-only 221 STATUS current 222 DESCRIPTION 223 "The total number of RADIUS Access-Request packets 224 received since server start-up." 225 ::= { radiusAuthServ 5} 227 radiusAuthServTotalInvalidRequests OBJECT-TYPE 228 SYNTAX Counter32 229 MAX-ACCESS read-only 230 STATUS current 231 DESCRIPTION 232 "The total number of RADIUS Access-Request packets 233 received from unknown addresses since server start-up." 234 ::= { radiusAuthServ 6 } 236 radiusAuthServTotalDupAccessRequests OBJECT-TYPE 237 SYNTAX Counter32 238 MAX-ACCESS read-only 239 STATUS current 240 DESCRIPTION 241 "The total number of duplicate RADIUS Access-Request 242 packets received since server start-up." 243 ::= { radiusAuthServ 7 } 245 radiusAuthServTotalAccessAccepts OBJECT-TYPE 246 SYNTAX Counter32 247 MAX-ACCESS read-only 248 STATUS current 249 DESCRIPTION 250 "The total number of RADIUS Access-Accept packets 251 sent since server start-up." 252 ::= { radiusAuthServ 8 } 254 radiusAuthServTotalAccessRejects OBJECT-TYPE 255 SYNTAX Counter32 256 MAX-ACCESS read-only 257 STATUS current 258 DESCRIPTION 259 "The total number of RADIUS Access-Reject packets 260 sent since server start-up." 261 ::= { radiusAuthServ 9 } 263 radiusAuthServTotalAccessChallenges OBJECT-TYPE 264 SYNTAX Counter32 265 MAX-ACCESS read-only 266 STATUS current 267 DESCRIPTION 268 "The total number of RADIUS Access-Challenge packets 269 sent since server start-up." 270 ::= { radiusAuthServ 10 } 272 radiusAuthServTotalMalformedAccessRequests OBJECT-TYPE 273 SYNTAX Counter32 274 MAX-ACCESS read-only 275 STATUS current 276 DESCRIPTION 277 "The total number of malformed RADIUS Access-Request 278 packets received since server start-up. Bad authenticators 279 are not included as malformed Access-Requests." 280 ::= { radiusAuthServ 11 } 282 radiusAuthServTotalBadAuthenticators OBJECT-TYPE 283 SYNTAX Counter32 284 MAX-ACCESS read-only 285 STATUS current 286 DESCRIPTION 287 "The total number of RADIUS Authentication-Request packets 288 which contained invalid Signature attributes received 289 since server start-up." 290 ::= { radiusAuthServ 12 } 292 radiusAuthServTotalPacketsDropped OBJECT-TYPE 293 SYNTAX Counter32 294 MAX-ACCESS read-only 295 STATUS current 296 DESCRIPTION 297 "The total number of packets dropped with no reply sent." 298 ::= { radiusAuthServ 13 } 300 radiusAuthServTotalUnknownType OBJECT-TYPE 301 SYNTAX Counter32 302 MAX-ACCESS read-only 303 STATUS current 305 DESCRIPTION 306 "The total number of RADIUS packets of unknown type which 307 were received since server start-up." 308 ::= { radiusAuthServ 14 } 310 -- End of new 312 radiusAuthClientTable OBJECT-TYPE 313 SYNTAX SEQUENCE OF RadiusAuthClientEntry 314 MAX-ACCESS not-accessible 315 STATUS current 316 DESCRIPTION 317 "The (conceptual) table listing the RADIUS authentication 318 clients with which the server shares a secret." 319 ::= { radiusAuthServ 15 } 321 radiusAuthClientEntry OBJECT-TYPE 322 SYNTAX RadiusAuthClientEntry 323 MAX-ACCESS not-accessible 324 STATUS current 325 DESCRIPTION 326 "An entry (conceptual row) representing a RADIUS 327 authentication client with which the server shares a secret." 328 INDEX { radiusAuthClientIndex } 329 ::= { radiusAuthClientTable 1 } 331 RadiusAuthClientEntry ::= SEQUENCE { 332 radiusAuthClientIndex Integer32, 333 radiusAuthClientAddress IpAddress, 334 radiusAuthClientID DisplayString, 335 radiusAuthServAccessRequests Counter32, 336 radiusAuthServDupAccessRequests Counter32, 337 radiusAuthServAccessAccepts Counter32, 338 radiusAuthServAccessRejects Counter32, 339 radiusAuthServAccessChallenges Counter32, 340 radiusAuthServMalformedAccessRequests Counter32, 341 radiusAuthServBadAuthenticators Counter32, 342 radiusAuthServPacketsDropped Counter32, 343 radiusAuthServUnknownType Counter32 344 } 346 radiusAuthClientIndex OBJECT-TYPE 347 SYNTAX Integer32 (0..MAX) 348 MAX-ACCESS not-accessible 349 STATUS current 350 DESCRIPTION 351 "A number uniquely identifying each RADIUS 352 authentication client with which this server 353 communicates." 354 ::= { radiusAuthClientEntry 1 } 356 radiusAuthClientAddress OBJECT-TYPE 357 SYNTAX IpAddress 358 MAX-ACCESS read-only 359 STATUS current 360 DESCRIPTION 361 "The NAS-IP-Address of the RADIUS authentication client 362 referred to in this table entry." 363 ::= { radiusAuthClientEntry 2 } 365 radiusAuthClientID OBJECT-TYPE 366 SYNTAX DisplayString 367 MAX-ACCESS read-only 368 STATUS current 369 DESCRIPTION 370 "The NAS-Identifier of the RADIUS authentication client 371 referred to in this table entry. This is not necessarily 372 the same as sysName in MIB II." 373 ::= { radiusAuthClientEntry 3 } 375 -- Server Counters 377 radiusAuthServAccessRequests OBJECT-TYPE 378 SYNTAX Counter32 379 MAX-ACCESS read-only 380 STATUS current 381 DESCRIPTION 382 "The total number of RADIUS Access-Request packets 383 received from this client since server start-up." 384 ::= { radiusAuthClientEntry 4 } 386 radiusAuthServDupAccessRequests OBJECT-TYPE 387 SYNTAX Counter32 388 MAX-ACCESS read-only 389 STATUS current 390 DESCRIPTION 391 "The total number of duplicate RADIUS Access-Request 392 packets received from this client since server start-up." 393 ::= { radiusAuthClientEntry 5 } 395 radiusAuthServAccessAccepts OBJECT-TYPE 396 SYNTAX Counter32 397 MAX-ACCESS read-only 398 STATUS current 399 DESCRIPTION 400 "The total number of RADIUS Access-Accept packets 401 sent to this client since server start-up." 402 ::= { radiusAuthClientEntry 6 } 404 radiusAuthServAccessRejects OBJECT-TYPE 405 SYNTAX Counter32 406 MAX-ACCESS read-only 407 STATUS current 408 DESCRIPTION 409 "The total number of RADIUS Access-Reject packets 410 sent to this client since server start-up." 411 ::= { radiusAuthClientEntry 7 } 413 radiusAuthServAccessChallenges OBJECT-TYPE 414 SYNTAX Counter32 415 MAX-ACCESS read-only 416 STATUS current 417 DESCRIPTION 418 "The total number of RADIUS Access-Challenge packets 419 sent to this client since server start-up." 420 ::= { radiusAuthClientEntry 8 } 422 radiusAuthServMalformedAccessRequests OBJECT-TYPE 423 SYNTAX Counter32 424 MAX-ACCESS read-only 425 STATUS current 426 DESCRIPTION 427 "The total number of malformed RADIUS Access-Request 428 packets received from this client since server start-up. 429 Bad authenticators are not included as 430 malformed Access-Requests." 431 ::= { radiusAuthClientEntry 9 } 433 radiusAuthServBadAuthenticators OBJECT-TYPE 434 SYNTAX Counter32 435 MAX-ACCESS read-only 436 STATUS current 437 DESCRIPTION 438 "The total number of RADIUS Authentication-Request packets 439 which contained invalid Signature attributes received 440 from this client since server start-up." 441 ::= { radiusAuthClientEntry 10 } 443 radiusAuthServPacketsDropped OBJECT-TYPE 444 SYNTAX Counter32 445 MAX-ACCESS read-only 446 STATUS current 447 DESCRIPTION 448 "The total number of packets dropped from this client, 449 with no reply sent." 450 ::= { radiusAuthClientEntry 11 } 452 radiusAuthServUnknownType OBJECT-TYPE 453 SYNTAX Counter32 454 MAX-ACCESS read-only 455 STATUS current 456 DESCRIPTION 457 "The total number of RADIUS packets of unknown type which 458 were received from this client since authentication server 459 start-up." 460 ::= { radiusAuthClientEntry 12 } 462 -- conformance information 464 radiusAuthServMIBConformance 465 OBJECT IDENTIFIER ::= { radiusAuthServMIB 2 } 466 radiusAuthServMIBCompliances 467 OBJECT IDENTIFIER ::= { radiusAuthServMIBConformance 1 } 468 radiusAuthServMIBGroups 469 OBJECT IDENTIFIER ::= { radiusAuthServMIBConformance 2 } 471 -- compliance statements 473 radiusAuthServMIBCompliance MODULE-COMPLIANCE 474 STATUS current 475 DESCRIPTION 476 "The compliance statement for authentication servers 477 implementing the RADIUS Authentication Server MIB." 478 MODULE -- this module 479 MANDATORY-GROUPS { radiusAuthServMIBGroup } 481 ::= { radiusAuthServMIBCompliances 1 } 483 -- units of conformance 485 radiusAuthServMIBGroup OBJECT-GROUP 486 OBJECTS {radiusAuthServIdent, 487 radiusAuthServUpTime, 488 radiusAuthServResetTime, 489 radiusAuthServConfigReset, 490 radiusAuthServTotalAccessRequests, 491 radiusAuthServTotalInvalidRequests, 492 radiusAuthServTotalDupAccessRequests, 493 radiusAuthServTotalAccessAccepts, 494 radiusAuthServTotalAccessRejects, 495 radiusAuthServTotalAccessChallenges, 496 radiusAuthServTotalMalformedAccessRequests, 497 radiusAuthServTotalBadAuthenticators, 498 radiusAuthServTotalPacketsDropped, 499 radiusAuthServTotalUnknownType, 500 radiusAuthClientAddress, 501 radiusAuthClientID, 502 radiusAuthServAccessRequests, 503 radiusAuthServDupAccessRequests, 504 radiusAuthServAccessAccepts, 505 radiusAuthServAccessRejects, 506 radiusAuthServAccessChallenges, 507 radiusAuthServMalformedAccessRequests, 508 radiusAuthServBadAuthenticators, 509 radiusAuthServPacketsDropped, 510 radiusAuthServUnknownType 511 } 512 STATUS current 513 DESCRIPTION 514 "The collection of objects providing management of 515 a RADIUS Authentication Server." 516 ::= { radiusAuthServMIBGroups 1 } 518 END 520 7. Security considerations 522 All MIB variables described in this document are read-only, with the 523 exception of radiusAuthServConfigReset. 525 8. Acknowledgments 527 Thanks to Narendra Gidwani of Microsoft, Allan C. Rubens of MERIT, 528 Carl Rigney of Livingston, and Peter Heitman of American Internet Cor- 529 poration for useful discussions of this problem space. 531 9. References 533 [1] C. Rigney, A. Rubens, W. Simpson, S. Willens. "Remote Authenti- 534 cation Dial In User Service (RADIUS)." RFC 2138, Livingston, Merit, 535 Daydreamer, April, 1997. 537 [2] C. Rigney. "RADIUS Authentication." RFC 2139, Livingston, April, 538 1997. 540 [3] C. Rigney, W. Willats. "RADIUS Extensions." draft-ietf-radius- 541 ext-00.txt, Livingston, January, 1997. 543 [4] "Information processing systems - Open Systems Interconnection - 544 Specification of Abstract Syntax Notation One (ASN.1)", International 545 Organization for Standardization, International Standard 8824, Decem- 546 ber 1987. 548 [5] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Introduc- 549 tion to Community-based SNMPv2", RFC 1901, SNMP Research, Inc., Cisco 550 Systems, Dover Beach Consulting, Inc., International Network Services, 551 January, 1996. 553 [6] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure 554 of Management Information for Version 2 of the Simple Network Manage- 555 ment Protocol (SNMPv2)", RFC 1902, SNMP Research, Inc., Cisco Systems, 556 Dover Beach Consulting, Inc., International Network Services, January, 557 1996. 559 [7] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Textual 560 Conventions for version 2 of the the Simple Network Management Proto- 561 col (SNMPv2)", RFC 1903, SNMP Research, Inc., Cisco Systems, Dover 562 Beach Consulting, Inc., International Network Services, January, 1996. 564 [8] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Confor- 565 mance Statements for version 2 of the the Simple Network Management 566 Protocol (SNMPv2)", RFC 1904, SNMP Research, Inc., Cisco Systems, 567 Dover Beach Consulting, Inc., International Network Services, January, 568 1996. 570 [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol 571 Operations for Version 2 of the Simple Network Management Protocol 572 (SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco Systems, Dover Beach 573 Consulting, Inc., International Network Services, January, 1996. 575 [10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport 576 Mappings for Version 2 of the Simple Network Management Protocol 577 (SNMPv2)", RFC 1906, SNMP Research, Inc., Cisco Systems, Dover Beach 578 Consulting, Inc., International Network Services, January, 1996. 580 [11] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Manage- 581 ment Information Base for Version 2 of the Simple Network Management 582 Protocol (SNMPv2)", RFC 1907, SNMP Research, nc., Cisco Systems, Dover 583 Beach Consulting, Inc., International Network Services, January, 1996. 585 [12] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Coexis- 586 tence between Version 1 and Version 2 of the Internet-standard Network 587 Management Framework", RFC 1908, SNMP Research, Inc., Cisco Systems, 588 Dover Beach Consulting, Inc., International Network Services, January, 589 1996. 591 [13] McCloghrie, K., "An Administrative Infrastructure for SNMPv2", 592 RFC 1909, Cisco Systems, February, 1996. 594 10. Authors' Addresses 596 Glen Zorn 597 Microsoft Corporation 598 One Microsoft Way 599 Redmond, WA 98052 601 Phone: 425-703-1559 602 EMail: glennz@microsoft.com 604 Bernard Aboba 605 Microsoft Corporation 606 One Microsoft Way 607 Redmond, WA 98052 609 Phone: 425-936-6605 610 EMail: bernarda@microsoft.com