draft-ietf-mpls-tp-te-mib-10.txt   draft-ietf-mpls-tp-te-mib-11.txt 
Network Working Group Network Working Group
INTERNET-DRAFT M.Venkatesan INTERNET-DRAFT M.Venkatesan
Intended Status: Standards Track Dell Inc. Intended Status: Standards Track Dell Inc.
Expires: June 17, 2015 Kannan KV Sampath Expires: June 21, 2015 Kannan KV Sampath
Redeem Redeem
Sam K. Aldrin Sam K. Aldrin
Huawei Technologies Huawei Technologies
Thomas D. Nadeau Thomas D. Nadeau
Brocade Brocade
December 14, 2014 December 18, 2014
MPLS-TP Traffic Engineering (TE) Management Information Base (MIB) MPLS-TP Traffic Engineering (TE) Management Information Base (MIB)
draft-ietf-mpls-tp-te-mib-10.txt draft-ietf-mpls-tp-te-mib-11.txt
Abstract Abstract
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it describes additional managed objects and textual In particular, it describes additional managed objects and textual
conventions for Tunnels, Identifiers and Label Switching Router to conventions for Tunnels, Identifiers and Label Switching Router to
support Multiprotocol Label Switching (MPLS) MIB modules for support Multiprotocol Label Switching (MPLS) MIB modules for
transport networks. transport networks.
skipping to change at page 1, line 48 skipping to change at page 1, line 48
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on June 17, 2015. This Internet-Draft will expire on June 21, 2015.
Copyright and License Notice Copyright and License Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 26 skipping to change at page 2, line 26
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. The Internet-Standard Management Framework . . . . . . . . . . 5 2. The Internet-Standard Management Framework . . . . . . . . . . 5
3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.1. Conventions used in this document . . . . . . . . . . . . . 5 3.1. Conventions used in this document . . . . . . . . . . . . . 5
3.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . 5 3.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . 5
3.3. Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . 6 3.3. Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . 7
4. Motivations . . . . . . . . . . . . . . . . . . . . . . . . . . 6 4. Motivations . . . . . . . . . . . . . . . . . . . . . . . . . . 7
5. Feature List . . . . . . . . . . . . . . . . . . . . . . . . . 6 5. Feature List . . . . . . . . . . . . . . . . . . . . . . . . . 7
6. Outline . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 6. Outline . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
6.1 MIB Module Extensions . . . . . . . . . . . . . . . . . . . 8 6.1 MIB Module Extensions . . . . . . . . . . . . . . . . . . . 9
6.1.1 Summary of MIB Module changes . . . . . . . . . . . . . 8 6.1.1 Summary of MIB Module changes . . . . . . . . . . . . . 9
6.2 MPLS-TE-EXT-STD-MIB . . . . . . . . . . . . . . . . . . . . 9 6.2 MPLS-TE-EXT-STD-MIB . . . . . . . . . . . . . . . . . . . . 10
6.2.1 mplsTunnelExtNodeConfigTable . . . . . . . . . . . . . . 9 6.2.1 mplsTunnelExtNodeConfigTable . . . . . . . . . . . . . . 10
6.2.2 mplsTunnelExtNodeIpMapTable . . . . . . . . . . . . . . 10 6.2.2 mplsTunnelExtNodeIpMapTable . . . . . . . . . . . . . . 11
6.2.3 mplsTunnelExtNodeIccMapTable . . . . . . . . . . . . . . 10 6.2.3 mplsTunnelExtNodeIccMapTable . . . . . . . . . . . . . . 11
6.2.4 mplsTunnelExtTable . . . . . . . . . . . . . . . . . . . 10 6.2.4 mplsTunnelExtTable . . . . . . . . . . . . . . . . . . . 11
6.3 MPLS-TC-EXT-STD-MIB . . . . . . . . . . . . . . . . . . . . 10 6.3 MPLS-TC-EXT-STD-MIB . . . . . . . . . . . . . . . . . . . . 11
6.4 MPLS-ID-STD-MIB . . . . . . . . . . . . . . . . . . . . . . 10 6.4 MPLS-ID-STD-MIB . . . . . . . . . . . . . . . . . . . . . . 11
6.5 MPLS-LSR-EXT-STD-MIB . . . . . . . . . . . . . . . . . . . . 11 6.5 MPLS-LSR-EXT-STD-MIB . . . . . . . . . . . . . . . . . . . . 12
6.6 The Use of RowPointer . . . . . . . . . . . . . . . . . . . 11 6.6 The Use of RowPointer . . . . . . . . . . . . . . . . . . . 12
7. MIB Modules Interdependencies . . . . . . . . . . . . . . . . . 12 7. MIB Modules Interdependencies . . . . . . . . . . . . . . . . . 13
8. Dependencies between MIB Module Tables . . . . . . . . . . . . 13 8. Dependencies between MIB Module Tables . . . . . . . . . . . . 14
9. Example of MPLS-TP Tunnel Setup . . . . . . . . . . . . . . . . 14 9. Example of MPLS-TP Tunnel Setup . . . . . . . . . . . . . . . . 15
9.1. Example of MPLS-TP static co-routed bidirectional tunnel 9.1. Example of MPLS-TP static co-routed bidirectional tunnel
setup . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 setup . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
9.1.1. mplsTunnelEntry . . . . . . . . . . . . . . . . . . . . 15 9.1.1. mplsTunnelEntry . . . . . . . . . . . . . . . . . . . . 16
9.1.2. mplsTunnelExtEntry . . . . . . . . . . . . . . . . . . 16 9.1.2. mplsTunnelExtEntry . . . . . . . . . . . . . . . . . . 17
9.1.3. Forward direction mplsOutSegmentEntry . . . . . . . . . 16 9.1.3. Forward direction mplsOutSegmentEntry . . . . . . . . . 17
9.1.4. Reverse direction mplsInSegmentEntry . . . . . . . . . 16 9.1.4. Reverse direction mplsInSegmentEntry . . . . . . . . . 17
9.1.5. Forward direction mplsXCEntry . . . . . . . . . . . . . 17 9.1.5. Forward direction mplsXCEntry . . . . . . . . . . . . . 18
9.1.6. Reverse direction mplsXCEntry . . . . . . . . . . . . . 17 9.1.6. Reverse direction mplsXCEntry . . . . . . . . . . . . . 18
9.1.7. Forward direction mplsXCExtEntry . . . . . . . . . . . 18 9.1.7. Forward direction mplsXCExtEntry . . . . . . . . . . . 19
9.1.8. Reverse direction mplsXCExtEntry . . . . . . . . . . . 18 9.1.8. Reverse direction mplsXCExtEntry . . . . . . . . . . . 19
9.2. Example of MPLS-TP static associated bidirectional tunnel 9.2. Example of MPLS-TP static associated bidirectional tunnel
setup . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 setup . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
9.2.1. Forward direction mplsTunnelEntry . . . . . . . . . . . 18 9.2.1. Forward direction mplsTunnelEntry . . . . . . . . . . . 19
9.2.2. Forward direction mplsTunnelExtEntry . . . . . . . . . 19 9.2.2. Forward direction mplsTunnelExtEntry . . . . . . . . . 20
9.2.3. Forward direction mplsOutSegmentTable . . . . . . . . . 19 9.2.3. Forward direction mplsOutSegmentTable . . . . . . . . . 20
9.2.4. Forward direction mplsXCEntry . . . . . . . . . . . . . 20 9.2.4. Forward direction mplsXCEntry . . . . . . . . . . . . . 21
9.2.5. Forward direction mplsXCExtEntry . . . . . . . . . . . 20 9.2.5. Forward direction mplsXCExtEntry . . . . . . . . . . . 21
9.2.6. Reverse direction mplsTunnelEntry . . . . . . . . . . . 20 9.2.6. Reverse direction mplsTunnelEntry . . . . . . . . . . . 21
9.2.7. Reverse direction mplsTunnelExtEntry . . . . . . . . . 21 9.2.7. Reverse direction mplsTunnelExtEntry . . . . . . . . . 22
9.2.8. Reverse direction mplsInSegmentEntry . . . . . . . . . 21 9.2.8. Reverse direction mplsInSegmentEntry . . . . . . . . . 22
9.2.9. Reverse direction mplsXCEntry . . . . . . . . . . . . . 22 9.2.9. Reverse direction mplsXCEntry . . . . . . . . . . . . . 23
9.2.10. Reverse direction mplsXCExtEntry . . . . . . . . . . . 22 9.2.10. Reverse direction mplsXCExtEntry . . . . . . . . . . . 23
9.3. Example of MPLS-TP signaled co-routed bidirectional 9.3. Example of MPLS-TP signaled co-routed bidirectional
tunnel setup . . . . . . . . . . . . . . . . . . . . . . . 22 tunnel setup . . . . . . . . . . . . . . . . . . . . . . . 23
9.3.1. mplsTunnelEntry . . . . . . . . . . . . . . . . . . . . 23 9.3.1. mplsTunnelEntry . . . . . . . . . . . . . . . . . . . . 24
9.3.2. mplsTunnelExtEntry . . . . . . . . . . . . . . . . . . 23 9.3.2. mplsTunnelExtEntry . . . . . . . . . . . . . . . . . . 24
9.3.3. Forward direction mplsOutSegmentEntry . . . . . . . . . 24 9.3.3. Forward direction mplsOutSegmentEntry . . . . . . . . . 25
9.3.4. Reverse direction mplsInSegmentEntry . . . . . . . . . 24 9.3.4. Reverse direction mplsInSegmentEntry . . . . . . . . . 25
9.3.5. Forward direction mplsXCEntry . . . . . . . . . . . . . 24 9.3.5. Forward direction mplsXCEntry . . . . . . . . . . . . . 25
9.3.6. Reverse direction mplsXCEntry . . . . . . . . . . . . . 24 9.3.6. Reverse direction mplsXCEntry . . . . . . . . . . . . . 25
9.3.7. Forward direction mplsXCExtEntry . . . . . . . . . . . 24 9.3.7. Forward direction mplsXCExtEntry . . . . . . . . . . . 25
9.3.8. Reverse direction mplsXCExtEntry . . . . . . . . . . . 25 9.3.8. Reverse direction mplsXCExtEntry . . . . . . . . . . . 26
10. MPLS Textual Convention Extension MIB definitions . . . . . . 25 10. MPLS Textual Convention Extension MIB definitions . . . . . . 26
11. MPLS Identifier MIB definitions . . . . . . . . . . . . . . . 28 11. MPLS Identifier MIB definitions . . . . . . . . . . . . . . . 29
12. MPLS LSR Extension MIB definitions . . . . . . . . . . . . . . 32 12. MPLS LSR Extension MIB definitions . . . . . . . . . . . . . . 34
13. MPLS Tunnel Extension MIB definitions . . . . . . . . . . . . 38 13. MPLS Tunnel Extension MIB definitions . . . . . . . . . . . . 39
14. Security Consideration . . . . . . . . . . . . . . . . . . . . 55 14. Security Consideration . . . . . . . . . . . . . . . . . . . . 56
15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 56 15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 57
15.1. IANA Considerations for MPLS-TC-EXT-STD-MIB . . . . . . . 56 15.1. IANA Considerations for MPLS-TC-EXT-STD-MIB . . . . . . . 58
15.2. IANA Considerations for MPLS-ID-STD-MIB . . . . . . . . . 56 15.2. IANA Considerations for MPLS-ID-STD-MIB . . . . . . . . . 58
15.3. IANA Considerations for MPLS-LSR-EXT-STD-MIB . . . . . . . 56 15.3. IANA Considerations for MPLS-LSR-EXT-STD-MIB . . . . . . . 58
15.4. IANA Considerations for MPLS-TE-EXT-STD-MIB . . . . . . . 56 15.4. IANA Considerations for MPLS-TE-EXT-STD-MIB . . . . . . . 58
16. References . . . . . . . . . . . . . . . . . . . . . . . . . . 56 16. References . . . . . . . . . . . . . . . . . . . . . . . . . . 58
16.1. Normative References . . . . . . . . . . . . . . . . . . . 56 16.1. Normative References . . . . . . . . . . . . . . . . . . . 58
16.2. Informative References . . . . . . . . . . . . . . . . . 57 16.2. Informative References . . . . . . . . . . . . . . . . . 59
17. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 58 17. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 60
18. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 58 18. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 60
1. Introduction 1. Introduction
This memo defines a portion of the Management Information Base (MIB) for This memo defines a portion of the Management Information Base (MIB) for
use with network management protocols in the Internet community. In use with network management protocols in the Internet community. In
particular, it describes additional textual conventions and managed particular, it describes additional textual conventions and managed
objects for Tunnels, Identifiers and Label Switching Router to support objects for Tunnels, Identifiers and Label Switching Router to support
Multiprotocol Label Switching (MPLS) MIB modules for transport networks. Multiprotocol Label Switching (MPLS) MIB modules for transport networks.
MIB modules defined in this document extend the existing MPLS MIB MIB modules defined in this document extend the existing MPLS MIB
objects in such a way that they support MPLS-TP but also other MPLS objects in such a way that they support MPLS-TP but also other MPLS
skipping to change at page 5, line 41 skipping to change at page 5, line 41
MIB are defined using the mechanisms defined in the Structure of MIB are defined using the mechanisms defined in the Structure of
Management Information (SMI). This memo specifies a MIB module that is Management Information (SMI). This memo specifies a MIB module that is
compliant to the SMIv2, which is described in STD 58 [RFC2578], STD 58 compliant to the SMIv2, which is described in STD 58 [RFC2578], STD 58
[RFC2579] and STD 58 [RFC2580]. [RFC2579] and STD 58 [RFC2580].
3. Overview 3. Overview
3.1. Conventions used in this document 3.1. Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
document are to be interpreted as described in [RFC2119]. "OPTIONAL" in this document are to be interpreted as described in
[RFC2119].
3.2. Terminology 3.2. Terminology
This document uses terminology from the Multiprotocol Label Switching This document uses terminology from the Multiprotocol Label Switching
Architecture [RFC3031], Multiprotocol Label Switching (MPLS) Traffic Architecture [RFC3031], Multiprotocol Label Switching (MPLS) Traffic
Engineering (TE) Management Information Base (MIB) [RFC3812], Engineering (TE) Management Information Base (MIB) [RFC3812],
Multiprotocol Label Switching (MPLS) Label Switching Router (LSR) Multiprotocol Label Switching (MPLS) Label Switching Router (LSR)
Management Information Base (MIB) [RFC3813] and MPLS Transport Profile Management Information Base (MIB) [RFC3813] and MPLS Transport Profile
(MPLS-TP) Identifiers [RFC6370]. (MPLS-TP) Identifiers [RFC6370].
skipping to change at page 9, line 25 skipping to change at page 10, line 25
6.2 MPLS-TE-EXT-STD-MIB 6.2 MPLS-TE-EXT-STD-MIB
The TE MIB module extensions and details of the tables are described The TE MIB module extensions and details of the tables are described
in the following sections. in the following sections.
6.2.1 mplsTunnelExtNodeConfigTable 6.2.1 mplsTunnelExtNodeConfigTable
The mplsTunnelExtNodeConfigTable is used to assign a local identifier The mplsTunnelExtNodeConfigTable is used to assign a local identifier
for a given ICC_Operator_ID::Node_ID or Global_ID::Node_ID for a given ICC_Operator_ID::Node_ID or Global_ID::Node_ID
combination as defined in [RFC6923] and [RFC6370] respectively. The combination as defined in [RFC6923] and [RFC6370] respectively. The
CC is a string of two alphabetic characters represented with upper CC is a string of two characters, each being an uppercase Basic Latin
case letters (i.e., A-Z). The ICC is a string of one to six alphabetic (i.e., A-Z). The ICC is a string of one to six characters,
characters, each character being either alphabetic (i.e. A-Z) or each an upper case Basic Latin alphabetic (i.e., A-Z) or numeric
numeric (i.e. 0-9) characters. Alphabetic characters in the ICC (i.e., 0-9). All of the characters are encoded using [T.50] as
should be represented with upper case letters. In the IP compatible described in [RFC6370].
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 In the IP compatible mode, Global_ID::Node_ID, is used to uniquely
unique entry in the table representing a node. As the regular TE identify a node. For each ICC_Operator_ID::Node_ID or
tunnels use IP address as LSR ID, the local identifier should be Global_ID::Node_ID, there is a unique entry in the table representing
below the first valid IP address, which is 16777216[1.0.0.0]. Every a node. As the regular TE tunnels use IP address as LSR ID, the
node is assigned a local identifier within a range of 0 to 16777215. local identifier should be below the first valid IP address, which is
This local identifier is used for indexing into mplsTunnelTable as 16777216[1.0.0.0]. Every node is assigned a local identifier within a
mplsTunnelIngressLSRId and mplsTunnelEgressLSRId. 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 For IP compatible environment, MPLS-TP tunnel is indexed by Tunnel
Index, Tunnel Instance, Source Global_ID, Source Node_ID, Destination Index, Tunnel Instance, Source Global_ID, Source Node_ID, Destination
Global_ID and Destination Node_ID. Global_ID and Destination Node_ID.
For ICC based environment, MPLS-TP tunnel is indexed by Tunnel Index, For ICC based environment, MPLS-TP tunnel is indexed by Tunnel Index,
Tunnel Instance, Source CC, Source ICC, Source Node_ID, Destination Tunnel Instance, Source CC, Source ICC, Source Node_ID, Destination
CC, Destination ICC and Destination Node_ID. CC, Destination ICC and Destination Node_ID.
As mplsTunnelTable is indexed by mplsTunnelIndex, As mplsTunnelTable is indexed by mplsTunnelIndex,
skipping to change at page 25, line 32 skipping to change at page 26, line 32
FROM SNMPv2-TC -- [RFC2579] FROM SNMPv2-TC -- [RFC2579]
mplsStdMIB mplsStdMIB
FROM MPLS-TC-STD-MIB -- [RFC3811] FROM MPLS-TC-STD-MIB -- [RFC3811]
; ;
mplsTcExtStdMIB MODULE-IDENTITY mplsTcExtStdMIB MODULE-IDENTITY
LAST-UPDATED LAST-UPDATED
"201412120000Z" -- December 12, 2014 "201412180000Z" -- December 18, 2014
ORGANIZATION ORGANIZATION
"Multiprotocol Label Switching (MPLS) Working Group" "Multiprotocol Label Switching (MPLS) Working Group"
CONTACT-INFO CONTACT-INFO
" "
Venkatesan Mahalingam Venkatesan Mahalingam
Dell Inc, Dell Inc,
5450 Great America Parkway, 5450 Great America Parkway,
Santa Clara, CA 95054, USA Santa Clara, CA 95054, USA
Email: venkat.mahalingams@gmail.com Email: venkat.mahalingams@gmail.com
skipping to change at page 26, line 21 skipping to change at page 27, line 21
"Copyright (c) 2014 IETF Trust and the persons identified "Copyright (c) 2014 IETF Trust and the persons identified
as the document authors. All rights reserved. as the document authors. All rights reserved.
This MIB module contains Textual Conventions for LSPs of MPLS This MIB module contains Textual Conventions for LSPs of MPLS
based transport networks." based transport networks."
-- Revision history. -- Revision history.
REVISION REVISION
"201412120000Z" -- December 12, 2014 "201412180000Z" -- December 18, 2014
DESCRIPTION DESCRIPTION
"MPLS Textual Convention Extensions" "MPLS Textual Convention Extensions"
::= { mplsStdMIB www } -- www to be replaced with correct value ::= { mplsStdMIB www } -- www to be replaced with correct value
MplsGlobalId ::= TEXTUAL-CONVENTION MplsGlobalId ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the Textual Convention for IP based "This object contains the Textual Convention for IP based
operator unique identifier (Global_ID), the Global_ID can operator unique identifier (Global_ID), the Global_ID can
skipping to change at page 26, line 52 skipping to change at page 27, line 52
contained within a single operator and MUST NOT be used contained within a single operator and MUST NOT be used
across an Network-to-Network Interface (NNI). A non-zero across an Network-to-Network Interface (NNI). A non-zero
Global_ID MUST be derived from an ASN owned by Global_ID MUST be derived from an ASN owned by
the operator." the operator."
REFERENCE REFERENCE
"MPLS Transport Profile (MPLS-TP) Identifiers, [RFC6370] "MPLS Transport Profile (MPLS-TP) Identifiers, [RFC6370]
Section 3" Section 3"
SYNTAX OCTET STRING (SIZE (4)) SYNTAX OCTET STRING (SIZE (4))
MplsCcId ::= TEXTUAL-CONVENTION MplsCcId ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The CC (Country Code) is a string of two alphabetic "The CC (Country Code) is a string of two characters, each
characters represented with upper case being an uppercase Basic Latin alphabetic (i.e., A-Z).
letters (i.e., A-Z). The size of the CC string MUST be The characters are encoded using ITU-T Recommendation T.50.
zero if the CC identifier is invalid." The size of the CC string MUST be zero if the CC identifier
is invalid."
REFERENCE REFERENCE
"MPLS-TP Identifiers Following ITU-T Conventions, "MPLS-TP Identifiers Following ITU-T Conventions,
[RFC6923] Section 3" RFC 6923, Section 3.
SYNTAX OCTET STRING (SIZE (2)) International Reference Alphabet (IRA) (Formerly
International Alphabet No. 5 or IA5) - Information
technology - 7-bit coded character set for information
exchange, ITU-T Recommendation T.50, September 1992. "
SYNTAX OCTET STRING (SIZE (0|2))
MplsIccId ::= TEXTUAL-CONVENTION MplsIccId ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The ICC is a string of one to six characters, each "The ICC is a string of one to six characters, each
character being either alphabetic (i.e. A-Z) or an upper case Basic Latin alphabetic (i.e., A-Z) or
numeric (i.e. 0-9) characters. numeric (i.e., 0-9). The characters are encoded
Alphabetic characters in the ICC SHOULD be represented using ITU-T Recommendation T.50. The size of
with upper case letters. The size of the ICC string MUST the ICC string MUST be zero if the ICC identifier
be zero if the ICC identifier is invalid." is invalid."
REFERENCE REFERENCE
"MPLS-TP Identifiers Following ITU-T Conventions, "MPLS-TP Identifiers Following ITU-T Conventions,
[RFC6923] Section 3" RFC6923, Section 3.
International Reference Alphabet (IRA) (Formerly
International Alphabet No. 5 or IA5) - Information
technology - 7-bit coded character set for information
exchange, ITU-T Recommendation T.50, September 1992. "
SYNTAX OCTET STRING (SIZE (0|1..6)) SYNTAX OCTET STRING (SIZE (0|1..6))
MplsNodeId ::= TEXTUAL-CONVENTION MplsNodeId ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Node_ID is assigned within the scope of "The Node_ID is assigned within the scope of
the Global_ID/ICC_Operator_ID. the Global_ID/ICC_Operator_ID.
When IPv4 addresses are in use, the value of this object When IPv4 addresses are in use, the value of this object
skipping to change at page 30, line 13 skipping to change at page 31, line 24
If this value is used in mplsTunnelExtNodeConfigNodeId If this value is used in mplsTunnelExtNodeConfigNodeId
for mapping ICC_Operator_ID::Node_ID with the local for mapping ICC_Operator_ID::Node_ID with the local
identifier then this object value MUST NOT be changed." identifier then this object value MUST NOT be changed."
::= { mplsIdObjects 2 } ::= { mplsIdObjects 2 }
mplsIdCc OBJECT-TYPE mplsIdCc OBJECT-TYPE
SYNTAX MplsCcId SYNTAX MplsCcId
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object allows the operator or service provider to "This object allows the operator or service provider to
assign a Country Code (CC) to the node. Global assign a Country Code (CC) to the node. Global
uniqueness of ICC is assured by concatenating the ICC uniqueness of ICC is assured by concatenating the ICC
with a Country Code (CC). with a Country Code (CC).
If this value is used in mplsTunnelExtNodeConfigCcId If this value is used in mplsTunnelExtNodeConfigCcId
for mapping ICC_Operator_ID::Node_ID with the local for mapping ICC_Operator_ID::Node_ID with the local
identifier then this object value MUST NOT be changed." identifier then this object value MUST NOT be changed."
REFERENCE REFERENCE
"MPLS-TP Identifiers Following ITU-T Conventions, "MPLS-TP Identifiers Following ITU-T Conventions,
[RFC6923] Section 3" [RFC6923] Section 3"
::= { mplsIdObjects 3 } ::= { mplsIdObjects 3 }
mplsIdIcc OBJECT-TYPE mplsIdIcc OBJECT-TYPE
SYNTAX MplsIccId SYNTAX MplsIccId
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object allows the operator or service provider to "This object allows the operator or service provider to
assign a unique MPLS-TP ITU-T Carrier Code (ICC) to assign a unique MPLS-TP ITU-T Carrier Code (ICC) to
the node. Together, the CC and the ICC form the node. Together, the CC and the ICC form
the ICC_Operator_ID as CC::ICC. the ICC_Operator_ID as CC::ICC.
If this value is used in mplsTunnelExtNodeConfigIccId If this value is used in mplsTunnelExtNodeConfigIccId
for mapping ICC_Operator_ID::Node_ID with the local for mapping ICC_Operator_ID::Node_ID with the local
identifier then this object value MUST NOT be changed." identifier then this object value MUST NOT be changed."
REFERENCE REFERENCE
"MPLS-TP Identifiers Following ITU-T Conventions, "MPLS-TP Identifiers Following ITU-T Conventions,
[RFC6923] Section 3" [RFC6923] Section 3"
::= { mplsIdObjects 4 }
::= { mplsIdObjects 4 }
-- Module compliance. -- Module compliance.
mplsIdCompliances mplsIdCompliances
OBJECT IDENTIFIER ::= { mplsIdConformance 1 } OBJECT IDENTIFIER ::= { mplsIdConformance 1 }
mplsIdGroups mplsIdGroups
OBJECT IDENTIFIER ::= { mplsIdConformance 2 } OBJECT IDENTIFIER ::= { mplsIdConformance 2 }
-- Compliance requirement for fully compliant implementations. -- Compliance requirement for fully compliant implementations.
skipping to change at page 55, line 30 skipping to change at page 56, line 40
-- MPLS-TE-EXT-STD-MIB module ends -- MPLS-TE-EXT-STD-MIB module ends
END END
14. Security Consideration 14. Security Consideration
This document follows the security consideration mentioned in the This document follows the security consideration mentioned in the
section 12 of [RFC3812]. These security considerations are also section 12 of [RFC3812]. These security considerations are also
applicable to the MIB objects and tables defined in this draft, which applicable to the MIB objects and tables defined in this draft, which
are identified as below. are identified as below.
Security consideration for read-write and/or read-create objects is - The common objects mplsIdGlobalId, mplsIdNodeId, mplsIdCc, and
also applicable for mplsIdIcc are used to define the identity of an MPLS-TP node for
OAM purposes. If write-access is allowed to these objects it
offers the possibility for incorrect values to be entered that
will confuse the information returned by OAM functions and
possibly prevent OAM from operating correctly. Furthermore,
there is the possibility of inducing one node to impersonate
another with confusing results.
- mplsTunnelExtNodeConfigTable, mplsTunnelExtTable and - mplsTunnelExtNodeConfigTable, mplsTunnelExtTable and
mplsXCExtTable collectively contain objects to provision MPLS-TP mplsXCExtTable collectively contain objects to provision MPLS-TP
tunnels, tunnel hops, and tunnel resources. tunnels, tunnel hops, and tunnel resources.
Some of the readable objects in this MIB module (i.e., objects with a Some of the readable objects in this MIB module (i.e., objects with a
MAX-ACCESS other than not-accessible) may be considered sensitive or MAX-ACCESS other than not-accessible) may be considered sensitive or
vulnerable in some network environments. vulnerable in some network environments. It is thus important to
control even GET and/or NOTIFY access to these objects and possibly
to even encrypt the values of these objects when sending them over
the network via SNMP. These are the tables and objects and their
sensitivity/vulnerability:
- mplsTunnelExtNodeConfigTable, mplsTunnelExtTable, - mplsTunnelExtNodeConfigTable, mplsTunnelExtTable,
and mplsXCExtTable collectively show the MPLS-TP tunnel network and mplsXCExtTable collectively show the MPLS-TP tunnel network
topology characteristics. If an Administrator does not want to topology characteristics. If an Administrator does not want to
reveal this information, then these tables should be considered reveal this information, then these tables should be considered
sensitive/vulnerable. sensitive/vulnerable.
When MIB is used to configure ICC_Operator_ID, as specified in SNMP versions prior to SNMPv3 did not include adequate security. Even
[RFC6370], it should be considered sensitive operation. Hence proper if the network itself is secure (for example by using IPsec), there
protection should be taken to allow configuration via SET operation is no control as to who on the secure network is allowed to access
in order to ensure its purpose of providing globally unique MPLS-TP and GET/SET (read/change/create/delete) the objects in this MIB
identifiers. module.
Implementations SHOULD provide the security features described by the
SNMPv3 framework (see [RFC3410]), and implementations claiming
compliance to the SNMPv3 standard MUST include full support for
authentication and privacy via the User-based Security Model (USM)
[RFC3414] with the AES cipher algorithm [RFC3826]. Implementations
MAY also provide support for the Transport Security Model (TSM)
[RFC5591] in combination with a secure transport such as SSH
[RFC5592] or TLS/DTLS [RFC6353].
Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them.
15. IANA Considerations 15. IANA Considerations
As described in [RFC4221], [RFC6639] and as requested in the MPLS-TC- As described in [RFC4221], [RFC6639] and as requested in the MPLS-TC-
STD-MIB [RFC3811], MPLS related standards track MIB modules should be STD-MIB [RFC3811], MPLS related standards track MIB modules should be
rooted under the mplsStdMIB subtree. There are 4 MPLS MIB Modules rooted under the mplsStdMIB subtree. There are 4 MPLS MIB Modules
contained in this document, each of the following "IANA contained in this document, each of the following "IANA
Considerations" subsections requests IANA for a new assignment under Considerations" subsections requests IANA for a new assignment under
the mplsStdMIB subtree. New assignments can only be made via a the mplsStdMIB subtree. New assignments can only be made via a
Standards Action as specified in [RFC5226]. Standards Action as specified in [RFC5226].
skipping to change at page 57, line 37 skipping to change at page 59, line 28
Multiprotocol Label Switching (GMPLS) Traffic Engineering Multiprotocol Label Switching (GMPLS) Traffic Engineering
Management Information Base", RFC 4802, February 2007. Management Information Base", RFC 4802, February 2007.
[RFC6370] Bocci, M., Swallow, G., and E. Gray, "MPLS Transport [RFC6370] Bocci, M., Swallow, G., and E. Gray, "MPLS Transport
Profile (MPLS-TP) Identifiers", RFC 6370, September 2011. Profile (MPLS-TP) Identifiers", RFC 6370, September 2011.
[RFC6923] Winter, R., Gray, E., Helvoort, H., and M. Betts, "MPLS-TP [RFC6923] Winter, R., Gray, E., Helvoort, H., and M. Betts, "MPLS-TP
Identifiers Following ITU-T Conventions", RFC 6923, May Identifiers Following ITU-T Conventions", RFC 6923, May
2013 2013
[T.50] "International Reference Alphabet (IRA) (Formerly
International Alphabet No. 5 or IA5) - Information
technology - 7-bit coded character set for information
exchange", ITU-T Recommendation T.50, September 1992.
16.2. Informative References 16.2. Informative References
[RFC3410] J. Case, R. Mundy, D. pertain, B.Stewart, "Introduction [RFC3410] J. Case, R. Mundy, D. pertain, B.Stewart, "Introduction
and Applicability Statement for Internet Standard and Applicability Statement for Internet Standard
Management Framework", RFC 3410, December 2002. Management Framework", RFC 3410, December 2002.
[RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model
(USM) for version 3 of the Simple Network Management
Protocol (SNMPv3)", STD 62, RFC 3414, December 2002.
[RFC3826] Blumenthal, U., F. Maino and K. McCloghrie, "The Advanced
Encryption Standard (AES) Cipher Algorithm in the SNMP
User-based Security Model", RFC 3826, June 2004.
[RFC4221] Nadeau, T., Srinivasan, C., and A. Farrel, "Multiprotocol [RFC4221] Nadeau, T., Srinivasan, C., and A. Farrel, "Multiprotocol
Label Switching (MPLS) Management Overview", RFC 4221, Label Switching (MPLS) Management Overview", RFC 4221,
November 2005. November 2005.
[RFC5226] Narten, T. and H. Alvestrand., "Guidelines for Writing an [RFC5226] Narten, T. and H. Alvestrand., "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226, IANA Considerations Section in RFCs", BCP 26, RFC 5226,
May 2008. May 2008.
[RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model
for the Simple Network Management Protocol (SNMP)",
RFC 5591, June 2009.
[RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure
Shell Transport Model for the Simple Network Management
Protocol (SNMP)", RFC 5592, June 2009.
[RFC5654] Niven-Jenkins, B., Ed., Brungard, D., Ed., Betts, M., [RFC5654] Niven-Jenkins, B., Ed., Brungard, D., Ed., Betts, M.,
Ed.,Sprecher, N., and S. Ueno, "Requirements of an MPLS Ed.,Sprecher, N., and S. Ueno, "Requirements of an MPLS
Transport Profile", RFC 5654, September 2009. Transport Profile", RFC 5654, September 2009.
[RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport
Model for the Simple Network Management Protocol (SNMP)",
STD 78, RFC 6353, July 2011.
[RFC6639] Venkatesan, M., King, D., "Multiprotocol Label Switching [RFC6639] Venkatesan, M., King, D., "Multiprotocol Label Switching
Transport Profile (MPLS-TP) MIB-Based Management Transport Profile (MPLS-TP) MIB-Based Management
Overview", RFC 6639, June 2012 Overview", RFC 6639, June 2012
17. Acknowledgments 17. Acknowledgments
The authors would like to thank Francesco Fondelli, Josh Littlefield, The authors would like to thank Francesco Fondelli, Josh Littlefield,
Agrahara Kiran Koushik, Metrri Jain, Muly Ilan, Randy Presuhn, Adrian Agrahara Kiran Koushik, Metrri Jain, Muly Ilan, Randy Presuhn, Elwyn
Farrel, Elwyn Davies and Tom Taylor for their valuable review and Davies, Tom Taylor and Pete Resnick for their valuable review and
comments. A special thanks to Joan Cucchiara for really getting the comments. A special thanks to Joan Cucchiara and Adrian Farrel for
MIB modules into shape. really getting the MIB modules into shape.
18. Authors' Addresses 18. Authors' Addresses
Venkatesan Mahalingam Venkatesan Mahalingam
Dell Inc. Dell Inc.
5450 Great America Parkway, 5450 Great America Parkway,
Santa Clara, CA 95054, USA Santa Clara, CA 95054, USA
Email: venkat.mahalingams@gmail.com Email: venkat.mahalingams@gmail.com
Sam Aldrin Sam Aldrin
 End of changes. 28 change blocks. 
144 lines changed or deleted 209 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/