rfc-6825

Traffic Engineering Database Management Information Base in Support of MPLS-TE/GMPLS

M. Miyazawa, T. Otani, K. Kumaki, T. Nadeau
date2013-01 streamIETF areartg wgccamp statusPROPOSED STANDARD pages40 canonicalhttps://www.rfc-editor.org/rfc/rfc6825 doi10.17487/RFC6825
This memo defines the Management Information Base (MIB) objects for managing the Traffic Engineering Database (TED) information with extensions in support of the Multiprotocol Label Switching (MPLS) with Traffic Engineering (TE) as well as Generalized MPLS (GMPLS) for use with network management protocols. [STANDARDS-TRACK]

Extracted elements (25)

design-rationale §2

The TED MIB module is designed to be independent of OSPF or IS-IS MIBs, enabling a management system to understand MPLS/GMPLS topology information using only this module when full routing protocol MIB support is unavailable.

mpls, routing, snmp

design-rationale §6

The TED MIB module is limited to read-only access for all objects except the two notification rate-limiting objects. This reflects the intent that TED is a passive topology database populated by routing protocols, not a configuration interface.

mpls, snmp

design-rationale §5

The tedLocalIfAddrTable, tedRemoteIfAddrTable, tedSwCapTable, and tedSrlgTable are defined as separate tables (rather than columns in tedTable) because their corresponding sub-TLVs may appear multiple times within the same Link-TLV, requiring a one-to-many relationship.

mpls, snmp

interoperability-note §6

When the TED MIB is used in a pure MPLS network (not GMPLS), GMPLS-specific tables (tedLocalIfAddrTable, tedRemoteIfAddrTable, tedSwCapTable, tedSrlgTable) are not supported. The module is intended for use alongside OSPFv2 MIB, OSPFv3 MIB, IS-IS MIB, RFC 3812, RFC 3813, RFC 4802, and RFC 4803 MIBs.

mpls, snmp, routing

normative-requirement §8 NOT RECOMMENDED

Deployment of SNMP versions prior to SNMPv3 is NOT RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to enable cryptographic security.

security, snmp

normative-requirement §7 MUST

If tedLinkInformationSource has the value unknown(0), the object tedLinkInformationData MUST contain a value of zeroDotZero.

mpls, snmp

normative-requirement §8 MUST

Implementations MUST provide the security features described by the SNMPv3 framework, including full support for authentication and privacy via the User-based Security Model (USM) with the AES cipher algorithm.

security, snmp, crypto

protocol-element §7

TedAreaIdTC is a textual convention (OCTET STRING, SIZE 0..20) representing the IGP area identifier: an ospfArea for OSPF or an area address for IS-IS.

mpls, routing, snmp

protocol-element §7

TedLinkIndexTC is a textual convention (OCTET STRING, SIZE 0..8) representing the link state identifier: ospfLsdbID for OSPF, isisLSPID for IS-IS, or an arbitrary locally-defined value for locally configured links.

mpls, routing, snmp

protocol-element §7

tedLinkInformationSource identifies the origin of TE link information with values: unknown(0), locallyConfigured(1), ospfv2(2), ospfv3(3), isis(4), or other(5). This field is a non-accessible index in tedTable.

mpls, routing, snmp

protocol-element §7

tedLinkProtectionType is a BITS object indicating the protection type of the TE link, with bit positions: extraTraffic(0), unprotected(1), shared(2), dedicatedOneToOne(3), dedicatedOnePlusOne(4), and enhanced(5). Referenced from RFC 4203 Section 1.2 and RFC 5307 Section 1.2.

mpls, snmp

protocol-element §7

TedRouterIdTC is a textual convention (OCTET STRING, SIZE 0..6) representing the router identifier: a Router ID for OSPF or a System ID for IS-IS.

mpls, routing, snmp

protocol-element §7

tedStatusChangeNotificationMaxRate and tedCreatedDeletedNotificationMaxRate are read-write Unsigned32 objects controlling the maximum number of respective notifications generated per minute, with a default value of 1. A value of 0 means no throttling.

mpls, snmp

protocol-element §7

tedSwCapIndication indicates whether the TE link interface supports Standard (0) or Arbitrary (1) SONET/SDH, as defined in RFC 4203 Section 1.4 and RFC 5307 Section 1.3.

mpls, snmp

protocol-element §7

tedSwCapMinLspBandwidth indicates the minimum bandwidth of the TE link for GMPLS LSP creation when the switching capability field is TDM, PSC-1, PSC-2, PSC-3, or PSC-4.

mpls, snmp

protocol-element §7

tedUnreservedBandwidthPri0 through tedUnreservedBandwidthPri7 are Float32TC objects (in bytes per second) representing the unreserved bandwidth at each of the 8 priority levels (0–7) on a TE link, as defined by RFC 3630 Section 2.5.8 and RFC 5305 Section 3.6.

mpls, snmp

protocol-element §5.2

The tedLocalIfAddrTable contains Local Interface IP Address information corresponding to the Local Interface IP Address sub-TLV of the Link-TLV. It is defined independently because the sub-TLV may appear more than once within the same Link-TLV.

mpls, snmp

protocol-element §5.3

The tedRemoteIfAddrTable contains Remote Interface IP Address information corresponding to the Remote Interface IP Address sub-TLV of the Link-TLV. It is independently defined because the sub-TLV may appear more than once within the same Link-TLV.

mpls, snmp

protocol-element §5.5

The tedSrlgTable contains Shared Risk Link Group (SRLG) values associated with each TE link, indexed by tedLinkIndex and tedSrlgIndex. It is independently defined because the SRLG sub-TLV may appear more than once within the same Link-TLV.

mpls, snmp

protocol-element §5.4

The tedSwCapTable contains GMPLS Interface Switching Capability Descriptor information per TE link, including switching type, encoding type, maximum and minimum LSP bandwidth per priority, MTU, and SONET/SDH indication. It is indexed by tedLinkIndex and tedSwCapIndex.

mpls, snmp

protocol-element §5.1

The tedTable is the core TED MIB table providing TE link information sourced from OSPFv2, OSPFv3, IS-IS, or local configuration. It is indexed by tedLocalRouterId, tedRemoteRouterId, tedLinkInformationSource, and tedLinkIndex, and contains bandwidth, metric, administrative group, and protection type fields.

mpls, routing, snmp, yang

protocol-element §7

Three notifications are defined: tedStatusChange (TE information changed), tedEntryCreated (new TED entry registered), and tedEntryDeleted (existing TED entry removed). All carry tedLinkState as the varbind.

mpls, snmp

registry §9

IANA assigned the value 273 to the TED-MIB module in the 'Internet-standard MIB - Transmission Group' registry. New assignments can only be made via Specification Required (RFC 5226). Value 273 is also marked 'Reserved' in the 'ifType definitions' registry.

registry, snmp, mpls

security-consideration §8

Malicious modification of tedStatusChangeNotificationMaxRate or tedCreatedDeletedNotificationMaxRate could cause the management agent, network, or router to become overloaded with notifications during periods of high churn.

security, snmp

security-consideration §8

The tedTable, tedLocalIfAddrTable, tedRemoteIfAddrTable, tedSwCapTable, and tedSrlgTable contain MPLS/GMPLS network topology information and should be considered sensitive. GET and NOTIFY access should be controlled and values may need to be encrypted when transmitted via SNMP.

security, snmp, mpls