draft-ietf-mpls-tp-te-mib-06.txt   draft-ietf-mpls-tp-te-mib-07.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: November 09, 2013 Kannan KV Sampath Expires: May 08, 2014 Kannan KV Sampath
Redeem Redeem
Sam K. Aldrin Sam K. Aldrin
Huawei Technologies Huawei Technologies
Thomas D. Nadeau Thomas D. Nadeau
Juniper Networks Juniper Networks
May 08, 2013 November 04, 2013
MPLS-TP Traffic Engineering (TE) Management Information Base (MIB) MPLS-TP Traffic Engineering (TE) Management Information Base (MIB)
draft-ietf-mpls-tp-te-mib-06.txt draft-ietf-mpls-tp-te-mib-07.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 managed objects of Tunnels, Identifiers, In particular, it describes managed objects of Tunnels, Identifiers,
Label Switch Router and Textual conventions for Multiprotocol Label Label Switching Router and Textual conventions for Multiprotocol
Switching (MPLS) based Transport Profile (TP). Label Switching (MPLS) based Transport Profile (TP).
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 47 skipping to change at page 1, line 47
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 November 09, 2013. This Internet-Draft will expire on May 08, 2014.
Copyright and License Notice Copyright and License Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2013 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 35 skipping to change at page 2, line 35
3.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . 4 3.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . 4
3.3. Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . 6 3.3. Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . 6
4. Motivations . . . . . . . . . . . . . . . . . . . . . . . . . . 6 4. Motivations . . . . . . . . . . . . . . . . . . . . . . . . . . 6
5. Feature List . . . . . . . . . . . . . . . . . . . . . . . . . 6 5. Feature List . . . . . . . . . . . . . . . . . . . . . . . . . 6
6. Brief description of MPLS-TE-EXT-STD-MIB Objects . . . . . . . 7 6. Brief description of MPLS-TE-EXT-STD-MIB Objects . . . . . . . 7
6.1. mplsTunnelExtNodeConfigTable . . . . . . . . . . . . . . . 7 6.1. mplsTunnelExtNodeConfigTable . . . . . . . . . . . . . . . 7
6.2. mplsTunnelExtNodeIpMapTable . . . . . . . . . . . . . . . . 8 6.2. mplsTunnelExtNodeIpMapTable . . . . . . . . . . . . . . . . 8
6.3. mplsTunnelExtNodeIccMapTable . . . . . . . . . . . . . . . 8 6.3. mplsTunnelExtNodeIccMapTable . . . . . . . . . . . . . . . 8
6.4. mplsTunnelExtTable . . . . . . . . . . . . . . . . . . . . 8 6.4. mplsTunnelExtTable . . . . . . . . . . . . . . . . . . . . 8
6.5. mplsTunnelExtReversePerfTable . . . . . . . . . . . . . . . 8 6.5. mplsTunnelExtReversePerfTable . . . . . . . . . . . . . . . 8
7. MIB Module Interdependencies . . . . . . . . . . . . . . . . . 8 7. MIB Module Interdependencies . . . . . . . . . . . . . . . . . 9
8. Dependencies between MIB Module Tables . . . . . . . . . . . . 11 8. Dependencies between MIB Module Tables . . . . . . . . . . . . 11
9.1. Example of MPLS-TP static co-routed bidirectional tunnel 9.1. Example of MPLS-TP static co-routed bidirectional tunnel
setup . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 setup . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
9.1.1. mplsTunnelEntry . . . . . . . . . . . . . . . . . . . . 12 9.1.1. mplsTunnelEntry . . . . . . . . . . . . . . . . . . . . 12
9.1.2. mplsTunnelExtEntry . . . . . . . . . . . . . . . . . . 13 9.1.2. mplsTunnelExtEntry . . . . . . . . . . . . . . . . . . 13
9.1.3. Forward direction mplsOutSegmentEntry . . . . . . . . . 14 9.1.3. Forward direction mplsOutSegmentEntry . . . . . . . . . 14
9.1.4. Reverse direction mplsInSegmentEntry . . . . . . . . . 14 9.1.4. Reverse direction mplsInSegmentEntry . . . . . . . . . 14
9.1.5. Forward direction mplsXCEntry . . . . . . . . . . . . . 14 9.1.5. Forward direction mplsXCEntry . . . . . . . . . . . . . 14
9.1.6. Reverse direction mplsXCEntry . . . . . . . . . . . . . 15 9.1.6. Reverse direction mplsXCEntry . . . . . . . . . . . . . 15
9.1.7. Forward direction mplsXCExtEntry . . . . . . . . . . . 15 9.1.7. Forward direction mplsXCExtEntry . . . . . . . . . . . 15
skipping to change at page 3, line 20 skipping to change at page 3, line 20
9.2.10. Reverse direction mplsXCExtEntry . . . . . . . . . . . 20 9.2.10. Reverse direction mplsXCExtEntry . . . . . . . . . . . 20
9.3.1. mplsTunnelEntry . . . . . . . . . . . . . . . . . . . . 20 9.3.1. mplsTunnelEntry . . . . . . . . . . . . . . . . . . . . 20
9.3.2. mplsTunnelExtEntry . . . . . . . . . . . . . . . . . . 21 9.3.2. mplsTunnelExtEntry . . . . . . . . . . . . . . . . . . 21
9.3.3. Forward direction mplsOutSegmentEntry . . . . . . . . . 21 9.3.3. Forward direction mplsOutSegmentEntry . . . . . . . . . 21
9.3.4. Reverse direction mplsInSegmentEntry . . . . . . . . . 21 9.3.4. Reverse direction mplsInSegmentEntry . . . . . . . . . 21
9.3.5. Forward direction mplsXCEntry . . . . . . . . . . . . . 22 9.3.5. Forward direction mplsXCEntry . . . . . . . . . . . . . 22
9.3.6. Reverse direction mplsXCEntry . . . . . . . . . . . . . 22 9.3.6. Reverse direction mplsXCEntry . . . . . . . . . . . . . 22
9.3.7. Forward direction mplsXCExtEntry . . . . . . . . . . . 22 9.3.7. Forward direction mplsXCExtEntry . . . . . . . . . . . 22
9.3.8. Reverse direction mplsXCExtEntry . . . . . . . . . . . 22 9.3.8. Reverse direction mplsXCExtEntry . . . . . . . . . . . 22
9.3.9. mplsTunnelExtReversePerfTable . . . . . . . . . . . . . 22 9.3.9. mplsTunnelExtReversePerfTable . . . . . . . . . . . . . 22
10. MPLS Textual Convention Extension MIB definitions . . . . . . 22
11. MPLS Identifier MIB definitions . . . . . . . . . . . . . . . 25 11. MPLS Identifier MIB definitions . . . . . . . . . . . . . . . 25
12. MPLS LSR Extension MIB definitions . . . . . . . . . . . . . . 30 12. MPLS LSR Extension MIB definitions . . . . . . . . . . . . . . 30
13. MPLS Tunnel Extension MIB definitions . . . . . . . . . . . . 35 13. MPLS Tunnel Extension MIB definitions . . . . . . . . . . . . 35
14. Security Consideration . . . . . . . . . . . . . . . . . . . . 53 14. Security Consideration . . . . . . . . . . . . . . . . . . . . 55
15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 55 15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 56
15.1. IANA Considerations for MPLS-TC-EXT-STD-MIB . . . . . . . 55 15.1. IANA Considerations for MPLS-TC-EXT-STD-MIB . . . . . . . 56
15.2. IANA Considerations for MPLS-ID-STD-MIB . . . . . . . . . 55 15.2. IANA Considerations for MPLS-ID-STD-MIB . . . . . . . . . 57
15.3. IANA Considerations for MPLS-LSR-EXT-STD-MIB . . . . . . . 55 15.3. IANA Considerations for MPLS-LSR-EXT-STD-MIB . . . . . . . 57
15.4. IANA Considerations for MPLS-TE-EXT-STD-MIB . . . . . . . 55 15.4. IANA Considerations for MPLS-TE-EXT-STD-MIB . . . . . . . 57
16. References . . . . . . . . . . . . . . . . . . . . . . . . . . 55 16. References . . . . . . . . . . . . . . . . . . . . . . . . . . 57
16.1. Normative References . . . . . . . . . . . . . . . . . . . 55 16.1. Normative References . . . . . . . . . . . . . . . . . . . 57
16.2. Informative References . . . . . . . . . . . . . . . . . 56 16.2. Informative References . . . . . . . . . . . . . . . . . 57
17. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 57 17. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 58
18. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 57 18. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 58
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 managed objects of Tunnels, Identifiers, Label particular, it describes managed objects of Tunnels, Identifiers, Label
Switch Router and Textual conventions for Multiprotocol Label Switching Switching Router and Textual conventions for Multiprotocol Label
(MPLS) based Transport Profile (TP). These MIB modules extend the Switching (MPLS) based Transport Profile (TP). These MIB modules extend
existing MPLS MIB objects for both MPLS-TP and Non-MPLS-TP operations, the existing MPLS MIB objects for both MPLS-TP and Non-MPLS-TP
so the MPLS-TP name is not included in the MIB module name. operations, so the MPLS-TP name is not included in the MIB module name.
The existing Multiprotocol Label Switching (MPLS) Traffic Engineering The existing Multiprotocol Label Switching (MPLS) Traffic Engineering
(TE) Management Information Base (MIB) [RFC3812] and Generalized (TE) Management Information Base (MIB) [RFC3812] and Generalized
Multiprotocol Label Switching (GMPLS) Traffic Engineering Management Multiprotocol Label Switching (GMPLS) Traffic Engineering Management
Information Base [RFC4802] do not support the transport network Information Base [RFC4802] do not support the transport network
requirements of NON-IP based management and static bidirectional requirements of NON-IP based management and static bidirectional
tunnels. These MIB modules should be used in conjunction with [RFC3812] tunnels. These MIB modules should be used in conjunction with [RFC3812]
and companion document [RFC3813] for MPLS-TP tunnel configuration and and companion document [RFC3813] for MPLS-TP tunnel configuration and
management. management.
skipping to change at page 6, line 7 skipping to change at page 6, line 7
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].
3.3. Acronyms 3.3. Acronyms
CC: Country Code
GMPLS: Generalized Multi-Protocol Label Switching GMPLS: Generalized Multi-Protocol Label Switching
ICC: ITU Carrier Code ICC: ITU Carrier Code
IP: Internet Protocol IP: Internet Protocol
ITU: International Telecommunication Union
ITU-T: ITU Telecommunication Standardization Sector
LSP: Label Switching Path LSP: Label Switching Path
LSR: Label Switching Router LSR: Label Switching Router
MIB: Management Information Base MIB: Management Information Base
MPLS: Multi-Protocol Label Switching MPLS: Multi-Protocol Label Switching
MPLS-TP: MPLS Transport Profile MPLS-TP: MPLS Transport Profile
OSPF: Open Shortest Path First OSPF: Open Shortest Path First
PW: Pseudowire PW: Pseudowire
TE: Traffic Engineering TE: Traffic Engineering
TP: Transport Profile TP: Transport Profile
skipping to change at page 6, line 35 skipping to change at page 6, line 38
Tunnels were enhanced. For example, MPLS-TP tunnels are bidirectional in Tunnels were enhanced. For example, MPLS-TP tunnels are bidirectional in
nature and could be used in non-IP environments. As the existing MPLS- nature and could be used in non-IP environments. As the existing MPLS-
TE-STD-MIB is not sufficient to capture all the characteristics of the TE-STD-MIB is not sufficient to capture all the characteristics of the
tunnels, enhancing the MIB to support MPLS TP tunnels is required. As tunnels, enhancing the MIB to support MPLS TP tunnels is required. As
most of the attributes of MPLS Traffic Engineering tunnels are also most of the attributes of MPLS Traffic Engineering tunnels are also
applicable to MPLS-TP tunnels, it is optimal to re-use the existing MIB applicable to MPLS-TP tunnels, it is optimal to re-use the existing MIB
definition instead of a new MIB. definition instead of a new MIB.
This document defines four MIB modules, namely MPLS-TE-EXT-STD-MIB, This document defines four MIB modules, namely MPLS-TE-EXT-STD-MIB,
MPLS-TC-EXT-STD-MIB, MPLS-ID-STD-MIB and MPLS-LSR-EXT-STD-MIB. As these MPLS-TC-EXT-STD-MIB, MPLS-ID-STD-MIB and MPLS-LSR-EXT-STD-MIB. As these
new MIB modules are small in size, these new MIB modules are retained in new MIB modules are required for MPLS-TP functionality, these are
the same document, instead of a separate document. retained in the same document, instead of a separate document.
5. Feature List 5. Feature List
The MPLS-TE-EXT-STD-MIB is designed to satisfy the following The MPLS-TE-EXT-STD-MIB is designed to satisfy the following
requirements and constraints: requirements and constraints:
The MIB module supports static and signaling point-to-point, co-routed The MIB module supports static and signaling point-to-point, co-routed
bi-directional and associated bi-directional tunnels. bi-directional and associated bi-directional tunnels.
- The MPLS tunnels need not be interfaces, but it is possible - The MPLS tunnels need not be interfaces, but it is possible
to configure a TP tunnel as an interface. to configure a TP tunnel as an interface.
- The mplsTunnelTable [RFC3812] to be also used for MPLS-TP - The mplsTunnelTable [RFC3812] to be also used for MPLS-TP
tunnels tunnels
- The mplsTunnelTable is extended to support MPLS-TP specific - The mplsTunnelTable is extended to support MPLS-TP specific
objects. objects.
- A node configuration table (mplsTunnelExtNodeConfigTable) - A node configuration table (mplsTunnelExtNodeConfigTable)
is used to translate the Global_ID::Node_ID or CC::ICC to is used to translate the Global_ID::Node_ID or
the local identifier in order to index mplsTunnelTable. ICC_Operator_ID::Node_ID to the local identifier in order
to index mplsTunnelTable.
- The MIB module supports persistent, as well as non-persistent - The MIB module supports persistent, as well as non-persistent
tunnels. tunnels.
6. Brief description of MPLS-TE-EXT-STD-MIB Objects 6. Brief description of MPLS-TE-EXT-STD-MIB Objects
The objects described in this section support the functionality The objects described in this section support the functionality
described in documents [RFC5654] and [RFC6370]. The tables support described in documents [RFC5654] and [RFC6370]. The tables support
both IP compatible and ICC based tunnel configurations. both IP compatible and ICC based tunnel configurations.
6.1. mplsTunnelExtNodeConfigTable 6.1. mplsTunnelExtNodeConfigTable
The mplsTunnelExtNodeConfigTable is used to assign a local identifier The mplsTunnelExtNodeConfigTable is used to assign a local identifier
for a given CC::ICC or Global_ID::Node_ID combination as defined in for a given ICC_Operator_ID::Node_ID or Global_ID::Node_ID
[I-D.ietf-mpls-tp-itu-t-identifiers] and [RFC6370] respectively. combination as defined in [RFC6923] and [RFC6370] respectively.
The CC is a string of two alphabetic characters represented with 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 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) characters, each character being either alphabetic (i.e. A-Z)
or numeric (i.e. 0-9) characters. Alphabetic characters in the ICC or numeric (i.e. 0-9) characters. Alphabetic characters in the ICC
should be represented with upper case letters. In the IP compatible should be represented with upper case letters. In the IP compatible
mode, Global_ID::Node_ID, is used to uniquely identify a node. mode, Global_ID::Node_ID, is used to uniquely identify a node.
Each CC::ICC or Global_ID::Node_ID contains one unique entry in the Each ICC_Operator_ID::Node_ID or Global_ID::Node_ID contains one
table representing a node. Every node is assigned a local identifier unique entry in the table representing a node. Every node is assigned
within a range of 0 to 16777215. This local identifier is used for a local identifier within a range of 0 to 16777215. This local
indexing into mplsTunnelTable as mplsTunnelIngressLSRId and identifier is used for indexing into mplsTunnelTable as
mplsTunnelEgressLSRId. 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, Destination CC and Tunnel Instance, Source CC, Source ICC, Source Node_ID, Destination
Destination ICC. CC, Destination ICC and Destination Node_ID.
As mplsTunnelTable is indexed by mplsTunnelIndex, As mplsTunnelTable is indexed by mplsTunnelIndex,
mplsTunnelInstance, mplsTunnelIngressLSRId, and mplsTunnelInstance, mplsTunnelIngressLSRId, and
mplsTunnelEgressLSRId, the MPLS-TP tunnel identifiers cannot be mplsTunnelEgressLSRId, the MPLS-TP tunnel identifiers cannot be
used directly. used directly.
The mplsTunnelExtNodeConfigTable will be used to store an entry for The mplsTunnelExtNodeConfigTable will be used to store an entry for
CC::ICC or Global_ID::Node_ID with a local identifier to be used as ICC_Operator_ID::Node_ID or Global_ID::Node_ID with a local
LSR ID in mplsTunnelTable. As the regular TE tunnels use IP address identifier to be used as LSR ID in mplsTunnelTable. As the regular TE
as LSR ID, the local identifier should be below the first valid IP tunnels use IP address as LSR ID, the local identifier should be
address, which is 16777216[1.0.0.0]. below the first valid IP address, which is 16777216[1.0.0.0].
6.2. mplsTunnelExtNodeIpMapTable 6.2. mplsTunnelExtNodeIpMapTable
The read-only mplsTunnelExtNodeIpMaptable is used to query the local The read-only mplsTunnelExtNodeIpMaptable is used to query the local
identifier assigned and stored in mplsTunnelExtNodeConfigTable for identifier assigned and stored in mplsTunnelExtNodeConfigTable for
a given Global_ID::Node_ID. In order to query the local identifier, a given Global_ID::Node_ID. In order to query the local identifier,
in the IP compatible mode, this table is indexed with 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. In the IP compatible mode for a TP tunnel,
Global_ID::Node_ID is used. Global_ID::Node_ID is used.
A separate query is made to get the local identifier of both A separate query is made to get the local identifier of both
Ingress and Egress Global_ID::Node_ID identifiers. These local Ingress and Egress Global_ID::Node_ID identifiers. These local
identifiers are used as mplsTunnelIngressLSRId and identifiers are used as mplsTunnelIngressLSRId and
mplsTunnelEgressLSRId, while indexing mplsTunnelTable. mplsTunnelEgressLSRId, while indexing mplsTunnelTable.
6.3. mplsTunnelExtNodeIccMapTable 6.3. mplsTunnelExtNodeIccMapTable
The read-only mplsTunnelExtNodeIccMapTable is used to query the local The read-only mplsTunnelExtNodeIccMapTable is used to query the local
identifier assigned and stored in the mplsTunnelExtNodeConfigTable identifier assigned and stored in the mplsTunnelExtNodeConfigTable
for a given CC::ICC. for a given ICC_Operator_ID::Node_ID.
A separate query is made to get the local identifier of both A separate query is made to get the local identifier of both
Ingress and Egress CC::ICC. These local identifiers are used as Ingress and Egress ICC_Operator_ID::Node_ID. These local identifiers
mplsTunnelIngressLSRId and mplsTunnelEgressLSRId, are used as mplsTunnelIngressLSRId and mplsTunnelEgressLSRId,
while indexing mplsTunnelTable. while indexing mplsTunnelTable.
6.4. mplsTunnelExtTable 6.4. mplsTunnelExtTable
mplsTunnelExtTable extends the mplsTunnelTable in order to support mplsTunnelExtTable extends the mplsTunnelTable in order to support
MPLS-TP tunnels with additional objects. All the additional MPLS-TP tunnels with additional objects. All the additional
attributes specific to supporting TP tunnel are contained in this attributes specific to supporting TP tunnel are contained in this
extended table and could be accessed with the mplsTunnelTable extended table and could be accessed with the mplsTunnelTable
indices. indices.
skipping to change at page 11, line 25 skipping to change at page 11, line 25
| +---------+ | | +---------+ |
| | | | | |
| V V | V V
mplsTunnelTable ---->mplsXCTable mplsTunnelTable ---->mplsXCTable
^ ^
| |
| |
mplsTunnelExtTable mplsTunnelExtTable
An existing mplsTunnelTable uses the mplsTunnelExtNodeConfigTable An existing mplsTunnelTable uses the mplsTunnelExtNodeConfigTable
table to map the Global_ID::Node_ID and/or CC::ICC with the local table to map the Global_ID::Node_ID and/or ICC_Operator_ID::Node_ID
number in order to accommodate in the existing tunnel table's with the local number in order to accommodate in the existing tunnel
ingress/egress LSR-id. table's ingress/egress LSR-id.
New mplsTunnelExtTable table provides the reverse direction LSP New mplsTunnelExtTable table provides the reverse direction LSP
information for the existing tunnel table in order to achieve information for the existing tunnel table in order to achieve
bidirectional LSPs. bidirectional LSPs.
mplsXCExtTable is extended from mplsLsrXCTable to provide mplsXCExtTable is extended from mplsLsrXCTable to provide
backward reference to tunnel entry. backward reference to tunnel entry.
9. Example of MPLS-TP Tunnel Setup 9. Example of MPLS-TP Tunnel Setup
In this section, we provide an example of the IP based MPLS-TP In this section, we provide an example of the IP based MPLS-TP
skipping to change at page 22, line 48 skipping to change at page 22, line 48
9.3.9. mplsTunnelExtReversePerfTable 9.3.9. mplsTunnelExtReversePerfTable
The mplsTunnelExtReversePerfTable SHOULD be populated incase the The mplsTunnelExtReversePerfTable SHOULD be populated incase the
single tunnel entry is used for co-routed bidirectional tunnel setup. single tunnel entry is used for co-routed bidirectional tunnel setup.
The mplsTunnelPerfTable will have the forward direction LSP The mplsTunnelPerfTable will have the forward direction LSP
performance counters and mplsTunnelExtReversePerfTable will have the performance counters and mplsTunnelExtReversePerfTable will have the
reverse direction LSP performance counters. reverse direction LSP performance counters.
10. MPLS Textual Convention Extension MIB definitions 10. MPLS Textual Convention Extension MIB definitions
MPLS-TC-EXT-STD-MIB DEFINITIONS ::= BEGIN MPLS-TC-EXT-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, Unsigned32 MODULE-IDENTITY, Unsigned32
FROM SNMPv2-SMI -- [RFC2578] FROM SNMPv2-SMI -- [RFC2578]
TEXTUAL-CONVENTION TEXTUAL-CONVENTION
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
"201304130000Z" -- April 13, 2013 "201311010000Z" -- November 01, 2013
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,
350 Holger way, San Jose, CA, USA 350 Holger way, San Jose, CA, USA
Email: venkat.mahalingams@gmail.com Email: venkat.mahalingams@gmail.com
Kannan KV Sampath Kannan KV Sampath
skipping to change at page 24, line 7 skipping to change at page 24, line 7
"Copyright (c) 2013 IETF Trust and the persons identified "Copyright (c) 2013 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 This MIB module contains Textual Conventions for
LSPs and PWs of MPLS based transport networks." LSPs and PWs of MPLS based transport networks."
-- Revision history. -- Revision history.
REVISION REVISION
"201304130000Z" -- April 13, 2013 "201311010000Z" -- November 01, 2013
DESCRIPTION DESCRIPTION
"MPLS Textual Convention Extensions" "MPLS Textual Convention Extensions"
::= { mplsStdMIB xxx } -- xxx to be replaced with correct value ::= { mplsStdMIB xxx } -- xxx to be replaced with correct value
MplsGlobalId ::= TEXTUAL-CONVENTION MplsGlobalId ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the Textual Convention of IP based "This object contains the Textual Convention of IP based
skipping to change at page 24, line 43 skipping to change at page 24, line 42
that no Global_ID is present. Note that a Global_ID of that no Global_ID is present. Note that a Global_ID of
zero is limited to entities contained within a single zero is limited to entities contained within a single
operator and MUST NOT be used across an NNI. operator and MUST NOT be used across an NNI.
A non-zero Global_ID MUST be derived from an ASN owned by A non-zero 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
STATUS current
DESCRIPTION
"The CC (Country Code) is a string of two alphabetic
characters represented with upper case
letters (i.e., A-Z)."
REFERENCE
"MPLS-TP Identifiers Following ITU-T Conventions,
[RFC6923] Section 3"
SYNTAX OCTET STRING (SIZE (2))
MplsIccId ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"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. The size of the ICC string MUST be
zero if the ICC identifier is invalid."
REFERENCE
"MPLS-TP Identifiers Following ITU-T Conventions,
[RFC6923] Section 3"
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 Global_ID. "The Node_ID is assigned within the scope of
the Global_ID/ICC_Operator_ID.
The value 0(or 0.0.0.0 in dotted decimal notation) is The value 0(or 0.0.0.0 in dotted decimal notation) is
reserved and MUST NOT be used. reserved and MUST NOT be used.
When IPv4 addresses are in use, the value of this object When IPv4 addresses are in use, the value of this object
can be derived from the LSR's IPv4 loop back address. can be derived from the LSR's IPv4 loop back address.
When IPv6 addresses are in use, the value of this object When IPv6 addresses are in use, the value of this object
can be a 32-bit value unique within the scope of can be a 32-bit value unique within the scope of
a Global_ID. a Global_ID.
Note that, when IP reach ability is not needed, the 32-bit Note that, when IP reach ability is not needed, the 32-bit
Node_ID is not required to have any association Node_ID is not required to have any association
with the IPv4 address space." with the IPv4 address space."
REFERENCE REFERENCE
"MPLS Transport Profile (MPLS-TP) Identifiers, [RFC6370] "MPLS Transport Profile (MPLS-TP) Identifiers, [RFC6370]
Section 4" Section 4"
SYNTAX Unsigned32 (0|1..4294967295) SYNTAX Unsigned32 (0|1..4294967295)
MplsCcId ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The CC (Country Code) is a string of two alphabetic
characters represented with upper case
letters (i.e., A-Z)."
REFERENCE
"MPLS-TP Identifiers Following ITU-T Conventions,
draft-ietf-mpls-tp-itu-t-identifiers-08 (work in
progress), February 2013. Section 3"
SYNTAX OCTET STRING (SIZE (2))
MplsIccId ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"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. The ICC string should be assigned
to zero if the ICC identifier is invalid."
REFERENCE
"MPLS-TP Identifiers Following ITU-T Conventions,
draft-ietf-mpls-tp-itu-t-identifiers-08 (work in
progress), February 2013. Section 3"
SYNTAX OCTET STRING (SIZE (0..6))
-- MPLS-TC-EXT-STD-MIB module ends -- MPLS-TC-EXT-STD-MIB module ends
END END
11. MPLS Identifier MIB definitions 11. MPLS Identifier MIB definitions
MPLS-ID-STD-MIB DEFINITIONS ::= BEGIN MPLS-ID-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE MODULE-IDENTITY, OBJECT-TYPE
FROM SNMPv2-SMI -- [RFC2578] FROM SNMPv2-SMI -- [RFC2578]
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF -- [RFC2580] FROM SNMPv2-CONF -- [RFC2580]
mplsStdMIB mplsStdMIB
FROM MPLS-TC-STD-MIB -- [RFC3811] FROM MPLS-TC-STD-MIB -- [RFC3811]
MplsGlobalId, MplsCcId, MplsIccId, MplsNodeId MplsGlobalId, MplsCcId, MplsIccId, MplsNodeId
FROM MPLS-TC-EXT-STD-MIB FROM MPLS-TC-EXT-STD-MIB
; ;
skipping to change at page 26, line 17 skipping to change at page 26, line 13
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF -- [RFC2580] FROM SNMPv2-CONF -- [RFC2580]
mplsStdMIB mplsStdMIB
FROM MPLS-TC-STD-MIB -- [RFC3811] FROM MPLS-TC-STD-MIB -- [RFC3811]
MplsGlobalId, MplsCcId, MplsIccId, MplsNodeId MplsGlobalId, MplsCcId, MplsIccId, MplsNodeId
FROM MPLS-TC-EXT-STD-MIB FROM MPLS-TC-EXT-STD-MIB
; ;
mplsIdStdMIB MODULE-IDENTITY mplsIdStdMIB MODULE-IDENTITY
LAST-UPDATED LAST-UPDATED
"201304130000Z" -- April 13, 2013 "201311010000Z" -- November 01, 2013
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,
350 Holger way, San Jose, CA, USA 350 Holger way, San Jose, CA, USA
Email: venkat.mahalingams@gmail.com Email: venkat.mahalingams@gmail.com
skipping to change at page 27, line 9 skipping to change at page 27, line 6
DESCRIPTION DESCRIPTION
"Copyright (c) 2013 IETF Trust and the persons identified "Copyright (c) 2013 IETF Trust and the persons identified
as the document authors. All rights reserved. as the document authors. All rights reserved.
This MIB module contains generic object definitions for This MIB module contains generic object definitions for
MPLS Traffic Engineering in transport networks." MPLS Traffic Engineering in transport networks."
-- Revision history. -- Revision history.
REVISION REVISION
"201304130000Z" -- April 13, 2013 "201311010000Z" -- November 01, 2013
DESCRIPTION DESCRIPTION
"This MIB modules defines the MIB objects for MPLS-TP "This MIB modules defines the MIB objects for MPLS-TP
identifiers" identifiers"
::= { mplsStdMIB xxx } -- xxx to be replaced with correct value ::= { mplsStdMIB xxx } -- xxx to be replaced with correct value
-- notifications
mplsIdNotifications OBJECT IDENTIFIER ::= { mplsIdStdMIB 0 }
-- tables, scalars -- tables, scalars
mplsIdObjects OBJECT IDENTIFIER ::= { mplsIdStdMIB 0 } mplsIdObjects OBJECT IDENTIFIER ::= { mplsIdStdMIB 1 }
-- conformance -- conformance
mplsIdConformance OBJECT IDENTIFIER ::= { mplsIdStdMIB 1 } mplsIdConformance OBJECT IDENTIFIER ::= { mplsIdStdMIB 2 }
-- MPLS common objects -- MPLS common objects
mplsIdGlobalId OBJECT-TYPE mplsIdGlobalId OBJECT-TYPE
SYNTAX MplsGlobalId SYNTAX MplsGlobalId
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object allows the operator to assign a unique "This object allows the operator to assign a unique
operator identifier also called MPLS-TP Global_ID. operator identifier also called MPLS-TP Global_ID.
skipping to change at page 27, line 44 skipping to change at page 27, line 43
mplsIdNodeId OBJECT-TYPE mplsIdNodeId OBJECT-TYPE
SYNTAX MplsNodeId SYNTAX MplsNodeId
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 Node_ID. assign a unique MPLS-TP Node_ID.
The Node_ID is assigned within the scope of The Node_ID is assigned within the scope of
the Global_ID. the Global_ID/ICC_Operator_ID.
If this value is used in mplsTunnelExtNodeConfigNodeId If this value is used in mplsTunnelExtNodeConfigNodeId
for mapping Global_ID::Node_ID with the local identifier for mapping Global_ID::Node_ID with the local identifier
then this object value SHOULD NOT be changed." then this object value SHOULD NOT be changed.
If this value is used in mplsTunnelExtNodeConfigNodeId
for mapping ICC_Operator_ID::Node_ID with the local
identifier then this object value SHOULD 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 unique Country Code (CC). Global uniqueness is assign a unique Country Code (CC). Global uniqueness is
assured by concatenating the ICC with a assured by concatenating the ICC with a
Country Code (CC). Country Code (CC).
If this value is used in mplsTunnelExtNodeConfigCcId If this value is used in mplsTunnelExtNodeConfigCcId
for mapping CC:ICC with the local identifier then this for mapping ICC_Operator_ID::Node_ID with the local
object value SHOULD NOT be changed." identifier then this object value SHOULD NOT be changed."
REFERENCE REFERENCE
"MPLS-TP Identifiers Following ITU-T Conventions, "MPLS-TP Identifiers Following ITU-T Conventions,
draft-ietf-mpls-tp-itu-t-identifiers-08 (work in [RFC6923] Section 3"
progress), February 2013. 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 a assign a unique MPLS-TP ITU-T Carrier Code (ICC) to a
network. Together, the CC and the ICC form network. 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 CC::ICC with the local identifier then for mapping ICC_Operator_ID::Node_ID with the local
this object value SHOULD NOT be changed." identifier then this object value SHOULD NOT be changed."
REFERENCE REFERENCE
"MPLS-TP Identifiers Following ITU-T Conventions, "MPLS-TP Identifiers Following ITU-T Conventions,
draft-ietf-mpls-tp-itu-t-identifiers-08 (work in [RFC6923] Section 3"
progress), February 2013. 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 }
skipping to change at page 29, line 20 skipping to change at page 29, line 19
-- The mandatory group has to be implemented by all -- The mandatory group has to be implemented by all
-- LSRs that originate/terminate MPLS-TP paths. -- LSRs that originate/terminate MPLS-TP paths.
MANDATORY-GROUPS { MANDATORY-GROUPS {
mplsIdScalarGroup mplsIdScalarGroup
} }
::= { mplsIdCompliances 1 } ::= { mplsIdCompliances 1 }
-- Compliance requirement for read-only implementations.
mplsIdModuleReadOnlyCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"Compliance statement for agents that only provide
read-only support for the MPLS-ID-STD-MIB module."
MODULE -- this module
MANDATORY-GROUPS {
mplsIdScalarGroup
}
OBJECT mplsIdGlobalId
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT mplsIdNodeId
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT mplsIdIcc
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT mplsIdCc
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
::= { mplsIdCompliances 2 }
-- Units of conformance. -- Units of conformance.
mplsIdScalarGroup OBJECT-GROUP mplsIdScalarGroup OBJECT-GROUP
OBJECTS { mplsIdGlobalId, OBJECTS { mplsIdGlobalId,
mplsIdNodeId, mplsIdNodeId,
mplsIdIcc, mplsIdIcc,
mplsIdCc mplsIdCc
} }
STATUS current STATUS current
skipping to change at page 30, line 25 skipping to change at page 30, line 45
FROM MPLS-TC-STD-MIB -- [RFC3811] FROM MPLS-TC-STD-MIB -- [RFC3811]
RowPointer RowPointer
FROM SNMPv2-TC -- [RFC2579] FROM SNMPv2-TC -- [RFC2579]
mplsXCIndex, mplsXCInSegmentIndex, mplsXCOutSegmentIndex, mplsXCIndex, mplsXCInSegmentIndex, mplsXCOutSegmentIndex,
mplsInterfaceGroup, mplsInSegmentGroup, mplsOutSegmentGroup, mplsInterfaceGroup, mplsInSegmentGroup, mplsOutSegmentGroup,
mplsXCGroup, mplsPerfGroup, mplsLsrNotificationGroup mplsXCGroup, mplsPerfGroup, mplsLsrNotificationGroup
FROM MPLS-LSR-STD-MIB; -- [RFC3813] FROM MPLS-LSR-STD-MIB; -- [RFC3813]
mplsLsrExtStdMIB MODULE-IDENTITY mplsLsrExtStdMIB MODULE-IDENTITY
LAST-UPDATED LAST-UPDATED
"201304130000Z" -- April 13, 2013 "201311010000Z" -- November 01, 2013
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,
350 Holger way, San Jose, CA, USA 350 Holger way, San Jose, CA, USA
Email: venkat.mahalingams@gmail.com Email: venkat.mahalingams@gmail.com
Kannan KV Sampath Kannan KV Sampath
skipping to change at page 31, line 14 skipping to change at page 31, line 36
"Copyright (c) 2013 IETF Trust and the persons identified "Copyright (c) 2013 IETF Trust and the persons identified
as the document authors. All rights reserved. as the document authors. All rights reserved.
This MIB module contains generic object definitions for This MIB module contains generic object definitions for
MPLS LSR in transport networks." MPLS LSR in transport networks."
-- Revision history. -- Revision history.
REVISION REVISION
"201304130000Z" -- April 13, 2013 "201311010000Z" -- November 01, 2013
DESCRIPTION DESCRIPTION
"MPLS LSR specific MIB objects extension" "MPLS LSR specific MIB objects extension"
::= { mplsStdMIB xxx } -- xxx to be replaced with correct value ::= { mplsStdMIB xxx } -- xxx to be replaced with correct value
-- notifications
mplsLsrExtNotifications OBJECT IDENTIFIER ::= { mplsLsrExtStdMIB 0 }
-- tables, scalars -- tables, scalars
mplsLsrExtObjects OBJECT IDENTIFIER mplsLsrExtObjects OBJECT IDENTIFIER
::= { mplsLsrExtStdMIB 0 } ::= { mplsLsrExtStdMIB 1 }
-- conformance -- conformance
mplsLsrExtConformance OBJECT IDENTIFIER mplsLsrExtConformance OBJECT IDENTIFIER
::= { mplsLsrExtStdMIB 1 } ::= { mplsLsrExtStdMIB 2 }
-- MPLS LSR common objects -- MPLS LSR common objects
mplsXCExtTable OBJECT-TYPE mplsXCExtTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsXCExtEntry SYNTAX SEQUENCE OF MplsXCExtEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table sparse augments the mplsXCTable of "This table sparse augments the mplsXCTable of
MPLS-LSR-STD-MIB [RFC3813] to provide MPLS-TP specific MPLS-LSR-STD-MIB [RFC3813] to provide MPLS-TP specific
information about associated tunnel information" information about associated tunnel information"
skipping to change at page 34, line 22 skipping to change at page 34, line 45
} }
MODULE -- this module MODULE -- this module
GROUP mplsXCExtReadOnlyObjectsGroup GROUP mplsXCExtReadOnlyObjectsGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for devices which support "This group is mandatory for devices which support
Opposite direction XC configuration of tunnels." Opposite direction XC configuration of tunnels."
-- mplsXCExtTable -- mplsXCExtTable
OBJECT mplsXCExtOppositeDirXCPtr OBJECT mplsXCExtOppositeDirXCPtr
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required. "Write access is not required.
This object indicates the pointer to the opposite This object indicates the pointer to the opposite
direction XC entry. The only valid value for XC direction XC entry. The only valid value for XC
Pointer is mplsXCTable entry." Pointer is mplsXCTable entry."
::= { mplsLsrExtCompliances 2 } ::= { mplsLsrExtCompliances 2 }
-- Units of conformance. -- Units of conformance.
mplsXCExtGroup OBJECT-GROUP mplsXCExtGroup OBJECT-GROUP
OBJECTS { OBJECTS {
mplsXCExtTunnelPointer, mplsXCExtTunnelPointer,
mplsXCExtOppositeDirXCPtr mplsXCExtOppositeDirXCPtr
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object should be supported in order to access "This object should be supported in order to access
the tunnel entry from XC entry." the tunnel entry from XC entry."
::= { mplsLsrExtGroups 1 } ::= { mplsLsrExtGroups 1 }
mplsXCExtReadOnlyObjectsGroup OBJECT-GROUP mplsXCExtReadOnlyObjectsGroup OBJECT-GROUP
OBJECTS { mplsXCExtOppositeDirXCPtr } OBJECTS {
mplsXCExtTunnelPointer,
mplsXCExtOppositeDirXCPtr
}
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This Object is needed to associate the opposite direction "This Object is needed to associate the opposite direction
(forward/reverse) XC entry." (forward/reverse) XC entry."
::= { mplsLsrExtGroups 2 } ::= { mplsLsrExtGroups 2 }
-- MPLS-LSR-EXT-STD-MIB module ends -- MPLS-LSR-EXT-STD-MIB module ends
END END
13. MPLS Tunnel Extension MIB definitions 13. MPLS Tunnel Extension MIB definitions
skipping to change at page 35, line 33 skipping to change at page 36, line 17
mplsStdMIB, MplsTunnelIndex, MplsTunnelInstanceIndex, mplsStdMIB, MplsTunnelIndex, MplsTunnelInstanceIndex,
MplsExtendedTunnelId MplsExtendedTunnelId
FROM MPLS-TC-STD-MIB -- [RFC3811] FROM MPLS-TC-STD-MIB -- [RFC3811]
mplsTunnelIndex, mplsTunnelInstance, mplsTunnelIngressLSRId, mplsTunnelIndex, mplsTunnelInstance, mplsTunnelIngressLSRId,
mplsTunnelEgressLSRId mplsTunnelEgressLSRId
FROM MPLS-TE-STD-MIB -- [RFC3812] FROM MPLS-TE-STD-MIB -- [RFC3812]
; ;
mplsTeExtStdMIB MODULE-IDENTITY mplsTeExtStdMIB MODULE-IDENTITY
LAST-UPDATED LAST-UPDATED
"201304130000Z" -- April 13, 2013 "201311010000Z" -- November 01, 2013
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,
350 Holger way, San Jose, CA, USA 350 Holger way, San Jose, CA, USA
Email: venkat.mahalingams@gmail.com Email: venkat.mahalingams@gmail.com
Kannan KV Sampath Kannan KV Sampath
skipping to change at page 36, line 22 skipping to change at page 37, line 6
DESCRIPTION DESCRIPTION
"Copyright (c) 2013 IETF Trust and the persons identified "Copyright (c) 2013 IETF Trust and the persons identified
as the document authors. All rights reserved. as the document authors. All rights reserved.
This MIB module contains generic object definitions for This MIB module contains generic object definitions for
MPLS Traffic Engineering in transport networks." MPLS Traffic Engineering in transport networks."
-- Revision history. -- Revision history.
REVISION REVISION
"201304130000Z" -- April 13, 2013 "201311010000Z" -- November 01, 2013
DESCRIPTION DESCRIPTION
"MPLS TE MIB objects extension" "MPLS TE MIB objects extension"
::= { mplsStdMIB xxx } -- xxx to be replaced ::= { mplsStdMIB xxx } -- xxx to be replaced
-- with correct value -- with correct value
-- Top level components of this MIB module. -- Top level components of this MIB module.
-- notifications
mplsTeExtNotifications OBJECT IDENTIFIER ::= { mplsTeExtStdMIB 0 }
-- tables, scalars -- tables, scalars
mplsTeExtObjects OBJECT IDENTIFIER mplsTeExtObjects OBJECT IDENTIFIER
::= { mplsTeExtStdMIB 0 } ::= { mplsTeExtStdMIB 1 }
-- conformance -- conformance
mplsTeExtConformance OBJECT IDENTIFIER mplsTeExtConformance OBJECT IDENTIFIER
::= { mplsTeExtStdMIB 1 } ::= { mplsTeExtStdMIB 2 }
-- Start of MPLS Transport Profile Node configuration table -- Start of MPLS Transport Profile Node configuration table
mplsTunnelExtNodeConfigTable OBJECT-TYPE mplsTunnelExtNodeConfigTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsTunnelExtNodeConfigEntry SYNTAX SEQUENCE OF MplsTunnelExtNodeConfigEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table allows the operator to map a node or "This table allows the operator to map a node or
LSR Identifier (IP compatible [Global_ID::Node_ID] or LSR Identifier (IP compatible [Global_ID::Node_ID] or
ICC based [CC::ICC]) with a local identifier. ICC based [ICC_Operator_ID::Node_ID]) with a local
identifier.
This table is created to reuse the existing This table is created to reuse the existing
mplsTunnelTable for MPLS based transport network mplsTunnelTable for MPLS based transport network
tunnels also. tunnels also.
Since the MPLS tunnel's Ingress/Egress LSR identifiers' Since the MPLS tunnel's Ingress/Egress LSR identifiers'
size (Unsigned32) value is not compatible for size (Unsigned32) value is not compatible for
MPLS-TP tunnel i.e. Global_ID::Node_ID of size 8 bytes and MPLS-TP tunnel i.e. Global_ID::Node_ID of size 8 bytes and
CC::ICC of size 8 bytes, there exists a need to map the ICC_Operator_ID::Node_ID of size 12 bytes, there exists a
Global_ID::Node_ID or CC::ICC with the local identifier of need to map the Global_ID::Node_ID or ICC_Operator_ID::Node_ID
size 4 bytes (Unsigned32) value in order to index with the local identifier of size 4 bytes (Unsigned32) value
(Ingress/Egress LSR identifier) the existing in order to index (Ingress/Egress LSR identifier)
mplsTunnelTable." the existing mplsTunnelTable."
::= { mplsTeExtObjects 1 } ::= { mplsTeExtObjects 1 }
mplsTunnelExtNodeConfigEntry OBJECT-TYPE mplsTunnelExtNodeConfigEntry OBJECT-TYPE
SYNTAX MplsTunnelExtNodeConfigEntry SYNTAX MplsTunnelExtNodeConfigEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table represents a mapping
identification for the operator or service provider
with node or LSR.
"An entry in this table represents a mapping As per [RFC6370], IP compatible mapping is represented
identification for the operator or service provider as Global_ID::Node_ID.
with node or LSR.
As per [RFC6370], IP compatible mapping is
represented as Global_ID::Node_ID.
As per [I-D.ietf-mpls-tp-itu-t-identifiers], ICC As per [RFC6923], the CC and the ICC form the ICC_Operator_ID
compatible mapping is represented as CC::ICC. as CC::ICC and ICC compatible mapping is represented
as ICC_Operator_ID::Node_ID.
Note: Each entry in this table should have a unique Note: Each entry in this table should have a unique
[Global_ID and Node_ID] or [CC and ICC] combination." [Global_ID and Node_ID] or [CC::ICC and Node_ID] combination."
INDEX { mplsTunnelExtNodeConfigLocalId } INDEX { mplsTunnelExtNodeConfigLocalId }
::= { mplsTunnelExtNodeConfigTable 1 } ::= { mplsTunnelExtNodeConfigTable 1 }
MplsTunnelExtNodeConfigEntry ::= SEQUENCE { MplsTunnelExtNodeConfigEntry ::= SEQUENCE {
mplsTunnelExtNodeConfigLocalId MplsExtendedTunnelId, mplsTunnelExtNodeConfigLocalId MplsExtendedTunnelId,
mplsTunnelExtNodeConfigGlobalId MplsGlobalId, mplsTunnelExtNodeConfigGlobalId MplsGlobalId,
mplsTunnelExtNodeConfigNodeId MplsNodeId,
mplsTunnelExtNodeConfigCcId MplsCcId, mplsTunnelExtNodeConfigCcId MplsCcId,
mplsTunnelExtNodeConfigIccId MplsIccId, mplsTunnelExtNodeConfigIccId MplsIccId,
mplsTunnelExtNodeConfigIccValid TruthValue, mplsTunnelExtNodeConfigNodeId MplsNodeId,
mplsTunnelExtNodeConfigRowStatus RowStatus, mplsTunnelExtNodeConfigIccValid TruthValue,
mplsTunnelExtNodeConfigStorageType StorageType mplsTunnelExtNodeConfigStorageType StorageType,
mplsTunnelExtNodeConfigRowStatus RowStatus
} }
mplsTunnelExtNodeConfigLocalId OBJECT-TYPE mplsTunnelExtNodeConfigLocalId OBJECT-TYPE
SYNTAX MplsExtendedTunnelId SYNTAX MplsExtendedTunnelId
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is used in accommodating the bigger "This object is used in accommodating the bigger
size Global_ID::Node_ID and/or CC::ICC with lower size LSR size Global_ID::Node_ID and/or the ICC_Operator_ID::Node_ID
identifier in order to index the mplsTunnelTable. with lower size LSR identifier in order to index
the mplsTunnelTable.
The Local Identifier is configured between 0 and 16777215, The Local Identifier is configured between 0 and 16777215,
as valid IP address range starts from 16777216(01.00.00.00). as valid IP address range starts from 16777216(01.00.00.00).
This range is chosen to identify the mplsTunnelTable's This range is chosen to identify the mplsTunnelTable's
Ingress/Egress LSR-id is IP address or Local identifier, Ingress/Egress LSR-id is IP address or Local identifier,
if the configured range is not IP address, operator is if the configured range is not IP address, operator is
expected to retrieve the complete information expected to retrieve the complete information
(Global_ID::Node_ID or CC::ICC) from (Global_ID::Node_ID or ICC_Operator_ID::Node_ID) from
mplsTunnelExtNodeConfigTable. mplsTunnelExtNodeConfigTable.
This way, existing mplsTunnelTable is reused for This way, existing mplsTunnelTable is reused for
bidirectional tunnel extensions for MPLS based transport bidirectional tunnel extensions for MPLS based transport
networks. networks.
This Local Identifier allows the operator to assign This Local Identifier allows the operator to assign
a unique identifier to map Global_ID::Node_ID and/or a unique identifier to map Global_ID::Node_ID and/or
CC::ICC. As this Local Identifier is unique within the node ICC_Operator_ID::Node_ID. As this Local Identifier is unique
and the same syntax of this object can be used for MPLS TE within the node and the same syntax of this object can be
tunnel also, it is up to the operator/local management used for MPLS TE tunnel also, it is up to the operator/local
entity to choose the non-conflicting value for indexing management entity to choose the non-conflicting value for
the MPLS and MPLS-TP tunnel entries." indexing the MPLS and MPLS-TP tunnel entries."
::= { mplsTunnelExtNodeConfigEntry 1 } ::= { mplsTunnelExtNodeConfigEntry 1 }
mplsTunnelExtNodeConfigGlobalId OBJECT-TYPE mplsTunnelExtNodeConfigGlobalId OBJECT-TYPE
SYNTAX MplsGlobalId SYNTAX MplsGlobalId
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the Global Operator Identifier. "This object indicates the Global Operator Identifier.
This object has no meaning when This object has no meaning when
mplsTunnelExtNodeConfigIccValid is set true." mplsTunnelExtNodeConfigIccValid is set true."
REFERENCE REFERENCE
"MPLS Transport Profile (MPLS-TP) Identifiers [RFC6370] "MPLS Transport Profile (MPLS-TP) Identifiers [RFC6370]
Section 3." Section 3."
::= { mplsTunnelExtNodeConfigEntry 2 } ::= { mplsTunnelExtNodeConfigEntry 2 }
mplsTunnelExtNodeConfigNodeId OBJECT-TYPE
SYNTAX MplsNodeId
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object indicates the Node_ID within the scope
of a Global_ID. This object has no meaning when
mplsTunnelExtNodeConfigIccValid is set true."
REFERENCE
"MPLS Transport Profile (MPLS-TP) Identifiers [RFC6370]
Section 4."
::= { mplsTunnelExtNodeConfigEntry 3 }
mplsTunnelExtNodeConfigCcId OBJECT-TYPE mplsTunnelExtNodeConfigCcId OBJECT-TYPE
SYNTAX MplsCcId SYNTAX MplsCcId
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object allows the operator or service provider to "This object allows the operator or service provider to
configure a unique MPLS-TP ITU-T Country Code (CC) configure a unique MPLS-TP ITU-T Country Code (CC)
either for Ingress ID or Egress ID. either for Ingress ID or Egress ID.
This object has no meaning when This object has no meaning when
mplsTunnelExtNodeConfigIccValid is set false." mplsTunnelExtNodeConfigIccValid is set false."
REFERENCE REFERENCE
"MPLS-TP Identifiers Following ITU-T Conventions, "MPLS-TP Identifiers Following ITU-T Conventions,
draft-ietf-mpls-tp-itu-t-identifiers-08 (work in [RFC6923] Section 3"
progress), February 2013. Section 3" ::= { mplsTunnelExtNodeConfigEntry 3 }
::= { mplsTunnelExtNodeConfigEntry 4 }
mplsTunnelExtNodeConfigIccId OBJECT-TYPE mplsTunnelExtNodeConfigIccId OBJECT-TYPE
SYNTAX MplsIccId SYNTAX MplsIccId
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object allows the operator or service provider to "This object allows the operator or service provider to
configure a unique MPLS-TP ITU-T Carrier Code (ICC) configure a unique MPLS-TP ITU-T Carrier Code (ICC)
either for Ingress ID or Egress ID. either for Ingress ID or Egress ID.
This object has no meaning when This object has no meaning when
mplsTunnelExtNodeConfigIccValid is set false." mplsTunnelExtNodeConfigIccValid is set false."
REFERENCE REFERENCE
"MPLS-TP Identifiers Following ITU-T Conventions, "MPLS-TP Identifiers Following ITU-T Conventions,
draft-ietf-mpls-tp-itu-t-identifiers-08 (work in [RFC6923] Section 3"
progress), February 2013. Section 3" ::= { mplsTunnelExtNodeConfigEntry 4 }
::= { mplsTunnelExtNodeConfigEntry 5 }
mplsTunnelExtNodeConfigNodeId OBJECT-TYPE
SYNTAX MplsNodeId
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object indicates the Node_ID within the scope
of a Global_ID or ICC_Operator_ID."
REFERENCE
"MPLS Transport Profile (MPLS-TP) Identifiers [RFC6370]
Section 4."
::= { mplsTunnelExtNodeConfigEntry 5 }
mplsTunnelExtNodeConfigIccValid OBJECT-TYPE mplsTunnelExtNodeConfigIccValid OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Denotes whether or not this entry uses "Denotes whether or not this entry uses
mplsTunnelExtNodeConfigCcId and mplsTunnelExtNodeConfigCcId,
mplsTunnelExtNodeConfigIccId for mapping mplsTunnelExtNodeConfigIccId and
mplsTunnelExtNodeConfigNodeId for mapping
the ICC based identifiers with the local identifier. the ICC based identifiers with the local identifier.
Note that if this variable is set to false then the Note that if this variable is set to false then the
mplsTunnelExtNodeConfigGlobalId and mplsTunnelExtNodeConfigGlobalId and
mplsTunnelExtNodeConfigNodeId objects should have mplsTunnelExtNodeConfigNodeId objects should have
the valid information." the valid information."
DEFVAL { false } DEFVAL { false }
::= { mplsTunnelExtNodeConfigEntry 6 } ::= { mplsTunnelExtNodeConfigEntry 6 }
mplsTunnelExtNodeConfigStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This variable indicates the storage type for this
object.
Conceptual rows having the value 'permanent'
need not allow write-access to any columnar
objects in the row."
DEFVAL { volatile }
::= { mplsTunnelExtNodeConfigEntry 7 }
mplsTunnelExtNodeConfigRowStatus OBJECT-TYPE mplsTunnelExtNodeConfigRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object allows the operator to create, modify, "This object allows the operator to create, modify,
and/or delete a row in this table." and/or delete a row in this table."
::= { mplsTunnelExtNodeConfigEntry 7 }
mplsTunnelExtNodeConfigStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This variable indicates the storage type for this
object.
Conceptual rows having the value 'permanent'
need not allow write-access to any columnar
objects in the row."
DEFVAL { volatile }
::= { mplsTunnelExtNodeConfigEntry 8 } ::= { mplsTunnelExtNodeConfigEntry 8 }
-- End of MPLS Transport Profile Node configuration table -- End of MPLS Transport Profile Node configuration table
-- Start of MPLS Transport Profile Node IP compatible -- Start of MPLS Transport Profile Node IP compatible
-- mapping table -- mapping table
mplsTunnelExtNodeIpMapTable OBJECT-TYPE mplsTunnelExtNodeIpMapTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsTunnelExtNodeIpMapEntry SYNTAX SEQUENCE OF MplsTunnelExtNodeIpMapEntry
skipping to change at page 42, line 26 skipping to change at page 43, line 15
-- End MPLS Transport Profile Node IP compatible table -- End MPLS Transport Profile Node IP compatible table
-- Start of MPLS Transport Profile Node ICC based table -- Start of MPLS Transport Profile Node ICC based table
mplsTunnelExtNodeIccMapTable OBJECT-TYPE mplsTunnelExtNodeIccMapTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsTunnelExtNodeIccMapEntry SYNTAX SEQUENCE OF MplsTunnelExtNodeIccMapEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This read-only table allows the operator to retrieve "This read-only table allows the operator to retrieve
the local identifier for a given CC::ICC in an ICC the local identifier for a given ICC_Operator_ID::Node_ID
operator environment. in an ICC operator environment.
This table MAY be used in on-demand and/or proactive This table MAY be used in on-demand and/or proactive
OAM operations to get the Ingress/Egress LSR OAM operations to get the Ingress/Egress LSR
identifier (Local Identifier) from Src-ICC identifier (Local Identifier) from Src-ICC
or Dst-ICC and the Ingress and Egress LSR or Dst-ICC and the Ingress and Egress LSR
identifiers are used to retrieve the tunnel entry. identifiers are used to retrieve the tunnel entry.
This table returns nothing when the associated entry This table returns nothing when the associated entry
is not defined in mplsTunnelExtNodeConfigTable." is not defined in mplsTunnelExtNodeConfigTable."
::= { mplsTeExtObjects 3 } ::= { mplsTeExtObjects 3 }
mplsTunnelExtNodeIccMapEntry OBJECT-TYPE mplsTunnelExtNodeIccMapEntry OBJECT-TYPE
SYNTAX MplsTunnelExtNodeIccMapEntry SYNTAX MplsTunnelExtNodeIccMapEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table represents a mapping of CC::ICC "An entry in this table represents a mapping of
with the local identifier. ICC_Operator_ID::Node_ID with the local identifier.
An entry in this table is created automatically when An entry in this table is created automatically when
the Local identifier is associated with CC::ICC in the Local identifier is associated with
ICC_Operator_ID::Node_ID in
the mplsTunnelExtNodeConfigTable." the mplsTunnelExtNodeConfigTable."
INDEX { mplsTunnelExtNodeIccMapCcId, INDEX { mplsTunnelExtNodeIccMapCcId,
mplsTunnelExtNodeIccMapIccId } mplsTunnelExtNodeIccMapIccId,
mplsTunnelExtNodeIccMapNodeId }
::= { mplsTunnelExtNodeIccMapTable 1 } ::= { mplsTunnelExtNodeIccMapTable 1 }
MplsTunnelExtNodeIccMapEntry ::= SEQUENCE { MplsTunnelExtNodeIccMapEntry ::= SEQUENCE {
mplsTunnelExtNodeIccMapCcId MplsCcId, mplsTunnelExtNodeIccMapCcId MplsCcId,
mplsTunnelExtNodeIccMapIccId MplsIccId, mplsTunnelExtNodeIccMapIccId MplsIccId,
mplsTunnelExtNodeIccMapNodeId MplsNodeId,
mplsTunnelExtNodeIccMapLocalId MplsExtendedTunnelId mplsTunnelExtNodeIccMapLocalId MplsExtendedTunnelId
} }
mplsTunnelExtNodeIccMapCcId OBJECT-TYPE mplsTunnelExtNodeIccMapCcId OBJECT-TYPE
SYNTAX MplsCcId SYNTAX MplsCcId
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object allows the operator or service provider to "This object allows the operator or service provider to
configure a unique MPLS-TP ITU-T Country Code (CC) configure a unique MPLS-TP ITU-T Country Code (CC)
skipping to change at page 43, line 40 skipping to change at page 44, line 32
to configure a unique MPLS-TP ITU-T Carrier to configure a unique MPLS-TP ITU-T Carrier
Code (ICC) either for Ingress or Egress LSR ID. Code (ICC) either for Ingress or Egress LSR ID.
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 character being either alphabetic (i.e. A-Z) or
numeric (i.e. 0-9) characters. Alphabetic characters numeric (i.e. 0-9) characters. Alphabetic characters
in the ICC should be represented with upper case in the ICC should be represented with upper case
letters." letters."
::= { mplsTunnelExtNodeIccMapEntry 2 } ::= { mplsTunnelExtNodeIccMapEntry 2 }
mplsTunnelExtNodeIccMapNodeId OBJECT-TYPE
SYNTAX MplsNodeId
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This object indicates the Node_ID within the
ICC based operator."
::= { mplsTunnelExtNodeIccMapEntry 3}
mplsTunnelExtNodeIccMapLocalId OBJECT-TYPE mplsTunnelExtNodeIccMapLocalId OBJECT-TYPE
SYNTAX MplsExtendedTunnelId SYNTAX MplsExtendedTunnelId
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains an ICC based local identifier "This object contains an ICC based local identifier
which is defined in mplsTunnelExtNodeConfigTable." which is defined in mplsTunnelExtNodeConfigTable."
::= { mplsTunnelExtNodeIccMapEntry 4 }
::= { mplsTunnelExtNodeIccMapEntry 3 }
-- End MPLS Transport Profile Node ICC based table -- End MPLS Transport Profile Node ICC based table
-- Start of MPLS Tunnel table extension -- Start of MPLS Tunnel table extension
mplsTunnelExtTable OBJECT-TYPE mplsTunnelExtTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsTunnelExtEntry SYNTAX SEQUENCE OF MplsTunnelExtEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table represents extensions to mplsTunnelTable "This table represents extensions to mplsTunnelTable
skipping to change at page 44, line 33 skipping to change at page 45, line 33
mplsTunnelTable is reused for forming the LSP_ID mplsTunnelTable is reused for forming the LSP_ID
as follows, as follows,
Source Tunnel_Num is mapped with mplsTunnelIndex, Source Tunnel_Num is mapped with mplsTunnelIndex,
Source Node_ID is mapped with Source Node_ID is mapped with
mplsTunnelIngressLSRId, Destination Node_ID is mplsTunnelIngressLSRId, Destination Node_ID is
mapped with mplsTunnelEgressLSRId LSP_Num is mapped with mapped with mplsTunnelEgressLSRId LSP_Num is mapped with
mplsTunnelInstance. mplsTunnelInstance.
Source Global_ID::Node_ID and/or CC::ICC and Destination Source Global_ID::Node_ID and/or ICC_Operator_ID::Node_ID and
Global_ID::Node_ID and/or CC::ICC are maintained in the Destination Global_ID::Node_ID and/or ICC_Operator_ID::Node-ID
mplsTunnelExtNodeConfigTable and are maintained in the mplsTunnelExtNodeConfigTable and
mplsTunnelExtNodeConfigLocalId is used to create an entry mplsTunnelExtNodeConfigLocalId is used to create an entry
in mplsTunnelTable." in mplsTunnelTable."
REFERENCE REFERENCE
"MPLS Transport Profile (MPLS-TP) Identifiers [RFC6370]." "MPLS Transport Profile (MPLS-TP) Identifiers [RFC6370]."
::= { mplsTeExtObjects 4 } ::= { mplsTeExtObjects 4 }
mplsTunnelExtEntry OBJECT-TYPE mplsTunnelExtEntry OBJECT-TYPE
SYNTAX MplsTunnelExtEntry SYNTAX MplsTunnelExtEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
skipping to change at page 47, line 34 skipping to change at page 48, line 34
DEFVAL { false } DEFVAL { false }
::= { mplsTunnelExtEntry 5 } ::= { mplsTunnelExtEntry 5 }
mplsTunnelExtIngressLSRLocalIdValid OBJECT-TYPE mplsTunnelExtIngressLSRLocalIdValid OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object denotes whether the mplsTunnelIngressLSRId "This object denotes whether the mplsTunnelIngressLSRId
contains the local value, which is used to reference contains the local value, which is used to reference
the complete Ingress Global_ID::Node_ID or ICC from the complete Ingress Global_ID::Node_ID or ICC_Operator_ID
the mplsTunnelExtNodeConfigTable. from the mplsTunnelExtNodeConfigTable.
If this object is set to FALSE, mplsTunnelExtNodeConfigTable If this object is set to FALSE, mplsTunnelExtNodeConfigTable
will not contain an entry to reference local identifier with will not contain an entry to reference local identifier with
Global_ID::Node_ID or ICC value. Global_ID::Node_ID or ICC_Operator_ID::Node_ID value.
This object is set to FALSE for legacy implementations like This object is set to FALSE for legacy implementations like
MPLS TE tunnels where mplsTunnelIngressId itself provides MPLS TE tunnels where mplsTunnelIngressId itself provides
complete Ingress LSRId." complete Ingress LSRId."
REFERENCE REFERENCE
"MPLS-TE-STD-MIB [RFC3812], Section 11. "MPLS-TE-STD-MIB [RFC3812], Section 11.
mplsTunnelIngressLSRId object in mplsTunnelTable." mplsTunnelIngressLSRId object in mplsTunnelTable."
DEFVAL { false } DEFVAL { false }
::= { mplsTunnelExtEntry 6 } ::= { mplsTunnelExtEntry 6 }
mplsTunnelExtEgressLSRLocalIdValid OBJECT-TYPE mplsTunnelExtEgressLSRLocalIdValid OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object denotes whether the mplsTunnelEgressLSRId "This object denotes whether the mplsTunnelEgressLSRId
contains the local value, which is used to reference contains the local value, which is used to reference
the complete Egress Global_ID::Node_ID or ICC from the complete Egress Global_ID::Node_ID or
ICC_Operator_ID::Node_ID from
the mplsTunnelExtNodeConfigTable. the mplsTunnelExtNodeConfigTable.
If this object is set to FALSE, mplsTunnelExtNodeConfigTable If this object is set to FALSE, mplsTunnelExtNodeConfigTable
will not contain an entry to reference local identifier with will not contain an entry to reference local identifier with
Global_ID::Node_ID or ICC value. Global_ID::Node_ID or ICC_Operator_ID::Node_ID value.
This object is set to FALSE for legacy implementations like This object is set to FALSE for legacy implementations like
MPLS TE tunnels where mplsTunnelEgressId itself provides MPLS TE tunnels where mplsTunnelEgressId itself provides
complete Egress LSRId." complete Egress LSRId."
REFERENCE REFERENCE
"MPLS-TE-STD-MIB [RFC3812], Section 11. "MPLS-TE-STD-MIB [RFC3812], Section 11.
mplsTunnelEgressLSRId object in mplsTunnelTable." mplsTunnelEgressLSRId object in mplsTunnelTable."
DEFVAL { false } DEFVAL { false }
::= { mplsTunnelExtEntry 7 } ::= { mplsTunnelExtEntry 7 }
skipping to change at page 51, line 9 skipping to change at page 52, line 9
-- LSRs that originate/terminate MPLS-TP tunnels. -- LSRs that originate/terminate MPLS-TP tunnels.
-- In addition, depending on the type of tunnels -- In addition, depending on the type of tunnels
-- supported, other groups become mandatory as -- supported, other groups become mandatory as
-- explained below. -- explained below.
MANDATORY-GROUPS { MANDATORY-GROUPS {
mplsTunnelExtGroup mplsTunnelExtGroup
} }
GROUP mplsTunnelExtIpOperatorGroup
DESCRIPTION
"This group is mandatory for devices which support
configuration of IP based identifier tunnels."
GROUP mplsTunnelExtIccOperatorGroup
DESCRIPTION
"This group is mandatory for devices which support
configuration of ICC based tunnels."
::= { mplsTeExtCompliances 1 } ::= { mplsTeExtCompliances 1 }
-- Compliance requirement for read-only implementations. -- Compliance requirement for read-only implementations.
mplsTeExtModuleReadOnlyCompliance MODULE-COMPLIANCE mplsTeExtModuleReadOnlyCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Compliance statement for agents that provide full "Compliance statement for agents that only provide
support the MPLS-TE-EXT-STD-MIB module." read-only support for MPLS-TE-EXT-STD-MIB module."
MODULE -- this module MODULE -- this module
-- The mandatory group has to be implemented by all MANDATORY-GROUPS {
-- LSRs that originate/terminate MPLS-TP tunnels. mplsTunnelExtGroup
-- In addition, depending on the type of tunnels }
-- supported, other groups become mandatory as
-- explained below.
MANDATORY-GROUPS { GROUP mplsTunnelExtIpOperatorGroup
mplsTunnelExtGroup DESCRIPTION
} "This group is mandatory for devices which support
configuration of IP based identifier tunnels."
GROUP mplsTunnelExtIpOperatorGroup GROUP mplsTunnelExtIccOperatorGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for devices which support "This group is mandatory for devices which support
configuration of IP based identifier tunnels." configuration of ICC based tunnels."
GROUP mplsTunnelExtIccOperatorGroup -- mplsTunnelExtTable
DESCRIPTION OBJECT mplsTunnelExtOppositeDirPtr
"This group is mandatory for devices which support MIN-ACCESS read-only
configuration of ICC based tunnels." DESCRIPTION
"Write access is not required."
OBJECT mplsTunnelExtOppositeDirTnlValid
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT mplsTunnelExtDestTnlIndex
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT mplsTunnelExtDestTnlLspIndex
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT mplsTunnelExtDestTnlValid
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT mplsTunnelExtIngressLSRLocalIdValid
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT mplsTunnelExtEgressLSRLocalIdValid
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT mplsTunnelExtNodeConfigGlobalId
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT mplsTunnelExtNodeConfigNodeId
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT mplsTunnelExtNodeConfigStorageType
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT mplsTunnelExtNodeConfigRowStatus
SYNTAX RowStatus { active(1) }
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT mplsTunnelExtNodeConfigCcId
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT mplsTunnelExtNodeConfigIccId
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT mplsTunnelExtNodeConfigIccValid
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
::= { mplsTeExtCompliances 2 } ::= { mplsTeExtCompliances 2 }
-- Units of conformance. -- Units of conformance.
mplsTunnelExtGroup OBJECT-GROUP mplsTunnelExtGroup OBJECT-GROUP
OBJECTS { OBJECTS {
mplsTunnelExtOppositeDirPtr, mplsTunnelExtOppositeDirPtr,
mplsTunnelExtOppositeDirTnlValid, mplsTunnelExtOppositeDirTnlValid,
mplsTunnelExtDestTnlIndex, mplsTunnelExtDestTnlIndex,
skipping to change at page 52, line 38 skipping to change at page 54, line 42
DESCRIPTION DESCRIPTION
"Necessary, but not sufficient, set of objects to "Necessary, but not sufficient, set of objects to
implement tunnels. In addition, depending on the implement tunnels. In addition, depending on the
operating environment, the following groups are operating environment, the following groups are
mandatory." mandatory."
::= { mplsTeExtGroups 1 } ::= { mplsTeExtGroups 1 }
mplsTunnelExtIpOperatorGroup OBJECT-GROUP mplsTunnelExtIpOperatorGroup OBJECT-GROUP
OBJECTS { mplsTunnelExtNodeConfigGlobalId, OBJECTS { mplsTunnelExtNodeConfigGlobalId,
mplsTunnelExtNodeConfigNodeId, mplsTunnelExtNodeConfigNodeId,
mplsTunnelExtNodeConfigRowStatus, mplsTunnelExtNodeIpMapLocalId,
mplsTunnelExtNodeConfigStorageType, mplsTunnelExtNodeConfigStorageType,
mplsTunnelExtNodeIpMapLocalId mplsTunnelExtNodeConfigRowStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Object(s) needed to implement IP compatible tunnels." "Object(s) needed to implement IP compatible tunnels."
::= { mplsTeExtGroups 2 } ::= { mplsTeExtGroups 2 }
mplsTunnelExtIccOperatorGroup OBJECT-GROUP mplsTunnelExtIccOperatorGroup OBJECT-GROUP
OBJECTS { mplsTunnelExtNodeConfigCcId, OBJECTS { mplsTunnelExtNodeConfigCcId,
mplsTunnelExtNodeConfigIccId, mplsTunnelExtNodeConfigIccId,
mplsTunnelExtNodeConfigNodeId,
mplsTunnelExtNodeConfigIccValid, mplsTunnelExtNodeConfigIccValid,
mplsTunnelExtNodeConfigRowStatus, mplsTunnelExtNodeIccMapLocalId,
mplsTunnelExtNodeConfigStorageType, mplsTunnelExtNodeConfigStorageType,
mplsTunnelExtNodeIccMapLocalId mplsTunnelExtNodeConfigRowStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Object(s) needed to implement ICC based tunnels." "Object(s) needed to implement ICC based tunnels."
::= { mplsTeExtGroups 3 } ::= { mplsTeExtGroups 3 }
-- MPLS-TE-EXT-STD-MIB module ends -- MPLS-TE-EXT-STD-MIB module ends
END END
14. Security Consideration 14. Security Consideration
skipping to change at page 55, line 7 skipping to change at page 56, line 40
recommended. Instead, it is recommended to deploy SNMPv3 and to recommended. Instead, it is recommended to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give instance of this MIB module is properly configured to give
access to the objects only to those principles (users) that access to the objects only to those principles (users) that
have legitimate rights to indeed GET or SET (change/create/delete) have legitimate rights to indeed GET or SET (change/create/delete)
them. them.
15. IANA Considerations 15. IANA Considerations
As described in [MPLSMGMT] and as requested in the MPLS-TC-STD-MIB As described in [RFC4221], [RFC6639] and as requested in the MPLS-TC-
[RFC3811], MPLS related standards track MIB modules should be rooted STD-MIB [RFC3811], MPLS related standards track MIB modules should be
under the mplsStdMIB subtree. There are 4 MPLS MIB Modules contained rooted under the mplsStdMIB subtree. There are 4 MPLS MIB Modules
in this document, each of the following "IANA Considerations" contained in this document, each of the following "IANA
subsections requests IANA for a new assignment under the mplsStdMIB Considerations" subsections requests IANA for a new assignment under
subtree. New assignments can only be made via a Standards Action as the mplsStdMIB subtree. New assignments can only be made via a
specified in [RFC5226]. Standards Action as specified in [RFC5226].
15.1. IANA Considerations for MPLS-TC-EXT-STD-MIB 15.1. IANA Considerations for MPLS-TC-EXT-STD-MIB
IANA is requested to assign an OID { mplsStdMIB OID } to the MPLS-TC- IANA is requested to assign an OID { mplsStdMIB OID } to the MPLS-TC-
EXT-STD-MIB module specified in this document. EXT-STD-MIB module specified in this document.
15.2. IANA Considerations for MPLS-ID-STD-MIB 15.2. IANA Considerations for MPLS-ID-STD-MIB
IANA is requested to assign an OID { mplsStdMIB IOD } to the MPLS-ID- IANA is requested to assign an OID { mplsStdMIB OID } to the MPLS-ID-
STD-MIB module specified in this document. STD-MIB module specified in this document.
15.3. IANA Considerations for MPLS-LSR-EXT-STD-MIB 15.3. IANA Considerations for MPLS-LSR-EXT-STD-MIB
IANA is requested to assign an OID { mplsStdMIB OID } to the MPLS- IANA is requested to assign an OID { mplsStdMIB OID } to the MPLS-
LSR-EXT-STD-MIB module specified in this document. LSR-EXT-STD-MIB module specified in this document.
15.4. IANA Considerations for MPLS-TE-EXT-STD-MIB 15.4. IANA Considerations for MPLS-TE-EXT-STD-MIB
IANA is requested to assign an OID { mplsStdMIB OID } to the MPLS-TE- IANA is requested to assign an OID { mplsStdMIB OID } to the MPLS-TE-
EXT-STD-MIB module specified in this document. EXT-STD-MIB module specified in this document.
16. References 16. References
16.1. Normative References 16.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder, [RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Structure of Management Information Version 2 (SMIv2)", "Structure of Management Information Version 2 (SMIv2)",
STD 58, RFC 2578, April 1999. STD 58, RFC 2578, April 1999.
[RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder, [RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Textual Conventions for SMIv2", STD 58, RFC 2579, April "Textual Conventions for SMIv2", STD 58, RFC 2579, April
1999. 1999.
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Conformance Statements for SMIv2", STD 58, RFC 2580,
April 1999.
"Conformance Statements for SMIv2", STD 58, RFC 2580, [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol
April 1999. Label Switching Architecture", RFC 3031, January 2001.
[RFC3031] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol
Label Switching Architecture", RFC 3031, January 2001.
16.2. Informative References 16.2. Informative References
[MPLSMGMT] Nadeau, T., Srinivasan, C., and A. Farrel, "Multiprotocol [RFC3410] J. Case, R. Mundy, D. pertain, B.Stewart, "Introduction
Label Switching (MPLS) Management Overview", Work in and Applicability Statement for Internet Standard
Progress, September 2003. Management Framework", RFC 3410, December 2002.
[RFC5226] Narten, T. and H. Alvestrand., "Guidelines for Writing [RFC3811] Nadeau, T., Ed., and J. Cucchiara, Ed., "Definitions of
an IANA Considerations Section in RFCs", BCP 26, Textual Conventions (TCs) for Multiprotocol Label
RFC 5226, May 2008. Switching (MPLS) Management", RFC 3811, June 2004.
[RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau, [RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau,
"Multiprotocol Label Switching (MPLS) Traffic Engineering "Multiprotocol Label Switching (MPLS) Traffic Engineering
(TE) Management Information Base (MIB)", RFC 3812, June (TE) Management Information Base (MIB)", RFC 3812, June
2004. 2004.
[RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau, [RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau,
"Multiprotocol Label Switching (MPLS) Label Switching "Multiprotocol Label Switching (MPLS) Label Switching
(LSR) Router Management Information Base (MIB)", RFC 3813, (LSR) Router Management Information Base (MIB)", RFC 3813,
June 2004. June 2004.
[RFC3410] J. Case, R. Mundy, D. pertain, B.Stewart, "Introduction
and Applicability Statement for Internet Standard
Management Framework", RFC 3410, December 2002.
[RFC3811] Nadeau, T., Ed., and J. Cucchiara, Ed., "Definitions of [RFC4221] Nadeau, T., Srinivasan, C., and A. Farrel, "MSMGMT Label
Textual Conventions (TCs) for Multiprotocol Label Switching (MPLS) Management Overview", RFC 4221, November
Switching (MPLS) Management", RFC 3811, June 2004. 2005.
[RFC4802] Nadeau, T., Ed., and A. Farrel, Ed., "Generalized [RFC4802] Nadeau, T., Ed., and A. Farrel, Ed., "Generalized
Multiprotocol Label Switching (GMPLS) Traffic Engineering
Management Information Base", RFC 4802, February 2007.
Multiprotocol Label Switching (GMPLS) Traffic [RFC5226] Narten, T. and H. Alvestrand., "Guidelines for Writing an
Engineering Management Information Base", RFC IANA Considerations Section in RFCs", BCP 26, RFC 5226,
4802, February 2007. May 2008.
[RFC5654] Niven-Jenkins, B., Ed., Brungard, D., Ed., Betts, M., Ed.,
Sprecher, N., and S. Ueno, "Requirements of an MPLS
Transport Profile", RFC 5654, September 2009.
[RFC6370] Bocci, M., Swallow, G., and E. Gray, "MPLS Transport [RFC5654] Niven-Jenkins, B., Ed., Brungard, D., Ed., Betts, M.,
Profile (MPLS-TP) Identifiers", RFC 6370, September Ed.,Sprecher, N., and S. Ueno, "Requirements of an MPLS
2011. Transport Profile", RFC 5654, September 2009.
[I-D.ietf-mpls-tp-itu-t-identifiers] Winter, R., Gray, E., Helvoort, [RFC6370] Bocci, M., Swallow, G., and E. Gray, "MPLS Transport
H., and M. Betts, "MPLS-TP Identifiers Following ITU-T Profile (MPLS-TP) Identifiers", RFC 6370, September 2011.
Conventions", draft-ietf-mpls-tp-itu-t-identifiers-08
(work in progress), February 2013 [RFC6639] Venkatesan, M., King, D., "Multiprotocol Label Switching
Transport Profile (MPLS-TP) MIB-Based Management
Overview", RFC 6639, June 2012
[RFC6923] Winter, R., Gray, E., Helvoort, H., and M. Betts, "MPLS-TP
Identifiers Following ITU-T Conventions", RFC 6923, May
2013
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 and Randy Presuhn for Agrahara Kiran Koushik, Metrri Jain, Muly Ilan and Randy Presuhn for
their valuable comments. A special thanks to Joan Cucchiara for their valuable comments. A special thanks to Joan Cucchiara for
really getting the MIB modules into shape. really getting the MIB modules into shape.
18. Authors' Addresses 18. Authors' Addresses
 End of changes. 111 change blocks. 
279 lines changed or deleted 399 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/