idnits 2.17.1 draft-ietf-radius-auth-servmib-00.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-24) 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 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 10 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 119 instances of too long lines in the document, the longest one being 8 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 13 has weird spacing: '...), its areas...' == Line 14 has weird spacing: '... its worki...' == Line 18 has weird spacing: '... and may ...' == Line 19 has weird spacing: '...afts as refer...' == Line 22 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 (9 August 1997) is 9755 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 442, but no explicit reference was found in the text == Unused Reference: '3' is defined on line 445, but no explicit reference was found in the text == Unused Reference: '4' is defined on line 448, but no explicit reference was found in the text == Unused Reference: '5' is defined on line 453, but no explicit reference was found in the text == Unused Reference: '6' is defined on line 458, but no explicit reference was found in the text == Unused Reference: '7' is defined on line 464, but no explicit reference was found in the text == Unused Reference: '8' is defined on line 469, but no explicit reference was found in the text == Unused Reference: '9' is defined on line 475, but no explicit reference was found in the text == Unused Reference: '10' is defined on line 480, but no explicit reference was found in the text == Unused Reference: '11' is defined on line 485, but no explicit reference was found in the text == Unused Reference: '12' is defined on line 490, but no explicit reference was found in the text == Unused Reference: '13' is defined on line 496, 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. -------------------------------------------------------------------------------- 2 RADIUS Working Group Glen Zorn 3 INTERNET-DRAFT Microsoft 4 Category: Standards Track Bernard Aboba 5 Microsoft 6 9 August 1997 8 RADIUS Authentication Server MIB 10 1. Status of this Memo 12 This document is an Internet-Draft. Internet-Drafts are working docu- 13 ments of the Internet Engineering Task Force (IETF), its areas, and 14 its working groups. Note that other groups may also distribute work- 15 ing documents as Internet-Drafts. 17 Internet-Drafts are draft documents valid for a maximum of six months 18 and may be updated, replaced, or obsoleted by other documents at any 19 time. It is inappropriate to use Internet-Drafts as reference mate- 20 rial or to cite them other than as ``work in progress.'' 22 To learn the current status of any Internet-Draft, please check the 23 ``1id-abstracts.txt'' listing contained in the Internet-Drafts Shadow 24 Directories on ds.internic.net (US East Coast), nic.nordu.net 25 (Europe), ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific Rim). 27 The distribution of this memo is unlimited. It is filed as , and expires February 1, 1998. 29 Please send comments to the authors. 31 2. Abstract 33 This memo defines a set of extensions which instrument RADIUS authen- 34 tication server functions. These extensions represent a portion of the 35 Management Information Base (MIB) for use with network management pro- 36 tocols in the Internet community. Using these extensions IP-based 37 management stations can manage RADIUS authentication servers. 39 3. Introduction 41 This memo defines a portion of the Management Information Base (MIB) 42 for use with network management protocols in the Internet community. 43 In particular, it describes managed objects used for managing RADIUS 44 authentication servers. 46 RADIUS authentication servers are today widely deployed by dialup 47 Internet Service Providers, in order to provide authentication ser- 48 vices. As a result, the effective management of RADIUS authentication 49 servers is of considerable importance. 51 4. The SNMPv2 Network Management Framework 53 The SNMPv2 Network Management Framework consists of four major compo- 54 nents. They are: 56 o RFC 1902 which defines the SMI, the mechanisms used for 57 describing and naming objects for the purpose of management. 59 o RFC 1905 which defines the protocol used for network access to 60 managed objects. 62 o RFC 1907 defines the core set of managed objects for the 63 Internet suite of protocols. 65 o RFC 1909 which defines the administrative aspects of the 66 framework. 68 The Framework permits new objects to be defined for the purpose of 69 experimentation and evaluation. 71 4.1. Object Definitions 73 Managed objects are accessed via a virtual information store, termed 74 the Management Information Base or MIB. Objects in the MIB are defined 75 using the subset of Abstract Syntax Notation One (ASN.1) defined in 76 the SMI. In particular, each object object type is named by an OBJECT 77 IDENTIFIER, an administratively assigned name. The object type 78 together with an object instance serves to uniquely identify a spe- 79 cific instantiation of the object. For human convenience, we often use 80 a textual string, termed the descriptor, to refer to the object type. 82 5. Overview 84 The RADIUS authentication protocol, described in [1], distinguishes 85 between the client function and the server function. In RADIUS authen- 86 tication, clients send Access-Requests, and servers reply with Access- 87 Accepts, Access-Rejects, and Access-Challenges. Typically NAS devices 88 implement the client function, and thus would be expected to implement 89 the RADIUS authentication client MIB, while RADIUS authentication 90 servers implement the server function, and thus would be expected to 91 implement the RADIUS authentication server MIB. 93 However, it is possible for a RADIUS authentication entity to perform 94 both client and server functions. For example, a RADIUS proxy may act 95 as a server to one or more RADIUS authentication clients, while simul- 96 taneously acting as an authentication client to one or more authenti- 97 cation servers. In such situations, it is expected that RADIUS enti- 98 ties combining client and server functionality will support both the 99 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 Authentication Client Table contains one row for each 106 RADIUS authentication client that the server shares a secret with. 108 Each entry in the RADIUS Authentication Client Table includes twelve 109 entries presenting a view of the activity of the RADIUS authentication 110 server. 112 6. Definitions 114 RADIUS-AUTH-SERVER-MIB DEFINITIONS ::= BEGIN 116 IMPORTS 117 MODULE-IDENTITY, OBJECT-TYPE, 118 OBJECT-IDENTITY, experimental, 119 Counter32, Gauge32, Integer32, 120 IpAddress, TimeTicks FROM SNMPv2-SMI 121 TEXTUAL-CONVENTION, RowStatus, 122 TruthValue, DisplayString FROM SNMPv2-TC 123 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF; 125 radius OBJECT-IDENTITY 126 STATUS current 127 DESCRIPTION 128 "The OID assigned to RADIUS MIB work by the IANA." 129 ::= { experimental 79 } 131 radiusAuthentication OBJECT-IDENTIFIER ::= {radius 1} 133 radiusAuthServMIB MODULE-IDENTITY 134 LAST-UPDATED "9708211659Z" 135 ORGANIZATION "IETF RADIUS Working Group." 136 CONTACT-INFO 137 " Glen Zorn 138 Microsoft 139 One Microsoft Way 140 Redmond, WA 98052 141 US 143 Phone: +1 425 703 1559 144 EMail: glennz@microsoft.com" 145 DESCRIPTION 146 "The MIB module for entities implementing the server 147 side of the Remote Access Dialin User Service (RADIUS) 148 authentication protocol." 149 ::= { radiusAuthentication 1 } 151 radiusAuthServMIBObjects OBJECT IDENTIFIER ::= { radiusAuthServMIB 1 } 152 radiusAuthServ OBJECT IDENTIFIER ::= { radiusAuthServMIBObjects 1 } 154 -- Textual conventions 156 RadiusTime ::= TEXTUAL-CONVENTION 157 DISPLAY-HINT "4d" 158 STATUS current 159 DESCRIPTION 160 "RadiusTime values are 32-bit unsigned integers which 161 measure time in seconds." 162 SYNTAX Gauge32 164 radiusAuthServIdent OBJECT-TYPE 165 SYNTAX DisplayString 166 MAX-ACCESS read-only 167 STATUS current 168 DESCRIPTION 169 "The implementation identification string for the 170 RADIUS authentication server software in use on the 171 system, for example; `FNS-2.1'" 172 ::= {radiusAuthServ 1} 174 radiusAuthServUpTime OBJECT-TYPE 175 SYNTAX RadiusTime 176 MAX-ACCESS read-only 177 STATUS current 178 DESCRIPTION 179 "If the server has a persistent state (e.g., a process), 180 this value will be the time elapsed since it started. 181 For software without persistent state, this value will 182 be zero." 183 ::= {radiusAuthServ 2} 185 radiusAuthServResetTime OBJECT-TYPE 186 SYNTAX RadiusTime 187 MAX-ACCESS read-only 188 STATUS current 189 DESCRIPTION 190 "If the server has a persistent state (e.g., a process) 191 and supports a `reset' operation (e.g., can be told to 192 re-read configuration files), this value will be the 193 time elapsed since the last time the name server was 194 `reset.' For software that does not have persistence or 195 does not support a `reset' operation, this value will be 196 zero." 197 ::= {radiusAuthServ 3} 199 radiusAuthServConfigReset OBJECT-TYPE 200 SYNTAX INTEGER { other(1), 201 reset(2), 202 initializing(3), 203 running(4)} 204 MAX-ACCESS read-write 205 STATUS current 206 DESCRIPTION 207 "Status/action object to reinitialize any persistent 208 server state. When set to reset(2), any persistent 209 server state (such as a process) is reinitialized as if 210 the server had just been started. This value will 211 never be returned by a read operation. When read, one of 212 the following values will be returned: 213 other(1) - server in some unknown state; 214 initializing(3) - server (re)initializing; 215 running(4) - server currently running." 216 ::= {radiusAuthServ 4} 218 radiusAuthServInvalidClientAddresses 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 from unknown addresses since server start-up." 225 ::= {radiusAuthServ 5} 227 radiusAuthClientTable OBJECT-TYPE 228 SYNTAX SEQUENCE OF RadiusAuthClientEntry 229 MAX-ACCESS not-accessible 230 STATUS current 231 DESCRIPTION 232 "The (conceptual) table listing the RADIUS authentication 233 clients with which the server shares a secret." 234 ::= { radiusAuthServ 6 } 236 radiusAuthClientEntry OBJECT-TYPE 237 SYNTAX RadiusAuthClientEntry 238 MAX-ACCESS not-accessible 239 STATUS current 240 DESCRIPTION 241 "An entry (conceptual row) representing a RADIUS 242 authentication client with which the server shares a secret." 243 INDEX { radiusAuthClientIndex } 244 ::= { radiusAuthClientTable 1 } 246 RadiusAuthClientEntry ::= SEQUENCE { 247 radiusAuthClientIndex Integer32, 248 radiusAuthClientAddress IpAddress, 249 radiusAuthClientID DisplayString, 250 radiusAuthServAccessRequests Counter32, 251 radiusAuthServDupAccessRequests Counter32, 252 radiusAuthServAccessAccepts Counter32, 253 radiusAuthServAccessRejects Counter32, 254 radiusAuthServAccessChallenges Counter32, 255 radiusAuthServMalformedAccessRequests Counter32, 256 radiusAuthServAuthenticationBadAuthenticators Counter32, 257 radiusAuthServPacketsDropped Counter32, 258 radiusAuthServUnknownType Counter32 259 } 260 radiusAuthClientIndex OBJECT-TYPE 261 SYNTAX Integer32 262 MAX-ACCESS not-accessible 263 STATUS current 264 DESCRIPTION 265 "The RADIUS authentication client referred to in this 266 table entry." 267 ::= { radiusAuthClientEntry 1 } 269 radiusAuthClientAddress OBJECT-TYPE 270 SYNTAX IpAddress 271 MAX-ACCESS read-only 272 STATUS current 273 DESCRIPTION 274 "The NAS-IP-Address of the RADIUS authentication client 275 referred to in this table entry." 276 ::= { radiusAuthClientEntry 2 } 278 radiusAuthClientID OBJECT-TYPE 279 SYNTAX DisplayString 280 MAX-ACCESS read-only 281 STATUS current 282 DESCRIPTION 283 "The NAS-Identifier of the RADIUS authentication client 284 referred to in this table entry." 285 ::= { radiusAuthClientEntry 3 } 287 -- Server Counters 289 radiusAuthServAccessRequests OBJECT-TYPE 290 SYNTAX Counter32 291 MAX-ACCESS read-only 292 STATUS current 293 DESCRIPTION 294 "The total number of RADIUS Access-Request packets 295 received from this client since server start-up." 296 ::= { radiusAuthClientEntry 4 } 298 radiusAuthServDupAccessRequests OBJECT-TYPE 299 SYNTAX Counter32 300 MAX-ACCESS read-only 301 STATUS current 302 DESCRIPTION 303 "The total number of duplicate RADIUS Access-Request 304 packets received from this client since server start-up." 305 ::= { radiusAuthClientEntry 5 } 307 radiusAuthServAccessAccepts OBJECT-TYPE 308 SYNTAX Counter32 309 MAX-ACCESS read-only 310 STATUS current 311 DESCRIPTION 312 "The total number of RADIUS Access-Accept packets 313 sent to this client since server start-up." 315 ::= { radiusAuthClientEntry 6 } 317 radiusAuthServAccessRejects OBJECT-TYPE 318 SYNTAX Counter32 319 MAX-ACCESS read-only 320 STATUS current 321 DESCRIPTION 322 "The total number of RADIUS Access-Reject packets 323 sent to this client since server start-up." 324 ::= { radiusAuthClientEntry 7 } 326 radiusAuthServAccessChallenges OBJECT-TYPE 327 SYNTAX Counter32 328 MAX-ACCESS read-only 329 STATUS current 330 DESCRIPTION 331 "The total number of RADIUS Access-Challenge packets 332 sent to this client since server start-up." 333 ::= { radiusAuthClientEntry 8 } 335 radiusAuthServMalformedAccessRequests OBJECT-TYPE 336 SYNTAX Counter32 337 MAX-ACCESS read-only 338 STATUS current 339 DESCRIPTION 340 "The total number of malformed RADIUS Access-Request 341 packets received from this client since server start-up. 342 Bad authenticators are not included as 343 malformed Access-Requests." 344 ::= { radiusAuthClientEntry 9 } 346 radiusAuthServAuthenticationBadAuthenticators OBJECT-TYPE 347 SYNTAX Counter32 348 MAX-ACCESS read-only 349 STATUS current 350 DESCRIPTION 351 "The total number of RADIUS Authentication-Request packets 352 which contained invalid Signature attributes received 353 from this client since server start-up." 354 ::= { radiusAuthClientEntry 10 } 356 radiusAuthServPacketsDropped OBJECT-TYPE 357 SYNTAX Counter32 358 MAX-ACCESS read-only 359 STATUS current 360 DESCRIPTION 361 "The total number of packets dropped from this client, 362 with no reply sent." 363 ::= { radiusAuthClientEntry 11 } 365 radiusAuthServUnknownType OBJECT-TYPE 366 SYNTAX Counter32 367 MAX-ACCESS read-only 368 STATUS current 369 DESCRIPTION 370 "The total number of RADIUS packets of unknown type which 371 were received from this client since authentication server 372 start-up." 373 ::= { radiusAuthClientEntry 12 } 375 -- conformance information 377 radiusAuthServMIBConformance 378 OBJECT IDENTIFIER ::= { radiusAuthServMIB 2 } 379 radiusAuthServMIBCompliances 380 OBJECT IDENTIFIER ::= { radiusAuthServMIBConformance 1 } 381 radiusAuthServMIBGroups 382 OBJECT IDENTIFIER ::= { radiusAuthServMIBConformance 2 } 384 -- compliance statements 386 radiusAuthServMIBCompliance MODULE-COMPLIANCE 387 STATUS current 388 DESCRIPTION 389 "The compliance statement for authentication servers 390 implementing the RADIUS Authentication Server MIB." 391 MODULE -- this module 392 MANDATORY-GROUPS { radiusAuthServMIBGroup } 394 ::= { radiusAuthServMIBCompliances 1 } 396 -- units of conformance 398 radiusAuthServMIBGroup OBJECT-GROUP 399 OBJECTS {radiusAuthServIdent, 400 radiusAuthServUpTime, 401 radiusAuthServResetTime, 402 radiusAuthServConfigReset, 403 radiusAuthServInvalidClientAddresses, 404 radiusAuthClientAddress, 405 radiusAuthClientID, 406 radiusAuthServAccessRequests, 407 radiusAuthServDupAccessRequests, 408 radiusAuthServAccessAccepts, 409 radiusAuthServAccessRejects, 410 radiusAuthServAccessChallenges, 411 radiusAuthServMalformedAccessRequests, 412 radiusAuthServAuthenticationBadAuthenticators, 413 radiusAuthServPacketsDropped, 414 radiusAuthServUnknownType 415 } 416 STATUS current 417 DESCRIPTION 418 "The collection of objects providing management of 419 a RADIUS Authentication Server." 421 ::= { radiusAuthServMIBGroups 1 } 423 END 425 7. Security considerations 427 All MIB variables described in this document are read-only, with the 428 exception of radiusAuthServConfigReset. 430 8. Acknowledgments 432 Thanks to Narendra Gidwani of Microsoft, Allan C. Rubens of MERIT, 433 Carl Rigney of Livingston, and Peter Heitman of American Internet Cor- 434 poration for useful discussions of this problem space. 436 9. References 438 [1] C. Rigney, A. Rubens, W. Simpson, S. Willens. "Remote Authenti- 439 cation Dial In User Service (RADIUS)." RFC 2138, Livingston, Merit, 440 Daydreamer, April, 1997. 442 [2] C. Rigney. "RADIUS Authentication." RFC 2139, Livingston, April, 443 1997. 445 [3] C. Rigney, W. Willats. "RADIUS Extensions." draft-ietf-radius- 446 ext-00.txt, Livingston, January, 1997. 448 [4] "Information processing systems - Open Systems Interconnection - 449 Specification of Abstract Syntax Notation One (ASN.1)", International 450 Organization for Standardization, International Standard 8824, Decem- 451 ber 1987. 453 [5] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Introduc- 454 tion to Community-based SNMPv2", RFC 1901, SNMP Research, Inc., Cisco 455 Systems, Dover Beach Consulting, Inc., International Network Services, 456 January, 1996. 458 [6] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure 459 of Management Information for Version 2 of the Simple Network Manage- 460 ment Protocol (SNMPv2)", RFC 1902, SNMP Research, Inc., Cisco Systems, 461 Dover Beach Consulting, Inc., International Network Services, January, 462 1996. 464 [7] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Textual 465 Conventions for version 2 of the the Simple Network Management Proto- 466 col (SNMPv2)", RFC 1903, SNMP Research, Inc., Cisco Systems, Dover 467 Beach Consulting, Inc., International Network Services, January, 1996. 469 [8] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Confor- 470 mance Statements for version 2 of the the Simple Network Management 471 Protocol (SNMPv2)", RFC 1904, SNMP Research, Inc., Cisco Systems, 472 Dover Beach Consulting, Inc., International Network Services, January, 473 1996. 475 [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol 476 Operations for Version 2 of the Simple Network Management Protocol 477 (SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco Systems, Dover Beach 478 Consulting, Inc., International Network Services, January, 1996. 480 [10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport 481 Mappings for Version 2 of the Simple Network Management Protocol 482 (SNMPv2)", RFC 1906, SNMP Research, Inc., Cisco Systems, Dover Beach 483 Consulting, Inc., International Network Services, January, 1996. 485 [11] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Manage- 486 ment Information Base for Version 2 of the Simple Network Management 487 Protocol (SNMPv2)", RFC 1907, SNMP Research, nc., Cisco Systems, Dover 488 Beach Consulting, Inc., International Network Services, January, 1996. 490 [12] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Coexis- 491 tence between Version 1 and Version 2 of the Internet-standard Network 492 Management Framework", RFC 1908, SNMP Research, Inc., Cisco Systems, 493 Dover Beach Consulting, Inc., International Network Services, January, 494 1996. 496 [13] McCloghrie, K., "An Administrative Infrastructure for SNMPv2", 497 RFC 1909, Cisco Systems, February, 1996. 499 10. Authors' Addresses 501 Glen Zorn 502 Microsoft Corporation 503 One Microsoft Way 504 Redmond, WA 98052 506 Phone: 425-703-1559 507 EMail: glennz@microsoft.com 509 Bernard Aboba 510 Microsoft Corporation 511 One Microsoft Way 512 Redmond, WA 98052 514 Phone: 425-936-6605 515 EMail: bernarda@microsoft.com