idnits 2.17.1 draft-ietf-radius-clientmib-02.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-16) 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 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 92 instances of too long lines in the document, the longest one being 15 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...' == (26 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: '1' is defined on line 431, but no explicit reference was found in the text == Unused Reference: '2' is defined on line 435, but no explicit reference was found in the text == Unused Reference: '3' is defined on line 438, but no explicit reference was found in the text == Unused Reference: '4' is defined on line 441, but no explicit reference was found in the text == Unused Reference: '5' is defined on line 446, but no explicit reference was found in the text == Unused Reference: '6' is defined on line 451, but no explicit reference was found in the text == Unused Reference: '7' is defined on line 457, but no explicit reference was found in the text == Unused Reference: '8' is defined on line 462, but no explicit reference was found in the text == Unused Reference: '9' is defined on line 468, but no explicit reference was found in the text == Unused Reference: '10' is defined on line 473, but no explicit reference was found in the text == Unused Reference: '11' is defined on line 478, but no explicit reference was found in the text == Unused Reference: '12' is defined on line 484, but no explicit reference was found in the text == Unused Reference: '13' is defined on line 490, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2058 (ref. '1') (Obsoleted by RFC 2138) ** Obsolete normative reference: RFC 2059 (ref. '2') (Obsoleted by RFC 2139) == 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 (~~), 23 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 RADIUS Working Group Bernard Aboba 3 INTERNET-DRAFT Microsoft 4 Glen Zorn 5 3 April 1997 Microsoft 7 RADIUS Client 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 October 1, 1997. Please 28 send comments to the authors. 30 2. Abstract 32 This memo defines a set of extensions which instrument RADIUS client 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 clients. 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 clients. 45 Today a wide range of network devices, including routers and NASes, 46 act as RADIUS clients in order to provide authentication, authoriza- 47 tion, and accounting services. As a result, the effective management 48 of RADIUS clients 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 74 defined using the subset of Abstract Syntax Notation One (ASN.1) 75 defined in the SMI. In particular, each object object type is named by 76 an OBJECT IDENTIFIER, an administratively assigned name. The object 77 type together with an object instance serves to uniquely identify a 78 specific instantiation of the object. For human convenience, we often 79 use a textual string, termed the descriptor, to refer to the object 80 type. 82 5. Overview 84 This MIB module contains two scalars as well as a single table: 86 (1) the RADIUS Server Table contains one row for each 87 RADIUS server that the client shares a secret with. 89 Each entry in the RADIUS Server Table includes twenty entries present- 90 ing a view of the activity of the RADIUS client. 92 6. Definitions 94 RADIUS-CLIENT-MIB DEFINITIONS ::= BEGIN 96 IMPORTS 97 MODULE-IDENTITY, OBJECT-TYPE, 98 OBJECT-IDENTITY, experimental, 99 Counter32, Gauge32, Integer32, 100 IpAddress, TimeTicks FROM SNMPv2-SMI 101 RowStatus, TruthValue, 102 DisplayString FROM SNMPv2-TC 103 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF; 105 radius OBJECT-IDENTITY 106 STATUS current 107 DESCRIPTION 108 "The OID assigned to RADIUS MIB work by the IANA." 109 ::= { not-assigned-yet } 111 radiusClientMIB MODULE-IDENTITY 112 LAST-UPDATED "9704021659Z" 113 ORGANIZATION "IETF RADIUS Working Group." 114 CONTACT-INFO 115 " Bernard Aboba 116 Microsoft 117 One Microsoft Way 118 Redmond, WA 98052 119 US 121 Phone: +1 206 936 6605 122 EMail: bernarda@microsoft.com" 123 DESCRIPTION 124 "The MIB module for RADIUS Client Management." 125 ::= { radius 2 } 127 radiusClientMIBObjects OBJECT IDENTIFIER ::= { radiusClientMIB 1 } 129 radiusClient OBJECT IDENTIFIER ::= { radiusClientMIBObjects 1 } 131 radiusClientInvalidServerAddresses OBJECT-TYPE 132 SYNTAX Counter32 133 MAX-ACCESS read-only 134 STATUS current 135 DESCRIPTION 136 "The total number of RADIUS Access-Response messages received 137 from unknown addresses since client start-up" 138 ::= { radiusClient 1 } 140 radiusClientIdentifier OBJECT-TYPE 141 SYNTAX DisplayString 142 MAX-ACCESS read-only 143 STATUS current 144 DESCRIPTION 145 "The NAS-Identifier of the RADIUS client." 146 ::= { radiusClient 2 } 148 radiusServerTable OBJECT-TYPE 149 SYNTAX SEQUENCE OF RadiusServerEntry 150 MAX-ACCESS not-accessible 151 STATUS current 152 DESCRIPTION 153 "The (conceptual) table listing the RADIUS servers with 154 which the client shares a secret." 155 ::= { radiusClient 3 } 157 radiusServerEntry OBJECT-TYPE 158 SYNTAX RadiusServerEntry 159 MAX-ACCESS not-accessible 160 STATUS current 161 DESCRIPTION 162 "An entry (conceptual row) representing a RADIUS server 163 with which the client shares a secret." 164 INDEX { radiusServerIndex } 165 ::= { radiusServerTable 1 } 167 RadiusServerEntry ::= SEQUENCE { 168 radiusServerIndex Integer32, 169 radiusServerAddress IpAddress, 170 radiusClientRoundTripTime TimeTicks, 171 radiusClientAccessRequests Counter32, 172 radiusClientAccessRetransmissions Counter32, 173 radiusClientAccessAccepts Counter32, 174 radiusClientAccessRejects Counter32, 175 radiusClientAccessChallenges Counter32, 176 radiusClientMalformedAccessResponses Counter32, 177 radiusClientAuthenticationBadAuthenticators Counter32, 178 radiusClientAuthenticationPendingRequests Counter32, 179 radiusClientAuthenticationTimeouts Counter32, 180 radiusClientAccountingRequests Counter32, 181 radiusClientAccountingRetransmissions Counter32, 182 radiusClientAccountingResponses Counter32, 183 radiusClientMalformedAccountingResponses Counter32, 184 radiusClientAccountingBadAuthenticators Counter32, 185 radiusClientAccountingPendingRequests Counter32, 186 radiusClientAccountingTimeouts Counter32, 187 radiusClientUnknownType Counter32 188 } 190 radiusServerIndex OBJECT-TYPE 191 SYNTAX Integer32 192 MAX-ACCESS not-accessible 193 STATUS current 194 DESCRIPTION 195 "The RADIUS server with which the client interacts" 196 ::= { radiusServerEntry 1 } 198 radiusServerAddress OBJECT-TYPE 199 SYNTAX IpAddress 200 MAX-ACCESS read-only 201 STATUS current 202 DESCRIPTION 203 "The IP address of the RADIUS server 204 referred to in this table entry" 205 ::= { radiusServerEntry 2 } 207 radiusClientRoundTripTime OBJECT-TYPE 208 SYNTAX TimeTicks 209 MAX-ACCESS read-only 210 STATUS current 211 DESCRIPTION 212 "The total roundtrip time of the last packet sent 213 between the client and the RADIUS server referred 214 to in this table entry" 215 ::= { radiusServerEntry 3 } 217 radiusClientAccessRequests OBJECT-TYPE 218 SYNTAX Counter32 219 MAX-ACCESS read-only 220 STATUS current 221 DESCRIPTION 222 "The total number of RADIUS Access-Request messages sent 223 since client start-up" 224 ::= { radiusServerEntry 4 } 226 radiusClientAccessRetransmissions OBJECT-TYPE 227 SYNTAX Counter32 228 MAX-ACCESS read-only 229 STATUS current 230 DESCRIPTION 231 "The total number of RADIUS Access-Request messages retransmitted 232 since client start-up" 233 ::= { radiusServerEntry 5 } 235 radiusClientAccessAccepts OBJECT-TYPE 236 SYNTAX Counter32 237 MAX-ACCESS read-only 238 STATUS current 239 DESCRIPTION 240 "The total number of RADIUS Access-Accept messages received 241 since client start-up" 242 ::= { radiusServerEntry 6 } 244 radiusClientAccessRejects OBJECT-TYPE 245 SYNTAX Counter32 246 MAX-ACCESS read-only 247 STATUS current 248 DESCRIPTION 249 "The total number of RADIUS Access-Reject messages received since client start-up" 250 ::= { radiusServerEntry 7 } 252 radiusClientAccessChallenges OBJECT-TYPE 253 SYNTAX Counter32 254 MAX-ACCESS read-only 255 STATUS current 256 DESCRIPTION 257 "The total number of RADIUS Access-Challenge messages received 258 since client start-up" 259 ::= { radiusServerEntry 8 } 261 -- "Access-Response" includes an Access-Accept, Access-Challenge or Access-Reject 262 radiusClientMalformedAccessResponses OBJECT-TYPE 263 SYNTAX Counter32 264 MAX-ACCESS read-only 265 STATUS current 266 DESCRIPTION 267 "The total number of malformed RADIUS Access-Response messages received 268 since client start-up" 269 ::= { radiusServerEntry 9 } 271 radiusClientAuthenticationBadAuthenticators OBJECT-TYPE 272 SYNTAX Counter32 273 MAX-ACCESS read-only 274 STATUS current 275 DESCRIPTION 276 "The total number of RADIUS Access-Response messages containing invalid 277 authenticators received since client start-up" 278 ::= { radiusServerEntry 10 } 280 radiusClientAuthenticationPendingRequests OBJECT-TYPE 281 SYNTAX Counter32 282 MAX-ACCESS read-only 283 STATUS current 284 DESCRIPTION 285 "The total number of RADIUS Access-Request messages that have not yet 286 timed out or received a response" 287 ::= { radiusServerEntry 11 } 289 radiusClientAuthenticationTimeouts OBJECT-TYPE 290 SYNTAX Counter32 291 MAX-ACCESS read-only 292 STATUS current 293 DESCRIPTION 294 "The total number of authentication timeouts since client startup" 295 ::= { radiusServerEntry 12 } 297 radiusClientAccountingRequests OBJECT-TYPE 298 SYNTAX Counter32 299 MAX-ACCESS read-only 300 STATUS current 301 DESCRIPTION 302 "The total number of RADIUS Accounting-Request messages sent 303 since client start-up" 304 ::= { radiusServerEntry 13 } 306 radiusClientAccountingRetransmissions OBJECT-TYPE 307 SYNTAX Counter32 308 MAX-ACCESS read-only 309 STATUS current 310 DESCRIPTION 311 "The total number of RADIUS Accounting-Request messages retransmitted 312 since client start-up" 313 ::= { radiusServerEntry 14 } 315 radiusClientAccountingResponses OBJECT-TYPE 316 SYNTAX Counter32 317 MAX-ACCESS read-only 318 STATUS current 319 DESCRIPTION 320 "The total number of RADIUS Accounting-Response messages received 321 since client start-up" 322 ::= { radiusServerEntry 15 } 324 radiusClientMalformedAccountingResponses OBJECT-TYPE 325 SYNTAX Counter32 326 MAX-ACCESS read-only 327 STATUS current 328 DESCRIPTION 329 "The total number of malformed RADIUS Accounting-Response messages received 330 since client start-up" 331 ::= { radiusServerEntry 16 } 333 radiusClientAccountingBadAuthenticators OBJECT-TYPE 334 SYNTAX Counter32 335 MAX-ACCESS read-only 336 STATUS current 337 DESCRIPTION 338 "The total number of RADIUS Accounting-Response messages which 339 contained invalid authenticators received since client start-up" 340 ::= { radiusServerEntry 17 } 342 radiusClientAccountingPendingRequests OBJECT-TYPE 343 SYNTAX Counter32 344 MAX-ACCESS read-only 345 STATUS current 346 DESCRIPTION 347 "The total number of RADIUS Accounting-Request messages that have not yet 348 timed out or received a response" 349 ::= { radiusServerEntry 18 } 351 radiusClientAccountingTimeouts OBJECT-TYPE 352 SYNTAX Counter32 353 MAX-ACCESS read-only 354 STATUS current 355 DESCRIPTION 356 "The total number of accounting timeouts since client startup" 357 ::= { radiusServerEntry 19 } 359 radiusClientUnknownType OBJECT-TYPE 360 SYNTAX Counter32 361 MAX-ACCESS read-only 362 STATUS current 363 DESCRIPTION 364 "The total number of RADIUS messages of unknown type which 365 were received since client start-up" 366 ::= { radiusServerEntry 20 } 368 -- conformance information 369 radiusClientMIBConformance 370 OBJECT IDENTIFIER ::= { radiusClientMIB 2 } 371 radiusClientMIBCompliances 372 OBJECT IDENTIFIER ::= { radiusClientMIBConformance 1 } 373 radiusClientMIBGroups OBJECT IDENTIFIER ::= { radiusClientMIBConformance 2 } 375 -- compliance statements 377 radiusClientMIBCompliance MODULE-COMPLIANCE 378 STATUS current 379 DESCRIPTION 380 "The compliance statement for Clients implementing the RADIUS Client 381 MIB." 382 MODULE -- this module 383 MANDATORY-GROUPS { radiusClientMIBGroup } 385 ::= { radiusClientMIBCompliances 1 } 387 -- units of conformance 389 radiusClientMIBGroup OBJECT-GROUP 390 OBJECTS { radiusClientInvalidServerAddresses, 391 radiusServerAddress, 392 radiusClientRoundTripTime, 393 radiusClientAccessRequests, 394 radiusClientAccessRetransmissions, 395 radiusClientAccessAccepts, 396 radiusClientAccessRejects, 397 radiusClientAccessChallenges, 398 radiusClientMalformedAccessResponses, 399 radiusClientAuthenticationBadAuthenticators, 400 radiusClientAuthenticationPendingRequests, 401 radiusClientAuthenticationTimeouts, 402 radiusClientRoundTripTime, 403 radiusClientAccountingRequests, 404 radiusClientAccountingRetransmissions, 405 radiusClientAccountingResponses, 406 radiusClientMalformedAccountingResponses, 407 radiusClientAccountingBadAuthenticators, 408 radiusClientAccountingPendingRequests, 409 radiusClientAccountingTimeouts, 410 radiusClientUnknownType 411 } 412 STATUS current 413 DESCRIPTION 414 "The basic collection of objects providing management of 415 RADIUS Clients." 416 ::= { radiusClientMIBGroups 1 } 418 END 419 7. Security considerations 421 All MIB variables described in this document are read-only. 423 8. Acknowledgments 425 Thanks to Narendra Gidwani of Microsoft, Allan C. Rubens of MERIT, 426 Carl Rigney of Livingston and Peter Heitman of American Internet Cor- 427 poration for useful discussions of this problem space. 429 9. References 431 [1] C. Rigney, A. Rubens, W. Simpson, S. Willens. "Remote Authenti- 432 cation Dial In User Service (RADIUS)." RFC 2058, Livingston, Merit, 433 Daydreamer, January, 1997. 435 [2] C. Rigney. "RADIUS Accounting." RFC 2059, Livingston, January, 436 1997. 438 [3] C. Rigney, W. Willats. "RADIUS Extensions." draft-ietf-radius- 439 ext-00.txt, Livingston, January, 1997. 441 [4] "Information processing systems - Open Systems Interconnection - 442 Specification of Abstract Syntax Notation One (ASN.1)", International 443 Organization for Standardization, International Standard 8824, Decem- 444 ber 1987. 446 [5] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Introduc- 447 tion to Community-based SNMPv2", RFC 1901, SNMP Research, Inc., Cisco 448 Systems, Dover Beach Consulting, Inc., International Network Services, 449 January, 1996. 451 [6] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure 452 of Management Information for Version 2 of the Simple Network Manage- 453 ment Protocol (SNMPv2)", RFC 1902, SNMP Research, Inc., Cisco Systems, 454 Dover Beach Consulting, Inc., International Network Services, January, 455 1996. 457 [7] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Textual 458 Conventions for version 2 of the the Simple Network Management Proto- 459 col (SNMPv2)", RFC 1903, SNMP Research, Inc., Cisco Systems, Dover 460 Beach Consulting, Inc., International Network Services, January, 1996. 462 [8] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Confor- 463 mance Statements for version 2 of the the Simple Network Management 464 Protocol (SNMPv2)", RFC 1904, SNMP Research, Inc., Cisco Systems, 465 Dover Beach Consulting, Inc., International Network Services, January, 466 1996. 468 [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol 469 Operations for Version 2 of the Simple Network Management Protocol 470 (SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco Systems, Dover Beach 471 Consulting, Inc., International Network Services, January, 1996. 473 [10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport 474 Mappings for Version 2 of the Simple Network Management Protocol 475 (SNMPv2)", RFC 1906, SNMP Research, Inc., Cisco Systems, Dover Beach 476 Consulting, Inc., International Network Services, January, 1996. 478 [11] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Manage- 479 ment Information Base for Version 2 of the Simple Network Management 480 Protocol (SNMPv2)", RFC 1907, SNMP Research, Inc., Cisco Systems, 481 Dover Beach Consulting, Inc., International Network Services, January, 482 1996. 484 [12] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Coexis- 485 tence between Version 1 and Version 2 of the Internet-standard Network 486 Management Framework", RFC 1908, SNMP Research, Inc., Cisco Systems, 487 Dover Beach Consulting, Inc., International Network Services, January, 488 1996. 490 [13] McCloghrie, K., "An Administrative Infrastructure for SNMPv2", 491 RFC 1909, Cisco Systems, February, 1996. 493 10. Authors' Addresses 495 Bernard Aboba 496 Microsoft Corporation 497 One Microsoft Way 498 Redmond, WA 98052 500 Phone: 206-936-6605 501 EMail: bernarda@microsoft.com 503 Glen Zorn 504 Microsoft Corporation 505 One Microsoft Way 506 Redmond, WA 98052 508 Phone: 206-703-1559 509 EMail: glennz@microsoft.com