idnits 2.17.1 draft-nadeau-ccamp-gmpls-tc-mib-01.txt: 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: ---------------------------------------------------------------------------- ** 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? == 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 abstract seems to contain references ([TCMIB]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- -- 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 (January 2002) is 8134 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) == Missing Reference: 'RFC2026' is mentioned on line 28, but not defined == Unused Reference: 'RFC2863' is defined on line 379, but no explicit reference was found in the text == Unused Reference: 'RFC3209' is defined on line 395, but no explicit reference was found in the text == Unused Reference: 'CRLDP' is defined on line 400, but no explicit reference was found in the text == Unused Reference: 'GMPLSSig' is defined on line 411, but no explicit reference was found in the text == Unused Reference: 'GMPLSCRLDP' is defined on line 422, but no explicit reference was found in the text == Unused Reference: 'GMPLSRSVPTE' is defined on line 433, but no explicit reference was found in the text == Unused Reference: 'GMPLSSonetSDH' is defined on line 444, but no explicit reference was found in the text == Unused Reference: 'RFC1213' is defined on line 465, but no explicit reference was found in the text == Unused Reference: 'RFC2514' is defined on line 488, but no explicit reference was found in the text == Unused Reference: 'RFC3031' is defined on line 532, but no explicit reference was found in the text == Unused Reference: 'RFC3032' is defined on line 536, but no explicit reference was found in the text == Unused Reference: 'RFC3034' is defined on line 541, but no explicit reference was found in the text == Unused Reference: 'RFC3035' is defined on line 545, but no explicit reference was found in the text == Unused Reference: 'RFC3036' is defined on line 550, but no explicit reference was found in the text == Unused Reference: 'LABELMIB' is defined on line 562, but no explicit reference was found in the text == Unused Reference: 'GMPLSTEMIB' is defined on line 569, but no explicit reference was found in the text == Unused Reference: 'GMPLSLSRMIB' is defined on line 577, but no explicit reference was found in the text ** Downref: Normative reference to an Historic RFC: RFC 1157 -- Possible downref: Non-RFC (?) normative reference: ref. 'GMPLSArch' == Outdated reference: A later version (-06) exists of draft-ietf-mpls-cr-ldp-05 -- Possible downref: Non-RFC (?) normative reference: ref. 'GMPLSSig' -- Possible downref: Non-RFC (?) normative reference: ref. 'GMPLSCRLDP' -- Possible downref: Non-RFC (?) normative reference: ref. 'GMPLSRSVPTE' -- Possible downref: Non-RFC (?) normative reference: ref. 'GMPLSSonetSDH' -- Obsolete informational reference (is this intentional?): RFC 1905 (Obsoleted by RFC 3416) -- Obsolete informational reference (is this intentional?): RFC 1906 (Obsoleted by RFC 3417) -- Obsolete informational reference (is this intentional?): RFC 2570 (Obsoleted by RFC 3410) -- Obsolete informational reference (is this intentional?): RFC 2571 (Obsoleted by RFC 3411) -- Obsolete informational reference (is this intentional?): RFC 2572 (Obsoleted by RFC 3412) -- Obsolete informational reference (is this intentional?): RFC 2573 (Obsoleted by RFC 3413) -- Obsolete informational reference (is this intentional?): RFC 2574 (Obsoleted by RFC 3414) -- Obsolete informational reference (is this intentional?): RFC 2575 (Obsoleted by RFC 3415) -- Obsolete informational reference (is this intentional?): RFC 3036 (Obsoleted by RFC 5036) Summary: 5 errors (**), 0 flaws (~~), 20 warnings (==), 16 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group Thomas D. Nadeau 3 Internet Draft Cisco Systems, Inc. 4 Expires: July 2002 5 Cheenu Srinivasan 6 Parama Networks, Inc. 8 Adrian Farrel 9 Movaz Networks, Inc. 11 Tim Hall 12 Edward Harrison 13 Data Connection Ltd. 15 January 2002 17 Definition of Textual Conventions and OBJECT-IDENTITIES 18 for Generalized Multiprotocol Label Switching (GMPLS) 19 Management 21 draft-nadeau-ccamp-gmpls-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 27 [RFC2026]. 29 Internet-Drafts are working documents of the Internet 30 Engineering Task Force (IETF), its areas, and its working 31 groups. Note that other groups may also distribute 32 working documents as Internet-Drafts. 34 Internet-Drafts are draft documents valid for a maximum 35 of six months and may be updated, replaced, or obsoleted 36 by other documents at any time. It is inappropriate to 37 use Internet- Drafts as reference material or to cite 38 them other than as "work in progress." 40 The list of current Internet-Drafts can be accessed at 41 http://www.ietf.org/ietf/1id-abstracts.txt. 43 The list of Internet-Draft Shadow Directories can be 44 accessed at http://www.ietf.org/shadow.html. 46 Abstract 48 This memo describes Textual Conventions and OBJECT- 49 IDENTITIES common to the Management Information Bases 50 (MIBs) for managing Generalized Multiprotocol Label 51 Switching (GMPLS) networks. 53 It supplements [TCMIB] which describes Textual 54 Conventions and OBJECT-IDENTITIES common to the 55 Management Information Bases (MIBs) for managing 56 Multiprotocol Label Switching (MPLS) networks. 58 Table of Contents 60 1. Changes and Pending Work .................................. 2 61 1.1. Changes Since the Last Version ......................... 2 62 1.2. Pending Work ........................................... 2 63 2. Introduction .............................................. 2 64 3. The SNMP Management Framework ............................. 3 65 4. GMPLS TC MIB Definitions .................................. 4 66 5. Security Considerations ................................... 8 67 6. References ................................................ 8 68 6.1. Normative References ................................... 8 69 6.2. Informational References ............................... 10 70 7. Authors' Addresses ........................................ 12 71 8. Full Copyright Statement .................................. 13 73 1. Changes and Pending Work 75 This section must be removed before the draft progresses 76 to RFC. 78 1.1. Changes Since the Last Version 80 Changes to get the MIB to compile. 82 1.2. Pending Work 84 No pending work items have been identified for this 85 draft. 87 2. Introduction 89 This memo defines a portion of the Management Information 90 Base (MIB) for use with network management protocols in 91 the Internet community. In particular, it defines 92 Textual Conventions used in IETF GMPLS and GMPLS-related 93 MIBs. 95 This document suplements [TCMIB] that defines Textual 96 Conventions and OBJECT-IDENTITIES for Multiprotocol Label 97 Switching (MPLS) Management. [TCMIB] may continue to be 98 used without this MIB in networks that support only MPLS. 100 Comments should be made directly to the CCAMP mailing 101 list at ccamp@ops.ietf.org. 103 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", 104 "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", 105 "MAY", and "OPTIONAL" in this document are to be 106 interpreted as described in RFC 2119, reference 107 [RFC2119]. 109 For an introduction to the concepts of GMPLS, see 110 [GMPLSArch]. 112 3. The SNMP Management Framework 114 The SNMP Management Framework presently consists of five 115 major components: 117 - An overall architecture, described in RFC 2571 118 [RFC2571]. 120 - Mechanisms for describing and naming objects and 121 events for the purpose of management. The first 122 version of this Structure of Management Information 123 (SMI) is called SMIv1 and described in STD 16, RFC 124 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and STD 16, 125 RFC 1215 [RFC1215]. The second version, called SMIv2, 126 is described in STD 58, RFC 2578 [RFC2578], STD 58, 127 RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580]. 129 - Message protocols for transferring management 130 information. The first version of the SNMP message 131 protocol is called SNMPv1 and described in STD 15, RFC 132 1157 [RFC1157]. A second version of the SNMP message 133 protocol, which is not an Internet standards track 134 protocol, is called SNMPv2c and described in RFC 1901 135 [RFC1901] and RFC 1906 [RFC1906]. The third version 136 of the message protocol is called SNMPv3 and described 137 in RFC 1906 [RFC1906], RFC 2572 [RFC2572] and RFC 2574 138 [RFC2574]. 140 - Protocol operations for accessing management 141 information. The first set of protocol operations and 142 associated PDU formats is described in STD 15, RFC 143 1157 [RFC1157]. A second set of protocol operations 144 and associated PDU formats is described in RFC 1905 145 [RFC1905]. 147 - A set of fundamental applications described in RFC 148 2573 [RFC2573] and the view-based access control 149 mechanism described in RFC 2575 [RFC2575]. 151 A more detailed introduction to the current SNMP 152 Management Framework can be found in RFC 2570 [RFC2570]. 154 Managed objects are accessed via a virtual information 155 store, termed the Management Information Base or MIB. 156 Objects in the MIB are defined using the mechanisms 157 defined in the SMI. 159 This memo specifies a MIB module that is compliant to the 160 SMIv2. A MIB conforming to the SMIv1 can be produced 161 through the appropriate translations. The resulting 162 translated MIB must be semantically equivalent, except 163 where objects or events are omitted because no 164 translation is possible (use of Counter64). Some machine 165 readable information in SMIv2 will be converted into 166 textual descriptions in SMIv1 during the translation 167 process. However, this loss of machine readable 168 information is not considered to change the semantics of 169 the MIB. 171 4. GMPLS TC MIB Definitions 173 GMPLS-TC-MIB DEFINITIONS ::= BEGIN 175 IMPORTS 176 MODULE-IDENTITY, experimental 177 FROM SNMPv2-SMI 178 TEXTUAL-CONVENTION 179 FROM SNMPv2-TC 180 ; 182 gmplsTCMIB MODULE-IDENTITY 183 LAST-UPDATED 184 "200201251200Z" -- 25 Jan 2002 12:00:00 GMT 185 ORGANIZATION 186 "Common Control And Management Protocols 187 (CCAMP) Working Group" 188 CONTACT-INFO 189 " Thomas D. Nadeau 190 Postal: Cisco Systems, Inc. 191 250 Apollo Drive 192 Chelmsford, MA 01824 193 Tel: +1-978-244-3051 194 Email: tnadeau@cisco.com 196 Cheenu Srinivasan 197 Postal: Parama Networks, Inc. 198 1030 Broad Street 199 Shrewsbury, NJ 07702 200 Tel: +1-732-544-9120 x731 201 Email: cheenu@paramanet.com: 203 Adrian Farrel 204 Postal: Movaz Networks, Inc. 205 7926 Jones Branch Drive 206 McLean, VA 22102 207 Tel: +1-703-847-1986 208 Email: afarrel@movaz.com 210 Edward Harrison 211 Postal: Data Connection Ltd. 212 100 Church Street 213 Enfield, Middlesex 214 EN2 6BQ, United Kingdom 215 Tel: +44-20-8366-1177 216 Email: eph@dataconnection.com 218 Tim Hall 219 Postal: Data Connection Ltd. 220 100 Church Street 221 Enfield, Middlesex 222 EN2 6BQ, United Kingdom 223 Tel: +44-20-8366-1177 224 Email: timhall@dataconnection.com 226 Email comments to the CCAMP WG Mailing List 227 at ccamp@ops.ietf.org." 229 DESCRIPTION 230 "This MIB module defines Textual Conventions 231 and OBJECT-IDENTITIES for use in documents 232 defining management information bases 233 (MIBs) for managing GMPLS networks." 235 -- Revision history. 236 REVISION 237 "200111111100Z" -- 11 Nov 2001 11:00:00 GMT 238 DESCRIPTION 239 "Initial version." 240 REVISION 241 "200201251200Z" -- 25 Jan 2002 12:00:00 GMT 243 DESCRIPTION 244 "Revision for compilation and work in 245 progress." 246 ::= { gmplsMIB 1 } 248 -- This object identifier needs to be assigned by IANA. 249 gmplsMIB OBJECT IDENTIFIER ::= { experimental xxx } 251 -- Textual Conventions (sorted alphabetically). 253 GmplsFreeformLabel ::= TEXTUAL-CONVENTION 254 STATUS current 255 DESCRIPTION 256 "This value represents a freeform 257 generalized MPLS Label. This can be used 258 to represent label types which are not 259 standard in the drafts." 260 SYNTAX OCTET STRING (SIZE (0..64)) 262 GmplsGeneralizedLabelSubtypes ::= TEXTUAL-CONVENTION 263 STATUS current 264 DESCRIPTION 265 "Determines the interpretation that should 266 be applied to a label given its label type 267 as specified by 268 GmplsGeneralizedLabelTypes." 269 SYNTAX INTEGER { 270 mplsLabel(1), 271 portWavelengthLabel(2), 272 freeformGeneralizedLabel(3), 273 sonetLabel(4), 274 sdhLabel(5), 275 wavebandLabel(6) 276 } 278 GmplsGeneralizedLabelTypes ::= TEXTUAL-CONVENTION 279 STATUS current 280 DESCRIPTION 281 "The label types that are defined for 282 Generalized MPLS." 283 SYNTAX INTEGER { 284 mplsLabel(1), 285 generalizedLabel(2) 286 } 288 GmplsHopAddrType ::= TEXTUAL-CONVENTION 289 STATUS current 290 DESCRIPTION 291 "Identifies the type of address encoded in 292 an address object that forms a hop of an 293 explicit or reported route." 294 SYNTAX INTEGER { 295 ipV4(1), 296 ipV6(2), 297 asNumber(3), 298 lspid(4), 299 lspidIpV6(5), 300 unnumberedIfIpV4(6), 301 unnumberedIfIpV6(7) 302 } 304 GmplsSegmentDirection ::= TEXTUAL-CONVENTION 305 STATUS current 306 DESCRIPTION 307 "The direction of data flow on an LSP 308 segment with respect to the head of the 309 LSP. 311 Where an LSP is signaled using a 312 conventional signaling protocol, the 'head' 313 of the LSP is the source of the signaling 314 (also known as the ingress) and the 'tail' 315 is the destination (also known as the 316 egress). 318 For manually configured LSPs an arbitrary 319 decision must be made about which LER is 320 the 'head'." 321 SYNTAX INTEGER { 322 forward(1), 323 reverse(2) 324 } 326 GmplsTrapEnable ::= TEXTUAL-CONVENTION 327 STATUS current 328 DESCRIPTION 329 "Controls whether a specific notification 330 (or set of notifications is generated, and 331 if so how. 332 If set to diabled (0), the notifications 333 are not emitted. If set to oneAtATime (1), 334 each notification may only carry 335 information about an event for a single 336 object. If set to rangeAllowed (2), each 337 notification MAY carry information an 338 identical event for a set of objects that 339 have contiguous indexing, but note that 340 implementations may send multiple 341 individual notifications even when 342 rangeAllowed is selected." 344 SYNTAX INTEGER { 345 disabled (0), 346 oneAtATime (1), 347 rangeAllowed (2) 348 } 350 END 352 5. Security Considerations 354 This memo defines textual conventions and object 355 identities for use in GMPLS MIB modules. Security issues 356 for these MIB modules are addressed in the memos defining 357 those modules. 359 6. References 361 6.1. Normative References 363 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and 364 J. Davin, "Simple Network Management 365 Protocol", RFC 1157, May 1990. 367 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB 368 Definitions", RFC 1212, March 1991. 370 [RFC2119] Bradner, S., "Key words for use in RFCs to 371 Indicate Requirement Levels", BCP 14, RFC 372 2119, March 1997. 374 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, 375 J., Case, J., Rose, M., and S. Waldbusser, 376 "Textual Conventions for SMIv2", STD 58, 377 RFC 2579, April 1999. 379 [RFC2863] McCloghrie, K. and F. Kastenholtz, "The 380 Interfaces Group MIB", RFC 2863, June 2000. 382 [GMPLSArch] Ashwood-Smith, P., Awduche, D., Banerjee, 383 A., Basak, D, Berger, L., Bernstein, G., 384 Drake, J., Fan, Y., Fedyk, D., Grammel, D., 385 Kompella, K., Kullberg, A., Lang, J., Liaw, 386 F., Papadimitriou, D., Pendarakis, D., 387 Rajagopalan, B., Rekhter, Y., Saha, D., 388 Sandick, H., Sharma, V., Swallow, G., Tang, 389 Z., Yu, J., Zinin, A., Nadeau, T., Mannie, 390 E., Generalized Multiprotocol Label 391 Switching (GMPLS) Architecture, Internet 392 Draft , March 2001, work in progress. 395 [RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., 396 Srinivasan, V., and G. Swallow, "RSVP-TE: 397 Extensions to RSVP for LSP Tunnels", 398 RFC3209, December 2001. 400 [CRLDP] Jamoussi, B., Aboul-Magd, O., Andersson, 401 L., Ashwood-Smith, P., Hellstrand, F., 402 Sundell, K., Callon, R., Dantu, R., Wu, L., 403 Doolan, P., Worster, T., Feldman, N., 404 Fredette, A., Girish, M., Gray, E., 405 Halpern, J., Heinanen, J., Kilty, T., 406 Malis, A., and P. Vaananen, "Constraint- 407 Based LSP Setup using LDP", draft-ietf-mpls- 408 cr-ldp-05.txt, February 2001, work in 409 progress. 411 [GMPLSSig] Ashwood-Smith, P., Awduche, D., Banerjee, 412 A., Basak, D, Berger, L., Bernstein, G., 413 Drake, J., Fan, Y., Fedyk, D., Grammel, D., 414 Kompella, K., Kullberg, A., Lang, 415 Rajagopalan, B., Rekhter, Y., Saha, D., 416 Sharma, V., Swallow, G., Bo Tang, Z., 417 Generalized MPLS - Signaling Functional 418 Description, , May 2001, work in 420 progress. 422 [GMPLSCRLDP] Ashwood-Smith, P., Awduche, D., Banerjee, 423 A., Basak, D, Berger, L., Bernstein, G., 424 Drake, J., Fan, Y., Fedyk, D., Grammel, D., 425 Kompella, K., Kullberg, A., Lang, 426 Rajagopalan, B., Rekhter, Y., Saha, D., 427 Sharma, V., Swallow, G., Bo Tang, Z., 428 Generalized MPLS Signaling - CR-LDP 429 Extensions, Internet Draft , May 2001, work 431 in progress. 433 [GMPLSRSVPTE] Ashwood-Smith, P., Awduche, D., Banerjee, 434 A., Basak, D, Berger, L., Bernstein, G., 435 Drake, J., Fan, Y., Fedyk, D., Grammel, D., 436 Kompella, K., Kullberg, A., Lang, 437 Rajagopalan, B., Rekhter, Y., Saha, D., 438 Sharma, V., Swallow, G., Bo Tang, Z., 439 Generalized MPLS Signaling - RSVP-TE 440 Extensions, Internet Draft , May 2001, work 442 in progress. 444 [GMPLSSonetSDH] Mannie, E., Ansorge, S., Ashwood-Smith, 445 P., Banerjee, A., Berger, L., Bernstein, 446 G., Chiu, A., Drake, J., Fan, Y., Fontana, 447 M., Grammel, G., Heiles, J., Katukam, S., 448 Kompella, K., Lang, J. P., Liaw, F., Lin, 449 Z., Mack-Crane, B., Papadimitriou, D., 450 Pendarakis, D., Raftelis, M., Rajagopalan, 451 B., Rekhter, Y., Saha, D., Sharma, V., 452 Swallow, G., Bo Tang, Z., Varma, E., 453 Vissers, M., Xu, Y., GMPLS Extensions for 454 SONET and SDH Control, Internet Draft 455 , 456 May 2001, work in progress. 458 6.2. Informational References 460 [RFC1155] Rose, M., and K. McCloghrie, "Structure and 461 Identification of Management Information 462 for TCP/IP-based Internets", RFC 1155, May 463 1990. 465 [RFC1213] McCloghrie, K, and M. Rose, "Management 466 Information Base for Network Management of 467 TCP/IP Based Internets", RFC 1213, March 468 1991. 470 [RFC1215] M. Rose, "A Convention for Defining Traps 471 for use with the SNMP", RFC 1215, March 472 1991. 474 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. 475 Waldbusser, "Introduction to Community- 476 based SNMPv2", RFC 1901, January 1996. 478 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. 479 Waldbusser, "Protocol Operations for 480 Version 2 of the Simple Network Management 481 Protocol (SNMPv2)", RFC 1905, January 1996. 483 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. 484 Waldbusser, "Transport Mappings for Version 485 2 of the Simple Network Management Protocol 486 (SNMPv2)", RFC 1906, January 1996. 488 [RFC2514] Noto, et. al., "Definitions of Textual 489 Conventions and OBJECT-IDENTITIES for ATM 490 Management", RFC 2514, Feb. 1999 492 [RFC2570] Case, J., Mundy, R., Partain, D., and B. 493 Stewart, "Introduction to Version 3 of the 494 Internet-standard Network Management 495 Framework", RFC 2570, April 1999. 497 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, 498 "An Architecture for Describing SNMP 499 Management Frameworks", RFC 2571, April 500 1999. 502 [RFC2572] Case, J., Harrington D., Presuhn R., and B. 503 Wijnen, "Message Processing and Dispatching 504 for the Simple Network Management Protocol 505 (SNMP)", RFC 2572, April 1999. 507 [RFC2573] Levi, D., Meyer, P., and B. Stewart, 508 "SNMPv3 Applications", RFC 2573, April 509 1999. 511 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based 512 Security Model (USM) for version 3 of the 513 Simple Network Management Protocol 514 (SNMPv3)", RFC 2574, April 1999. 516 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, 517 "View-based Access Control Model (VACM) for 518 the Simple Network Management Protocol 519 (SNMP)", RFC 2575, April 1999. 521 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, 522 J., Case, J., Rose, M., and S. Waldbusser, 523 "Structure of Management Information 524 Version 2 (SMIv2)", STD 58, RFC 2578, April 525 1999. 527 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, 528 J., Case, J., Rose, M., and S. Waldbusser, 529 "Conformance Statements for SMIv2", STD 58, 530 RFC 2580, April 1999. 532 [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, 533 "Multiprotocol Label Switching 534 Architecture", RFC 3031, August 1999. 536 [RFC3032] Rosen, E., Rekhter, Y., Tappan, D., 537 Farinacci, D., Federokow, G., Li, T., and 538 A. Conta, "MPLS Label Stack Encoding", RFC 539 3032, January 2001. 541 [RFC3034] Conta, A., Doolan, P., Malis, A., "Use of 542 Label Switching on Frame Relay Networks 543 Specification", RFC 3034, January 2001. 545 [RFC3035] Davie, B., Lawrence, J., McCloghrie, K., 546 Rosen, E., Swallow, G., Rekhter, Y., and P. 547 Doolan, "MPLS using LDP and ATM VC 548 switching", RFC 3035, January 2001. 550 [RFC3036] Anderson, L., Doolan, P., Feldman, N., 551 Fredette, A., and B. Thomas, "LDP 552 Specification", RFC 3036, January 2001. 554 [TCMIB] Nadeau, T., Cucchiara, J., Srinivasan, C, 555 Viswanathan, A. and H. Sjostrand, 556 "Definition of Textual Conventions and 557 OBJECT-IDENTITIES for Multiprotocol Label 558 Switching (MPLS) Management", Internet 559 Draft , 560 January 2002, work in progress. 562 [LABELMIB] Nadeau, T., Srinivasan, C., Farrel, A., 563 Hall, T., and Harrison, E., "Generalized 564 Multiprotocol Label Switching (GMPLS) Label 565 Management Information Base", draft-nadeau- 566 ccamp-gmpls-label-mib-01.txt, January 2002, 567 work in progress. 569 [GMPLSTEMIB] Nadeau, T., Srinivasan, C., Farrel, A., 570 Hall, T., and Harrison, E., "Extensions to 571 the MPLS Traffic Engineering Management 572 Information Base in Support of Generalized 573 Multiprotocol Label Switching", draft- 574 nadeau-ccamp-gmpls-te-mib-01.txt, January 575 2002, work in progress. 577 [GMPLSLSRMIB] Nadeau, T., Srinivasan, C., Farrel, A., 578 Hall, T., and Harrison, E., "GMPLS Label 579 Switching Router Management Information 580 Base Using SMIv2", draft-nadeau-ccamp-gmpls- 581 lsr-mib-01.txt, January 2002, work in 582 progress. 584 7. Authors' Addresses 586 Thomas D. Nadeau 587 Cisco Systems, Inc. 588 300 Apollo Drive 589 Chelmsford, MA 01824 590 Phone: +1-978-244-3051 591 Email: tnadeau@cisco.com 593 Cheenu Srinivasan 594 Parama Networks, Inc. 595 1030 Broad Street 596 Shrewsbury, NJ 07702 597 Phone: +1-732-544-9120 x731 598 Email: cheenu@paramanet.com 600 Adrian Farrel 601 Movaz Networks, Inc. 602 7926 Jones Branch Drive, Suite 615 603 McLean VA, 22102USA 604 Phone: +1-703-847-9847 605 Email: afarrel@movaz.com 607 Tim Hall 608 Data Connection Ltd. 609 100 Church Street 610 Enfield, Middlesex 611 EN2 6BQ, UK 612 Phone: +44 20 8366 1177 613 Email: timhall@dataconnection.com 615 Edward Harrison 616 Data Connection Ltd. 617 100 Church Street 618 Enfield, Middlesex 619 EN2 6BQ, UK 620 Phone: +44 20 8366 1177 621 Email: eph@dataconnection.com 623 8. Full Copyright Statement 625 Copyright (C) The Internet Society (2002). All Rights 626 Reserved. 628 This document and translations of it may be copied and 629 furnished to others, and derivative works that comment on 630 or otherwise explain it or assist in its implementation 631 may be prepared, copied, published and distributed, in 632 whole or in part, without restriction of any kind, 633 provided that the above copyright notice and this 634 paragraph are included on all such copies and derivative 635 works. However, this document itself may not be modified 636 in any way, such as by removing the copyright notice or 637 references to the Internet Society or other Internet 638 organizations, except as needed for the purpose of 639 developing Internet standards in which case the 640 procedures for copyrights defined in the Internet 641 Standards process must be followed, or as required to 642 translate it into languages other than English. 644 The limited permissions granted above are perpetual and 645 will not be revoked by the Internet Society or its 646 successors or assigns. This document and the information 647 contained herein is provided on an "AS IS" basis and THE 648 INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE 649 DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 650 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 651 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY 652 IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A 653 PARTICULAR PURPOSE.