-- extracted from draft-ietf-ccamp-gmpls-tc-mib-10.txt -- at Wed Apr 12 06:06:18 2006 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 "200604060001Z" -- 06 April 2006 00:00:01 GMT ORGANIZATION "IETF 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 (2006). This version of this MIB module is part of RFC XXX; see the RFC itself for full legal notices. -- RFC Editor. Please replace XXX above with the correct RFC number and -- remove this note. This MIB module defines TEXTUAL-CONVENTIONs for concepts used in Generalized Multiprotocol Label Switching (GMPLS) networks." REVISION "200604060001Z" -- 06 April 2006 00:00:01 GMT DESCRIPTION -- RFC Editor: Please see the IANA Considerations Section. draft-ietf-ccamp-gmpls-tc-mib-10.txt April 11, 2006 -- This MIB module is contained in the OID sub-tree -- rooted at mplsStdMIB. "Initial version published as part of RFC XXX." ::= { mplsStdMIB XXX } -- RFC Editor. Please replace XXX above with the correct RFC number and -- remove this note. -- RFC Editor. Please replace YYY above with the OID assigned by IANA -- and remove this note GmplsFreeformLabelTC ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "This Textual Convention can be used as the syntax of an object that contains any GMPLS label. Objects with this syntax can be used to represent labels that have label types that are not defined in any RFCs. The freeform GMPLS Label may also be used by systems that do not wish to represent labels that have label types defined in RFCs using type-specific syntaxes." REFERENCE "1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling Functional Description, RFC 3471, section 3.2." SYNTAX OCTET STRING (SIZE (0..64)) GmplsLabelTypeTC ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "Determines the interpretation that should be applied to an object that encodes a label. The possible types are: gmplsMplsLabel(1) - The label is an MPLS packet, cell, or frame label and is encoded as described for the Textual Convention MplsLabel defined in RFC 3811. gmplsPortWavelengthLabel(2) - The label is a port or wavelength label as defined in RFC 3471. gmplsFreeformLabel(3) - The label is any form of label encoded as an OCTET STRING using the Textual Convention GmplsFreeformLabel. gmplsSonetLabel(4) - The label is a SONET label as defined in RFC 3946. draft-ietf-ccamp-gmpls-tc-mib-10.txt April 11, 2006 gmplsSdhLabel(5) - The label is an SDH label as defined in RFC 3946. gmplsWavebandLabel(6) - The label is a waveband label as defined in RFC 3471." REFERENCE "1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling Functional Description, RFC 3471, section 3. 2. Definition of Textual Conventions and for Multiprotocol Label Switching (MPLS) Management, RFC 3811, section 3. 3. Generalized Multi-Protocol Label Switching (GMPLS) Extensions for Synchronous Optical Network (SONET) and Synchronous Digital Hierarchy (SDH) Control, RFC 3946, section 3." SYNTAX INTEGER { gmplsMplsLabel(1), gmplsPortWavelengthLabel(2), gmplsFreeformGeneralizedLabel(3), gmplsSonetLabel(4), gmplsSdhLabel(5), gmplsWavebandLabel(6) } GmplsSegmentDirectionTC ::= 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'." SYNTAX INTEGER { forward(1), -- data flows from head-end of LSP toward tail-end reverse(2) -- data flows from tail-end of LSP toward head-end } END -- -- Copyright (C) The Internet Society (2006). 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, -- 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.