idnits 2.17.00 (12 Aug 2021) /tmp/idnits12920/draft-ietf-radius-servmib-04.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 (2022-05-14) 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) 2022 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. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 12 longer pages, the longest (page 2) being 66 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 12 pages 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 117 instances of too long lines in the document, the longest one being 7 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...' == (33 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.) -- Couldn't find a document date in the document -- date freshness check skipped. 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: '3' is defined on line 509, but no explicit reference was found in the text == Unused Reference: '4' is defined on line 512, but no explicit reference was found in the text == Unused Reference: '5' is defined on line 517, but no explicit reference was found in the text == Unused Reference: '6' is defined on line 522, but no explicit reference was found in the text == Unused Reference: '7' is defined on line 528, but no explicit reference was found in the text == Unused Reference: '8' is defined on line 533, but no explicit reference was found in the text == Unused Reference: '9' is defined on line 539, but no explicit reference was found in the text == Unused Reference: '10' is defined on line 544, but no explicit reference was found in the text == Unused Reference: '11' is defined on line 549, but no explicit reference was found in the text == Unused Reference: '12' is defined on line 554, but no explicit reference was found in the text == Unused Reference: '13' is defined on line 560, 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: draft-ietf-radius-ext has been published as RFC 2869 ** 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 (~~), 21 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 RADIUS Working Group Glen Zorn 3 INTERNET-DRAFT Microsoft 4 Bernard Aboba 5 24 July 1997 Microsoft 7 RADIUS 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 February 1, 1998. Please 28 send comments to the authors. 30 2. Abstract 32 This memo defines a set of extensions which instrument RADIUS server 33 functions. These extensions represent a portion of the Management 34 Information Base (MIB) for use with network management protocols in 35 the Internet community. Using these extensions IP-based management 36 stations can manage RADIUS 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 servers. 45 RADIUS servers are today widely deployed by dialup Internet Service 46 Providers, in order to provide for authentication, authorization, and 47 accounting. As a result, the effective management of RADIUS servers is 48 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 BaseIB. 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 protocol, described in [1] and [2], distinguishes between 84 the client function and the server function; RADIUS clients send 85 requests, and RADIUS servers reply to those requests. In RADIUS 86 authentication, clients send Access-Requests, and servers reply with 87 Access-Accepts, Access-Rejects, and Access-Challenges. In RADIUS 88 accounting, clients send Accounting-Requests, and servers reply with 89 Accounting-Responses. Typically NAS devices implement the client func- 90 tion, and thus would be expected to implement the RADIUS client MIB, 91 while RADIUS servers implement the server function, and thus would be 92 expected to implement the RADIUS server MIB. 94 However, it is possible for a RADIUS entity to perform both client and 95 server functions. For example, a RADIUS proxy may act as a server to 96 one or more RADIUS clients, while simultaneously acting as a client to 97 one or more servers. In such situations, it is expected that RADIUS 98 entities combining client and server functionality will support both 99 the client and server MIBs. 101 5.1. Selected objects 103 This MIB module contains five scalars as well as a single table: 105 (1) the RADIUS Client Table contains one row for each 106 RADIUS client that the server shares a secret with. 108 Each entry in the RADIUS Client Table includes eighteen entries pre- 109 senting a view of the activity of the RADIUS server. 111 6. Definitions 113 RADIUS-SERVER-MIB DEFINITIONS ::= BEGIN 115 IMPORTS 116 MODULE-IDENTITY, OBJECT-TYPE, 117 OBJECT-IDENTITY, experimental, 118 Counter32, Gauge32, Integer32, 119 IpAddress, TimeTicks FROM SNMPv2-SMI 120 TEXTUAL-CONVENTION, RowStatus, 121 TruthValue, DisplayString FROM SNMPv2-TC 122 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF; 124 radius OBJECT-IDENTITY 125 STATUS current 126 DESCRIPTION 127 "The OID assigned to RADIUS MIB work by the IANA." 128 ::= { experimental 79 } 130 radiusServMIB MODULE-IDENTITY 131 LAST-UPDATED "9707211659Z" 132 ORGANIZATION "IETF RADIUS Working Group." 133 CONTACT-INFO 134 " Glen Zorn 135 Microsoft 136 One Microsoft Way 137 Redmond, WA 98052 138 US 140 Phone: +1 425 703 1559 141 EMail: glennz@microsoft.com" 142 DESCRIPTION 143 "The MIB module for entities implementing the server side of 144 the Remote Access Dialin User Service (RADIUS) protocol." 145 ::= { radius 1 } 147 radiusServMIBObjects OBJECT IDENTIFIER ::= { radiusServMIB 1 } 149 radiusServ OBJECT IDENTIFIER ::= { radiusServMIBObjects 1 } 151 -- Textual conventions 152 RadiusTime ::= TEXTUAL-CONVENTION 153 DISPLAY-HINT "4d" 154 STATUS current 155 DESCRIPTION 156 "RadiusTime values are 32-bit unsigned integers which 157 measure time in seconds." 158 SYNTAX Gauge32 160 radiusServIdent OBJECT-TYPE 161 SYNTAX DisplayString 162 MAX-ACCESS read-only 163 STATUS current 164 DESCRIPTION 165 "The implementation identification string for the 166 RADIUS server software in use on the system, for 167 example; `FNS-2.1'" 168 ::= {radiusServ 1} 170 radiusServUpTime OBJECT-TYPE 171 SYNTAX RadiusTime 172 MAX-ACCESS read-only 173 STATUS current 174 DESCRIPTION 175 "If the server has a persistent state (e.g., a process), 176 this value will be the time elapsed since it started. 177 For software without persistent state, this value will 178 be zero." 179 ::= {radiusServ 2} 181 radiusServResetTime OBJECT-TYPE 182 SYNTAX RadiusTime 183 MAX-ACCESS read-only 184 STATUS current 185 DESCRIPTION 186 "If the server has a persistent state (e.g., a process) 187 and supports a `reset' operation (e.g., can be told to 188 re-read configuration files), this value will be the 189 time elapsed since the last time the name server was 190 `reset.' For software that does not have persistence or 191 does not support a `reset' operation, this value will be 192 zero." 193 ::= {radiusServ 3} 195 radiusServConfigReset OBJECT-TYPE 196 SYNTAX INTEGER { other(1), 197 reset(2), 198 initializing(3), 199 running(4)} 200 MAX-ACCESS read-write 201 STATUS current 202 DESCRIPTION 203 "Status/action object to reinitialize any persistent 204 server state. When set to reset(2), any persistent 205 server state (such as a process) is reinitialized as if 206 the server had just been started. This value will 207 never be returned by a read operation. When read, one of 208 the following values will be returned: 209 other(1) - server in some unknown state; 210 initializing(3) - server (re)initializing; 211 running(4) - server currently running." 212 ::= {radiusServ 4} 214 radiusServInvalidClientAddresses OBJECT-TYPE 215 SYNTAX Counter32 216 MAX-ACCESS read-only 217 STATUS current 218 DESCRIPTION 219 "The total number of RADIUS Access-Request packets 220 received from unknown addresses since server start-up." 221 ::= {radiusServ 5} 223 radiusClientTable OBJECT-TYPE 224 SYNTAX SEQUENCE OF RadiusClientEntry 225 MAX-ACCESS not-accessible 226 STATUS current 227 DESCRIPTION 228 "The (conceptual) table listing the RADIUS clients with 229 which the server shares a secret." 230 ::= { radiusServ 6 } 232 radiusClientEntry OBJECT-TYPE 233 SYNTAX RadiusClientEntry 234 MAX-ACCESS not-accessible 235 STATUS current 236 DESCRIPTION 237 "An entry (conceptual row) representing a RADIUS client 238 with which the server shares a secret." 239 INDEX { radiusClientIndex } 240 ::= { radiusClientTable 1 } 242 RadiusClientEntry ::= SEQUENCE { 243 radiusClientIndex Integer32, 244 radiusClientAddress IpAddress, 245 radiusClientID DisplayString, 246 radiusServAccessRequests Counter32, 247 radiusServDupAccessRequests Counter32, 248 radiusServAccessAccepts Counter32, 249 radiusServAccessRejects Counter32, 250 radiusServAccessChallenges Counter32, 251 radiusServMalformedAccessRequests Counter32, 252 radiusServAuthenticationBadAuthenticators Counter32, 253 radiusServPacketsDropped Counter32, 254 radiusServAccountingRequests Counter32, 255 radiusServDupAccountingRequests Counter32, 256 radiusServAccountingResponses Counter32, 257 radiusServAccountingBadAuthenticators Counter32, 258 radiusServMalformedAccountingRequests Counter32, 259 radiusServAccountingNoRecord Counter32, 260 radiusServUnknownType Counter32 261 } 263 radiusClientIndex OBJECT-TYPE 264 SYNTAX Integer32 265 MAX-ACCESS not-accessible 266 STATUS current 267 DESCRIPTION 268 "The RADIUS client referred to in this 269 table entry." 270 ::= { radiusClientEntry 1 } 272 radiusClientAddress OBJECT-TYPE 273 SYNTAX IpAddress 274 MAX-ACCESS read-only 275 STATUS current 276 DESCRIPTION 277 "The NAS-IP-Address of the RADIUS client 278 referred to in this table entry." 279 ::= { radiusClientEntry 2 } 281 radiusClientID OBJECT-TYPE 282 SYNTAX DisplayString 283 MAX-ACCESS read-only 284 STATUS current 285 DESCRIPTION 286 "The NAS-Identifier of the RADIUS client 287 referred to in this table entry." 288 ::= { radiusClientEntry 3 } 290 -- Server Counters 292 radiusServAccessRequests OBJECT-TYPE 293 SYNTAX Counter32 294 MAX-ACCESS read-only 295 STATUS current 296 DESCRIPTION 297 "The total number of RADIUS Access-Request packets 298 received from this client since server start-up." 299 ::= { radiusClientEntry 4 } 301 radiusServDupAccessRequests OBJECT-TYPE 302 SYNTAX Counter32 303 MAX-ACCESS read-only 304 STATUS current 305 DESCRIPTION 306 "The total number of duplicate RADIUS Access-Request 307 packets received from this client since server start-up." 308 ::= { radiusClientEntry 5 } 310 radiusServAccessAccepts OBJECT-TYPE 311 SYNTAX Counter32 312 MAX-ACCESS read-only 313 STATUS current 314 DESCRIPTION 315 "The total number of RADIUS Access-Accept packets 316 sent to this client since server start-up." 317 ::= { radiusClientEntry 6 } 319 radiusServAccessRejects OBJECT-TYPE 320 SYNTAX Counter32 321 MAX-ACCESS read-only 322 STATUS current 323 DESCRIPTION 324 "The total number of RADIUS Access-Reject packets 325 sent to this client since server start-up." 326 ::= { radiusClientEntry 7 } 328 radiusServAccessChallenges OBJECT-TYPE 329 SYNTAX Counter32 330 MAX-ACCESS read-only 331 STATUS current 332 DESCRIPTION 333 "The total number of RADIUS Access-Challenge packets 334 sent to this client since server start-up." 335 ::= { radiusClientEntry 8 } 337 radiusServMalformedAccessRequests OBJECT-TYPE 338 SYNTAX Counter32 339 MAX-ACCESS read-only 340 STATUS current 341 DESCRIPTION 342 "The total number of malformed RADIUS Access-Request 343 packets received from this client since server start-up. 344 Bad authenticators are not included as 345 malformed Access-Requests." 346 ::= { radiusClientEntry 9 } 348 radiusServAuthenticationBadAuthenticators OBJECT-TYPE 349 SYNTAX Counter32 350 MAX-ACCESS read-only 351 STATUS current 352 DESCRIPTION 353 "The total number of RADIUS Authentication-Request packets 354 which contained invalid Signature attributes received 355 from this client since server start-up." 356 ::= { radiusClientEntry 10 } 358 radiusServPacketsDropped OBJECT-TYPE 359 SYNTAX Counter32 360 MAX-ACCESS read-only 361 STATUS current 362 DESCRIPTION 363 "The total number of packets dropped from this client, 364 with no reply sent." 365 ::= { radiusClientEntry 11 } 367 radiusServAccountingRequests OBJECT-TYPE 368 SYNTAX Counter32 369 MAX-ACCESS read-only 370 STATUS current 371 DESCRIPTION 372 "The total number of RADIUS Accounting-Request packets 373 received from this client since server start-up." 374 ::= { radiusClientEntry 12 } 376 radiusServDupAccountingRequests OBJECT-TYPE 377 SYNTAX Counter32 378 MAX-ACCESS read-only 379 STATUS current 380 DESCRIPTION 381 "The total number of duplicate RADIUS Accounting-Request 382 packets received from this client since server start-up." 383 ::= { radiusClientEntry 13 } 385 radiusServAccountingResponses OBJECT-TYPE 386 SYNTAX Counter32 387 MAX-ACCESS read-only 388 STATUS current 389 DESCRIPTION 390 "The total number of RADIUS Accounting-Response packets 391 sent to this client since server start-up." 392 ::= { radiusClientEntry 14 } 394 radiusServAccountingBadAuthenticators OBJECT-TYPE 395 SYNTAX Counter32 396 MAX-ACCESS read-only 397 STATUS current 398 DESCRIPTION 399 "The total number of RADIUS Accounting-Request packets 400 which contained invalid authenticators received 401 from this client since server start-up." 402 ::= { radiusClientEntry 15 } 404 radiusServMalformedAccountingRequests OBJECT-TYPE 405 SYNTAX Counter32 406 MAX-ACCESS read-only 407 STATUS current 408 DESCRIPTION 409 "The total number of malformed RADIUS Accounting-Request 410 packets which were received from this client since 411 server start-up. Bad authenticators are not included as 412 malformed Accounting-Requests." 413 ::= { radiusClientEntry 16 } 415 radiusServAccountingNoRecord OBJECT-TYPE 416 SYNTAX Counter32 417 MAX-ACCESS read-only 418 STATUS current 419 DESCRIPTION 420 "The total number of RADIUS Accounting-Request packets 421 which were received from this client but not recorded 422 since server start-up." 423 ::= { radiusClientEntry 17 } 425 radiusServUnknownType OBJECT-TYPE 426 SYNTAX Counter32 427 MAX-ACCESS read-only 428 STATUS current 429 DESCRIPTION 430 "The total number of RADIUS packets of unknown type which 431 were received from this client since server start-up." 432 ::= { radiusClientEntry 18 } 434 -- conformance information 436 radiusServMIBConformance 437 OBJECT IDENTIFIER ::= { radiusServMIB 2 } 438 radiusServMIBCompliances 439 OBJECT IDENTIFIER ::= { radiusServMIBConformance 1 } 440 radiusServMIBGroups 441 OBJECT IDENTIFIER ::= { radiusServMIBConformance 2 } 443 -- compliance statements 445 radiusServMIBCompliance MODULE-COMPLIANCE 446 STATUS current 447 DESCRIPTION 448 "The compliance statement for servers implementing the RADIUS 449 MIB." 450 MODULE -- this module 451 MANDATORY-GROUPS { radiusServMIBGroup } 453 ::= { radiusServMIBCompliances 1 } 455 -- units of conformance 457 radiusServMIBGroup OBJECT-GROUP 458 OBJECTS {radiusServIdent, 459 radiusServUpTime, 460 radiusServResetTime, 461 radiusServConfigReset, 462 radiusServInvalidClientAddresses, 463 radiusClientAddress, 464 radiusClientID, 465 radiusServAccessRequests, 466 radiusServDupAccessRequests, 467 radiusServAccessAccepts, 468 radiusServAccessRejects, 469 radiusServAccessChallenges, 470 radiusServMalformedAccessRequests, 471 radiusServAuthenticationBadAuthenticators, 472 radiusServPacketsDropped, 473 radiusServAccountingRequests, 474 radiusServDupAccountingRequests, 475 radiusServAccountingResponses, 476 radiusServAccountingBadAuthenticators, 477 radiusServMalformedAccountingRequests, 478 radiusServAccountingNoRecord, 479 radiusServUnknownType 480 } 481 STATUS current 482 DESCRIPTION 483 "The collection of objects providing management of 484 a RADIUS Server." 485 ::= { radiusServMIBGroups 1 } 487 END 489 7. Security considerations 491 All MIB variables described in this document are read-only, with the 492 exception of radiusServConfigReset. 494 8. Acknowledgments 496 Thanks to Narendra Gidwani of Microsoft, Allan C. Rubens of MERIT, 497 Carl Rigney of Livingston, and Peter Heitman of American Internet Cor- 498 poration for useful discussions of this problem space. 500 9. References 502 [1] C. Rigney, A. Rubens, W. Simpson, S. Willens. "Remote Authenti- 503 cation Dial In User Service (RADIUS)." RFC 2138, Livingston, Merit, 504 Daydreamer, April, 1997. 506 [2] C. Rigney. "RADIUS Accounting." RFC 2139, Livingston, April, 507 1997. 509 [3] C. Rigney, W. Willats. "RADIUS Extensions." draft-ietf-radius- 510 ext-00.txt, Livingston, January, 1997. 512 [4] "Information processing systems - Open Systems Interconnection - 513 Specification of Abstract Syntax Notation One (ASN.1)", International 514 Organization for Standardization, International Standard 8824, Decem- 515 ber 1987. 517 [5] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Introduc- 518 tion to Community-based SNMPv2", RFC 1901, SNMP Research, Inc., Cisco 519 Systems, Dover Beach Consulting, Inc., International Network Services, 520 January, 1996. 522 [6] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure 523 of Management Information for Version 2 of the Simple Network 524 Management Protocol (SNMPv2)", RFC 1902, SNMP Research, Inc., Cisco 525 Systems, Dover Beach Consulting, Inc., International Network Services, 526 January, 1996. 528 [7] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Textual 529 Conventions for version 2 of the the Simple Network Management Proto- 530 col (SNMPv2)", RFC 1903, SNMP Research, Inc., Cisco Systems, Dover 531 Beach Consulting, Inc., International Network Services, January, 1996. 533 [8] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Confor- 534 mance Statements for version 2 of the the Simple Network Management 535 Protocol (SNMPv2)", RFC 1904, SNMP Research, Inc., Cisco Systems, 536 Dover Beach Consulting, Inc., International Network Services, January, 537 1996. 539 [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol 540 Operations for Version 2 of the Simple Network Management Protocol 541 (SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco Systems, Dover Beach 542 Consulting, Inc., International Network Services, January, 1996. 544 [10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport 545 Mappings for Version 2 of the Simple Network Management Protocol 546 (SNMPv2)", RFC 1906, SNMP Research, Inc., Cisco Systems, Dover Beach 547 Consulting, Inc., International Network Services, January, 1996. 549 [11] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Manage- 550 ment Information Base for Version 2 of the Simple Network Management 551 Protocol (SNMPv2)", RFC 1907, SNMP Research, nc., Cisco Systems, Dover 552 Beach Consulting, Inc., International Network Services, January, 1996. 554 [12] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Coexis- 555 tence between Version 1 and Version 2 of the Internet-standard Network 556 Management Framework", RFC 1908, SNMP Research, Inc., Cisco Systems, 557 Dover Beach Consulting, Inc., International Network Services, January, 558 1996. 560 [13] McCloghrie, K., "An Administrative Infrastructure for SNMPv2", 561 RFC 1909, Cisco Systems, February, 1996. 563 10. Authors' Addresses 565 Glen Zorn 566 Microsoft Corporation 567 One Microsoft Way 568 Redmond, WA 98052 570 Phone: 425-703-1559 571 EMail: glennz@microsoft.com 573 Bernard Aboba 574 Microsoft Corporation 575 One Microsoft Way 576 Redmond, WA 98052 578 Phone: 425-936-6605 579 EMail: bernarda@microsoft.com