idnits 2.17.1 draft-ietf-mpls-tc-mib-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): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard 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. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 218 has weird spacing: '...lly the defau...' -- 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 (August 2001) is 8289 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: 'RFC2514' is defined on line 471, but no explicit reference was found in the text == Unused Reference: 'RFC3036' is defined on line 536, but no explicit reference was found in the text == Unused Reference: 'Assigned' is defined on line 540, but no explicit reference was found in the text == Unused Reference: 'RSVPTE' is defined on line 545, but no explicit reference was found in the text == Unused Reference: 'CRLDP' is defined on line 551, but no explicit reference was found in the text ** Downref: Normative reference to an Historic RFC: RFC 1157 ** Downref: Normative reference to an Informational RFC: RFC 1215 ** Downref: Normative reference to an Historic RFC: RFC 1901 ** Obsolete normative reference: RFC 1905 (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 1906 (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2570 (Obsoleted by RFC 3410) ** Obsolete normative reference: RFC 2571 (Obsoleted by RFC 3411) ** Obsolete normative reference: RFC 2572 (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2573 (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2574 (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 2575 (Obsoleted by RFC 3415) ** Obsolete normative reference: RFC 3036 (Obsoleted by RFC 5036) ** Obsolete normative reference: RFC 1700 (ref. 'Assigned') (Obsoleted by RFC 3232) == Outdated reference: A later version (-09) exists of draft-ietf-mpls-rsvp-lsp-tunnel-08 == Outdated reference: A later version (-06) exists of draft-ietf-mpls-cr-ldp-05 Summary: 17 errors (**), 0 flaws (~~), 9 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group Thomas D. Nadeau 2 Internet Draft Cisco Systems, Inc. 3 Expires: February 2002 4 Joan Cucchiara 5 Crescent Networks 7 Cheenu Srinivasan 8 Alphion Corp. 10 Arun Viswanathan 11 Force10 Networks, Inc. 13 Hans Sjostrand 14 ipUnplugged 16 August 2001 18 Definition of Textual Conventions and OBJECT-IDENTITIES for 19 Multi-Protocol Label Switching (MPLS) Management 21 draft-ietf-mpls-tc-mib-02.txt 23 Status of this Memo 25 This document is an Internet-Draft and is in full 26 conformance with all provisions of Section 10 of RFC 2026. 28 Internet-Drafts are working documents of the Internet 29 Engineering Task Force (IETF), its areas, and its working 30 groups. Note that other groups may also distribute working 31 documents as Internet-Drafts. 33 Internet-Drafts are draft documents valid for a maximum of 34 six months and may be updated, replaced, or obsoleted by 35 other documents at any time. It is inappropriate to use 36 Internet-Drafts as reference material or to cite them other 37 than as "work in progress." 39 The list of current Internet-Drafts can be accessed at 40 http://www.ietf.org/ietf/1id-abstracts.txt. 42 The list of Internet-Draft Shadow Directories can be 43 accessed at http://www.ietf.org/shadow.html. 45 Table of Contents 47 1. Abstract 2 48 2. Introduction 2 49 3. The SNMP Management Framework 2 50 4. MPLS TC MIB Definitions 3 51 5. Security Considerations 9 52 6. References 9 53 7. Authors' Addresses 12 54 8. Full Copyright Statement 13 56 1. Abstract 58 This memo describes Textual Conventions and OBJECT- 59 IDENTITIES used for managing MPLS networks. 61 2. Introduction 63 This memo defines a portion of the Management Information 64 Base (MIB) for use with network management protocols in the 65 Internet community. In particular, it defines Textual 66 Conventions used in IETF MPLS and MPLS-related MIBs. 68 Comments should be made directly to the MPLS mailing list 69 at mpls@uu.net. 71 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", 72 "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", 73 and "OPTIONAL" in this document are to be interpreted as 74 described in RFC 2119, reference [RFC2119]. 76 For an introduction to the concepts of MPLS, see [RFC3031]. 78 3. The SNMP Management Framework 80 The SNMP Management Framework presently consists of five 81 major components: 83 - An overall architecture, described in RFC 2571 84 [RFC2571]. 86 - Mechanisms for describing and naming objects and events 87 for the purpose of management. The first version of 88 this Structure of Management Information (SMI) is 89 called SMIv1 and described in STD 16, RFC 1155 90 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 1215 91 [RFC1215]. The second version, called SMIv2, is 92 described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 93 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580]. 95 - Message protocols for transferring management 96 information. The first version of the SNMP message 97 protocol is called SNMPv1 and described in STD 15, RFC 98 1157 [RFC1157]. A second version of the SNMP message 99 protocol, which is not an Internet standards track 100 protocol, is called SNMPv2c and described in RFC 1901 101 [RFC1901] and RFC 1906 [RFC1906]. The third version of 102 the message protocol is called SNMPv3 and described in 103 RFC 1906 [RFC1906], RFC 2572 [RFC2572] and RFC 2574 104 [RFC2574]. 106 - Protocol operations for accessing management 107 information. The first set of protocol operations and 108 associated PDU formats is described in STD 15, RFC 1157 109 [RFC1157]. A second set of protocol operations and 110 associated PDU formats is described in RFC 1905 111 [RFC1905]. 113 - A set of fundamental applications described in RFC 2573 114 [RFC2573] and the view-based access control mechanism 115 described in RFC 2575 [RFC2575]. 117 A more detailed introduction to the current SNMP Management 118 Framework can be found in RFC 2570 [RFC2570]. 120 Managed objects are accessed via a virtual information 121 store, termed the Management Information Base or MIB. 122 Objects in the MIB are defined using the mechanisms defined 123 in the SMI. 125 This memo specifies a MIB module that is compliant to the 126 SMIv2. A MIB conforming to the SMIv1 can be produced 127 through the appropriate translations. The resulting 128 translated MIB must be semantically equivalent, except 129 where objects or events are omitted because no translation 130 is possible (use of Counter64). Some machine readable 131 information in SMIv2 will be converted into textual 132 descriptions in SMIv1 during the translation process. 133 However, this loss of machine readable information is not 134 considered to change the semantics of the MIB. 136 4. MPLS TC MIB Definitions 138 MPLS-TC-MIB DEFINITIONS ::= BEGIN 140 IMPORTS 141 MODULE-IDENTITY, Unsigned32, Integer32 142 FROM SNMPv2-SMI 143 transmission 144 FROM RFC1213-MIB 145 TEXTUAL-CONVENTION 146 FROM SNMPv2-TC; 148 mplsTCMIB MODULE-IDENTITY 149 LAST-UPDATED 150 "200108211200Z" -- 21 August 2001 12:00:00 GMT 151 ORGANIZATION 152 "Multiprotocol Label Switching (MPLS) Working Group" 153 CONTACT-INFO 154 " Thomas D. Nadeau 155 Cisco Systems, Inc. 156 tnadeau@cisco.com 158 Joan Cucchiara 159 Crescent Networks 160 jcucchiara@crescentnetworks.com 162 Cheenu Srinivasan 163 Alphion Corp. 164 cheenu@alphion.com 166 Arun Viswanathan 167 Force10 Networks, Inc. 168 arun@force10networks.com 170 Hans Sjostrand 171 ipUnplugged 172 hans@ipunplugged.com 174 Email comments to the MPLS WG Mailing List at 175 mpls@uu.net." 176 DESCRIPTION 177 "This MIB module defines Textual Conventions and 178 OBJECT-IDENTITIES for use in documents defining 179 management information bases (MIBs) for managing 180 MPLS networks." 182 -- Revision history. 184 REVISION 185 "200108211200Z" -- 21 August 2001 12:00:00 GMT 186 DESCRIPTION 187 "Reordered TCs alphabetically. Changed MplsPortAddr 188 to MplsPortNumber and redefined it to use Integer32 189 instead of INTEGER." 190 REVISION 191 "200108161200Z" -- 16 August 2001 12:00:00 GMT 192 DESCRIPTION 193 "Updates based on IESG review." 194 REVISION 195 "200104101200Z" -- 10 April 2001 12:00:00 GMT 196 DESCRIPTION 197 "Initial version." 199 ::= { mplsMIB 1 } 201 -- This object identifier needs to be assigned by IANA. 202 -- Since mpls has been assigned an ifType of 166 we recommend 203 -- that this OID be 166 as well. 205 mplsMIB OBJECT IDENTIFIER 206 ::= { transmission xxx } 208 -- Textual Conventions (sorted alphabetically). 210 MplsAtmVcIdentifier ::= TEXTUAL-CONVENTION 211 STATUS current 212 DESCRIPTION 213 "The VCI value for a VCL. The maximum VCI value 214 cannot exceed the value allowable by 215 atmInterfaceMaxVciBits defined in ATM-MIB. The 216 minimum value is 32, values 0 to 31 are reserved 217 for other uses by the ITU and ATM Forum. 32 is 218 typically the default value for the Control VC." 219 REFERENCE 220 "Definitions of Textual Conventions and OBJECT- 221 IDENTITIES for ATM Management, RFC 2514, Feb. 222 1999." 223 SYNTAX Integer32 (32..65535) 225 MplsBitRate ::= TEXTUAL-CONVENTION 226 DISPLAY-HINT "d" 227 STATUS current 228 DESCRIPTION 229 "An estimate of bandwidth in units of 1,000 bits per 230 second. If this object reports a value of 'n' then 231 the rate of the object is somewhere in the range of 232 'n-500' to 'n+499'. For objects which do not vary 233 in bit rate, or for those where no accurate 234 estimation can be made, this object should contain 235 the nominal bit rate." 236 SYNTAX Integer32 (1..2147483647) 238 MplsBurstSize ::= TEXTUAL-CONVENTION 239 DISPLAY-HINT "d" 240 STATUS current 241 DESCRIPTION 242 "The number of octets of MPLS data that the stream 243 may send back-to-back without concern for 244 policing." 245 SYNTAX Unsigned32 (1..4294967295) 247 MplsExtendedTunnelId ::= TEXTUAL-CONVENTION 248 STATUS current 249 DESCRIPTION 250 "A unique identifier for an MPLS Tunnel. This MAY 251 represent an IpV4 address of the ingress or egress 252 LSR for the tunnel. This value is derived from the 253 Extended Tunnel Id in RSVP or the Ingress Router ID 254 for CR-LDP." 255 REFERENCE 256 "1. Awduche, D., et al., RSVP-TE: Extensions to RSVP 257 for LSP Tunnels, draft-ietf-mpls-rsvp-lsp-tunnel- 258 08.txt, February 2001. 259 2. Constraint-Based LSP Setup using LDP, Jamoussi, 260 B., et al., draft-ietf-mpls-cr-ldp-05.txt, February 261 2001." 262 SYNTAX Unsigned32 264 MplsFTNIndex ::= TEXTUAL-CONVENTION 265 STATUS current 266 DESCRIPTION 267 "Index for a FEC-to-NHLFE (FTN) entry." 268 SYNTAX Integer32(1..2147483647) 270 MplsFTNIndexOrZero ::= TEXTUAL-CONVENTION 271 STATUS current 272 DESCRIPTION 273 "Index for a FTN entry or zero." 274 SYNTAX Integer32(0..2147483647) 276 MplsInitialCreationSource ::= TEXTUAL-CONVENTION 277 STATUS current 278 DESCRIPTION 279 "The entity that originally created the object in 280 question. The values of this enumeration are 281 defined as follows: 283 other(1) - This is used when an entity which has not 284 been enumerated in this textual convention but 285 which is known by the agent. 287 snmp(2) - The Simple Network Management Protocol was 288 used to configure this object initially. 290 ldp(3 - The Label Distribution Protocol was used to 291 configure this object initially. 293 rsvp(4) - The Resource Reservation Protocol was used 294 to configure this object initially. 296 crldp(5) - The Constraint-Based Label Distribution 297 Protocol was used to configure this object 298 initially. 300 policyAgent(6) - A policy agent (perhaps in 301 combination with one of the above protocols) was 302 used to configure this object initially. 304 unknown(7) - the agent cannot discern which 305 component created the object." 306 SYNTAX INTEGER { 307 other(1), 308 snmp(2), 309 ldp(3), 310 rsvp(4), 311 crldp(5), 312 policyAgent(6), 313 unknown (7) 314 } 316 MplsLSPID ::= TEXTUAL-CONVENTION 317 STATUS current 318 DESCRIPTION 319 "An identifier that is assigned to each LSP and is 320 used to uniquely identify it. This is assigned at 321 the head end of the LSP and can be used by all LSRs 322 to identify this LSP. This value is piggybacked by 323 the signaling protocol when this LSP is signaled 324 within the network. This identifier can then be 325 used at each LSR to identify which labels are being 326 swapped to other labels for this LSP. For IPv4 327 addresses this results in a 6-octet long cookie." 328 SYNTAX OCTET STRING (SIZE (0..31)) 330 MplsLabel ::= TEXTUAL-CONVENTION 331 STATUS current 332 DESCRIPTION 333 "This value represents an MPLS label as defined in 334 [RFC3031], [RFC3032], [RFC3034] and [RFC3035]." 335 REFERENCE 336 "1. Multiprotocol Label Switching Architecture, Rosen 337 et al, RFC 3031, August 1999. 338 2. MPLS Label Stack Encoding, Rosen et al, RFC 3032, 339 January 2001. 340 3. Use of Label Switching on Frame Relay Networks, 341 Conta et al, RFC 3034, January 2001. 342 4. MPLS using LDP and ATM VC switching, Davie et al, 343 RFC 3035, January 2001." 344 SYNTAX Unsigned32 (0..4294967295) 346 MplsLdpGenAddr ::= TEXTUAL-CONVENTION 347 STATUS current 348 DESCRIPTION 349 "The value of an network layer or data link layer 350 address." 351 SYNTAX OCTET STRING (SIZE (0..64)) 353 MplsLdpIdentifier ::= TEXTUAL-CONVENTION 354 STATUS current 355 DESCRIPTION 356 "The LDP identifier is a six octet quantity which is 357 used to identify an Label Switch Router (LSR) label 358 space. 360 The first four octets identify the LSR and must be a 361 globally unique value, such as a 32-bit router ID 362 assigned to the LSR, and the last two octets 363 identify a specific label space within the LSR." 364 SYNTAX OCTET STRING (SIZE (6)) 366 MplsLdpLabelTypes ::= TEXTUAL-CONVENTION 367 STATUS current 368 DESCRIPTION 369 "The Layer 2 label types which are defined for MPLS 370 LDP/CRLDP are generic(1), atm(2), or 371 frameRelay(3)." 372 SYNTAX INTEGER { 373 generic(1), 374 atm(2), 375 frameRelay(3) 376 } 378 MplsLsrIdentifier ::= TEXTUAL-CONVENTION 379 STATUS current 380 DESCRIPTION 381 "The Label Switch Router (LSR) identifier is the 382 first 4 bytes of the Label Distribution Protocol 383 (LDP) identifier." 384 SYNTAX OCTET STRING (SIZE (4)) 386 MplsPathIndex ::= TEXTUAL-CONVENTION 387 STATUS current 388 DESCRIPTION 389 "A unique identifier used to identify a specific path 390 used by a tunnel." 391 SYNTAX Unsigned32 393 MplsPathIndexOrZero ::= TEXTUAL-CONVENTION 394 STATUS current 395 DESCRIPTION 396 "A unique identifier used to identify a specific path 397 used by a tunnel. If this value is set to 0, it 398 indicates that no path is in use." 399 SYNTAX Unsigned32 401 MplsPortNumber ::= TEXTUAL-CONVENTION 402 STATUS current 403 DESCRIPTION 404 "A TCP or UDP port number. Along with an IP address 405 identifies a stream of IP traffic uniquely." 406 SYNTAX Integer32 (0..65535) 408 MplsTunnelAffinity ::= TEXTUAL-CONVENTION 409 STATUS current 410 DESCRIPTION 411 "Include-any, include-all, or exclude-all constraint 412 for link selection." 413 SYNTAX Unsigned32 415 MplsTunnelIndex ::= TEXTUAL-CONVENTION 416 STATUS current 417 DESCRIPTION 418 "Index into mplsTunnelTable." 419 SYNTAX Integer32 (1..65535) 421 MplsTunnelInstanceIndex ::= TEXTUAL-CONVENTION 422 STATUS current 423 DESCRIPTION 424 "Instance index into mplsTunnelTable." 425 SYNTAX Unsigned32 (0..65535) 427 END 429 5. Security Considerations 431 This memo defines textual conventions and object identities 432 for use in MPLS MIB modules. Security issues for these MIB 433 modules are addressed in the memos defining those modules. 435 6. References 437 [RFC1155] Rose, M., and K. McCloghrie, "Structure and 438 Identification of Management Information for 439 TCP/IP-based Internets", STD 16, RFC 1155, 440 May 1990. 442 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. 443 Davin, "Simple Network Management Protocol", 444 STD 15, RFC 1157, May 1990. 446 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB 447 Definitions", STD 16, RFC 1212, March 1991. 449 [RFC1215] M. Rose, "A Convention for Defining Traps 450 for use with the SNMP", RFC 1215, March 451 1991. 453 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. 454 Waldbusser, "Introduction to Community-based 455 SNMPv2", RFC 1901, January 1996. 457 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. 458 Waldbusser, "Protocol Operations for Version 459 2 of the Simple Network Management Protocol 460 (SNMPv2)", RFC 1905, January 1996. 462 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. 463 Waldbusser, "Transport Mappings for Version 464 2 of the Simple Network Management Protocol 465 (SNMPv2)", RFC 1906, January 1996. 467 [RFC2119] Bradner, S., "Key words for use in RFCs to 468 Indicate Requirement Levels", BCP 14, RFC 469 2119, March 1997. 471 [RFC2514] Noto, et. al., "Definitions of Textual 472 Conventions and OBJECT-IDENTITIES for ATM 473 Management", RFC 2514, Feb. 1999 475 [RFC2570] Case, J., Mundy, R., Partain, D., and B. 476 Stewart, "Introduction to Version 3 of the 477 Internet-standard Network Management 478 Framework", RFC 2570, April 1999. 480 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, 481 "An Architecture for Describing SNMP 482 Management Frameworks", RFC 2571, April 483 1999. 485 [RFC2572] Case, J., Harrington D., Presuhn R., and B. 486 Wijnen, "Message Processing and Dispatching 487 for the Simple Network Management Protocol 488 (SNMP)", RFC 2572, April 1999. 490 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 491 Applications", RFC 2573, April 1999. 493 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based 494 Security Model (USM) for version 3 of the 495 Simple Network Management Protocol 496 (SNMPv3)", RFC 2574, April 1999. 498 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, 499 "View-based Access Control Model (VACM) for 500 the Simple Network Management Protocol 501 (SNMP)", RFC 2575, April 1999. 503 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, 504 J., Case, J., Rose, M., and S. Waldbusser, 505 "Structure of Management Information Version 506 2 (SMIv2)", STD 58, RFC 2578, April 1999. 508 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, 509 J., Case, J., Rose, M., and S. Waldbusser, 510 "Textual Conventions for SMIv2", STD 58, RFC 511 2579, April 1999. 513 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, 514 J., Case, J., Rose, M., and S. Waldbusser, 515 "Conformance Statements for SMIv2", STD 58, 516 RFC 2580, April 1999. 518 [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, 519 "Multiprotocol Label Switching 520 Architecture", RFC 3031, August 1999. 522 [RFC3032] Rosen, E., Rekhter, Y., Tappan, D., 523 Farinacci, D., Federokow, G., Li, T., and A. 524 Conta, "MPLS Label Stack Encoding", RFC 525 3032, January 2001. 527 [RFC3034] Conta, A., Doolan, P., Malis, A., "Use of 528 Label Switching on Frame Relay Networks 529 Specification", RFC 3034, January 2001. 531 [RFC3035] Davie, B., Lawrence, J., McCloghrie, K., 532 Rosen, E., Swallow, G., Rekhter, Y., and P. 533 Doolan, "MPLS using LDP and ATM VC 534 switching", RFC 3035, January 2001. 536 [RFC3036] Anderson, L., Doolan, P., Feldman, N., 537 Fredette, A., and B. Thomas, "LDP 538 Specification", RFC 3036, January 2001. 540 [Assigned] Reynolds, J., and J. Postel, "Assigned 541 Numbers", RFC 1700, October 1994. See also: 542 http://www.isi.edu/in- 543 notes/iana/assignments/smi-numbers 545 [RSVPTE] Awduche, D., Berger, L., Gan, D., Li, T., 546 Srinivasan, V., and G. Swallow, "RSVP-TE: 547 Extensions to RSVP for LSP Tunnels", draft- 548 ietf-mpls-rsvp-lsp-tunnel-08.txt, February 549 2001. 551 [CRLDP] Jamoussi, B., Aboul-Magd, O., Andersson, L., 552 Ashwood-Smith, P., Hellstrand, F., Sundell, 553 K., Callon, R., Dantu, R., Wu, L., Doolan, 554 P., Worster, T., Feldman, N., Fredette, A., 555 Girish, M., Gray, E., Halpern, J., Heinanen, 556 J., Kilty, T., Malis, A., and P. Vaananen, 557 "Constraint-Based LSP Setup using LDP", 558 draft-ietf-mpls-cr-ldp-05.txt, February 559 2001." 561 7. Authors' Addresses 563 Thomas D. Nadeau 564 Cisco Systems, Inc. 565 250 Apollo Drive 566 Chelmsford, MA 01824 567 Phone: +1-978-244-3051 568 Email: tnadeau@cisco.com 570 Joan Cucchiara 571 Crescent Networks 572 900 Chelmsford Street 573 Lowell, MA 01851 574 Phone: +1-978-275-3183 575 email: jcucchiara@crescentnetworks.com 577 Cheenu Srinivasan 578 Alphion Corp. 579 4 Industrial Way West 580 Eatontown, NJ 07724 581 Phone: +1-732-676-7066 582 Email: cheenu@alphion.com 584 Arun Viswanathan 585 Force10 Networks, Inc. 586 1440 McCarthy Blvd 587 Milpitas, CA 95035 588 Phone: +1-408-571-3516 589 Email: arun@force10networks.com 591 Hans Sjostrand 592 ipUnplugged 593 P.O. Box 101 60 594 S-121 28 Stockholm, Sweden 595 Phone: +46-8-725-5930 596 Email: hans@ipunplugged.com 598 8. Full Copyright Statement 600 Copyright (C) The Internet Society (2001). All Rights 601 Reserved. 603 This document and translations of it may be copied and 604 furnished to others, and derivative works that comment on 605 or otherwise explain it or assist in its implementation may 606 be prepared, copied, published and distributed, in whole or 607 in part, without restriction of any kind, provided that the 608 above copyright notice and this paragraph are included on 609 all such copies and derivative works. However, this 610 document itself may not be modified in any way, such as by 611 removing the copyright notice or references to the Internet 612 Society or other Internet organizations, except as needed 613 for the purpose of developing Internet standards in which 614 case the procedures for copyrights defined in the Internet 615 Standards process must be followed, or as required to 616 translate it into languages other than English. 618 The limited permissions granted above are perpetual and 619 will not be revoked by the Internet Society or its 620 successors or assigns. This document and the information 621 contained herein is provided on an "AS IS" basis and THE 622 INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE 623 DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT 624 NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 625 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 626 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR 627 PURPOSE.