idnits 2.17.1 draft-ietf-radius-clientmib-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 (2024-04-23) 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. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 10 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 11 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 109 instances of too long lines in the document, the longest one being 10 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 11 has weird spacing: '...), its areas...' == Line 12 has weird spacing: '... its worki...' == Line 16 has weird spacing: '... and may ...' == Line 17 has weird spacing: '...afts as refer...' == Line 20 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 489, but no explicit reference was found in the text == Unused Reference: '4' is defined on line 492, but no explicit reference was found in the text == Unused Reference: '5' is defined on line 497, but no explicit reference was found in the text == Unused Reference: '6' is defined on line 502, but no explicit reference was found in the text == Unused Reference: '7' is defined on line 508, but no explicit reference was found in the text == Unused Reference: '8' is defined on line 513, but no explicit reference was found in the text == Unused Reference: '9' is defined on line 519, but no explicit reference was found in the text == Unused Reference: '10' is defined on line 524, but no explicit reference was found in the text == Unused Reference: '11' is defined on line 529, but no explicit reference was found in the text == Unused Reference: '12' is defined on line 535, but no explicit reference was found in the text == Unused Reference: '13' is defined on line 541, 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 (~~), 21 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 RADIUS Working Group Bernard Aboba 2 INTERNET-DRAFT Microsoft 3 Glen Zorn 4 24 July 1997 Microsoft 6 RADIUS Client MIB 8 1. Status of this Memo 10 This document is an Internet-Draft. Internet-Drafts are working docu- 11 ments of the Internet Engineering Task Force (IETF), its areas, and 12 its working groups. Note that other groups may also distribute work- 13 ing documents as Internet-Drafts. 15 Internet-Drafts are draft documents valid for a maximum of six months 16 and may be updated, replaced, or obsoleted by other documents at any 17 time. It is inappropriate to use Internet-Drafts as reference mate- 18 rial or to cite them other than as ``work in progress.'' 20 To learn the current status of any Internet-Draft, please check the 21 ``1id-abstracts.txt'' listing contained in the Internet-Drafts Shadow 22 Directories on ds.internic.net (US East Coast), nic.nordu.net 23 (Europe), ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific Rim). 25 The distribution of this memo is unlimited. It is filed as , and expires February 1, 1998. Please 27 send comments to the authors. 29 2. Abstract 31 This memo defines a set of extensions which instrument RADIUS client 32 functions. These extensions represent a portion of the Management 33 Information Base (MIB) for use with network management protocols in 34 the Internet community. Using these extensions IP-based management 35 stations can manage RADIUS clients. 37 3. Introduction 39 This memo defines a portion of the Management Information Base (MIB) 40 for use with network management protocols in the Internet community. 41 In particular, it describes managed objects used for managing RADIUS 42 clients. 44 Today a wide range of network devices, including routers and NASes, 45 act as RADIUS clients in order to provide authentication, authoriza- 46 tion, and accounting services. As a result, the effective management 47 of RADIUS clients is of considerable importance. 49 4. The SNMPv2 Network Management Framework 51 The SNMPv2 Network Management Framework consists of four major compo- 52 nents. They are: 54 o RFC 1902 which defines the SMI, the mechanisms used for 55 describing and naming objects for the purpose of management. 57 o RFC 1905 which defines the protocol used for network access to 58 managed objects. 60 o RFC 1907 defines the core set of managed objects for the 61 Internet suite of protocols. 63 o RFC 1909 which defines the administrative aspects of the 64 framework. 66 The Framework permits new objects to be defined for the purpose of 67 experimentation and evaluation. 69 4.1. Object Definitions 71 Managed objects are accessed via a virtual information store, termed 72 the Management Information Base or MIB. Objects in the MIB are 73 defined using the subset of Abstract Syntax Notation One (ASN.1) 74 defined in the SMI. In particular, each object object type is named by 75 an OBJECT IDENTIFIER, an administratively assigned name. The object 76 type together with an object instance serves to uniquely identify a 77 specific instantiation of the object. For human convenience, we often 78 use a textual string, termed the descriptor, to refer to the object 79 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 102 This MIB module contains two scalars as well as a single table: 104 (1) the RADIUS Server Table contains one row for each 105 RADIUS server that the client shares a secret with. 107 Each entry in the RADIUS Server Table includes twenty entries present- 108 ing a view of the activity of the RADIUS client. 110 6. Definitions 112 RADIUS-CLIENT-MIB DEFINITIONS ::= BEGIN 114 IMPORTS 115 MODULE-IDENTITY, OBJECT-TYPE, 116 OBJECT-IDENTITY, experimental, 117 Counter32, Gauge32, Integer32, 118 IpAddress, TimeTicks FROM SNMPv2-SMI 119 TEXTUAL-CONVENTION, RowStatus, 120 TruthValue, DisplayString FROM SNMPv2-TC 121 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF; 123 radius OBJECT-IDENTITY 124 STATUS current 125 DESCRIPTION 126 "The OID assigned to RADIUS MIB work by the IANA." 127 ::= { experimental 79 } 129 radiusClientMIB MODULE-IDENTITY 130 LAST-UPDATED "9707211659Z" 131 ORGANIZATION "IETF RADIUS Working Group." 132 CONTACT-INFO 133 " Bernard Aboba 134 Microsoft 135 One Microsoft Way 136 Redmond, WA 98052 137 US 139 Phone: +1 425 936 6605 140 EMail: bernarda@microsoft.com" 141 DESCRIPTION 142 "The MIB module for entities implementing the client side of 143 the Remote Access Dialin User Service (RADIUS) protocol." 144 ::= { radius 2 } 146 radiusClientMIBObjects OBJECT IDENTIFIER ::= { radiusClientMIB 1 } 148 radiusClient OBJECT IDENTIFIER ::= { radiusClientMIBObjects 1 } 150 radiusClientInvalidServerAddresses OBJECT-TYPE 151 SYNTAX Counter32 152 MAX-ACCESS read-only 153 STATUS current 154 DESCRIPTION 155 "The total number of RADIUS Access-Response packets 156 received from unknown addresses since client start-up." 157 ::= { radiusClient 1 } 159 radiusClientIdentifier OBJECT-TYPE 160 SYNTAX DisplayString 161 MAX-ACCESS read-only 162 STATUS current 163 DESCRIPTION 164 "The NAS-Identifier of the RADIUS client." 165 ::= { radiusClient 2 } 167 radiusServerTable OBJECT-TYPE 168 SYNTAX SEQUENCE OF RadiusServerEntry 169 MAX-ACCESS not-accessible 170 STATUS current 171 DESCRIPTION 172 "The (conceptual) table listing the RADIUS servers with 173 which the client shares a secret." 174 ::= { radiusClient 3 } 176 radiusServerEntry OBJECT-TYPE 177 SYNTAX RadiusServerEntry 178 MAX-ACCESS not-accessible 179 STATUS current 180 DESCRIPTION 181 "An entry (conceptual row) representing a RADIUS server 182 with which the client shares a secret." 183 INDEX { radiusServerIndex } 184 ::= { radiusServerTable 1 } 186 RadiusServerEntry ::= SEQUENCE { 187 radiusServerIndex Integer32, 188 radiusServerAddress IpAddress, 189 radiusClientRoundTripTime TimeTicks, 190 radiusClientAccessRequests Counter32, 191 radiusClientAccessRetransmissions Counter32, 192 radiusClientAccessAccepts Counter32, 193 radiusClientAccessRejects Counter32, 194 radiusClientAccessChallenges Counter32, 195 radiusClientMalformedAccessResponses Counter32, 196 radiusClientAuthenticationBadAuthenticators Counter32, 197 radiusClientAuthenticationPendingRequests Counter32, 198 radiusClientAuthenticationTimeouts Counter32, 199 radiusClientAccountingRequests Counter32, 200 radiusClientAccountingRetransmissions Counter32, 201 radiusClientAccountingResponses Counter32, 202 radiusClientMalformedAccountingResponses Counter32, 203 radiusClientAccountingBadAuthenticators Counter32, 204 radiusClientAccountingPendingRequests Counter32, 205 radiusClientAccountingTimeouts Counter32, 206 radiusClientUnknownType Counter32 208 } 210 radiusServerIndex OBJECT-TYPE 211 SYNTAX Integer32 212 MAX-ACCESS not-accessible 213 STATUS current 214 DESCRIPTION 215 "The RADIUS server with which the client interacts." 216 ::= { radiusServerEntry 1 } 218 radiusServerAddress OBJECT-TYPE 219 SYNTAX IpAddress 220 MAX-ACCESS read-only 221 STATUS current 222 DESCRIPTION 223 "The IP address of the RADIUS server 224 referred to in this table entry." 225 ::= { radiusServerEntry 2 } 227 radiusClientRoundTripTime OBJECT-TYPE 228 SYNTAX TimeTicks 229 MAX-ACCESS read-only 230 STATUS current 231 DESCRIPTION 232 "The total roundtrip time of the last packet sent 233 between the client and the RADIUS server referred 234 to in this table entry." 235 ::= { radiusServerEntry 3 } 237 radiusClientAccessRequests OBJECT-TYPE 238 SYNTAX Counter32 239 MAX-ACCESS read-only 240 STATUS current 241 DESCRIPTION 242 "The total number of RADIUS Access-Request packets sent 243 to this server since client start-up. This does not 244 include retransmissions." 245 ::= { radiusServerEntry 4 } 247 radiusClientAccessRetransmissions OBJECT-TYPE 248 SYNTAX Counter32 249 MAX-ACCESS read-only 250 STATUS current 251 DESCRIPTION 252 "The total number of RADIUS Access-Request packets 253 retransmitted to the same server since client start-up." 254 ::= { radiusServerEntry 5 } 256 radiusClientAccessAccepts OBJECT-TYPE 257 SYNTAX Counter32 258 MAX-ACCESS read-only 259 STATUS current 260 DESCRIPTION 261 "The total number of RADIUS Access-Accept packets 262 received from this server since client start-up." 263 ::= { radiusServerEntry 6 } 265 radiusClientAccessRejects OBJECT-TYPE 266 SYNTAX Counter32 267 MAX-ACCESS read-only 268 STATUS current 269 DESCRIPTION 270 "The total number of RADIUS Access-Reject packets 271 received from this server since client start-up." 272 ::= { radiusServerEntry 7 } 274 radiusClientAccessChallenges OBJECT-TYPE 275 SYNTAX Counter32 276 MAX-ACCESS read-only 277 STATUS current 278 DESCRIPTION 279 "The total number of RADIUS Access-Challenge packets 280 received from this server since client start-up." 281 ::= { radiusServerEntry 8 } 283 -- "Access-Response" includes an Access-Accept, Access-Challenge 284 -- or Access-Reject 286 radiusClientMalformedAccessResponses OBJECT-TYPE 287 SYNTAX Counter32 288 MAX-ACCESS read-only 289 STATUS current 290 DESCRIPTION 291 "The total number of malformed RADIUS Access-Response 292 packets received from this server since client 293 start-up. Bad authenticators are not included as 294 malformed access responses." 295 ::= { radiusServerEntry 9 } 297 radiusClientAuthenticationBadAuthenticators OBJECT-TYPE 298 SYNTAX Counter32 299 MAX-ACCESS read-only 300 STATUS current 301 DESCRIPTION 302 "The total number of RADIUS Access-Response packets 303 containing invalid authenticators received from this server 304 since client start-up." 305 ::= { radiusServerEntry 10 } 307 radiusClientAuthenticationPendingRequests OBJECT-TYPE 308 SYNTAX Counter32 309 MAX-ACCESS read-only 310 STATUS current 311 DESCRIPTION 312 "The total number of RADIUS Access-Request packets 313 destined for this server that have not yet timed out 314 or received a response. This variable is incremented 315 when an Access-Request is sent and decremented due to 316 a timeout or retransmission." 317 ::= { radiusServerEntry 11 } 319 radiusClientAuthenticationTimeouts OBJECT-TYPE 320 SYNTAX Counter32 321 MAX-ACCESS read-only 322 STATUS current 323 DESCRIPTION 324 "The total number of authentication timeouts to this server 325 since client startup. After a timeout the client may 326 retry to the same server, send to a different server, or 327 give up. A retry to the same server is counted as a 328 retransmit as well as a timeout. A send to a different 329 server is counted as a Request as well as a timeout." 330 ::= { radiusServerEntry 12 } 332 radiusClientAccountingRequests OBJECT-TYPE 333 SYNTAX Counter32 334 MAX-ACCESS read-only 335 STATUS current 336 DESCRIPTION 337 "The total number of RADIUS Accounting-Request packets 338 sent since client start-up. This does not include 339 retransmissions." 340 ::= { radiusServerEntry 13 } 342 radiusClientAccountingRetransmissions OBJECT-TYPE 343 SYNTAX Counter32 344 MAX-ACCESS read-only 345 STATUS current 346 DESCRIPTION 347 "The total number of RADIUS Accounting-Request packets 348 retransmitted to the same server since client start-up. 349 Retransmissions include retries where the 350 Identifier and Acct-Delay have been updated." 351 ::= { radiusServerEntry 14 } 353 radiusClientAccountingResponses OBJECT-TYPE 354 SYNTAX Counter32 355 MAX-ACCESS read-only 356 STATUS current 357 DESCRIPTION 358 "The total number of RADIUS Accounting-Response 359 packets received from this server since client start-up." 360 ::= { radiusServerEntry 15 } 362 radiusClientMalformedAccountingResponses OBJECT-TYPE 363 SYNTAX Counter32 364 MAX-ACCESS read-only 365 STATUS current 366 DESCRIPTION 367 "The total number of malformed RADIUS Accounting-Response 368 packets received from this server since client start-up. 369 Bad authenticators are not included as malformed access 370 responses." 371 ::= { radiusServerEntry 16 } 373 radiusClientAccountingBadAuthenticators OBJECT-TYPE 374 SYNTAX Counter32 375 MAX-ACCESS read-only 376 STATUS current 377 DESCRIPTION 378 "The total number of RADIUS Accounting-Response 379 packets which contained invalid authenticators 380 received from this server since client start-up." 381 ::= { radiusServerEntry 17 } 383 radiusClientAccountingPendingRequests OBJECT-TYPE 384 SYNTAX Counter32 385 MAX-ACCESS read-only 386 STATUS current 387 DESCRIPTION 388 "The total number of RADIUS Accounting-Request packets 389 sent to this server that have not yet timed out or 390 received a response. This variable is incremented when an 391 Accounting-Request is sent and decremented due to a timeout 392 or retransmission." 393 ::= { radiusServerEntry 18 } 395 radiusClientAccountingTimeouts OBJECT-TYPE 396 SYNTAX Counter32 397 MAX-ACCESS read-only 398 STATUS current 399 DESCRIPTION 400 "The total number of accounting timeouts to this server 401 since client startup. After a timeout the client may 402 retry to the same server, send to a different server, or 403 give up. A retry to the same server is counted as a 404 retransmit as well as a timeout. A send to a different 405 server is counted as an Accounting-Request as well as a timeout." 406 ::= { radiusServerEntry 19 } 408 radiusClientUnknownType OBJECT-TYPE 409 SYNTAX Counter32 410 MAX-ACCESS read-only 411 STATUS current 412 DESCRIPTION 413 "The total number of RADIUS packets of unknown type which 414 were received from this server since client start-up." 415 ::= { radiusServerEntry 20 } 417 -- conformance information 419 radiusClientMIBConformance 420 OBJECT IDENTIFIER ::= { radiusClientMIB 2 } 421 radiusClientMIBCompliances 422 OBJECT IDENTIFIER ::= { radiusClientMIBConformance 1 } 423 radiusClientMIBGroups 424 OBJECT IDENTIFIER ::= { radiusClientMIBConformance 2 } 426 -- compliance statements 428 radiusClientMIBCompliance MODULE-COMPLIANCE 429 STATUS current 430 DESCRIPTION 431 "The compliance statement for Clients implementing the 432 RADIUS Client MIB." 433 MODULE -- this module 434 MANDATORY-GROUPS { radiusClientMIBGroup } 436 ::= { radiusClientMIBCompliances 1 } 438 -- units of conformance 440 radiusClientMIBGroup OBJECT-GROUP 441 OBJECTS { radiusClientInvalidServerAddresses, 442 radiusServerAddress, 443 radiusClientRoundTripTime, 444 radiusClientAccessRequests, 445 radiusClientAccessRetransmissions, 446 radiusClientAccessAccepts, 447 radiusClientAccessRejects, 448 radiusClientAccessChallenges, 449 radiusClientMalformedAccessResponses, 450 radiusClientAuthenticationBadAuthenticators, 451 radiusClientAuthenticationPendingRequests, 452 radiusClientAuthenticationTimeouts, 453 radiusClientAccountingRequests, 454 radiusClientAccountingRetransmissions, 455 radiusClientAccountingResponses, 456 radiusClientMalformedAccountingResponses, 457 radiusClientAccountingBadAuthenticators, 458 radiusClientAccountingPendingRequests, 459 radiusClientAccountingTimeouts, 460 radiusClientUnknownType 461 } 462 STATUS current 463 DESCRIPTION 464 "The basic collection of objects providing management of 465 RADIUS Clients." 466 ::= { radiusClientMIBGroups 1 } 468 END 470 7. Security considerations 472 All MIB variables described in this document are read-only. 474 8. Acknowledgments 476 Thanks to Narendra Gidwani of Microsoft, Allan C. Rubens of MERIT, 477 Carl Rigney of Livingston and Peter Heitman of American Internet Cor- 478 poration for useful discussions of this problem space. 480 9. References 482 [1] C. Rigney, A. Rubens, W. Simpson, S. Willens. "Remote Authenti- 483 cation Dial In User Service (RADIUS)." RFC 2138, Livingston, Merit, 484 Daydreamer, April, 1997. 486 [2] C. Rigney. "RADIUS Accounting." RFC 2139, Livingston, April, 487 1997. 489 [3] C. Rigney, W. Willats. "RADIUS Extensions." draft-ietf-radius- 490 ext-00.txt, Livingston, January, 1997. 492 [4] "Information processing systems - Open Systems Interconnection - 493 Specification of Abstract Syntax Notation One (ASN.1)", International 494 Organization for Standardization, International Standard 8824, Decem- 495 ber 1987. 497 [5] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Introduc- 498 tion to Community-based SNMPv2", RFC 1901, SNMP Research, Inc., Cisco 499 Systems, Dover Beach Consulting, Inc., International Network Services, 500 January, 1996. 502 [6] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure 503 of Management Information for Version 2 of the Simple Network Manage- 504 ment Protocol (SNMPv2)", RFC 1902, SNMP Research, Inc., Cisco Systems, 505 Dover Beach Consulting, Inc., International Network Services, January, 506 1996. 508 [7] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Textual 509 Conventions for version 2 of the the Simple Network Management Proto- 510 col (SNMPv2)", RFC 1903, SNMP Research, Inc., Cisco Systems, Dover 511 Beach Consulting, Inc., International Network Services, January, 1996. 513 [8] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Confor- 514 mance Statements for version 2 of the the Simple Network Management 515 Protocol (SNMPv2)", RFC 1904, SNMP Research, Inc., Cisco Systems, 516 Dover Beach Consulting, Inc., International Network Services, January, 517 1996. 519 [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol 520 Operations for Version 2 of the Simple Network Management Protocol 521 (SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco Systems, Dover Beach 522 Consulting, Inc., International Network Services, January, 1996. 524 [10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport 525 Mappings for Version 2 of the Simple Network Management Protocol 526 (SNMPv2)", RFC 1906, SNMP Research, Inc., Cisco Systems, Dover Beach 527 Consulting, Inc., International Network Services, January, 1996. 529 [11] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Manage- 530 ment Information Base for Version 2 of the Simple Network Management 531 Protocol (SNMPv2)", RFC 1907, SNMP Research, Inc., Cisco Systems, 532 Dover Beach Consulting, Inc., International Network Services, January, 533 1996. 535 [12] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Coexis- 536 tence between Version 1 and Version 2 of the Internet-standard Network 537 Management Framework", RFC 1908, SNMP Research, Inc., Cisco Systems, 538 Dover Beach Consulting, Inc., International Network Services, January, 539 1996. 541 [13] McCloghrie, K., "An Administrative Infrastructure for SNMPv2", 542 RFC 1909, Cisco Systems, February, 1996. 544 10. Authors' Addresses 546 Bernard Aboba 547 Microsoft Corporation 548 One Microsoft Way 549 Redmond, WA 98052 551 Phone: 425-936-6605 552 EMail: bernarda@microsoft.com 554 Glen Zorn 555 Microsoft Corporation 556 One Microsoft Way 557 Redmond, WA 98052 559 Phone: 425-703-1559 560 EMail: glennz@microsoft.com