Network Working Group Thomas D. Nadeau Internet Draft Cisco Systems, Inc. Expires: December 2002 Cheenu Srinivasan Parama Networks, Inc. Adrian Farrel Movaz Networks, Inc. Edward Harrison Tim Hall Data Connection Ltd. June 2002 Definition of Textual Conventions and OBJECT-IDENTITIES for Generalized Multiprotocol Label Switching (GMPLS) Management draft-ietf-ccamp-gmpls-tc-mib-00.txt Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC 2026 [RFC2026]. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet- Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. Abstract This memo describes Textual Conventions and OBJECT- IDENTITIES common to the Management Information Bases (MIBs) for managing Generalized Multiprotocol Label Switching (GMPLS) networks. It supplements [TCMIB] which describes Textual Conventions and OBJECT-IDENTITIES common to the Management Information Bases (MIBs) for managing Multiprotocol Label Switching (MPLS) networks. Nadeau, et al. [Page 1 ] draft-ietf-ccamp-gmpls-tc-mib-00.txt June 2002 Table of Contents 1. Changes and Pending Work 2 1.1. Changes Since the Last Version 2 1.2. Pending Work 2 2. Introduction 2 3. The SNMP Management Framework 3 4. GMPLS TC MIB Definitions 4 5. Security Considerations 6 6. References 7 6.1. Normative References 7 6.2. Informational References 7 7. Authors' Addresses 10 8. Full Copyright Statement 11 1. Changes and Pending Work This section must be removed before the draft progresses to RFC. 1.1. Changes Since the Last Version This is the first version of this draft. 1.2. Pending Work - Update reference to latest versions of drafts. - Check compilation of MIB. 2. Introduction This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines Textual Conventions used in IETF GMPLS and GMPLS-related MIBs. This document supplements [TCMIB] that defines Textual Conventions and OBJECT-IDENTITIES for Multiprotocol Label Switching (MPLS) Management. [TCMIB] may continue to be used without this MIB in networks that support only MPLS. Comments should be made directly to the CCAMP mailing list at ccamp@ops.ietf.org. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be Nadeau, et al. [Page 2 ] draft-ietf-ccamp-gmpls-tc-mib-00.txt June 2002 interpreted as described in RFC 2119, reference [RFC2119]. For an introduction to the concepts of GMPLS, see [GMPLSArch]. 3. The SNMP Management Framework The SNMP Management Framework presently consists of five major components: - An overall architecture, described in RFC 2571 [RFC2571]. - Mechanisms for describing and naming objects and events for the purpose of management. The first version of this Structure of Management Information (SMI) is called SMIv1 and described in STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and STD 16, RFC 1215 [RFC1215]. The second version, called SMIv2, is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580]. - Message protocols for transferring management information. The first version of the SNMP message protocol is called SNMPv1 and described in STD 15, RFC 1157 [RFC1157]. A second version of the SNMP message protocol, which is not an Internet standards track protocol, is called SNMPv2c and described in RFC 1901 [RFC1901] and RFC 1906 [RFC1906]. The third version of the message protocol is called SNMPv3 and described in RFC 1906 [RFC1906], RFC 2572 [RFC2572] and RFC 2574 [RFC2574]. - Protocol operations for accessing management information. The first set of protocol operations and associated PDU formats is described in STD 15, RFC 1157 [RFC1157]. A second set of protocol operations and associated PDU formats is described in RFC 1905 [RFC1905]. - A set of fundamental applications described in RFC 2573 [RFC2573] and the view-based access control mechanism described in RFC 2575 [RFC2575]. A more detailed introduction to the current SNMP Management Framework can be found in RFC 2570 [RFC2570]. Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. Objects in the MIB are defined using the mechanisms defined in the SMI. This memo specifies a MIB module that is compliant to the SMIv2. A MIB conforming to the SMIv1 can be produced Nadeau, et al. [Page 3 ] draft-ietf-ccamp-gmpls-tc-mib-00.txt June 2002 through the appropriate translations. The resulting translated MIB must be semantically equivalent, except where objects or events are omitted because no translation is possible (use of Counter64). Some machine readable information in SMIv2 will be converted into textual descriptions in SMIv1 during the translation process. However, this loss of machine readable information is not considered to change the semantics of the MIB. 4. GMPLS TC MIB Definitions GMPLS-TC-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, Unsigned32, Integer32 FROM SNMPv2-SMI TEXTUAL-CONVENTION FROM SNMPv2-TC ; gmplsTCMIB MODULE-IDENTITY LAST-UPDATED "200224060900Z" -- 24 June 2002 9:00:00 GMT ORGANIZATION "Common Control And Management Protocols (CCAMP) Working Group" CONTACT-INFO " Thomas D. Nadeau Postal: Cisco Systems, Inc. 250 Apollo Drive Chelmsford, MA 01824 Tel: +1-978-244-3051 Email: tnadeau@cisco.com Cheenu Srinivasan Postal: Parama Networks, Inc. 1030 Broad Street Shrewsbury, NJ 07702 Tel: +1-732-544-9120 x731 Email: cheenu@paramanet.com Tel: +1-732-544-9120x731 Adrian Farrel Postal: Movaz Networks, Inc. 7926 Jones Branch Drive McLean, VA 22102 Tel: +1-703-847-1867 Email: afarrel@movaz.com Edward Harrison Postal: Data Connection Ltd. 100 Church Street Enfield, Middlesex EN2 6BQ, United Kingdom Nadeau, et al. [Page 4 ] draft-ietf-ccamp-gmpls-tc-mib-00.txt June 2002 Tel: +44-20-8366-1177 Email: eph@dataconnection.com Tim Hall Postal: Data Connection Ltd. 100 Church Street Enfield, Middlesex EN2 6BQ, United Kingdom Tel: +44-20-8366-1177 Email: timhall@dataconnection.com Email comments to the CCAMP WG Mailing List at ccamp@ops.ietf.org." DESCRIPTION "This MIB module defines Textual Conventions and OBJECT-IDENTITIES for use in documents defining management information bases (MIBs) for managing GMPLS networks." -- Revision history. REVISION "200224060900Z" -- 24 June 2002 09:00:00 GMT DESCRIPTION "Initial version." -- Above revision history to be replaced as below. -- REVISION -- "yyyymmddhhmmZ"-- DESCRIPTION "Initial version, published as RFC xxxx" -- xxxx to be assigned by RFC Editor ::= { gmplsMIB 1 } -- This object identifier needs to be assigned by IANA. -- Note that MPLS has been assigned an ifType of 166 and that an OID -- of 166 has been suggested for the MPLS MIBs. gmplsMIB OBJECT IDENTIFIER ::= { transmission xxx } -- Textual Conventions (sorted alphabetically). GmplsFreeformLabel ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "This value represents a freeform generalized MPLS Label. This can be used to represent label types which are not standard in the drafts." SYNTAX OCTET STRING (SIZE (0..64)) GmplsGeneralizedLabelSubtypes ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "Determines the interpretation that should be applied to a label given its label type as specified by GmplsGeneralizedLabelTypes." SYNTAX INTEGER { mplsLabel(1), Nadeau, et al. [Page 5 ] draft-ietf-ccamp-gmpls-tc-mib-00.txt June 2002 portWavelengthLabel(2), freeformGeneralizedLabel(3), sonetLabel(4), sdhLabel(5), wavebandLabel(6) } GmplsGeneralizedLabelTypes ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "The label types that are defined for Generalized MPLS." SYNTAX INTEGER { mplsLabel(1), generalizedLabel(2) } GmplsHopUnnumAddrTypes ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "Identifies whether a hop of an explicit or reported route uses unnumbered addresses and, if so, the type of unnumbered address." SYNTAX INTEGER { numbered(1), unnumberedIfIpV4(2), unnumberedIfIpV6(3) } GmplsSegmentDirection ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "The direction of data flow on an LSP segment with respect to the head of the LSP. Where an LSP is signaled using a conventional signaling protocol, the 'head' of the LSP is the source of the signaling (also known as the ingress) and the 'tail' is the destination (also known as the egress). For manually configured LSPs an arbitrary decision must be made about which LER is the 'head'." SYNTAX INTEGER { forward(1), reverse(2) } END Nadeau, et al. [Page 6 ] draft-ietf-ccamp-gmpls-tc-mib-00.txt June 2002 5. Security Considerations This memo defines textual conventions and object identities for use in GMPLS MIB modules. Security issues for these MIB modules are addressed in the memos defining those modules. 6. References 6.1. Normative References [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network Management Protocol", RFC 1157, May 1990. [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 1212, March 1991. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999. [RFC2863] McCloghrie, K. and F. Kastenholtz, "The Interfaces Group MIB", RFC 2863, June 2000. [GMPLSArch] Ashwood-Smith, P., Awduche, D., Banerjee, A., Basak, D, Berger, L., Bernstein, G., Drake, J., Fan, Y., Fedyk, D., Grammel, D., Kompella, K., Kullberg, A., Lang, J., Liaw, F., Papadimitriou, D., Pendarakis, D., Rajagopalan, B., Rekhter, Y., Saha, D., Sandick, H., Sharma, V., Swallow, G., Tang, Z., Yu, J., Zinin, A., Nadeau, T., Mannie, E., Generalized Multiprotocol Label Switching (GMPLS) Architecture, Internet Draft , March 2001, work in progress. 6.2. Informational References [RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification of Management Information for TCP/IP-based Internets", RFC 1155, May 1990. [RFC1213] McCloghrie, K, and M. Rose, "Management Information Base for Network Management of TCP/IP Based Internets", RFC 1213, March Nadeau, et al. [Page 7 ] draft-ietf-ccamp-gmpls-tc-mib-00.txt June 2002 1991. [RFC1215] M. Rose, "A Convention for Defining Traps for use with the SNMP", RFC 1215, March 1991. [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Introduction to Community- based SNMPv2", RFC 1901, January 1996. [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol Operations for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1905, January 1996. [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport Mappings for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1906, January 1996. [RFC2514] Noto, et. al., "Definitions of Textual Conventions and OBJECT-IDENTITIES for ATM Management", RFC 2514, Feb. 1999 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction to Version 3 of the Internet-standard Network Management Framework", RFC 2570, April 1999. [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for Describing SNMP Management Frameworks", RFC 2571, April 1999. [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message Processing and Dispatching for the Simple Network Management Protocol (SNMP)", RFC 2572, April 1999. [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC 2573, April 1999. [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 2574, April 1999. [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)", RFC 2575, April 1999. [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., and S. Waldbusser, "Structure of Management Information Nadeau, et al. [Page 8 ] draft-ietf-ccamp-gmpls-tc-mib-00.txt June 2002 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999. [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol Label Switching Architecture", RFC 3031, August 1999. [RFC3032] Rosen, E., Rekhter, Y., Tappan, D., Farinacci, D., Federokow, G., Li, T., and A. Conta, "MPLS Label Stack Encoding", RFC 3032, January 2001. [RFC3034] Conta, A., Doolan, P., Malis, A., "Use of Label Switching on Frame Relay Networks Specification", RFC 3034, January 2001. [RFC3035] Davie, B., Lawrence, J., McCloghrie, K., Rosen, E., Swallow, G., Rekhter, Y., and P. Doolan, "MPLS using LDP and ATM VC switching", RFC 3035, January 2001. [RFC3036] Anderson, L., Doolan, P., Feldman, N., Fredette, A., and B. Thomas, "LDP Specification", RFC 3036, January 2001. [RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V., and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP Tunnels", RFC3209, December 2001. [CRLDP] Jamoussi, B., Aboul-Magd, O., Andersson, L., Ashwood-Smith, P., Hellstrand, F., Sundell, K., Callon, R., Dantu, R., Wu, L., Doolan, P., Worster, T., Feldman, N., Fredette, A., Girish, M., Gray, E., Halpern, J., Heinanen, J., Kilty, T., Malis, A., and P. Vaananen, "Constraint- Based LSP Setup using LDP", draft-ietf-mpls- cr-ldp-05.txt, February 2001, work in progress. [GMPLSSig] Ashwood-Smith, P., Awduche, D., Banerjee, A., Basak, D, Berger, L., Bernstein, G., Drake, J., Fan, Y., Fedyk, D., Grammel, D., Kompella, K., Kullberg, A., Lang, Rajagopalan, B., Rekhter, Y., Saha, D., Sharma, V., Swallow, G., Bo Tang, Z., Generalized MPLS - Signaling Functional Description, , May 2001, work in progress. Nadeau, et al. [Page 9 ] draft-ietf-ccamp-gmpls-tc-mib-00.txt June 2002 [GMPLSCRLDP] Ashwood-Smith, P., Awduche, D., Banerjee, A., Basak, D, Berger, L., Bernstein, G., Drake, J., Fan, Y., Fedyk, D., Grammel, D., Kompella, K., Kullberg, A., Lang, Rajagopalan, B., Rekhter, Y., Saha, D., Sharma, V., Swallow, G., Bo Tang, Z., Generalized MPLS Signaling - CR-LDP Extensions, Internet Draft , May 2001, work in progress. [GMPLSRSVPTE] Ashwood-Smith, P., Awduche, D., Banerjee, A., Basak, D, Berger, L., Bernstein, G., Drake, J., Fan, Y., Fedyk, D., Grammel, D., Kompella, K., Kullberg, A., Lang, Rajagopalan, B., Rekhter, Y., Saha, D., Sharma, V., Swallow, G., Bo Tang, Z., Generalized MPLS Signaling - RSVP-TE Extensions, Internet Draft , May 2001, work in progress. [GMPLSSonetSDH] Mannie, E., Ansorge, S., Ashwood-Smith, P., Banerjee, A., Berger, L., Bernstein, G., Chiu, A., Drake, J., Fan, Y., Fontana, M., Grammel, G., Heiles, J., Katukam, S., Kompella, K., Lang, J. P., Liaw, F., Lin, Z., Mack-Crane, B., Papadimitriou, D., Pendarakis, D., Raftelis, M., Rajagopalan, B., Rekhter, Y., Saha, D., Sharma, V., Swallow, G., Bo Tang, Z., Varma, E., Vissers, M., Xu, Y., GMPLS Extensions for SONET and SDH Control, Internet Draft , May 2001, work in progress. [TCMIB] Nadeau, T., Cucchiara, J., Srinivasan, C, Viswanathan, A. and H. Sjostrand, "Definition of Textual Conventions and OBJECT-IDENTITIES for Multiprotocol Label Switching (MPLS) Management", Internet Draft , January 2002, work in progress. [GMPLSTEMIB] Nadeau, T., Srinivasan, C., Farrel, A., Hall, T., and Harrison, E., "Extensions to the MPLS Traffic Engineering Management Information Base in Support of Generalized Multiprotocol Label Switching", draft- nadeau-ccamp-gmpls-te-mib-01.txt, January 2002, work in progress. 7. Authors' Addresses Nadeau, et al. [Page 10] draft-ietf-ccamp-gmpls-tc-mib-00.txt June 2002 Thomas D. Nadeau Cisco Systems, Inc. 300 Apollo Drive Chelmsford, MA 01824 Phone: +1-978-244-3051 Email: tnadeau@cisco.com Cheenu Srinivasan Parama Networks, Inc. 1030 Broad Street Shrewsbury, NJ 07702 Phone: +1-732-544-9120 x731 Email: cheenu@paramanet.com Adrian Farrel Movaz Networks, Inc. 7926 Jones Branch Drive, Suite 615 McLean VA, 22102USA Phone: +1-703-847-1867 Email: afarrel@movaz.com Tim Hall Data Connection Ltd. 100 Church Street Enfield, Middlesex EN2 6BQ, UK Phone: +44 20 8366 1177 Email: timhall@dataconnection.com Edward Harrison Data Connection Ltd. 100 Church Street Enfield, Middlesex EN2 6BQ, UK Phone: +44 20 8366 1177 Email: eph@dataconnection.com 8. Full Copyright Statement Copyright (C) The Internet Society (2002). All Rights Reserved. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the Nadeau, et al. [Page 11] draft-ietf-ccamp-gmpls-tc-mib-00.txt June 2002 procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English. The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns. This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Nadeau, et al. [Page 12]