Definitions of Textual Conventions for Generalized Multiprotocol Label Switching (GMPLS) Management
Extracted elements (10)
For manually configured bidirectional LSPs, the designation of which LER is the 'head' is explicitly described as an arbitrary decision, acknowledging that there is no signaling-derived head-end in such configurations.
GmplsFreeformLabelTC exists to handle label types not defined in any RFC and to serve systems that prefer a single generic label representation over type-specific syntaxes, providing a universal fallback encoding.
The GMPLS TC MIB is defined as a supplement to RFC 3811 (MPLS TC MIB) rather than a replacement. RFC 3811 can continue to be used alone in networks that support only MPLS, while GMPLS-specific networks import both.
The GMPLS TC MIB module is rooted under mplsStdMIB and imports from MPLS-TC-STD-MIB (RFC 3811), establishing a dependency such that any SNMP agent implementing this module must also support RFC 3811.
New OID assignments under the mplsStdMIB subtree for GMPLS-related standards-track MIB modules can only be made via a Standards Action as specified in RFC 2434.
GmplsFreeformLabelTC is a textual convention for representing any GMPLS label as an OCTET STRING of 0 to 64 bytes. It is used for labels whose types are not defined in any RFCs, or by systems that prefer not to use type-specific syntaxes.
GmplsLabelTypeTC defines an enumerated textual convention that determines how a GMPLS label object should be interpreted. Six types are defined: gmplsMplsLabel(1), gmplsPortWavelengthLabel(2), gmplsFreeformGeneralizedLabel(3), gmplsSonetLabel(4), gmplsSdhLabel(5), and gmplsWavebandLabel(6).
GmplsSegmentDirectionTC defines the direction of data flow on an LSP segment relative to the LSP head. Values are forward(1) (data flows from head-end toward tail-end) and reverse(2) (data flows from tail-end toward head-end).
IANA assigned OID 12 under mplsStdMIB (1.3.6.1.2.1.10.166) to the GMPLS-TC-STD-MIB module. Future GMPLS-related standards-track MIB modules should be rooted under this mplsStdMIB subtree, with new assignments requiring a Standards Action per RFC 2434.
This MIB module defines only textual conventions and no management objects. Because no objects are defined, there is no direct security impact on the Internet; security considerations apply to the MIB modules that import and use these TCs to define actual management objects.