Network Working Group Thomas D. Nadeau, Ed. Internet Draft Cisco Systems, Inc. Proposed Status: Standards Track Expires: April 2005 Adrian Farrel, Ed. Old Dog Consulting October 2004 Definitions of Textual Conventions for Generalized Multiprotocol Label Switching (GMPLS) Management draft-ietf-ccamp-gmpls-tc-mib-06.txt Status of this Memo By submitting this Internet-Draft, I certify that any applicable patent or other IPR claims of which I am aware have been disclosed, and any of which I become aware will be disclosed, in accordance with RFC 3668. 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. Abstract This document defines a Management Information Base (MIB) module which contains Textual Conventions to represent commonly used Generalized Multiprotocol Label Switching (GMPLS) management information. The intent is that these TEXTUAL CONVENTIONS (TCs) will be imported and used in GMPLS related MIB modules that would otherwise define their own representations. Nadeau and Farrel (Editors) [Page 1] Internet Draft draft-ietf-ccamp-gmpls-tc-mib-06.txt October 2004 Table of Contents 1. Introduction ................................... 2 2. The SNMP Management Framework .................. 2 3. GMPLS Textual Conventions MIB Definitions ...... 3 4. Security Considerations ........................ 5 5. IANA Considerations ............................ 5 6. References ..................................... 5 6.1. Normative References ......................... 5 6.2. Informational References ..................... 6 7. Acknowledgments ................................ 7 8. Authors' Addresses ............................. 7 9. Intellectual Property Notice ................... 9 10. Full Copyright Statement ..................... 10 1. Introduction This document defines a MIB module which contains Textual Conventions for Generalized Multiprotocol Label Switching (GMPLS) networks. These Textual Conventions should be imported by MIB modules which manage GMPLS networks. This MIB module supplements the MIB module in [RFC3811] that defines Textual Conventions for Multiprotocol Label Switching (MPLS) Management. [RFC3811] may continue to be used without this MIB module 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 interpreted as described in BCP 14, RFC 2119, reference [RFC2119]. For an introduction to the concepts of GMPLS, see [GMPLSArch]. 2. The Internet-Standard Management Framework For a detailed overview of the documents that describe the current Internet-Standard Management Framework, please refer to section 7 of RFC 3410 [RFC3410]. Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. MIB objects are generally accessed through the Simple Network Management Protocol (SNMP). Objects in the MIB are defined using the mechanisms defined in the Structure of Management Information (SMI). This memo specifies a MIB module that is compliant to the SMIv2, which is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580]. Nadeau and Farrel (Editors) [Page 2] Internet Draft draft-ietf-ccamp-gmpls-tc-mib-06.txt October 2004 3. GMPLS Textual Conventions MIB Definitions GMPLS-TC-STD-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY FROM SNMPv2-SMI -- [RFC2578] TEXTUAL-CONVENTION FROM SNMPv2-TC -- [RFC2579] mplsStdMIB FROM MPLS-TC-STD-MIB -- [RFC3811] ; gmplsTCStdMIB MODULE-IDENTITY LAST-UPDATED "200410080001Z" -- 8 October 2004 00:00:01 GMT ORGANIZATION "Common Control And Measurement Plane (CCAMP) Working Group" CONTACT-INFO " Thomas D. Nadeau Cisco Systems, Inc. Email: tnadeau@cisco.com Adrian Farrel Old Dog Consulting Email: adrian@olddog.co.uk Comments about this document should be emailed direct to the CCAMP working group mailing list at ccamp@ops.ietf.org" DESCRIPTION "Copyright (C) The Internet Society (2004). The initial version of this MIB module was published in RFC xxxx. For full legal notices see the RFC itself or see: http://www.ietf.org/copyrights/ianamib.html This MIB module defines TEXTUAL-CONVENTIONs for concepts used in Generalized Multiprotocol Label Switching (GMPLS) networks." -- Revision history. REVISION "200410080001Z" -- 8 October 2004 00:00:01 GMT DESCRIPTION "Initial version published as part of RFC XXXX." -- Please see the IANA Considerations Section. -- This MIB module is contained in the OID sub-tree -- rooted at mplsStdMIB. -- The requested mplsStdMIB subId is xx, i.e. ::= { mplsStdMIB xx } Nadeau and Farrel (Editors) [Page 3] Internet Draft draft-ietf-ccamp-gmpls-tc-mib-06.txt October 2004 -- 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. It may also be used by systems that do not wish to represent the labels using the specific label types." REFERENCE "Generalized Multi-Protocol Label Switching (GMPLS) Signaling Functional Description, RFC 3471." SYNTAX OCTET STRING (SIZE (0..64)) GmplsGeneralizedLabelTypes ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "Determines the interpretation that should be applied to a label." REFERENCE "Generalized Multi-Protocol Label Switching (GMPLS) Signaling Functional Description, RFC 3471." SYNTAX INTEGER { gmplsMplsLabel(1), gmplsPortWavelengthLabel(2), gmplsFreeformGeneralizedLabel(3), gmplsSonetLabel(4), gmplsSdhLabel(5), gmplsWavebandLabel(6) } 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 unidirectional LSPs, this usually matches the direction of flow of data. For manually configured unidirectional LSPs the direction of the LSP segment matches the direction of flow of data. For manually configured bidirecitonal LSPs, an arbitrary decision must be made about which LER is the 'head'." Nadeau and Farrel (Editors) [Page 4] Internet Draft draft-ietf-ccamp-gmpls-tc-mib-06.txt October 2004 SYNTAX INTEGER { forward(1), reverse(2) } END 4. Security Considerations This module does not define any management objects. Instead, it defines a set of textual conventions which may be used by other MPLS MIB modules to define management objects. Meaningful security considerations can only be written in the MIB modules that define management objects. Therefore, this document has no impact on the security of the Internet. 5. IANA Considerations IANA is requested to root MIB objects in this MIB module under the mplsStdMIB subtree by assigning an OID to gmplsTCStdMIB. In the future, GMPLS related standards track MIB modules should be rooted under the mplsStdMIB (sic) subtree. IANA has been requested to manage that namespace. New assignments can only be made via a Standards Action as specified in [RFC2434]. The IANA has assigned { mplsStdMIB 1 } to the MPLS-TC-STD-MIB. 6. References 6.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 2579, 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. Nadeau and Farrel (Editors) [Page 5] Internet Draft draft-ietf-ccamp-gmpls-tc-mib-06.txt October 2004 [RFC3471] Berger, L. (Editor), "Generalized Multi-Protocol Label Switching (GMPLS) Signaling Functional Description", RFC 3471, January 2003. 6.2. Informational References [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP: 26, RFC 2434, October 1998. [RFC3031] Rosen, E., Viswananthan, A., and R. Callon, Multiprotocol Label Switching Architecture", RFC 3031, January 2001. [RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V., Swallow, G., "RSVP-TE: Extensions to RSVP for LSP Tunnels", RFC 3209, December 2001. [RFC3212] Jamoussi, B., (editor), et. al. "Constraint-Based LSP Setup using LDP", RFC 3212, January 2002. [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, "Introduction and Applicability Statements for Internet-Standard Management Framework", RFC 3410, December 2002. [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for Describing Simple Network Management Protocol (SNMP) Management Frameworks", STD 62, RFC 3411, December 2002. [RFC3472] Ashwood-Smith, P., Berger, L. (Editors), "Generalized MPLS Signaling - CR-LDP Extensions", RFC 3472, January 2003. [RFC3473] Berger, L. (Editor), "Generalized MPLS Signaling - RSVP-TE Extensions", RFC 3473 January 2003. [RFC3811] Nadeau, T. and J. Cucchiara, "Definition of Textual Conventions and for Multiprotocol Label Switching (MPLS) Management", RFC 3811, June 2004. [GMPLSSonetSDH] Mannie, E., Papadimitriou, D. (Editors), "Generalized Multi-Protocol Label Switching Extensions for SONET and SDH Control", Internet Draft , February 2003, work in progress. Nadeau and Farrel (Editors) [Page 6] Internet Draft draft-ietf-ccamp-gmpls-tc-mib-06.txt October 2004 [GMPLSLSRMIB] Nadeau, T., Farrel, A. (Editors) "Generalized Multiprotocol Label Switching (GMPLS) Label Switching Router (LSR) Management Information Base", draft-ietf-ccamp-gmpls-lsr-mib-06.txt, October 2004, work in progress. [GMPLSTEMIB] Nadeau, T., Farrel, A. (Editors) "Generalized Multiprotocol Label Switching (GMPLS) Traffic Engineering Management Information Base", draft-ietf-ccamp-gmpls-te-mib-06.txt, October 2004, work in progress. [GMPLSArch] Mannie, E. (Editor), "Generalized Multiprotocol Label Switching (GMPLS) Architecture", Internet Draft , May 2003, work in progress. 7. Acknowledgements This draft is the work of the five authors listed in the next section. Special thanks to Joan Cucchiara for her help with compilation issues. 8. Authors' Addresses Thomas D. Nadeau Cisco Systems, Inc. 300 Apollo Drive Chelmsford, MA 01824 Phone: +1-978-244-3051 Email: tnadeau@cisco.com Cheenu Srinivasan Bloomberg L.P. 499 Park Ave., New York, NY 10022 Phone: +1-212-893-3682 Email: cheenu@bloomberg.net Adrian Farrel Old Dog Consulting Phone: +44 1978 860944 Email: adrian@olddog.co.uk Nadeau and Farrel (Editors) [Page 7] Internet Draft draft-ietf-ccamp-gmpls-tc-mib-06.txt October 2004 Tim Hall Data Connection Ltd. 100 Church Street Enfield, Middlesex EN2 6BQ, UK Phone: +44 20 8366 1177 Email: tim.hall@dataconnection.com Ed Harrison Data Connection Ltd. 100 Church Street Enfield, Middlesex EN2 6BQ, UK Phone: +44 20 8366 1177 Email: ed.harrison@dataconnection.com 9. Intellectual Property Considerations The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79. Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org. 10. Full Copyright Statement Copyright (C) The Internet Society (2004). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, Nadeau and Farrel (Editors) [Page 8] Internet Draft draft-ietf-ccamp-gmpls-tc-mib-06.txt October 2004 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 and Farrel (Editors) [Page 9]