--- 1/draft-ietf-mpls-tp-te-mib-08.txt 2014-09-22 22:14:35.710657931 -0700 +++ 2/draft-ietf-mpls-tp-te-mib-09.txt 2014-09-22 22:14:35.806660305 -0700 @@ -1,25 +1,25 @@ Network Working Group INTERNET-DRAFT M.Venkatesan Intended Status: Standards Track Dell Inc. -Expires: November 7, 2014 Kannan KV Sampath +Expires: March 26, 2015 Kannan KV Sampath Redeem Sam K. Aldrin Huawei Technologies Thomas D. Nadeau Brocade - May 6, 2014 + September 22, 2014 MPLS-TP Traffic Engineering (TE) Management Information Base (MIB) - draft-ietf-mpls-tp-te-mib-08.txt + draft-ietf-mpls-tp-te-mib-09.txt Abstract This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes additional managed objects of Tunnels, Identifiers, Label Switching Router and Textual conventions to support Multiprotocol Label Switching (MPLS) MIB modules for transport networks. @@ -37,21 +37,21 @@ 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. - This Internet-Draft will expire on November 7, 2014. + This Internet-Draft will expire on March 26, 2015. Copyright and License Notice Copyright (c) 2014 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -72,69 +72,69 @@ 5. Feature List . . . . . . . . . . . . . . . . . . . . . . . . . 6 6. Brief description of MIB modules . . . . . . . . . . . . . . . 7 6.1. mplsTunnelExtNodeConfigTable . . . . . . . . . . . . . . . 7 6.2. mplsTunnelExtNodeIpMapTable . . . . . . . . . . . . . . . . 8 6.3. mplsTunnelExtNodeIccMapTable . . . . . . . . . . . . . . . 8 6.4. mplsTunnelExtTable . . . . . . . . . . . . . . . . . . . . 9 6.5 MPLS-TC-EXT-STD-MIB . . . . . . . . . . . . . . . . . . . . 9 6.6 MPLS-ID-STD-MIB . . . . . . . . . . . . . . . . . . . . . . 9 6.7 MPLS-LSR-EXT-STD-MIB . . . . . . . . . . . . . . . . . . . . 9 7. MIB Module Interdependencies . . . . . . . . . . . . . . . . . 9 - 8. Dependencies between MIB Module Tables . . . . . . . . . . . . 10 - 9. Example of MPLS-TP Tunnel Setup . . . . . . . . . . . . . . . . 11 + 8. Dependencies between MIB Module Tables . . . . . . . . . . . . 11 + 9. Example of MPLS-TP Tunnel Setup . . . . . . . . . . . . . . . . 12 9.1. Example of MPLS-TP static co-routed bidirectional tunnel - setup . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 - 9.1.1. mplsTunnelEntry . . . . . . . . . . . . . . . . . . . . 13 - 9.1.2. mplsTunnelExtEntry . . . . . . . . . . . . . . . . . . 13 - 9.1.3. Forward direction mplsOutSegmentEntry . . . . . . . . . 14 - 9.1.4. Reverse direction mplsInSegmentEntry . . . . . . . . . 14 - 9.1.5. Forward direction mplsXCEntry . . . . . . . . . . . . . 15 - 9.1.6. Reverse direction mplsXCEntry . . . . . . . . . . . . . 15 - 9.1.7. Forward direction mplsXCExtEntry . . . . . . . . . . . 15 - 9.1.8. Reverse direction mplsXCExtEntry . . . . . . . . . . . 15 + setup . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 + 9.1.1. mplsTunnelEntry . . . . . . . . . . . . . . . . . . . . 14 + 9.1.2. mplsTunnelExtEntry . . . . . . . . . . . . . . . . . . 14 + 9.1.3. Forward direction mplsOutSegmentEntry . . . . . . . . . 15 + 9.1.4. Reverse direction mplsInSegmentEntry . . . . . . . . . 15 + 9.1.5. Forward direction mplsXCEntry . . . . . . . . . . . . . 16 + 9.1.6. Reverse direction mplsXCEntry . . . . . . . . . . . . . 16 + 9.1.7. Forward direction mplsXCExtEntry . . . . . . . . . . . 16 + 9.1.8. Reverse direction mplsXCExtEntry . . . . . . . . . . . 16 9.2. Example of MPLS-TP static associated bidirectional tunnel - setup . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 - 9.2.1. Forward direction mplsTunnelEntry . . . . . . . . . . . 16 - 9.2.2. Forward direction mplsTunnelExtEntry . . . . . . . . . 17 - 9.2.3. Forward direction mplsOutSegmentTable . . . . . . . . . 17 - 9.2.4. Forward direction mplsXCEntry . . . . . . . . . . . . . 17 - 9.2.5. Forward direction mplsXCExtEntry . . . . . . . . . . . 18 - 9.2.6. Reverse direction mplsTunnelEntry . . . . . . . . . . . 18 - 9.2.7. Reverse direction mplsTunnelExtEntry . . . . . . . . . 19 - 9.2.8. Reverse direction mplsInSegmentEntry . . . . . . . . . 19 - 9.2.9. Reverse direction mplsXCEntry . . . . . . . . . . . . . 19 - 9.2.10. Reverse direction mplsXCExtEntry . . . . . . . . . . . 20 + setup . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 + 9.2.1. Forward direction mplsTunnelEntry . . . . . . . . . . . 17 + 9.2.2. Forward direction mplsTunnelExtEntry . . . . . . . . . 18 + 9.2.3. Forward direction mplsOutSegmentTable . . . . . . . . . 18 + 9.2.4. Forward direction mplsXCEntry . . . . . . . . . . . . . 18 + 9.2.5. Forward direction mplsXCExtEntry . . . . . . . . . . . 19 + 9.2.6. Reverse direction mplsTunnelEntry . . . . . . . . . . . 19 + 9.2.7. Reverse direction mplsTunnelExtEntry . . . . . . . . . 20 + 9.2.8. Reverse direction mplsInSegmentEntry . . . . . . . . . 20 + 9.2.9. Reverse direction mplsXCEntry . . . . . . . . . . . . . 20 + 9.2.10. Reverse direction mplsXCExtEntry . . . . . . . . . . . 21 9.3. Example of MPLS-TP signaled co-routed bidirectional - tunnel setup . . . . . . . . . . . . . . . . . . . . . . . 20 - 9.3.1. mplsTunnelEntry . . . . . . . . . . . . . . . . . . . . 20 - 9.3.2. mplsTunnelExtEntry . . . . . . . . . . . . . . . . . . 21 - 9.3.3. Forward direction mplsOutSegmentEntry . . . . . . . . . 22 - 9.3.4. Reverse direction mplsInSegmentEntry . . . . . . . . . 22 - 9.3.5. Forward direction mplsXCEntry . . . . . . . . . . . . . 22 - 9.3.6. Reverse direction mplsXCEntry . . . . . . . . . . . . . 22 - 9.3.7. Forward direction mplsXCExtEntry . . . . . . . . . . . 22 - 9.3.8. Reverse direction mplsXCExtEntry . . . . . . . . . . . 22 - 10. MPLS Textual Convention Extension MIB definitions . . . . . . 22 - 11. MPLS Identifier MIB definitions . . . . . . . . . . . . . . . 25 - 12. MPLS LSR Extension MIB definitions . . . . . . . . . . . . . . 30 - 13. MPLS Tunnel Extension MIB definitions . . . . . . . . . . . . 35 - 14. Security Consideration . . . . . . . . . . . . . . . . . . . . 53 - 15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 54 - 15.1. IANA Considerations for MPLS-TC-EXT-STD-MIB . . . . . . . 54 - 15.2. IANA Considerations for MPLS-ID-STD-MIB . . . . . . . . . 54 - 15.3. IANA Considerations for MPLS-LSR-EXT-STD-MIB . . . . . . . 54 - 15.4. IANA Considerations for MPLS-TE-EXT-STD-MIB . . . . . . . 55 - 16. References . . . . . . . . . . . . . . . . . . . . . . . . . . 55 - 16.1. Normative References . . . . . . . . . . . . . . . . . . . 55 - 16.2. Informative References . . . . . . . . . . . . . . . . . 55 - 17. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 56 - 18. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 56 + tunnel setup . . . . . . . . . . . . . . . . . . . . . . . 21 + 9.3.1. mplsTunnelEntry . . . . . . . . . . . . . . . . . . . . 21 + 9.3.2. mplsTunnelExtEntry . . . . . . . . . . . . . . . . . . 22 + 9.3.3. Forward direction mplsOutSegmentEntry . . . . . . . . . 23 + 9.3.4. Reverse direction mplsInSegmentEntry . . . . . . . . . 23 + 9.3.5. Forward direction mplsXCEntry . . . . . . . . . . . . . 23 + 9.3.6. Reverse direction mplsXCEntry . . . . . . . . . . . . . 23 + 9.3.7. Forward direction mplsXCExtEntry . . . . . . . . . . . 23 + 9.3.8. Reverse direction mplsXCExtEntry . . . . . . . . . . . 23 + 10. MPLS Textual Convention Extension MIB definitions . . . . . . 23 + 11. MPLS Identifier MIB definitions . . . . . . . . . . . . . . . 26 + 12. MPLS LSR Extension MIB definitions . . . . . . . . . . . . . . 31 + 13. MPLS Tunnel Extension MIB definitions . . . . . . . . . . . . 36 + 14. Security Consideration . . . . . . . . . . . . . . . . . . . . 54 + 15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 55 + 15.1. IANA Considerations for MPLS-TC-EXT-STD-MIB . . . . . . . 55 + 15.2. IANA Considerations for MPLS-ID-STD-MIB . . . . . . . . . 55 + 15.3. IANA Considerations for MPLS-LSR-EXT-STD-MIB . . . . . . . 55 + 15.4. IANA Considerations for MPLS-TE-EXT-STD-MIB . . . . . . . 56 + 16. References . . . . . . . . . . . . . . . . . . . . . . . . . . 56 + 16.1. Normative References . . . . . . . . . . . . . . . . . . . 56 + 16.2. Informative References . . . . . . . . . . . . . . . . . 56 + 17. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 57 + 18. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 57 1. 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 describes additional managed objects of Tunnels, Identifiers, Label Switching Router and Textual conventions to support Multiprotocol Label Switching (MPLS) MIB modules for transport networks. MIB modules defined in this document extends the existing MPLS MIB objects in such a way that they support MPLS-TP and Non-MPLS-TP networks @@ -278,43 +278,43 @@ The mplsTunnelExtNodeConfigTable is used to assign a local identifier for a given ICC_Operator_ID::Node_ID or Global_ID::Node_ID combination as defined in [RFC6923] and [RFC6370] respectively. The CC is a string of two alphabetic characters represented with upper case letters (i.e., A-Z). The ICC is a string of one to six characters, each character being either alphabetic (i.e. A-Z) or numeric (i.e. 0-9) characters. Alphabetic characters in the ICC should be represented with upper case letters. In the IP compatible mode, Global_ID::Node_ID, is used to uniquely identify a node. For each ICC_Operator_ID::Node_ID or Global_ID::Node_ID, there is a - unique entry in the table representing a node. Every node is assigned - a local identifier within a range of 0 to 16777215. This local - identifier is used for indexing into mplsTunnelTable as + unique entry in the table representing a node. As the regular TE + tunnels use IP address as LSR ID, the local identifier should be + below the first valid IP address, which is 16777216[1.0.0.0]. Every + node is assigned a local identifier within a range of 0 to 16777215. + This local identifier is used for indexing into mplsTunnelTable as mplsTunnelIngressLSRId and mplsTunnelEgressLSRId. For IP compatible environment, MPLS-TP tunnel is indexed by Tunnel Index, Tunnel Instance, Source Global_ID, Source Node_ID, Destination Global_ID and Destination Node_ID. For ICC based environment, MPLS-TP tunnel is indexed by Tunnel Index, Tunnel Instance, Source CC, Source ICC, Source Node_ID, Destination CC, Destination ICC and Destination Node_ID. As mplsTunnelTable is indexed by mplsTunnelIndex, mplsTunnelInstance, mplsTunnelIngressLSRId, and mplsTunnelEgressLSRId, the MPLS-TP tunnel identifiers cannot be used directly. The mplsTunnelExtNodeConfigTable will be used to store an entry for ICC_Operator_ID::Node_ID or Global_ID::Node_ID with a local - identifier to be used as LSR ID in mplsTunnelTable. As the regular TE - tunnels use IP address as LSR ID, the local identifier should be - below the first valid IP address, which is 16777216[1.0.0.0]. + identifier to be used as LSR ID in mplsTunnelTable. 6.2. mplsTunnelExtNodeIpMapTable The read-only mplsTunnelExtNodeIpMapTable is used to query the local identifier assigned and stored in mplsTunnelExtNodeConfigTable for a given Global_ID::Node_ID. In order to query the local identifier, in the IP compatible mode, this table is indexed with Global_ID::Node_ID. In the IP compatible mode for a TP tunnel, Global_ID::Node_ID is used. @@ -334,20 +334,25 @@ while indexing mplsTunnelTable. 6.4. mplsTunnelExtTable This table sparsely extends the mplsTunnelTable in order to support MPLS-TP tunnels with additional objects. All the additional attributes specific to supporting TP tunnel are contained in this extended table and could be accessed with the mplsTunnelTable indices. + The gmplsTunnelReversePerfTable [RFC4802] should be used to provide + per-tunnel packet performance information for the reverse direction + of a bidirectional tunnel. It can be seen as supplementing the + mplsTunnelPerfTable, which augments the mplsTunnelTable. + 6.5 MPLS-TC-EXT-STD-MIB This MIB module contains Textual Conventions for LSPs of MPLS based transport networks. 6.6 MPLS-ID-STD-MIB This MIB module contains generic object definitions for MPLS Traffic Engineering in transport networks. @@ -1486,21 +1491,22 @@ ::= { mplsXCExtEntry 1 } mplsXCExtOppositeDirXCPtr OBJECT-TYPE SYNTAX RowPointer MAX-ACCESS read-create STATUS current DESCRIPTION "This object indicates the pointer to the opposite direction XC entry. This object cannot be modified if mplsXCRowStatus for the corresponding entry in the - mplsXCTable is active(1)." + mplsXCTable is active(1). If this pointer is not set or + removed, mplsXCOperStatus should be set to down(2)." REFERENCE "1. Multiprotocol Label Switching (MPLS) Label Switching Router (LSR) Management Information Base (MIB), RFC 3813." ::= { mplsXCExtEntry 2 } mplsLsrExtCompliances OBJECT IDENTIFIER ::= { mplsLsrExtConformance 1 } mplsLsrExtGroups OBJECT IDENTIFIER ::= { mplsLsrExtConformance 2 }