idnits 2.17.1 draft-ietf-mpls-tc-mib-01.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 321 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 16, 2001) is 8287 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 486, but no explicit reference was found in the text == Unused Reference: 'RFC3036' is defined on line 553, but no explicit reference was found in the text == Unused Reference: 'Assigned' is defined on line 557, but no explicit reference was found in the text == Unused Reference: 'RSVPTE' is defined on line 562, but no explicit reference was found in the text == Unused Reference: 'CRLDP' is defined on line 568, 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 -- Possible downref: Non-RFC (?) normative reference: ref. 'CRLDP' Summary: 17 errors (**), 0 flaws (~~), 8 warnings (==), 3 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: January 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 16, 2001 18 Definition of Textual Conventions and OBJECT-IDENTITIES for 19 Multi-Protocol Label Switching (MPLS) Management 21 draft-ietf-mpls-tc-mib-01.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 10 52 6. References 10 54 IETF Draft MPLS TC MIB August 2001 56 7. Authors' Addresses 12 57 8. Full Copyright Statement 12 59 1. Abstract 61 This memo describes Textual Conventions and OBJECT- 62 IDENTITIES used for managing MPLS networks. 64 2. Introduction 66 This memo defines a portion of the Management Information 67 Base (MIB) for use with network management protocols in the 68 Internet community. In particular, it defines Textual 69 Conventions used in IETF MPLS and MPLS-related MIBs. 71 Comments should be made directly to the MPLS mailing list 72 at mpls@uu.net. 74 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", 75 "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", 76 and "OPTIONAL" in this document are to be interpreted as 77 described in RFC 2119, reference [RFC2119]. 79 For an introduction to the concepts of MPLS, see [RFC3031]. 81 3. The SNMP Management Framework 83 The SNMP Management Framework presently consists of five 84 major components: 86 - An overall architecture, described in RFC 2571 87 [RFC2571]. 89 - Mechanisms for describing and naming objects and events 90 for the purpose of management. The first version of 91 this Structure of Management Information (SMI) is 92 called SMIv1 and described in STD 16, RFC 1155 93 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 1215 94 [RFC1215]. The second version, called SMIv2, is 95 described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 96 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580]. 98 - Message protocols for transferring management 99 information. The first version of the SNMP message 100 protocol is called SNMPv1 and described in STD 15, RFC 101 1157 [RFC1157]. A second version of the SNMP message 103 IETF Draft MPLS TC MIB August 2001 105 protocol, which is not an Internet standards track 106 protocol, is called SNMPv2c and described in RFC 1901 107 [RFC1901] and RFC 1906 [RFC1906]. The third version of 108 the message protocol is called SNMPv3 and described in 109 RFC 1906 [RFC1906], RFC 2572 [RFC2572] and RFC 2574 110 [RFC2574]. 112 - Protocol operations for accessing management 113 information. The first set of protocol operations and 114 associated PDU formats is described in STD 15, RFC 1157 115 [RFC1157]. A second set of protocol operations and 116 associated PDU formats is described in RFC 1905 117 [RFC1905]. 119 - A set of fundamental applications described in RFC 2573 120 [RFC2573] and the view-based access control mechanism 121 described in RFC 2575 [RFC2575]. 123 A more detailed introduction to the current SNMP Management 124 Framework can be found in RFC 2570 [RFC2570]. 126 Managed objects are accessed via a virtual information 127 store, termed the Management Information Base or MIB. 128 Objects in the MIB are defined using the mechanisms defined 129 in the SMI. 131 This memo specifies a MIB module that is compliant to the 132 SMIv2. A MIB conforming to the SMIv1 can be produced 133 through the appropriate translations. The resulting 134 translated MIB must be semantically equivalent, except 135 where objects or events are omitted because no translation 136 is possible (use of Counter64). Some machine readable 137 information in SMIv2 will be converted into textual 138 descriptions in SMIv1 during the translation process. 139 However, this loss of machine readable information is not 140 considered to change the semantics of the MIB. 142 4. MPLS TC MIB Definitions 144 MPLS-TC-MIB DEFINITIONS ::= BEGIN 146 IMPORTS 147 MODULE-IDENTITY, Unsigned32, Integer32 148 FROM SNMPv2-SMI 149 transmission 150 FROM RFC1213-MIB 151 TEXTUAL-CONVENTION 152 FROM SNMPv2-TC; 154 IETF Draft MPLS TC MIB August 2001 156 mplsTCMIB MODULE-IDENTITY 157 LAST-UPDATED 158 "200108161200Z" -- 16 August 2001 12:00:00 GMT 159 ORGANIZATION 160 "Multiprotocol Label Switching (MPLS) Working Group" 161 CONTACT-INFO 162 " Thomas D. Nadeau 163 Cisco Systems, Inc. 164 tnadeau@cisco.com 166 Joan Cucchiara 167 Crescent Networks 168 jcucchiara@crescentnetworks.com 170 Cheenu Srinivasan 171 Alphion Corp. 172 cheenu@alphion.com 174 Arun Viswanathan 175 Force10 Networks, Inc. 176 arun@force10networks.com 178 Hans Sjostrand 179 ipUnplugged 180 hans@ipunplugged.com 182 Email comments to the MPLS WG Mailing List at 183 mpls@uu.net." 184 DESCRIPTION 185 "This MIB module defines Textual Conventions and 186 OBJECT-IDENTITIES for use in documents defining 187 management information bases (MIBs) for managing 188 MPLS networks." 190 -- Revision history. 192 REVISION 193 "200108161200Z" -- 16 August 2001 12:00:00 GMT 194 DESCRIPTION 195 "Updates based on IESG review." 196 REVISION 197 "200104101200Z" -- 10 April 2001 12:00:00 GMT 198 DESCRIPTION 199 "Initial version." 201 ::= { mplsMIB 1 } 203 -- This object identifier needs to be assigned by IANA. 204 -- Since mpls has been assigned an ifType of 166 we recommend 205 -- that this OID be 166 as well. 207 IETF Draft MPLS TC MIB August 2001 209 mplsMIB OBJECT IDENTIFIER 210 ::= { transmission xxx } 212 -- Textual Conventions. 214 MplsBitRate ::= TEXTUAL-CONVENTION 215 DISPLAY-HINT "d" 216 STATUS current 217 DESCRIPTION 218 "An estimate of bandwidth in units of 1,000 bits per 219 second. If this object reports a value of 'n' then 220 the rate of the object is somewhere in the range of 221 'n-500' to 'n+499'. For objects which do not vary 222 in bit rate, or for those where no accurate 223 estimation can be made, this object should contain 224 the nominal bit rate." 225 SYNTAX Integer32 (1..2147483647) 227 MplsBurstSize ::= TEXTUAL-CONVENTION 228 DISPLAY-HINT "d" 229 STATUS current 230 DESCRIPTION 231 "The number of octets of MPLS data that the stream 232 may send back-to-back without concern for 233 policing." 234 SYNTAX Unsigned32 (1..4294967295) 236 MplsPortAddr ::= TEXTUAL-CONVENTION 237 STATUS current 238 DESCRIPTION 239 "A TCP or UDP port number. Along with an IP address 240 identifies a stream of IP traffic uniquely." 241 SYNTAX INTEGER (0..65535) 243 MplsExtendedTunnelId ::= TEXTUAL-CONVENTION 244 STATUS current 245 DESCRIPTION 246 "A unique identifier for an MPLS Tunnel. This MAY 247 represent an IpV4 address of the ingress or egress 248 LSR for the tunnel. This value is derived from the 249 Extended Tunnel Id in RSVP or the Ingress Router ID 250 for CR-LDP." 251 REFERENCE 252 "1. Awduche, D., et al., RSVP-TE: Extensions to RSVP 253 for LSP Tunnels, draft-ietf-mpls-rsvp-lsp-tunnel- 254 08.txt, February 2001. 255 2. Constraint-Based LSP Setup using LDP, Jamoussi, 256 B., et al., draft-ietf-mpls-cr-ldp-05.txt, February 257 2001." 259 IETF Draft MPLS TC MIB August 2001 261 SYNTAX Unsigned32 263 MplsLabel ::= TEXTUAL-CONVENTION 264 STATUS current 265 DESCRIPTION 266 "This value represents an MPLS label as defined in 267 [RFC3031], [RFC3032], [RFC3034] and [RFC3035]." 268 REFERENCE 269 "1. Multiprotocol Label Switching Architecture, Rosen 270 et al, RFC 3031, August 1999. 271 2. MPLS Label Stack Encoding, Rosen et al, RFC 3032, 272 January 2001. 273 3. Use of Label Switching on Frame Relay Networks, 274 Conta et al, RFC 3034, January 2001. 275 4. MPLS using LDP and ATM VC switching, Davie et al, 276 RFC 3035, January 2001." 277 SYNTAX Unsigned32 (0..4294967295) 279 MplsLdpGenAddr ::= TEXTUAL-CONVENTION 280 STATUS current 281 DESCRIPTION 282 "The value of an network layer or data link layer 283 address." 284 SYNTAX OCTET STRING (SIZE (0..64)) 286 MplsLdpIdentifier ::= TEXTUAL-CONVENTION 287 STATUS current 288 DESCRIPTION 289 "The LDP identifier is a six octet quantity which is 290 used to identify an Label Switch Router (LSR) label 291 space. 293 The first four octets identify the LSR and must be a 294 globally unique value, such as a 32-bit router ID 295 assigned to the LSR, and the last two octets 296 identify a specific label space within the LSR." 297 SYNTAX OCTET STRING (SIZE (6)) 299 MplsLdpLabelTypes ::= TEXTUAL-CONVENTION 300 STATUS current 301 DESCRIPTION 302 "The Layer 2 label types which are defined for MPLS 303 LDP/CRLDP are generic(1), atm(2), or 304 frameRelay(3)." 305 SYNTAX INTEGER { 306 generic(1), 307 atm(2), 308 frameRelay(3) 309 } 311 IETF Draft MPLS TC MIB August 2001 313 MplsAtmVcIdentifier ::= TEXTUAL-CONVENTION 314 STATUS current 315 DESCRIPTION 316 "The VCI value for a VCL. The maximum VCI value 317 cannot exceed the value allowable by 318 atmInterfaceMaxVciBits defined in ATM-MIB. The 319 minimum value is 32, values 0 to 31 are reserved 320 for other uses by the ITU and ATM Forum. 32 is 321 typically the default value for the Control VC." 322 REFERENCE 323 "Definitions of Textual Conventions and OBJECT- 324 IDENTITIES for ATM Management, RFC 2514, Feb. 325 1999." 326 SYNTAX Integer32 (32..65535) 328 MplsLSPID ::= TEXTUAL-CONVENTION 329 STATUS current 330 DESCRIPTION 331 "An identifier that is assigned to each LSP and is 332 used to uniquely identify it. This is assigned at 333 the head end of the LSP and can be used by all LSRs 334 to identify this LSP. This value is piggybacked by 335 the signaling protocol when this LSP is signaled 336 within the network. This identifier can then be 337 used at each LSR to identify which labels are being 338 swapped to other labels for this LSP. For IPv4 339 addresses this results in a 6-octet long cookie." 340 SYNTAX OCTET STRING (SIZE (0..31)) 342 MplsLsrIdentifier ::= TEXTUAL-CONVENTION 343 STATUS current 344 DESCRIPTION 345 "The Label Switch Router (LSR) identifier is the 346 first 4 bytes of the Label Distribution Protocol 347 (LDP) identifier." 348 SYNTAX OCTET STRING (SIZE (4)) 350 MplsInitialCreationSource ::= TEXTUAL-CONVENTION 351 STATUS current 352 DESCRIPTION 353 "The entity that originally created the object in 354 question. The values of this enumeration are 355 defined as follows: 357 other(1) - This is used when an entity which has not 358 been enumerated in this textual convention but 359 which is known by the agent. 361 snmp(2) - The Simple Network Management Protocol was 362 used to configure this object initially. 364 IETF Draft MPLS TC MIB August 2001 366 ldp(3 - The Label Distribution Protocol was used to 367 configure this object initially. 369 rsvp(4) - The Resource Reservation Protocol was used 370 to configure this object initially. 372 crldp(5) - The Constraint-Based Label Distribution 373 Protocol was used to configure this object 374 initially. 376 policyAgent(6) - A policy agent (perhaps in 377 combination with one of the above protocols) was 378 used to configure this object initially. 380 unknown(7) - the agent cannot discern which 381 component created the object." 382 SYNTAX INTEGER { 383 other(1), 384 snmp(2), 385 ldp(3), 386 rsvp(4), 387 crldp(5), 388 policyAgent(6), 389 unknown (7) 390 } 392 MplsPathIndex ::= TEXTUAL-CONVENTION 393 STATUS current 394 DESCRIPTION 395 "A unique identifier used to identify a specific path 396 used by a tunnel." 397 SYNTAX Unsigned32 399 MplsPathIndexOrZero ::= TEXTUAL-CONVENTION 400 STATUS current 401 DESCRIPTION 402 "A unique identifier used to identify a specific path 403 used by a tunnel. If this value is set to 0, it 404 indicates that no path is in use." 405 SYNTAX Unsigned32 407 MplsTunnelAffinity ::= TEXTUAL-CONVENTION 408 STATUS current 409 DESCRIPTION 410 "Include-any, include-all, or exclude-all constraint 411 for link selection." 412 SYNTAX Unsigned32 414 MplsTunnelIndex ::= TEXTUAL-CONVENTION 415 IETF Draft MPLS TC MIB August 2001 417 STATUS current 418 DESCRIPTION 419 "Index into mplsTunnelTable." 420 SYNTAX Integer32 (1..65535) 422 MplsTunnelInstanceIndex ::= TEXTUAL-CONVENTION 423 STATUS current 424 DESCRIPTION 425 "Instance index into mplsTunnelTable." 426 SYNTAX Unsigned32 (0..65535) 428 MplsFTNIndex ::= TEXTUAL-CONVENTION 429 STATUS current 430 DESCRIPTION 431 "Index for an FEC-to-NHLFE (FTN) entry." 432 SYNTAX Integer32(1..2147483647) 434 MplsFTNIndexOrZero ::= TEXTUAL-CONVENTION 435 STATUS current 436 DESCRIPTION 437 "Index for an FTN entry or zero." 438 SYNTAX Integer32(0..2147483647) 440 END 442 5. Security Considerations 444 This memo defines textual conventions and object identities 445 for use in MPLS MIB modules. Security issues for these MIB 446 modules are addressed in the memos defining those modules. 448 6. References 450 [RFC1155] Rose, M., and K. McCloghrie, "Structure and 451 Identification of Management Information for 452 TCP/IP-based Internets", STD 16, RFC 1155, 453 May 1990. 455 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. 456 Davin, "Simple Network Management Protocol", 457 STD 15, RFC 1157, May 1990. 459 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB 460 Definitions", STD 16, RFC 1212, March 1991. 462 [RFC1215] M. Rose, "A Convention for Defining Traps 463 for use with the SNMP", RFC 1215, March 464 1991. 466 IETF Draft MPLS TC MIB August 2001 468 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. 469 Waldbusser, "Introduction to Community-based 470 SNMPv2", RFC 1901, January 1996. 472 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. 473 Waldbusser, "Protocol Operations for Version 474 2 of the Simple Network Management Protocol 475 (SNMPv2)", RFC 1905, January 1996. 477 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. 478 Waldbusser, "Transport Mappings for Version 479 2 of the Simple Network Management Protocol 480 (SNMPv2)", RFC 1906, January 1996. 482 [RFC2119] Bradner, S., "Key words for use in RFCs to 483 Indicate Requirement Levels", BCP 14, RFC 484 2119, March 1997. 486 [RFC2514] Noto, et. al., "Definitions of Textual 487 Conventions and OBJECT-IDENTITIES for ATM 488 Management", RFC 2514, Feb. 1999 490 [RFC2570] Case, J., Mundy, R., Partain, D., and B. 491 Stewart, "Introduction to Version 3 of the 492 Internet-standard Network Management 493 Framework", RFC 2570, April 1999. 495 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, 496 "An Architecture for Describing SNMP 497 Management Frameworks", RFC 2571, April 498 1999. 500 [RFC2572] Case, J., Harrington D., Presuhn R., and B. 501 Wijnen, "Message Processing and Dispatching 502 for the Simple Network Management Protocol 503 (SNMP)", RFC 2572, April 1999. 505 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 506 Applications", RFC 2573, April 1999. 508 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based 509 Security Model (USM) for version 3 of the 510 Simple Network Management Protocol 511 (SNMPv3)", RFC 2574, April 1999. 513 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, 514 "View-based Access Control Model (VACM) for 515 the Simple Network Management Protocol 516 (SNMP)", RFC 2575, April 1999. 518 IETF Draft MPLS TC MIB August 2001 520 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, 521 J., Case, J., Rose, M., and S. Waldbusser, 522 "Structure of Management Information Version 523 2 (SMIv2)", STD 58, RFC 2578, April 1999. 525 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, 526 J., Case, J., Rose, M., and S. Waldbusser, 527 "Textual Conventions for SMIv2", STD 58, RFC 528 2579, April 1999. 530 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, 531 J., Case, J., Rose, M., and S. Waldbusser, 532 "Conformance Statements for SMIv2", STD 58, 533 RFC 2580, April 1999. 535 [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, 536 "Multiprotocol Label Switching 537 Architecture", RFC 3031, August 1999. 539 [RFC3032] Rosen, E., Rekhter, Y., Tappan, D., 540 Farinacci, D., Federokow, G., Li, T., and A. 541 Conta, "MPLS Label Stack Encoding", RFC 542 3032, January 2001. 544 [RFC3034] Conta, A., Doolan, P., Malis, A., "Use of 545 Label Switching on Frame Relay Networks 546 Specification", RFC 3034, January 2001. 548 [RFC3035] Davie, B., Lawrence, J., McCloghrie, K., 549 Rosen, E., Swallow, G., Rekhter, Y., and P. 550 Doolan, "MPLS using LDP and ATM VC 551 switching", RFC 3035, January 2001. 553 [RFC3036] Anderson, L., Doolan, P., Feldman, N., 554 Fredette, A., and B. Thomas, "LDP 555 Specification", RFC 3036, January 2001. 557 [Assigned] Reynolds, J., and J. Postel, "Assigned 558 Numbers", RFC 1700, October 1994. See also: 559 http://www.isi.edu/in- 560 notes/iana/assignments/smi-numbers 562 [RSVPTE] Awduche, D., Berger, L., Gan, D., Li, T., 563 Srinivasan, V., Swallow, G., RSVP-TE: 564 Extensions to RSVP for LSP Tunnels, draft- 565 ietf-mpls-rsvp-lsp-tunnel-08.txt, February 566 2001. 568 [CRLDP] Jamoussi, B., Aboul-Magd, O., Andersson, L., 570 IETF Draft MPLS TC MIB August 2001 572 Ashwood-Smith, P., Hellstrand, F., Sundell, 573 K., Callon, R., Dantu, R., Wu, L., Doolan, 574 P., Worster, T., Feldman, N., Fredette, A., 575 Girish, M., Gray, E., Halpern, J., Heinanen, 576 J., Kilty, T., Malis, A., Vaananen, P., 577 Constraint-Based LSP Setup using LDP, draft- 578 ietf-mpls-cr-ldp-05.txt, February 2001." 580 7. Authors' Addresses 582 Thomas D. Nadeau 583 Cisco Systems, Inc. 584 250 Apollo Drive 585 Chelmsford, MA 01824 586 Phone: +1-978-244-3051 587 Email: tnadeau@cisco.com 589 Joan Cucchiara 590 Crescent Networks 591 900 Chelmsford Street 592 Lowell, MA 01851 593 Phone: +1-978-275-3183 594 email: jcucchiara@crescentnetworks.com 596 Cheenu Srinivasan 597 Alphion Corp. 598 4 Industrial Way West 599 Eatontown, NJ 07724 600 Phone: +1-732-676-7066 601 Email: cheenu@alphion.com 603 Arun Viswanathan 604 Force10 Networks, Inc. 605 1440 McCarthy Blvd 606 Milpitas, CA 95035 607 Phone: +1-408-571-3516 608 Email: arun@force10networks.com 610 Hans Sjostrand 611 ipUnplugged 612 P.O. Box 101 60 613 S-121 28 Stockholm, Sweden 614 Phone: +46-8-725-5930 615 Email: hans@ipunplugged.com 617 8. Full Copyright Statement 619 Copyright (C) The Internet Society (2001). All Rights 621 IETF Draft MPLS TC MIB August 2001 623 Reserved. 625 This document and translations of it may be copied and 626 furnished to others, and derivative works that comment on 627 or otherwise explain it or assist in its implementation may 628 be prepared, copied, published and distributed, in whole or 629 in part, without restriction of any kind, provided that the 630 above copyright notice and this paragraph are included on 631 all such copies and derivative works. However, this 632 document itself may not be modified in any way, such as by 633 removing the copyright notice or references to the Internet 634 Society or other Internet organizations, except as needed 635 for the purpose of developing Internet standards in which 636 case the procedures for copyrights defined in the Internet 637 Standards process must be followed, or as required to 638 translate it into languages other than English. 640 The limited permissions granted above are perpetual and 641 will not be revoked by the Internet Society or its 642 successors or assigns. This document and the information 643 contained herein is provided on an "AS IS" basis and THE 644 INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE 645 DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT 646 NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 647 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 648 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR 649 PURPOSE.