draft-ietf-mpls-tp-te-mib-11.txt   rfc7453.txt 
Network Working Group Internet Engineering Task Force (IETF) M. Venkatesan
INTERNET-DRAFT M.Venkatesan Request for Comments: 7453 Dell Inc.
Intended Status: Standards Track Dell Inc. Category: Standards Track K. Sampath
Expires: June 21, 2015 Kannan KV Sampath ISSN: 2070-1721 Redeem
Redeem S. Aldrin
Sam K. Aldrin
Huawei Technologies Huawei Technologies
Thomas D. Nadeau T. Nadeau
Brocade Brocade
February 2015
December 18, 2014 MPLS Transport Profile (MPLS-TP) Traffic Engineering (TE)
Management Information Base (MIB)
MPLS-TP Traffic Engineering (TE) Management Information Base (MIB)
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 Routers to
support Multiprotocol Label Switching (MPLS) MIB modules for support Multiprotocol Label Switching (MPLS) MIB modules for
transport networks. transport networks.
Status of this Memo Status of This Memo
This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at This is an Internet Standards Track document.
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at This document is a product of the Internet Engineering Task Force
http://www.ietf.org/shadow.html. (IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
This Internet-Draft will expire on June 21, 2015. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc7453.
Copyright and License Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2015 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
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 ................................................6
3.3. Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . 7 3.3. Acronyms ...................................................6
4. Motivations . . . . . . . . . . . . . . . . . . . . . . . . . . 7 4. Motivations .....................................................6
5. Feature List . . . . . . . . . . . . . . . . . . . . . . . . . 7 5. Feature List ....................................................7
6. Outline . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 6. Outline .........................................................7
6.1 MIB Module Extensions . . . . . . . . . . . . . . . . . . . 9 6.1. MIB Module Extensions ......................................8
6.1.1 Summary of MIB Module changes . . . . . . . . . . . . . 9 6.1.1. Summary of MIB Module Changes .......................8
6.2 MPLS-TE-EXT-STD-MIB . . . . . . . . . . . . . . . . . . . . 10 6.2. MPLS-TE-EXT-STD-MIB ........................................9
6.2.1 mplsTunnelExtNodeConfigTable . . . . . . . . . . . . . . 10 6.2.1. mplsTunnelExtNodeConfigTable ........................9
6.2.2 mplsTunnelExtNodeIpMapTable . . . . . . . . . . . . . . 11 6.2.2. mplsTunnelExtNodeIpMapTable .........................9
6.2.3 mplsTunnelExtNodeIccMapTable . . . . . . . . . . . . . . 11 6.2.3. mplsTunnelExtNodeIccMapTable .......................10
6.2.4 mplsTunnelExtTable . . . . . . . . . . . . . . . . . . . 11 6.2.4. mplsTunnelExtTable .................................10
6.3 MPLS-TC-EXT-STD-MIB . . . . . . . . . . . . . . . . . . . . 11 6.3. MPLS-TC-EXT-STD-MIB .......................................10
6.4 MPLS-ID-STD-MIB . . . . . . . . . . . . . . . . . . . . . . 11 6.4. MPLS-ID-STD-MIB ...........................................10
6.5 MPLS-LSR-EXT-STD-MIB . . . . . . . . . . . . . . . . . . . . 12 6.5. MPLS-LSR-EXT-STD-MIB ......................................11
6.6 The Use of RowPointer . . . . . . . . . . . . . . . . . . . 12 6.6. The Use of RowPointer .....................................11
7. MIB Modules Interdependencies . . . . . . . . . . . . . . . . . 13 7. MIB Modules' Interdependencies .................................11
8. Dependencies between MIB Module Tables . . . . . . . . . . . . 14 8. Dependencies between MIB Module Tables .........................13
9. Example of MPLS-TP Tunnel Setup . . . . . . . . . . . . . . . . 15 9. Example of MPLS-TP Tunnel Setup ................................13
9.1. Example of MPLS-TP static co-routed bidirectional tunnel 9.1. Example of MPLS-TP Static Co-routed Bidirectional
setup . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Tunnel Setup ..............................................15
9.1.1. mplsTunnelEntry . . . . . . . . . . . . . . . . . . . . 16 9.1.1. mplsTunnelEntry ....................................15
9.1.2. mplsTunnelExtEntry . . . . . . . . . . . . . . . . . . 17 9.1.2. mplsTunnelExtEntry .................................16
9.1.3. Forward direction mplsOutSegmentEntry . . . . . . . . . 17 9.1.3. Forward-Direction mplsOutSegmentEntry ..............16
9.1.4. Reverse direction mplsInSegmentEntry . . . . . . . . . 17 9.1.4. Reverse-Direction mplsInSegmentEntry ...............16
9.1.5. Forward direction mplsXCEntry . . . . . . . . . . . . . 18 9.1.5. Forward-Direction mplsXCEntry ......................17
9.1.6. Reverse direction mplsXCEntry . . . . . . . . . . . . . 18 9.1.6. Reverse-Direction mplsXCEntry ......................17
9.1.7. Forward direction mplsXCExtEntry . . . . . . . . . . . 19 9.1.7. Forward-Direction mplsXCExtEntry ...................18
9.1.8. Reverse direction mplsXCExtEntry . . . . . . . . . . . 19 9.1.8. Reverse-Direction mplsXCExtEntry ...................18
9.2. Example of MPLS-TP static associated bidirectional tunnel 9.2. Example of MPLS-TP Static Associated Bidirectional
setup . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Tunnel Setup ..............................................18
9.2.1. Forward direction mplsTunnelEntry . . . . . . . . . . . 19 9.2.1. Forward-Direction mplsTunnelEntry ..................18
9.2.2. Forward direction mplsTunnelExtEntry . . . . . . . . . 20 9.2.2. Forward-Direction mplsTunnelExtEntry ...............19
9.2.3. Forward direction mplsOutSegmentTable . . . . . . . . . 20 9.2.3. Forward-Direction mplsOutSegmentTable ..............20
9.2.4. Forward direction mplsXCEntry . . . . . . . . . . . . . 21 9.2.4. Forward-Direction mplsXCEntry ......................20
9.2.5. Forward direction mplsXCExtEntry . . . . . . . . . . . 21 9.2.5. Forward-Direction mplsXCExtEntry ...................20
9.2.6. Reverse direction mplsTunnelEntry . . . . . . . . . . . 21 9.2.6. Reverse-Direction mplsTunnelEntry ..................21
9.2.7. Reverse direction mplsTunnelExtEntry . . . . . . . . . 22 9.2.7. Reverse-Direction mplsTunnelExtEntry ...............22
9.2.8. Reverse direction mplsInSegmentEntry . . . . . . . . . 22 9.2.8. Reverse-Direction mplsInSegmentEntry ...............22
9.2.9. Reverse direction mplsXCEntry . . . . . . . . . . . . . 23 9.2.9. Reverse-Direction mplsXCEntry ......................22
9.2.10. Reverse direction mplsXCExtEntry . . . . . . . . . . . 23 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
tunnel setup . . . . . . . . . . . . . . . . . . . . . . . 23 Bidirectional Tunnel Setup ................................23
9.3.1. mplsTunnelEntry . . . . . . . . . . . . . . . . . . . . 24 9.3.1. mplsTunnelEntry ....................................23
9.3.2. mplsTunnelExtEntry . . . . . . . . . . . . . . . . . . 24 9.3.2. mplsTunnelExtEntry .................................24
9.3.3. Forward direction mplsOutSegmentEntry . . . . . . . . . 25 9.3.3. Forward-Direction mplsOutSegmentEntry ..............24
9.3.4. Reverse direction mplsInSegmentEntry . . . . . . . . . 25 9.3.4. Reverse-Direction mplsInSegmentEntry ...............25
9.3.5. Forward direction mplsXCEntry . . . . . . . . . . . . . 25 9.3.5. Forward-Direction mplsXCEntry ......................25
9.3.6. Reverse direction mplsXCEntry . . . . . . . . . . . . . 25 9.3.6. Reverse-Direction mplsXCEntry ......................25
9.3.7. Forward direction mplsXCExtEntry . . . . . . . . . . . 25 9.3.7. Forward-Direction mplsXCExtEntry ...................25
9.3.8. Reverse direction mplsXCExtEntry . . . . . . . . . . . 26 9.3.8. Reverse-Direction mplsXCExtEntry ...................25
10. MPLS Textual Convention Extension MIB definitions . . . . . . 26 10. MPLS Textual Convention Extension MIB Definitions .............26
11. MPLS Identifier MIB definitions . . . . . . . . . . . . . . . 29 11. MPLS Identifier MIB Definitions ...............................29
12. MPLS LSR Extension MIB definitions . . . . . . . . . . . . . . 34 12. MPLS LSR Extension MIB Definitions ............................34
13. MPLS Tunnel Extension MIB definitions . . . . . . . . . . . . 39 13. MPLS Tunnel Extension MIB Definitions .........................39
14. Security Consideration . . . . . . . . . . . . . . . . . . . . 56 14. Security Considerations .......................................57
15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 57 15. IANA Considerations ...........................................58
15.1. IANA Considerations for MPLS-TC-EXT-STD-MIB . . . . . . . 58 15.1. IANA Considerations for MPLS-TC-EXT-STD-MIB ..............58
15.2. IANA Considerations for MPLS-ID-STD-MIB . . . . . . . . . 58 15.2. IANA Considerations for MPLS-ID-STD-MIB ..................58
15.3. IANA Considerations for MPLS-LSR-EXT-STD-MIB . . . . . . . 58 15.3. IANA Considerations for MPLS-LSR-EXT-STD-MIB .............58
15.4. IANA Considerations for MPLS-TE-EXT-STD-MIB . . . . . . . 58 15.4. IANA Considerations for MPLS-TE-EXT-STD-MIB ..............59
16. References . . . . . . . . . . . . . . . . . . . . . . . . . . 58 16. References ....................................................59
16.1. Normative References . . . . . . . . . . . . . . . . . . . 58 16.1. Normative References .....................................59
16.2. Informative References . . . . . . . . . . . . . . . . . 59 16.2. Informative References ...................................60
17. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 60 Acknowledgments ...................................................62
18. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 60 Authors' Addresses ................................................62
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)
use with network management protocols in the Internet community. In for use with network management protocols in the Internet community.
particular, it describes additional textual conventions and managed In particular, it describes additional textual conventions and
objects for Tunnels, Identifiers and Label Switching Router to support managed objects for tunnels, identifiers, and Label Switching Routers
Multiprotocol Label Switching (MPLS) MIB modules for transport networks. to support Multiprotocol Label Switching (MPLS) MIB modules for
MIB modules defined in this document extend the existing MPLS MIB transport networks. MIB modules defined in this document extend the
objects in such a way that they support MPLS-TP but also other MPLS existing MPLS MIB objects in such a way that they support the MPLS
networks as well. Hence, the MPLS-TP name is not included in the MIB Transport Profile (MPLS-TP) but also other MPLS networks. Hence,
module name. "MPLS-TP" is not included in the MIB module names.
As described in the MPLS Traffic Engineering (TE) Management Information As described in the MPLS Traffic Engineering (TE) MIB definition
Base (MIB) definition [RFC3812], MPLS traffic engineering is concerned [RFC3812], MPLS traffic engineering is concerned with the creation
with the creation and management of MPLS tunnels. This term is a and management of MPLS tunnels. This term is a shorthand for a
shorthand for a combination of one or more LSPs linking an ingress and combination of one or more LSPs linking an ingress and an egress LSR.
an egress LSR. Several types of point-to-point MPLS tunnels may be Several types of point-to-point MPLS tunnels may be constructed
constructed between a pair of LSRs A and B: between a pair of LSRs A and B:
- Unidirectional with a single LSP (say) from A to B. - Unidirectional with a single LSP (say, from A to B).
- Associated bidirectional consisting of two separately routed LSPs, - Associated bidirectional consisting of two separately routed
one linking A to B and the other linking B to A. Together the pair LSPs, one linking A to B and the other linking B to A.
provide a single logical bidirectional transport path. Together, the pair provides a single logical bidirectional
transport path.
- Co-routed bidirectional consisting of an associated bidirectional - Co-routed bidirectional consisting of an associated
tunnel but with the second LSP from B to A following the reverse bidirectional tunnel but with the second LSP from B to A
of the path of the LSP from A to B, in terms of both nodes and following the reverse of the path of the LSP from A to B, in
links. terms of both nodes and links.
Tunnels may be either statically configured by management action or Tunnels may be either statically configured by management action or
dynamically created using a LSP management protocol. dynamically created using an LSP management protocol.
The existing MPLS TE MIB [RFC3812] and the Generalized Multiprotocol The existing MPLS TE MIB [RFC3812] and the GMPLS TE MIB [RFC4802]
Label Switching (GMPLS) Traffic Engineering Management Information Base address only a subset of the combinations of statically and
[RFC4802] address only a subset of the combinations of statically and dynamically configured tunnel types, catering to statically
dynamically configured tunnel types, catering for statically configured configured unidirectional tunnels together with dynamically
unidirectional tunnels together with dynamically configured configured unidirectional and co-routed bidirectional tunnels. They
unidirectional and co-routed bidirectional tunnels. They are also are also restricted to two endpoint LSRs identified by IP addresses.
restricted to two end point LSRs identified by IP addresses.
The MPLS-TP TE MIB defined in this document extends the MIB modules The MPLS-TP TE MIB defined in this document extends the MIB modules
defined in [RFC3812] to cover all six combinations (that is adding defined in [RFC3812] to cover all six combinations (that is, adding
support for statically configured associated and co-routed bidirectional support for statically configured associated and co-routed
plus dynamically configured associated bidirectional tunnels). It also bidirectional plus dynamically configured associated bidirectional
extends support to end points that are identified other than with IP tunnels). It also extends support to endpoints that have identifiers
addresses. other than IP addresses.
This support is provided by a suite of four MIB modules that are to be This support is provided by a suite of four MIB modules that are to
used in conjunction with the MIB modules defined in [RFC3812] and the be used in conjunction with the MIB modules defined in [RFC3812] and
companion document [RFC3813] for MPLS Transport Profile (MPLS-TP) tunnel the companion document [RFC3813] for MPLS-TP tunnel management.
management.
At the time of writing, SNMP SET is no longer recommended as a way to At the time of writing, SNMP SET is no longer recommended as a way to
configure MPLS networks as was described in [RFC3812]. However, since configure MPLS networks as described in [RFC3812]. However, since
the MIB modules specified in this document extend and are intended to the MIB modules specified in this document extend and are intended to
work in parallel with the MIB modules for MPLS specified in [RFC3812], work in parallel with the MIB modules for MPLS specified in
certain objects defined here are specified with MAX-ACCESS of read-write [RFC3812], certain objects defined here are specified with MAX-ACCESS
or read-create so that specifications of the base tables in [RFC3812] of read-write or read-create so that specifications of the base
and the extensions in this document are consistent. Although the tables in [RFC3812] and the extensions in this document are
examples described in Section 9 specify means to configure MPLS-TP consistent. Although the examples described in Section 9 specify
tunnels in a similar way to the examples in [RFC3812], this should be means to configure MPLS-TP Tunnels in a similar way to the examples
seen as indicating how the MIB values would be returned in the specified in [RFC3812], this should be seen as indicating how the MIB values
circumstances having been configured by alternative means. would be returned if the specified circumstances were configured by
alternative means.
2. The Internet-Standard Management Framework 2. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of RFC Internet-Standard Management Framework, please refer to section 7 of
3410 [RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed the Managed objects are accessed via a virtual information store, termed
Management Information Base or MIB. MIB objects are generally accessed the Management Information Base or MIB. MIB objects are generally
through the Simple Network Management Protocol (SNMP). Objects in the accessed through the Simple Network Management Protocol (SNMP).
MIB are defined using the mechanisms defined in the Structure of Objects in the MIB are defined using the mechanisms defined in the
Management Information (SMI). This memo specifies a MIB module that is Structure of Management Information (SMI). This memo specifies a MIB
compliant to the SMIv2, which is described in STD 58 [RFC2578], STD 58 module that is compliant to the SMIv2, which is described in STD 58,
[RFC2579] and STD 58 [RFC2580]. RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[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", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in "OPTIONAL" in this document are to be interpreted as described in
[RFC2119]. [RFC2119].
3.2. Terminology 3.2. Terminology
This document uses terminology from the Multiprotocol Label Switching This document uses terminology from the "Multiprotocol Label
Architecture [RFC3031], Multiprotocol Label Switching (MPLS) Traffic Switching Architecture" [RFC3031], "Multiprotocol Label Switching
Engineering (TE) Management Information Base (MIB) [RFC3812], (MPLS) Traffic Engineering (TE) Management Information Base (MIB)"
Multiprotocol Label Switching (MPLS) Label Switching Router (LSR) [RFC3812], "Multiprotocol Label Switching (MPLS) Label Switching
Management Information Base (MIB) [RFC3813] and MPLS Transport Profile Router (LSR) Management Information Base (MIB)" [RFC3813], and"MPLS
(MPLS-TP) Identifiers [RFC6370]. Transport Profile (MPLS-TP) Identifiers" [RFC6370].
3.3. Acronyms 3.3. Acronyms
CC: Country Code CC: Country Code
ICC: ITU Carrier Code ICC: ITU Carrier Code
LSP: Label Switching Path LSP: Label Switched Path
LSR: Label Switching Router LSR: Label Switching Router
MPLS-TP: MPLS Transport Profile MPLS-TP: MPLS Transport Profile
TE: Traffic Engineering TE: Traffic Engineering
TP: Transport Profile TP: Transport Profile
4. Motivations 4. Motivations
Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management "Multiprotocol Label Switching (MPLS) Traffic Engineering (TE)
Information Base (MIB) [RFC3812] provides support for Traffic Management Information Base (MIB)" [RFC3812] provides support for
Engineering tunnels. In MPLS, the actual transport of packets is Traffic Engineering tunnels. In MPLS, the actual transport of
provided by Label Switched Paths (LSPs). A transport service may be packets is provided by Label Switched Paths (LSPs). A transport
composed of multiple LSPs. In order to clearly identify the MPLS-TP service may be composed of multiple LSPs. In order to clearly
service, as defined in [RFC6370], we use the term "MPLS-TP Tunnel" or identify the MPLS-TP service, as defined in [RFC6370], we use the
simply "tunnel". However, with MPLS-TP, the characteristics of the term "MPLS-TP Tunnel" or simply "tunnel". However, with MPLS-TP, the
tunnels were enhanced. For example, MPLS-TP tunnels, are bidirectional characteristics of the tunnels were enhanced. For example, MPLS-TP
in nature and could be used with non-IP identifiers for the tunnel end Tunnels are bidirectional in nature and could be used with non-IP
points. As the existing MPLS-TE-STD-MIB and GMPLS-TE-STD-MIB were identifiers for the tunnel endpoints. As the existing
defined mainly to support unidirectional tunnels and signaled co-routed MPLS-TE-STD-MIB and GMPLS-TE-STD-MIB were defined mainly to support
bidirectional tunnel definitions respectively, these existing MIB unidirectional tunnels and signaled co-routed bidirectional tunnel
modules are not sufficient to capture all the characteristics of the definitions, respectively, these existing MIB modules are not
tunnels. Hence, enhancing the MIB modules to support MPLS-TP tunnels is sufficient to capture all the characteristics of the tunnels. Hence,
required. As most of the attributes of MPLS Traffic Engineering tunnels enhancing the MIB modules to support MPLS-TP Tunnels is required. As
are also applicable to MPLS-TP tunnels, it is optimal to re-use and most of the attributes of MPLS Traffic Engineering tunnels are also
extend the existing MIB module definition instead of defining a new MIB applicable to MPLS-TP Tunnels, it is optimal to reuse and extend the
module. existing MIB module definition instead of defining a new MIB module.
This document defines four additional MIB modules, namely MPLS-TE-EXT- This document defines four additional MIB modules, namely,
STD-MIB, MPLS-TC-EXT-STD-MIB, MPLS-ID-STD-MIB and MPLS-LSR-EXT-STD-MIB. MPLS-TE-EXT-STD-MIB, MPLS-TC-EXT-STD-MIB, MPLS-ID-STD-MIB, and
As these additional MIB modules are required for MPLS-TP functionality, MPLS-LSR-EXT-STD-MIB. As these additional MIB modules are required
these are all defined in this document, instead of being documented for MPLS-TP functionality, these are all defined in this document,
separately. instead of being documented separately.
5. Feature List 5. Feature List
The MIBs in this document satisfy the following requirements and The MIBs in this document satisfy the following requirements and
constraints: constraints:
The MIB modules, taken together, support statically configured and The MIB modules, taken together, support statically configured and
dynamically signaled point-to-point, co-routed bidirectional and dynamically signaled point-to-point, co-routed bidirectional and
associated bidirectional tunnels. associated bidirectional tunnels.
- The MPLS tunnels need not be interfaces, but it is possible - The MPLS tunnels need not be interfaces, but it is possible to
to configure an MPLS TP tunnel as an interface. Same ifType 150, configure an MPLS-TP Tunnel as an interface. The same ifType
as defined in section 8 of [RFC3812], will be used for MPLS-TP 150, as defined in Section 8 of [RFC3812], will be used for
tunnels as well. MPLS-TP Tunnels as well.
- The mplsTunnelTable [RFC3812] is also to be used for MPLS-TP - The mplsTunnelTable [RFC3812] is also to be used for MPLS-TP
tunnels. Tunnels.
- New MPLS-TP specific textual conventions and identifiers are - New MPLS-TP-specific textual conventions and identifiers are
required. required.
- The mplsTunnelTable is sparsely extended to support MPLS-TP - The mplsTunnelTable is sparsely extended to support objects
tunnel specific objects. specific to MPLS-TP Tunnels.
- A node configuration table (mplsTunnelExtNodeConfigTable), as - A node configuration table (mplsTunnelExtNodeConfigTable), as
detailed in the below section 6.1.2, is used to translate detailed in Section 6.2.1, below, is used to translate the
the Global_ID::Node_ID or ICC_Operator_ID::Node_ID to Global_ID::Node_ID or ICC_Operator_ID::Node_ID to the local
the local identifier in order to index mplsTunnelTable. identifier in order to index the mplsTunnelTable.
- The mplsXCTable is sparsely extended to support MPLS-TP - The mplsXCTable is sparsely extended to support objects specific
XC(Cross Connect) specific objects. to MPLS-TP XC (Cross Connect).
- The MIB module supports persistent, as well as non-persistent - The MIB module supports persistent, as well as non-persistent,
tunnels. tunnels.
6. Outline 6. Outline
Traffic Engineering support for the MPLS-TP tunnels requires the set up Traffic Engineering support for the MPLS-TP Tunnels requires the
of the co-routed or associated bidirectional tunnel. The tables and MIB setup of the co-routed or associated bidirectional tunnel. The
modules that are mentioned in the below subsections support the tables and MIB modules that are mentioned in the below subsections
functionality described in documents [RFC5654] and [RFC6370]. These support the functionality described in [RFC5654] and [RFC6370].
tables support both IP compatible and ITU Carrier Code (ICC) based These tables support both IP-compatible and ICC-based tunnel
tunnel configurations. configurations.
The below Figure 1 depicts how the table references are followed in this Figure 1, below, depicts how the table references are followed in
MIB. this MIB.
Tunnel1-->XC1<-------------- Tunnel1-->XC1<--------------
^ ^ | | | ^ ^ | | |
| | | |-->InSeg1 | | | | |-->InSeg1 |
| | | |-->OutSeg1 | | | | |-->OutSeg1 |
| | v | | | v |
| ------XCext1 | | ------XCext1 |
| | | | | |
V v | V v |
Tunnel2-->XC1 | Tunnel2-->XC1 |
^ | | | ^ | | |
| | |-->InSeg2 | | | |-->InSeg2 |
| | |-->OutSeg2 | | | |-->OutSeg2 |
| v | | v |
------XCext2------------ ------XCext2------------
Figure 1: Table references of MIB modules Figure 1: Table References of MIB Modules
6.1 MIB Module Extensions 6.1. MIB Module Extensions
Four MIB modules are extended to support MPLS-TP tunnels, namely, Four MIB modules are extended to support MPLS-TP Tunnels, namely,
MPLS-TE-EXT-STD-MIB, MPLS-TC-EXT-STD-MIB, MPLS-ID-STD-MIB and MPLS- MPLS-TE-EXT-STD-MIB, MPLS-TC-EXT-STD-MIB, MPLS-ID-STD-MIB, and
LSR-EXT-STD-MIB. Following section provides the summary of changes. MPLS-LSR-EXT-STD-MIB. The following section provides the summary of
changes.
6.1.1 Summary of MIB Module changes 6.1.1. Summary of MIB Module Changes
- Node configuration table (mplsTunnelExtNodeConfigTable) for - Node configuration table (mplsTunnelExtNodeConfigTable) for setting
setting the local identifier for Tunnel Ingress and Egress the local identifier for Tunnel Ingress and Egress identifiers.
identifiers.
- Node IP map table (mplsTunnelExtNodeIpMapTable) for querying - Node IP map table (mplsTunnelExtNodeIpMapTable) for querying the
the local identifier for a given Global_ID and Node_ID. local identifier for a given Global_ID and Node_ID.
- Node ICC map table (mplsTunnelExtNodeIccMapTable) for querying - Node ICC map table (mplsTunnelExtNodeIccMapTable) for querying the
the local identifier for a given ICC_Operator_ID and Node_ID. local identifier for a given ICC_Operator_ID and Node_ID.
- Tunnel extension table (mplsTunnelExtTable) for setting up - Tunnel extension table (mplsTunnelExtTable) for setting up MPLS-TP
MPLS-TP tunnels with sparse extension of mplsTunnelTable. Tunnels with sparse extension of mplsTunnelTable.
- Textual conventions and object definitions for MPLS-TP Tunnels - Textual conventions and object definitions for MPLS-TP Tunnels.
- Cross connect extension table (mplsXCExtTable) for setting up - Cross-connect extension table (mplsXCExtTable) for setting up the
the MPLS-TP LSPs. MPLS-TP LSPs.
These tables are described in the subsequent sections. These tables are described in the subsequent sections.
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
in the following sections. described 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 characters, each being an uppercase Basic Latin CC is a string of two characters, each being an uppercase Basic Latin
alphabetic (i.e., A-Z). The ICC is a string of one to six characters, alphabetic (i.e., A-Z). The ICC is a string of one to six
each an upper case Basic Latin alphabetic (i.e., A-Z) or numeric characters, each an uppercase Basic Latin alphabetic (i.e., A-Z) or
(i.e., 0-9). All of the characters are encoded using [T.50] as numeric (i.e., 0-9). All of the characters are encoded using [T.50]
described in [RFC6370]. as described in [RFC6370].
In the IP compatible mode, Global_ID::Node_ID, is used to uniquely In the IP-compatible mode, Global_ID::Node_ID, is used to uniquely
identify a node. For each ICC_Operator_ID::Node_ID or identify a node. For each ICC_Operator_ID::Node_ID or
Global_ID::Node_ID, there is a unique entry in the table representing Global_ID::Node_ID, there is a unique entry in the table representing
a node. As the regular TE tunnels use IP address as LSR ID, the a node. As the regular TE tunnels use the IP address as the LSR ID,
local identifier should be below the first valid IP address, which is the local identifier should be below the first valid IP address,
16777216[1.0.0.0]. Every node is assigned a local identifier within a which is 16777216[1.0.0.0]. Every node is assigned a local
range of 0 to 16777215. This local identifier is used for indexing identifier within a range of 0 to 16777215. This local identifier is
into mplsTunnelTable as mplsTunnelIngressLSRId and used for indexing into mplsTunnelTable as mplsTunnelIngressLSRId and
mplsTunnelEgressLSRId. mplsTunnelEgressLSRId.
For IP compatible environment, MPLS-TP tunnel is indexed by Tunnel For IP-compatible environments, an MPLS-TP Tunnel is indexed by
Index, Tunnel Instance, Source Global_ID, Source Node_ID, Destination Tunnel Index, Tunnel Instance, Source Global_ID, Source Node_ID,
Global_ID and Destination Node_ID. Destination Global_ID, and Destination Node_ID.
For ICC based environment, MPLS-TP tunnel is indexed by Tunnel Index, For ICC-based environments, an MPLS-TP Tunnel is indexed by Tunnel
Tunnel Instance, Source CC, Source ICC, Source Node_ID, Destination Index, Tunnel Instance, Source CC, Source ICC, Source Node_ID,
CC, Destination ICC and Destination Node_ID. Destination CC, Destination ICC, and Destination Node_ID.
As mplsTunnelTable is indexed by mplsTunnelIndex, As mplsTunnelTable is indexed by mplsTunnelIndex, mplsTunnelInstance,
mplsTunnelInstance, mplsTunnelIngressLSRId, and mplsTunnelIngressLSRId, and mplsTunnelEgressLSRId, the MPLS-TP tunnel
mplsTunnelEgressLSRId, the MPLS-TP tunnel identifiers cannot be 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
ICC_Operator_ID::Node_ID or Global_ID::Node_ID with a local ICC_Operator_ID::Node_ID or Global_ID::Node_ID with a local
identifier to be used as LSR ID in mplsTunnelTable. identifier to be used as the LSR ID in mplsTunnelTable.
6.2.2 mplsTunnelExtNodeIpMapTable 6.2.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
a given Global_ID::Node_ID. In order to query the local identifier, given Global_ID::Node_ID. In order to query the local identifier, in
in the IP compatible mode, this table is indexed with 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
Ingress and Egress Global_ID::Node_ID identifiers. These local and Egress Global_ID::Node_ID identifiers. These local identifiers
identifiers are used as mplsTunnelIngressLSRId and are used as mplsTunnelIngressLSRId and mplsTunnelEgressLSRId when
mplsTunnelEgressLSRId, while indexing mplsTunnelTable. indexing mplsTunnelTable.
6.2.3 mplsTunnelExtNodeIccMapTable 6.2.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 ICC_Operator_ID::Node_ID. 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
Ingress and Egress ICC_Operator_ID::Node_ID. These local identifiers and Egress ICC_Operator_ID::Node_ID. These local identifiers are
are used as mplsTunnelIngressLSRId and mplsTunnelEgressLSRId, used as mplsTunnelIngressLSRId and mplsTunnelEgressLSRId when
while indexing mplsTunnelTable. indexing mplsTunnelTable.
6.2.4 mplsTunnelExtTable 6.2.4. mplsTunnelExtTable
This table sparsely extends the mplsTunnelTable in order to support This table sparsely 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 a 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.
The gmplsTunnelReversePerfTable [RFC4802] should be used to provide The gmplsTunnelReversePerfTable [RFC4802] should be used to provide
per-tunnel packet performance information for the reverse direction per-tunnel packet performance information for the reverse direction
of a bidirectional tunnel. It can be seen as supplementing the of a bidirectional tunnel. It can be seen as supplementing the
mplsTunnelPerfTable, which augments the mplsTunnelTable. mplsTunnelPerfTable, which augments the mplsTunnelTable.
6.3 MPLS-TC-EXT-STD-MIB 6.3. MPLS-TC-EXT-STD-MIB
This MIB module contains textual Conventions for LSPs of MPLS based This MIB module contains textual conventions for LSPs of MPLS-based
transport networks. transport networks.
6.4 MPLS-ID-STD-MIB 6.4. MPLS-ID-STD-MIB
This MIB module contains generic object definitions for MPLS Traffic
Engineering in transport networks.
6.5 MPLS-LSR-EXT-STD-MIB This MIB module contains identifier object definitions for MPLS
Traffic Engineering in transport networks.
This MIB module contains generic object definitions (Cross connect 6.5. MPLS-LSR-EXT-STD-MIB
extension table - mplsXCExtTable, for setting up the MPLS-TP LSPs
with sparse extension of mplsXCTable) for MPLS LSRs in transport
networks.
6.6 The Use of RowPointer This MIB module contains generic object definitions (including the
mplsXCExtTable -- cross-connect extension table -- for setting up the
MPLS-TP LSPs with sparse extension of mplsXCTable) for MPLS LSRs in
transport networks.
This document follows the RowPointer usage as described in the 6.6. The Use of RowPointer
section 10 of [RFC3812].
This document follows the RowPointer usage as described in Section 10
of [RFC3812].
A new RowPointer object, mplsTunnelExtOppositeDirPtr, is added to A new RowPointer object, mplsTunnelExtOppositeDirPtr, is added to
mplsTunnelExtTable of MPLS-TE-EXT-STD-MIB MIB module. This RowPointer mplsTunnelExtTable of MPLS-TE-EXT-STD-MIB module. This RowPointer
object points to the opposite direction tunnel entry. object points to the tunnel entry in the opposite direction.
Two additional RowPointers objects, mplsXCExtTunnelPointer and Two additional RowPointers objects, mplsXCExtTunnelPointer and
mplsXCExtOppositeDirXCPtr are added to mplsXCExtTable of MPLS-LSR- mplsXCExtOppositeDirXCPtr, are added to the mplsXCExtTable of
EXT-STD-MIB. The RowPointer mplsXCExtTunnelPointer is read-only MPLS-LSR-EXT-STD-MIB. The RowPointer mplsXCExtTunnelPointer is a
object used to indicate the back pointer to the tunnel entry. The read-only object used to indicate the back pointer to the tunnel
RowPointer mplsXCExtOppositeDirXCPtr object points to the opposite entry. The RowPointer mplsXCExtOppositeDirXCPtr object points to the
direction XC entry. opposite-direction XC entry.
If these RowPointer returns zeroDotZero, it implies that there is no If either of these RowPointers return zeroDotZero, it implies that
entry associated with the RowPointer object. there is no entry associated with the RowPointer object.
7. MIB Modules Interdependencies 7. MIB Modules' Interdependencies
This section provides an overview of the relationship between the This section provides an overview of the relationships between the
MPLS-TP TE MIB module and other MPLS MIB modules. MPLS-TP TE MIB module and other MPLS MIB modules.
The arrows in the following diagram show a 'depends on' The arrows in the following diagram show a "depends on" relationship.
relationship. A relationship "MIB module A depends on MIB module B" A relationship of "MIB module A depends on MIB module B" means that
means that MIB module A uses an object, object identifier, or MIB module A uses an object, object identifier, or textual convention
textual convention defined in MIB module B, or that MIB module A defined in MIB module B, or that MIB module A contains a pointer
contains a pointer (index or RowPointer) to an object in (index or RowPointer) to an object in MIB module B.
MIB module B.
MPLS-TC-EXT-STD-MIB MPLS-TC-EXT-STD-MIB
^ ^
| |
| |
+<---- MPLS-ID-STD-MIB +<---- MPLS-ID-STD-MIB
^ ^
| | | |
+<---- MPLS-TE-EXT-STD-MIB +<---- MPLS-TE-EXT-STD-MIB
| | | |
skipping to change at page 13, line 37 skipping to change at page 12, line 25
| MPLS-TE-STD-MIB | MPLS-TE-STD-MIB
| | | |
| | | |
| V | V
| MPLS-LSR-STD-MIB | MPLS-LSR-STD-MIB
| ^ | ^
| | | |
| | | |
+------MPLS-LSR-EXT-STD-MIB +------MPLS-LSR-EXT-STD-MIB
Figure 2: MIB modules interdependencies Figure 2: MIB Modules' Interdependencies
Thus: Thus:
- All the new MPLS extension MIB modules depend on - All the new MPLS extension MIB modules depend on
MPLS-TC-EXT-STD-MIB. MPLS-TC-EXT-STD-MIB.
- MPLS-ID-STD-MIB contains references to objects in - MPLS-ID-STD-MIB contains references to objects in
MPLS-TE-STD-MIB [RFC3812]. MPLS-TE-STD-MIB [RFC3812].
- MPLS-TE-EXT-STD-MIB contains references to objects in - MPLS-TE-EXT-STD-MIB contains references to objects in
MPLS-TE-STD-MIB [RFC3812]. MPLS-TE-STD-MIB [RFC3812].
- MPLS-LSR-EXT-STD-MIB contains references to objects in - MPLS-LSR-EXT-STD-MIB contains references to objects in
MPLS-LSR-STD-MIB [RFC3813]. MPLS-LSR-STD-MIB [RFC3813].
The mplsTunnelExtTable sparsely extends the mplsTunnelTable of The mplsTunnelExtTable sparsely extends the mplsTunnelTable of
MPLS-TE-STD-MIB [RFC3812]. This helps in associating the reverse MPLS-TE-STD-MIB [RFC3812]. This helps in associating the reverse-
direction tunnel information. direction tunnel information.
The mplsXCExtTable sparsely extends the mplsXCTable of The mplsXCExtTable sparsely extends the mplsXCTable of
MPLS-LSR-STD-MIB [RFC3813]. This helps in pointing back to the tunnel MPLS-LSR-STD-MIB [RFC3813]. This helps in pointing back to the
entry for easy tunnel access from XC entry. tunnel entry for easy tunnel access from the XC entry.
Note that all of the MIB modules shown above in the figure also Note that all of the MIB modules shown above in the figure also have
have a dependency on MPLS-TC-STD-MIB. a dependency on MPLS-TC-STD-MIB.
8. Dependencies between MIB Module Tables 8. Dependencies between MIB Module Tables
The tables in MPLS-TE-EXT-STD-MIB are related as shown on the diagram The tables in MPLS-TE-EXT-STD-MIB are related as shown on the diagram
below. The arrows indicate a reference from one table to another. below. The arrows indicate a reference from one table to another.
mplsTunnelExtNodeConfigTable mplsTunnelExtNodeConfigTable
^ ^ ^ ^ ^ ^
| | | | | |
| | | | | |
| | | | | |
| | +----------------------+ | | +----------------------+
skipping to change at page 14, line 43 skipping to change at page 13, line 32
| | | | | |
| | | | | |
| V V | V V
mplsTunnelTable ---->mplsXCTable mplsTunnelTable ---->mplsXCTable
^ ^
| |
| |
| |
mplsTunnelExtTable mplsTunnelExtTable
Figure 3: Dependencies between MIB module tables Figure 3: Dependencies between MIB Module Tables
An existing mplsTunnelTable uses the mplsTunnelExtNodeConfigTable An existing mplsTunnelTable uses the mplsTunnelExtNodeConfigTable
table to map the Global_ID::Node_ID and/or ICC_Operator_ID::Node_ID table to map the Global_ID::Node_ID and/or ICC_Operator_ID::Node_ID
with the local number in order to accommodate in the existing tunnel with the local number in order to accommodate in the existing tunnel
table's ingress/egress LSR-id. table's ingress/egress LSR ID.
New mplsTunnelExtTable table provides the reverse direction LSP The new mplsTunnelExtTable provides the reverse-direction LSP
information for the existing tunnel table in order to achieve information for the existing tunnel table so that bidirectional LSPs
bidirectional LSPs. can be created.
mplsXCExtTable sparsely extends the mplsLsrXCTable to provide The mplsXCExtTable sparsely extends the 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 to configure MPLS-TP In this section, we provide an example of configuring MPLS-TP
bidirectional tunnels with IP tunnel identifiers. This example bidirectional tunnels with IP tunnel identifiers. This example
provides the usage of MPLS-TP Tunnel MIB along with the extended MIB provides the usage of the MPLS-TP Tunnel MIB along with the extended
modules introduced in this document. MIB modules introduced in this document.
Do note that a MPLS-TP tunnel could be setup statically as well as Do note that a MPLS-TP Tunnel could be set up statically as well as
signaled via control plane. This example considers accessing MIB signaled via the control plane. This example considers accessing MIB
objects on a head-end for a static and signaled MPLS-TP tunnels. This objects on a head-end for static and signaled MPLS-TP Tunnels. This
section shows the configuration of the forward and reverse direction section shows the configuration of the forward- and reverse-direction
MPLS-TP LSPs that run between East and West and vice-versa. Only MPLS-TP LSPs that run between East and West, and vice versa. Only
objects relevant to MPLS-TP tunnels are illustrated here. objects relevant to MPLS-TP Tunnels are illustrated here.
In mplsTunnelExtNodeConfigTable: In mplsTunnelExtNodeConfigTable:
{ {
-- Non-IP Ingress LSR-Id (Index to the table) -- Non-IP Ingress LSR_ID (Index to the table)
mplsTunnelExtNodeConfigLocalId = 1, mplsTunnelExtNodeConfigLocalId = 1,
mplsTunnelExtNodeConfigGlobalId = 1234, mplsTunnelExtNodeConfigGlobalId = 1234,
mplsTunnelExtNodeConfigNodeId = 10, mplsTunnelExtNodeConfigNodeId = 10,
-- Mandatory parameters needed to activate the row go here -- Mandatory parameters needed to activate the row go here
mplsTunnelExtNodeConfigRowStatus = createAndGo (4) mplsTunnelExtNodeConfigRowStatus = createAndGo (4)
-- Non-IP Egress LSR-Id (Index to the table) -- Non-IP Egress LSR ID (Index to the table)
mplsTunnelExtNodeConfigLocalId = 2, mplsTunnelExtNodeConfigLocalId = 2,
mplsTunnelExtNodeConfigGlobalId = 1234, mplsTunnelExtNodeConfigGlobalId = 1234,
mplsTunnelExtNodeConfigNodeId = 20, mplsTunnelExtNodeConfigNodeId = 20,
-- Mandatory parameters needed to activate the row go here -- Mandatory parameters needed to activate the row go here
mplsTunnelExtNodeConfigRowStatus = createAndGo (4) mplsTunnelExtNodeConfigRowStatus = createAndGo (4)
} }
This will create an entry in the mplsTunnelExtNodeConfigTable for a This will create an entry in the mplsTunnelExtNodeConfigTable for a
Global_ID::Node_ID. A separate entry is made for both Ingress LSR Global_ID::Node_ID. The Ingress and Egress LSR are represented by
and Egress LSR. separate entries.
The following read-only mplsTunnelExtNodeIpMapTable table is The following read-only mplsTunnelExtNodeIpMapTable table is
populated automatically upon creating an entry in populated automatically upon creating an entry in
mplsTunnelExtNodeConfigTable and this table is used to retrieve mplsTunnelExtNodeConfigTable, and this table is used to retrieve the
the local identifier for the given Global_ID::Node_ID. local identifier for the given Global_ID::Node_ID.
In mplsTunnelExtNodeIpMapTable: In mplsTunnelExtNodeIpMapTable:
{ {
-- Global_ID (Index to the table) -- Global_ID (Index to the table)
mplsTunnelExtNodeIpMapGlobalId = 1234, mplsTunnelExtNodeIpMapGlobalId = 1234,
-- Node Identifier (Index to the table) -- Node Identifier (Index to the table)
mplsTunnelExtNodeIpMapNodeId = 10, mplsTunnelExtNodeIpMapNodeId = 10,
mplsTunnelExtNodeIpMapLocalId = 1 mplsTunnelExtNodeIpMapLocalId = 1
skipping to change at page 16, line 14 skipping to change at page 15, line 4
{ {
-- Global_ID (Index to the table) -- Global_ID (Index to the table)
mplsTunnelExtNodeIpMapGlobalId = 1234, mplsTunnelExtNodeIpMapGlobalId = 1234,
-- Node Identifier (Index to the table) -- Node Identifier (Index to the table)
mplsTunnelExtNodeIpMapNodeId = 10, mplsTunnelExtNodeIpMapNodeId = 10,
mplsTunnelExtNodeIpMapLocalId = 1 mplsTunnelExtNodeIpMapLocalId = 1
-- Global_ID (Index to the table) -- Global_ID (Index to the table)
mplsTunnelExtNodeIpMapGlobalId = 1234, mplsTunnelExtNodeIpMapGlobalId = 1234,
-- Node Identifier (Index to the table) -- Node Identifier (Index to the table)
mplsTunnelExtNodeIpMapNodeId = 20, mplsTunnelExtNodeIpMapNodeId = 20,
mplsTunnelExtNodeIpMapLocalId = 2 mplsTunnelExtNodeIpMapLocalId = 2
} }
9.1. Example of MPLS-TP static co-routed bidirectional tunnel setup 9.1. Example of MPLS-TP Static Co-routed Bidirectional Tunnel Setup
The following denotes the co-routed bidirectional tunnel "head" The following denotes the co-routed bidirectional tunnel "head"
entry. entry.
9.1.1. mplsTunnelEntry 9.1.1. mplsTunnelEntry
In mplsTunnelTable: In mplsTunnelTable:
{ {
mplsTunnelIndex = 1, mplsTunnelIndex = 1,
mplsTunnelInstance = 1, mplsTunnelInstance = 1,
-- Local map number created in mplsTunnelExtNodeConfigTable for -- Local map number created in mplsTunnelExtNodeConfigTable for
-- Ingress LSR-Id -- Ingress LSR ID
mplsTunnelIngressLSRId = 1, mplsTunnelIngressLSRId = 1,
-- Local map number created in mplsTunnelExtNodeConfigTable for -- Local map number created in mplsTunnelExtNodeConfigTable for
-- Egress LSR-Id -- Egress LSR ID
mplsTunnelEgressLSRId = 2, mplsTunnelEgressLSRId = 2,
mplsTunnelName = "TP co-routed bidirectional LSP", mplsTunnelName = "TP co-routed bidirectional LSP",
mplsTunnelDescr = "East to West", mplsTunnelDescr = "East to West",
mplsTunnelIsIf = true (1), mplsTunnelIsIf = true (1),
-- RowPointer MUST point to the first accessible column -- RowPointer MUST point to the first accessible column
mplsTunnelXCPointer = mplsTunnelXCPointer =
mplsXCLspId.4.0.0.0.1.1.0.4.0.0.0.1, mplsXCLspId.4.0.0.0.1.1.0.4.0.0.0.1,
mplsTunnelSignallingProto = none (1), mplsTunnelSignallingProto = none (1),
mplsTunnelSetupPrio = 0, mplsTunnelSetupPrio = 0,
mplsTunnelHoldingPrio = 0, mplsTunnelHoldingPrio = 0,
skipping to change at page 17, line 12 skipping to change at page 16, line 5
mplsTunnelInstancePriority = 1, mplsTunnelInstancePriority = 1,
mplsTunnelHopTableIndex = 1, mplsTunnelHopTableIndex = 1,
mplsTunnelIncludeAnyAffinity = 0, mplsTunnelIncludeAnyAffinity = 0,
mplsTunnelIncludeAllAffinity = 0, mplsTunnelIncludeAllAffinity = 0,
mplsTunnelExcludeAnyAffinity = 0, mplsTunnelExcludeAnyAffinity = 0,
mplsTunnelRole = head (1), mplsTunnelRole = head (1),
-- Mandatory parameters needed to activate the row go here -- Mandatory parameters needed to activate the row go here
mplsTunnelRowStatus = createAndGo (4) mplsTunnelRowStatus = createAndGo (4)
} }
9.1.2. mplsTunnelExtEntry 9.1.2. mplsTunnelExtEntry
-- An MPLS extension table -- An MPLS extension table
In mplsTunnelExtTable: In mplsTunnelExtTable:
{ {
-- This opposite direction tunnel pointer may point to 0.0 -- This opposite-direction tunnel pointer may point to 0.0
-- if co-routed bidirectional tunnel is managed by single tunnel -- if co-routed bidirectional tunnel is managed by single tunnel
-- entry -- entry
mplsTunnelExtOppositeDirTnlPtr = 0.0 mplsTunnelExtOppositeDirTnlPtr = 0.0
-- Set both the Ingress and Egress LocalId objects to TRUE as -- Set both the Ingress and Egress LocalId objects to TRUE, as
-- this tunnel entry uses the local identifiers. -- this tunnel entry uses the local identifiers.
mplsTunnelExtIngressLSRLocalIdValid = true, mplsTunnelExtIngressLSRLocalIdValid = true,
mplsTunnelExtEgressLSRLocalIdValid = true mplsTunnelExtEgressLSRLocalIdValid = true
} }
We must next create the appropriate in-segment and out-segment Next, we must create the appropriate in-segment and out-segment
entries. These are done in [RFC3813] using the mplsInSegmentTable and entries. These are done in [RFC3813] using the mplsInSegmentTable
mplsOutSegmentTable. and mplsOutSegmentTable.
9.1.3. Forward direction mplsOutSegmentEntry 9.1.3. Forward-Direction mplsOutSegmentEntry
For the forward direction, For the forward direction:
In mplsOutSegmentTable: In mplsOutSegmentTable:
{ {
mplsOutSegmentIndex = 0x0000001, mplsOutSegmentIndex = 0x0000001,
mplsOutSegmentInterface = 13, -- outgoing interface mplsOutSegmentInterface = 13, -- outgoing interface
mplsOutSegmentPushTopLabel = true(1), mplsOutSegmentPushTopLabel = true(1),
mplsOutSegmentTopLabel = 22, -- outgoing label mplsOutSegmentTopLabel = 22, -- outgoing label
-- RowPointer MUST point to the first accessible column. -- RowPointer MUST point to the first accessible column.
mplsOutSegmentTrafficParamPtr = 0.0, mplsOutSegmentTrafficParamPtr = 0.0,
mplsOutSegmentRowStatus = createAndGo (4) mplsOutSegmentRowStatus = createAndGo (4)
} }
9.1.4. Reverse direction mplsInSegmentEntry 9.1.4. Reverse-Direction mplsInSegmentEntry
For the reverse direction, For the reverse direction:
In mplsInSegmentTable: In mplsInSegmentTable:
{ {
mplsInSegmentIndex = 0x0000001 mplsInSegmentIndex = 0x0000001
mplsInSegmentLabel = 21, -- incoming label mplsInSegmentLabel = 21, -- incoming label
mplsInSegmentNPop = 1, mplsInSegmentNPop = 1,
mplsInSegmentInterface = 13, -- incoming interface mplsInSegmentInterface = 13, -- incoming interface
-- RowPointer MUST point to the first accessible column. -- RowPointer MUST point to the first accessible column.
mplsInSegmentTrafficParamPtr = 0.0, mplsInSegmentTrafficParamPtr = 0.0,
mplsInSegmentRowStatus = createAndGo (4) mplsInSegmentRowStatus = createAndGo (4)
} }
Next, two cross-connect entries are created in the mplsXCTable of the Next, two cross-connect entries are created in the mplsXCTable of the
MPLS-LSR-STD-MIB [RFC3813], thereby associating the newly created MPLS-LSR-STD-MIB [RFC3813], thereby associating the newly created
segments together. segments together.
9.1.5. Forward direction mplsXCEntry 9.1.5. Forward-Direction mplsXCEntry
In mplsXCTable: In mplsXCTable:
{ {
mplsXCIndex = 0x01, mplsXCIndex = 0x01,
mplsXCInSegmentIndex = 0x00000000, mplsXCInSegmentIndex = 0x00000000,
mplsXCOutSegmentIndex = 0x00000001, mplsXCOutSegmentIndex = 0x00000001,
mplsXCLspId = 0x0102 -- unique ID mplsXCLspId = 0x0102 -- unique ID
-- only a single outgoing label -- only a single outgoing label
mplsXCLabelStackIndex = 0x00, mplsXCLabelStackIndex = 0x00,
mplsXCRowStatus = createAndGo(4) mplsXCRowStatus = createAndGo(4)
} }
9.1.6. Reverse direction mplsXCEntry 9.1.6. Reverse-Direction mplsXCEntry
In mplsXCTable: In mplsXCTable:
{ {
mplsXCIndex = 0x01, mplsXCIndex = 0x01,
mplsXCInSegmentIndex = 0x00000001, mplsXCInSegmentIndex = 0x00000001,
mplsXCOutSegmentIndex = 0x00000000, mplsXCOutSegmentIndex = 0x00000000,
mplsXCLspId = 0x0102 -- unique ID mplsXCLspId = 0x0102 -- unique ID
-- only a single outgoing label -- only a single outgoing label
mplsXCLabelStackIndex = 0x00, mplsXCLabelStackIndex = 0x00,
mplsXCRowStatus = createAndGo(4) mplsXCRowStatus = createAndGo(4)
} }
This table entry is extended by entry in the This table entry is extended by an entry in the mplsXCExtTable. Note
mplsXCExtTable. Note that the nature of the 'extends' that the nature of the 'extends' relationship is a sparse
relationship is a sparse augmentation so that the entry in the augmentation so that the entry in the mplsXCExtTable has the same
mplsXCExtTable has the same index values as the entry in index values as the entry in the mplsXCTable.
the mplsXCTable.
9.1.7. Forward direction mplsXCExtEntry 9.1.7. Forward-Direction mplsXCExtEntry
In mplsXCExtTable (0x01, 0x00000000, 0x00000001) In mplsXCExtTable (0x01, 0x00000000, 0x00000001)
{ {
-- Back pointer from XC table to Tunnel table -- Back pointer from XC table to Tunnel table
mplsXCExtTunnelPointer = mplsTunnelName.1.1.1.2 mplsXCExtTunnelPointer = mplsTunnelName.1.1.1.2
mplsXCExtOppositeDirXCPtr = mplsXCExtOppositeDirXCPtr =
mplsXCLspId.4.0.0.0.1.4.0.0.0.1.1.0 mplsXCLspId.4.0.0.0.1.4.0.0.0.1.1.0
} }
9.1.8. Reverse direction mplsXCExtEntry 9.1.8. Reverse-Direction mplsXCExtEntry
Next for the reverse direction: Next, for the reverse direction:
In mplsXCExtTable (0x01, 0x00000001, 0x00000000) In mplsXCExtTable (0x01, 0x00000001, 0x00000000)
{ {
-- Back pointer from XC table to Tunnel table -- Back pointer from XC table to Tunnel table
mplsXCExtTunnelPointer = mplsTunnelName.1.1.1.2 mplsXCExtTunnelPointer = mplsTunnelName.1.1.1.2
mplsXCExtOppositeDirXCPtr = mplsXCExtOppositeDirXCPtr =
mplsXCLspId.4.0.0.0.1.1.0.4.0.0.0.1 mplsXCLspId.4.0.0.0.1.1.0.4.0.0.0.1
} }
9.2. Example of MPLS-TP static associated bidirectional tunnel setup 9.2. Example of MPLS-TP Static Associated Bidirectional Tunnel Setup
The MPLS-TP associated bidirectional tunnel is implemented by two The MPLS-TP associated bidirectional tunnel is implemented by two
different unidirectional tunnels [Forward and Reverse LSPs] and these different unidirectional tunnels (Forward and Reverse LSPs), and
are associated together using mplsTunnelExtTable. Two different these are associated together using mplsTunnelExtTable. Two
tunnel entries to provide the forward and reverse directions MAY be different tunnel entries to provide the forward and reverse
used for co-routed bidirectional tunnels as well. directions MAY be used for co-routed bidirectional tunnels as well.
The following denotes the associated bidirectional forward tunnel The following denotes the associated bidirectional forward tunnel
"head" entry: "head" entry:
9.2.1. Forward direction mplsTunnelEntry 9.2.1. Forward-Direction mplsTunnelEntry
In mplsTunnelTable: In mplsTunnelTable:
{ {
mplsTunnelIndex = 1, mplsTunnelIndex = 1,
mplsTunnelInstance = 1, mplsTunnelInstance = 1,
-- Local map number created in mplsTunnelExtNodeConfigTable for -- Local map number created in mplsTunnelExtNodeConfigTable for
-- Ingress LSR-Id -- Ingress LSR ID
mplsTunnelIngressLSRId = 1, mplsTunnelIngressLSRId = 1,
-- Local map number created in mplsTunnelExtNodeConfigTable for -- Local map number created in mplsTunnelExtNodeConfigTable for
-- Egress LSR-Id -- Egress LSR ID
mplsTunnelEgressLSRId = 2, mplsTunnelEgressLSRId = 2,
mplsTunnelName = "TP associated bidirectional mplsTunnelName = "TP associated bidirectional
forward LSP", forward LSP",
mplsTunnelDescr = "East to West", mplsTunnelDescr = "East to West",
mplsTunnelIsIf = true (1), mplsTunnelIsIf = true (1),
-- RowPointer MUST point to the first accessible column -- RowPointer MUST point to the first accessible column
mplsTunnelXCPointer = mplsTunnelXCPointer =
mplsXCLspId.4.0.0.0.1.1.0.4.0.0.0.1, mplsXCLspId.4.0.0.0.1.1.0.4.0.0.0.1,
mplsTunnelSignallingProto = none (1), mplsTunnelSignallingProto = none (1),
mplsTunnelSetupPrio = 0, mplsTunnelSetupPrio = 0,
skipping to change at page 20, line 30 skipping to change at page 19, line 33
mplsTunnelHopTableIndex = 1, mplsTunnelHopTableIndex = 1,
mplsTunnelIncludeAnyAffinity = 0, mplsTunnelIncludeAnyAffinity = 0,
mplsTunnelIncludeAllAffinity = 0, mplsTunnelIncludeAllAffinity = 0,
mplsTunnelExcludeAnyAffinity = 0, mplsTunnelExcludeAnyAffinity = 0,
mplsTunnelRole = head (1), mplsTunnelRole = head (1),
-- Mandatory parameters needed to activate the row go here -- Mandatory parameters needed to activate the row go here
mplsTunnelRowStatus = createAndGo (4) mplsTunnelRowStatus = createAndGo (4)
} }
9.2.2. Forward direction mplsTunnelExtEntry 9.2.2. Forward-Direction mplsTunnelExtEntry
For the associated bidirectional forward LSP,
in mplsTunnelExtTable:
For Associated bidirectional forward LSP,
In mplsTunnelExtTable:
{ {
mplsTunnelExtOppositeDirPtr = mplsTunnelName.2.1.2.1 mplsTunnelExtOppositeDirPtr = mplsTunnelName.2.1.2.1
-- Set both the Ingress and Egress LocalId objects to TRUE as -- Set both the Ingress and Egress LocalId objects to TRUE, as
-- this tunnel entry uses the local identifiers. -- this tunnel entry uses the local identifiers.
mplsTunnelExtIngressLSRLocalIdValid = true, mplsTunnelExtIngressLSRLocalIdValid = true,
mplsTunnelExtEgressLSRLocalIdValid = true mplsTunnelExtEgressLSRLocalIdValid = true
} }
9.2.3. Forward direction mplsOutSegmentTable 9.2.3. Forward-Direction mplsOutSegmentTable
For the forward direction. For the forward direction:
In mplsOutSegmentTable: In mplsOutSegmentTable:
{ {
mplsOutSegmentIndex = 0x0000001, mplsOutSegmentIndex = 0x0000001,
mplsOutSegmentInterface = 13, -- outgoing interface mplsOutSegmentInterface = 13, -- outgoing interface
mplsOutSegmentPushTopLabel = true(1), mplsOutSegmentPushTopLabel = true(1),
mplsOutSegmentTopLabel = 22, -- outgoing label mplsOutSegmentTopLabel = 22, -- outgoing label
-- RowPointer MUST point to the first accessible column. -- RowPointer MUST point to the first accessible column.
mplsOutSegmentTrafficParamPtr = 0.0, mplsOutSegmentTrafficParamPtr = 0.0,
mplsOutSegmentRowStatus = createAndGo (4) mplsOutSegmentRowStatus = createAndGo (4)
} }
9.2.4. Forward direction mplsXCEntry 9.2.4. Forward-Direction mplsXCEntry
In mplsXCTable: In mplsXCTable:
{ {
mplsXCIndex = 0x01, mplsXCIndex = 0x01,
mplsXCInSegmentIndex = 0x00000000, mplsXCInSegmentIndex = 0x00000000,
mplsXCOutSegmentIndex = 0x00000001, mplsXCOutSegmentIndex = 0x00000001,
mplsXCLspId = 0x0102 -- unique ID mplsXCLspId = 0x0102 -- unique ID
-- only a single outgoing label -- only a single outgoing label
mplsXCLabelStackIndex = 0x00, mplsXCLabelStackIndex = 0x00,
mplsXCRowStatus = createAndGo(4) mplsXCRowStatus = createAndGo(4)
skipping to change at page 21, line 20 skipping to change at page 20, line 32
In mplsXCTable: In mplsXCTable:
{ {
mplsXCIndex = 0x01, mplsXCIndex = 0x01,
mplsXCInSegmentIndex = 0x00000000, mplsXCInSegmentIndex = 0x00000000,
mplsXCOutSegmentIndex = 0x00000001, mplsXCOutSegmentIndex = 0x00000001,
mplsXCLspId = 0x0102 -- unique ID mplsXCLspId = 0x0102 -- unique ID
-- only a single outgoing label -- only a single outgoing label
mplsXCLabelStackIndex = 0x00, mplsXCLabelStackIndex = 0x00,
mplsXCRowStatus = createAndGo(4) mplsXCRowStatus = createAndGo(4)
} }
9.2.5. Forward direction mplsXCExtEntry 9.2.5. Forward-Direction mplsXCExtEntry
In mplsXCExtTable (0x01, 0x00000000, 0x00000001) In mplsXCExtTable (0x01, 0x00000000, 0x00000001)
{ {
-- Back pointer from XC table to Tunnel table -- Back pointer from XC table to Tunnel table
mplsXCExtTunnelPointer = mplsTunnelName.1.1.1.2 mplsXCExtTunnelPointer = mplsTunnelName.1.1.1.2
mplsXCExtOppositeDirXCPtr = mplsXCExtOppositeDirXCPtr =
mplsXCLspId.4.0.0.0.1.4.0.0.0.1.1.0 mplsXCLspId.4.0.0.0.1.4.0.0.0.1.1.0
} }
9.2.6. Reverse direction mplsTunnelEntry 9.2.6. Reverse-Direction mplsTunnelEntry
The following denotes the configured associated bidirectional reverse The following denotes the configured associated bidirectional reverse
tunnel "tail" entry: tunnel "tail" entry:
In mplsTunnelTable: In mplsTunnelTable:
{ {
mplsTunnelIndex = 2, mplsTunnelIndex = 2,
mplsTunnelInstance = 1, mplsTunnelInstance = 1,
-- Local map number created in mplsTunnelExtNodeConfigTable for -- Local map number created in mplsTunnelExtNodeConfigTable for
-- Ingress LSR-Id -- Ingress LSR ID
mplsTunnelIngressLSRId = 2, mplsTunnelIngressLSRId = 2,
-- Local map number created in mplsTunnelExtNodeConfigTable for -- Local map number created in mplsTunnelExtNodeConfigTable for
-- Egress LSR-Id -- Egress LSR ID
mplsTunnelEgressLSRId = 1, mplsTunnelEgressLSRId = 1,
mplsTunnelName = "TP associated bidirectional mplsTunnelName = "TP associated bidirectional
reverse LSP", reverse LSP",
mplsTunnelDescr = "West to East", mplsTunnelDescr = "West to East",
mplsTunnelIsIf = true (1), mplsTunnelIsIf = true (1),
-- RowPointer MUST point to the first accessible column -- RowPointer MUST point to the first accessible column
mplsTunnelXCPointer = mplsTunnelXCPointer =
mplsXCLspId.4.0.0.0.1.4.0.0.0.1.1.0, mplsXCLspId.4.0.0.0.1.4.0.0.0.1.1.0,
mplsTunnelSignallingProto = none (1), mplsTunnelSignallingProto = none (1),
mplsTunnelSetupPrio = 0, mplsTunnelSetupPrio = 0,
skipping to change at page 22, line 27 skipping to change at page 22, line 5
mplsTunnelHopTableIndex = 1, mplsTunnelHopTableIndex = 1,
mplsTunnelIncludeAnyAffinity = 0, mplsTunnelIncludeAnyAffinity = 0,
mplsTunnelIncludeAllAffinity = 0, mplsTunnelIncludeAllAffinity = 0,
mplsTunnelExcludeAnyAffinity = 0, mplsTunnelExcludeAnyAffinity = 0,
mplsTunnelRole = head (1), mplsTunnelRole = head (1),
-- Mandatory parameters needed to activate the row go here -- Mandatory parameters needed to activate the row go here
mplsTunnelRowStatus = createAndGo (4) mplsTunnelRowStatus = createAndGo (4)
} }
9.2.7. Reverse direction mplsTunnelExtEntry 9.2.7. Reverse-Direction mplsTunnelExtEntry
For the associated bidirectional reverse LSP,
in mplsTunnelExtTable:
For Associated bidirectional reverse LSP,
In mplsTunnelExtTable:
{ {
mplsTunnelExtOppositeDirPtr = mplsTunnelName.1.1.1.2 mplsTunnelExtOppositeDirPtr = mplsTunnelName.1.1.1.2
-- Set both the Ingress and Egress LocalId objects to TRUE as -- Set both the Ingress and Egress LocalId objects to TRUE, as
-- this tunnel entry uses the local identifiers. -- this tunnel entry uses the local identifiers.
mplsTunnelExtIngressLSRLocalIdValid = true, mplsTunnelExtIngressLSRLocalIdValid = true,
mplsTunnelExtEgressLSRLocalIdValid = true mplsTunnelExtEgressLSRLocalIdValid = true
} }
9.2.8. Reverse direction mplsInSegmentEntry 9.2.8. Reverse-Direction mplsInSegmentEntry
We must next create the appropriate in-segment and out-segment Next, we must create the appropriate in-segment and out-segment
entries. These are done in [RFC3813] using the mplsInSegmentTable and entries. These are done in [RFC3813] using the mplsInSegmentTable
mplsOutSegmentTable. and mplsOutSegmentTable.
In mplsInSegmentTable: In mplsInSegmentTable:
{ {
mplsInSegmentIndex = 0x0000001 mplsInSegmentIndex = 0x0000001
mplsInSegmentLabel = 21, -- incoming label mplsInSegmentLabel = 21, -- incoming label
mplsInSegmentNPop = 1, mplsInSegmentNPop = 1,
mplsInSegmentInterface = 13, -- incoming interface mplsInSegmentInterface = 13, -- incoming interface
-- RowPointer MUST point to the first accessible column. -- RowPointer MUST point to the first accessible column.
mplsInSegmentTrafficParamPtr = 0.0, mplsInSegmentTrafficParamPtr = 0.0,
mplsInSegmentRowStatus = createAndGo (4) mplsInSegmentRowStatus = createAndGo (4)
} }
Next, two cross-connect entries are created in the mplsXCTable of the Next, two cross-connect entries are created in the mplsXCTable of the
MPLS-LSR-STD-MIB [RFC3813], thereby associating the newly created MPLS-LSR-STD-MIB [RFC3813], thereby associating the newly created
segments together. segments together.
9.2.9. Reverse direction mplsXCEntry 9.2.9. Reverse-Direction mplsXCEntry
In mplsXCTable: In mplsXCTable:
{ {
mplsXCIndex = 0x01, mplsXCIndex = 0x01,
mplsXCInSegmentIndex = 0x00000001, mplsXCInSegmentIndex = 0x00000001,
mplsXCOutSegmentIndex = 0x00000000, mplsXCOutSegmentIndex = 0x00000000,
mplsXCLspId = 0x0102 -- unique ID mplsXCLspId = 0x0102 -- unique ID
-- only a single outgoing label -- only a single outgoing label
mplsXCLabelStackIndex = 0x00, mplsXCLabelStackIndex = 0x00,
mplsXCRowStatus = createAndGo(4) mplsXCRowStatus = createAndGo(4)
} }
This table entry is extended by an entry in the mplsXCExtTable. Note
that the nature of the 'extends' relationship is a sparse
augmentation so that the entry in the mplsXCExtTable has the same
index values as the entry in the mplsXCTable.
This table entry is extended by entry in the 9.2.10. Reverse-Direction mplsXCExtEntry
mplsXCExtTable. Note that the nature of the 'extends'
relationship is a sparse augmentation so that the entry in the
mplsXCExtTable has the same index values as the entry in
the mplsXCTable.
9.2.10. Reverse direction mplsXCExtEntry
Next for the reverse direction: Next, for the reverse direction:
In mplsXCExtTable (0x01, 0x00000001, 0x00000000) In mplsXCExtTable (0x01, 0x00000001, 0x00000000)
{ {
-- Back pointer from XC table to Tunnel table -- Back pointer from XC table to Tunnel table
mplsXCExtTunnelPointer = mplsTunnelName.2.1.2.1 mplsXCExtTunnelPointer = mplsTunnelName.2.1.2.1
mplsXCExtOppositeDirXCPtr = mplsXCExtOppositeDirXCPtr =
mplsXCLspId.4.0.0.0.1.1.0.4.0.0.0.1 mplsXCLspId.4.0.0.0.1.1.0.4.0.0.0.1
} }
9.3. Example of MPLS-TP signaled co-routed bidirectional tunnel setup 9.3. Example of MPLS-TP Signaled Co-routed Bidirectional Tunnel Setup
The following denotes the co-routed bidirectional tunnel "head" entry The following denotes the co-routed bidirectional tunnel "head"
and in intermediate and tail-end nodes, the tunnel table and its entry. In intermediate and tail-end nodes, the tunnel table and its
associated tables are created by the local management subsystem associated tables are created by the local management subsystem
(e.g. agent) when the MPLS TP tunnel is signaled successfully. (e.g., agent) when the MPLS-TP Tunnel is signaled successfully.
Refer to [RFC3812] and [RFC4802] for examples of signaled tunnel
Refer [RFC3812] and [RFC4802] for signaled tunnel table table configuration.
configuration examples.
9.3.1. mplsTunnelEntry 9.3.1. mplsTunnelEntry
In mplsTunnelTable: In mplsTunnelTable:
{ {
mplsTunnelIndex = 1, mplsTunnelIndex = 1,
mplsTunnelInstance = 0, mplsTunnelInstance = 0,
-- Local map number created in mplsTunnelExtNodeConfigTable for -- Local map number created in mplsTunnelExtNodeConfigTable for
-- Ingress LSR-Id, for the intermediate and tail-end nodes, -- Ingress LSR-Id. For the intermediate and tail-end nodes,
-- the local management entity is expected to pick a first available -- the local management entity is expected to pick the first
-- local identifier which is not used in mplsTunnelTable. -- available local identifier that is not used in mplsTunnelTable.
mplsTunnelIngressLSRId = 1, mplsTunnelIngressLSRId = 1,
-- Local map number created in mplsTunnelExtNodeConfigTable for -- Local map number created in mplsTunnelExtNodeConfigTable for
-- Egress LSR-Id -- Egress LSR ID
mplsTunnelEgressLSRId = 2, mplsTunnelEgressLSRId = 2,
mplsTunnelName = "TP co-routed bidirectional LSP", mplsTunnelName = "TP co-routed bidirectional LSP",
mplsTunnelDescr = "East to West", mplsTunnelDescr = "East to West",
mplsTunnelIsIf = true (1), mplsTunnelIsIf = true (1),
-- RowPointer MUST point to the first accessible column -- RowPointer MUST point to the first accessible column
mplsTunnelXCPointer = mplsTunnelXCPointer =
mplsXCLspId.4.0.0.0.1.1.0.4.0.0.0.1, mplsXCLspId.4.0.0.0.1.1.0.4.0.0.0.1,
mplsTunnelSignallingProto = none (1), mplsTunnelSignallingProto = none (1),
mplsTunnelSetupPrio = 0, mplsTunnelSetupPrio = 0,
skipping to change at page 24, line 48 skipping to change at page 24, line 25
mplsTunnelInstancePriority = 1, mplsTunnelInstancePriority = 1,
mplsTunnelHopTableIndex = 1, mplsTunnelHopTableIndex = 1,
mplsTunnelIncludeAnyAffinity = 0, mplsTunnelIncludeAnyAffinity = 0,
mplsTunnelIncludeAllAffinity = 0, mplsTunnelIncludeAllAffinity = 0,
mplsTunnelExcludeAnyAffinity = 0, mplsTunnelExcludeAnyAffinity = 0,
mplsTunnelRole = head (1), mplsTunnelRole = head (1),
-- Mandatory parameters needed to activate the row go here -- Mandatory parameters needed to activate the row go here
mplsTunnelRowStatus = createAndGo (4) mplsTunnelRowStatus = createAndGo (4)
} }
9.3.2. mplsTunnelExtEntry 9.3.2. mplsTunnelExtEntry
-- An MPLS extension table -- An MPLS extension table
In mplsTunnelExtTable: In mplsTunnelExtTable:
{ {
-- This opposite direction tunnel pointer may point to 0.0 -- This opposite-direction tunnel pointer may point to 0.0
-- if co-routed bidirectional tunnel is managed by single tunnel -- if co-routed bidirectional tunnel is managed by a single
-- entry -- tunnel entry
mplsTunnelExtOppositeDirTnlPtr = 0.0 mplsTunnelExtOppositeDirTnlPtr = 0.0
-- Set both the Ingress and Egress LocalId objects to TRUE as -- Set both the Ingress and Egress LocalId objects to TRUE, as
-- this tunnel entry uses the local identifiers. -- this tunnel entry uses the local identifiers.
mplsTunnelExtIngressLSRLocalIdValid = true, mplsTunnelExtIngressLSRLocalIdValid = true,
mplsTunnelExtEgressLSRLocalIdValid = true mplsTunnelExtEgressLSRLocalIdValid = true
} }
We must next create the appropriate in-segment and out-segment Next, we must create the appropriate in-segment and out-segment
entries. These are done in [RFC3813] using the mplsInSegmentTable and entries. These are done in [RFC3813] using the mplsInSegmentTable
mplsOutSegmentTable. and mplsOutSegmentTable.
9.3.3. Forward direction mplsOutSegmentEntry 9.3.3. Forward-Direction mplsOutSegmentEntry
The forward direction mplsOutSegmentTable will be populated The forward-direction mplsOutSegmentTable will be populated
automatically based on the information received from the signaling automatically based on the information received from the signaling
protocol. protocol.
9.3.4. Reverse direction mplsInSegmentEntry 9.3.4. Reverse-Direction mplsInSegmentEntry
The reverse direction mplsOutSegmentTable will be populated The reverse-direction mplsOutSegmentTable will be populated
automatically based on the information received from the signaling automatically based on the information received from the signaling
protocol. protocol.
Next, two cross-connect entries are created in the mplsXCTable of the Next, two cross-connect entries are created in the mplsXCTable of the
MPLS-LSR-STD-MIB [RFC3813], thereby associating the newly created MPLS-LSR-STD-MIB [RFC3813], thereby associating the newly created
segments together. segments together.
9.3.5. Forward direction mplsXCEntry 9.3.5. Forward-Direction mplsXCEntry
The forward direction mplsXCEntry will be populated as soon as the The forward-direction mplsXCEntry will be populated as soon as the
forward path label information is available. forward-path label information is available.
9.3.6. Reverse direction mplsXCEntry 9.3.6. Reverse-Direction mplsXCEntry
The reverse direction mplsXCEntry will be populated as soon as the The reverse-direction mplsXCEntry will be populated as soon as the
reverse path label information is available. reverse-path label information is available.
This table entry is extended by entry in the mplsXCExtTable. Note This table entry is extended by an entry in the mplsXCExtTable. Note
that the nature of the 'extends' relationship is a sparse that the nature of the 'extends' relationship is a sparse
augmentation so that the entry in the mplsXCExtTable has the same augmentation so that the entry in the mplsXCExtTable has the same
index values as the entry in the mplsXCTable. index values as the entry in the mplsXCTable.
9.3.7. Forward direction mplsXCExtEntry 9.3.7. Forward-Direction mplsXCExtEntry
Once the forward path information is negotiated using signaling Once the forward path information is negotiated using the signaling
protocol, the forward direction mplsXCExtEntry will be created for protocol, the forward-direction mplsXCExtEntry will be created for
associating the opposite direction XC entry and tunnel table entry. associating the opposite-direction XC entry and tunnel table entry.
9.3.8. Reverse direction mplsXCExtEntry 9.3.8. Reverse-Direction mplsXCExtEntry
Once the reverse path information is negotiated using signaling Once the reverse path information is negotiated using the signaling
protocol, the reverse direction mplsXCExtEntry will be created for protocol, the reverse-direction mplsXCExtEntry will be created for
associating the opposite direction XC entry and tunnel table entry. associating the opposite-direction XC entry and tunnel table entry.
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 -- RFC 2578
TEXTUAL-CONVENTION TEXTUAL-CONVENTION
FROM SNMPv2-TC -- [RFC2579] FROM SNMPv2-TC -- RFC 2579
mplsStdMIB mplsStdMIB
FROM MPLS-TC-STD-MIB -- [RFC3811] FROM MPLS-TC-STD-MIB -- RFC 3811
; ;
mplsTcExtStdMIB MODULE-IDENTITY mplsTcExtStdMIB MODULE-IDENTITY
LAST-UPDATED LAST-UPDATED
"201412180000Z" -- December 18, 2014 "201502020000Z" -- February 2, 2015
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 27, line 4 skipping to change at page 26, line 44
Kannan KV Sampath Kannan KV Sampath
Redeem, Redeem,
India India
Email: kannankvs@gmail.com Email: kannankvs@gmail.com
Sam Aldrin Sam Aldrin
Huawei Technologies Huawei Technologies
2330 Central Express Way, 2330 Central Express Way,
Santa Clara, CA 95051, USA Santa Clara, CA 95051, USA
Email: aldrin.ietf@gmail.com Email: aldrin.ietf@gmail.com
Thomas D. Nadeau Thomas D. Nadeau
Email: tnadeau@lucidvision.com Email: tnadeau@lucidvision.com
" "
DESCRIPTION DESCRIPTION
"Copyright (c) 2014 IETF Trust and the persons identified "This MIB module contains Textual Conventions for LSPs of MPLS-
as the document authors. All rights reserved. based transport networks.
This MIB module contains Textual Conventions for LSPs of MPLS Copyright (c) 2015 IETF Trust and the persons identified as
based transport networks." authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject to
the license terms contained in, the Simplified BSD License set
forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents
(http://trustee.ietf.org/license-info)."
-- Revision history. -- Revision history.
REVISION REVISION
"201502020000Z" -- February 2, 2015
"201412180000Z" -- December 18, 2014
DESCRIPTION DESCRIPTION
"MPLS Textual Convention Extensions" "MPLS Textual Convention Extensions"
::= { mplsStdMIB www } -- www to be replaced with correct value ::= { mplsStdMIB 17 }
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 an IP-based
operator unique identifier (Global_ID), the Global_ID can operator-unique identifier (Global_ID). The Global_ID can
contain the 2-octet or 4-octet value of the operator's contain the 2-octet or 4-octet value of the operator's
Autonomous System Number (ASN). Autonomous System Number (ASN).
When the Global_ID is derived from a 2-octet AS number, When the Global_ID is derived from a 2-octet ASN,
the two high-order octets of this 4-octet identifier the two high-order octets of this 4-octet identifier
MUST be set to zero(0x00). Further ASN 0 is reserved. MUST be set to zero (0x00). Further, ASN 0 is reserved.
The size of the Global_ID string MUST be zero if The size of the Global_ID string MUST be zero if
the Global_ID is invalid. the Global_ID is invalid.
Note that a Global_ID of zero is limited to entities Note that a Global_ID of zero is limited to entities
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 a 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, RFC 6370,
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 characters, each "The CC (Country Code) is a string of two characters, each
being an uppercase Basic Latin alphabetic (i.e., A-Z). being an uppercase Basic Latin alphabetic (i.e., A-Z).
The characters are encoded using ITU-T Recommendation T.50. The characters are encoded using ITU-T Recommendation T.50.
The size of the CC string MUST be zero if the CC identifier The size of the CC string MUST be zero if the CC identifier
is invalid." is invalid."
REFERENCE REFERENCE
"MPLS-TP Identifiers Following ITU-T Conventions, "MPLS-TP Identifiers Following ITU-T Conventions,
RFC 6923, Section 3. RFC 6923, Section 3.
International Reference Alphabet (IRA) (Formerly International Reference Alphabet (IRA) (Formerly
International Alphabet No. 5 or IA5) - Information International Alphabet No. 5 or IA5) - Information
technology - 7-bit coded character set for information technology - 7-bit coded character set for information
exchange, ITU-T Recommendation T.50, September 1992. " exchange, ITU-T Recommendation T.50, September 1992."
SYNTAX OCTET STRING (SIZE (0|2)) 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
an upper case Basic Latin alphabetic (i.e., A-Z) or an uppercase Basic Latin alphabetic (i.e., A-Z) or
numeric (i.e., 0-9). The characters are encoded numeric (i.e., 0-9). The characters are encoded
using ITU-T Recommendation T.50. The size of using ITU-T Recommendation T.50. The size of
the ICC string MUST be zero if the ICC identifier the ICC string MUST 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. RFC 6923, Section 3.
International Reference Alphabet (IRA) (Formerly International Reference Alphabet (IRA) (Formerly
International Alphabet No. 5 or IA5) - Information International Alphabet No. 5 or IA5) - Information
technology - 7-bit coded character set for information technology - 7-bit coded character set for information
exchange, ITU-T Recommendation T.50, September 1992. " 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
can be derived from the LSR's IPv4 loop back address. can be derived from the LSR's IPv4 loopback 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 reachability is not needed, the 32-bit Note that, when IP reachability 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. The value of 0 indicates with the IPv4 address space. The value of 0 indicates
the invalid Node identifier." an invalid Node_ID."
REFERENCE REFERENCE
"MPLS Transport Profile (MPLS-TP) Identifiers, [RFC6370] "MPLS Transport Profile (MPLS-TP) Identifiers, RFC 6370,
Section 4" Section 4"
SYNTAX Unsigned32 (0|1..4294967295) SYNTAX Unsigned32 (0|1..4294967295)
-- 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
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE
FROM SNMPv2-SMI -- [RFC2578]
MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF -- [RFC2580]
mplsStdMIB
FROM MPLS-TC-STD-MIB -- [RFC3811]
MplsGlobalId, MplsCcId, MplsIccId, MplsNodeId
FROM MPLS-TC-EXT-STD-MIB
;
mplsIdStdMIB MODULE-IDENTITY
LAST-UPDATED
"201412120000Z" -- December 12, 2014
ORGANIZATION
"Multiprotocol Label Switching (MPLS) Working Group"
CONTACT-INFO
"
Venkatesan Mahalingam
Dell Inc,
5450 Great America Parkway,
Santa Clara, CA 95054, USA
Email: venkat.mahalingams@gmail.com
Kannan KV Sampath MPLS-ID-STD-MIB DEFINITIONS ::= BEGIN
Redeem, IMPORTS
India MODULE-IDENTITY, OBJECT-TYPE
Email: kannankvs@gmail.com FROM SNMPv2-SMI -- RFC 2578
MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF -- RFC 2580
mplsStdMIB
FROM MPLS-TC-STD-MIB -- RFC 3811
MplsGlobalId, MplsCcId, MplsIccId, MplsNodeId
FROM MPLS-TC-EXT-STD-MIB
;
Sam Aldrin mplsIdStdMIB MODULE-IDENTITY
Huawei Technologies LAST-UPDATED
2330 Central Express Way, "201502020000Z" -- February 2, 2015
Santa Clara, CA 95051, USA ORGANIZATION
Email: aldrin.ietf@gmail.com "Multiprotocol Label Switching (MPLS) Working Group"
Thomas D. Nadeau CONTACT-INFO
Email: tnadeau@lucidvision.com
" "
DESCRIPTION Venkatesan Mahalingam
"Copyright (c) 2014 IETF Trust and the persons identified Dell Inc,
as the document authors. All rights reserved. 5450 Great America Parkway,
Santa Clara, CA 95054, USA
Email: venkat.mahalingams@gmail.com
This MIB module contains generic object definitions for Kannan KV Sampath
MPLS Traffic Engineering in transport networks." Redeem,
India
Email: kannankvs@gmail.com
-- Revision history. Sam Aldrin
Huawei Technologies
2330 Central Express Way,
Santa Clara, CA 95051, USA
Email: aldrin.ietf@gmail.com
Thomas D. Nadeau
Email: tnadeau@lucidvision.com
"
DESCRIPTION
"This MIB module contains identifier object definitions for
MPLS Traffic Engineering in transport networks.
REVISION Copyright (c) 2015 IETF Trust and the persons identified as
"201412120000Z" -- December 12, 2014 authors of the code. All rights reserved.
DESCRIPTION
"This MIB modules defines the MIB objects for MPLS-TP
identifiers"
::= { mplsStdMIB xxx } -- xxx to be replaced with correct value Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject to
the license terms contained in, the Simplified BSD License set
forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents
(http://trustee.ietf.org/license-info)."
-- notifications -- Revision history.
mplsIdNotifications OBJECT IDENTIFIER ::= { mplsIdStdMIB 0 }
-- tables, scalars
mplsIdObjects OBJECT IDENTIFIER ::= { mplsIdStdMIB 1 }
-- conformance
mplsIdConformance OBJECT IDENTIFIER ::= { mplsIdStdMIB 2 }
-- MPLS common objects REVISION
"201502020000Z" -- February 2, 2015
DESCRIPTION
"This MIB modules defines the MIB objects for MPLS-TP
identifiers"
mplsIdGlobalId OBJECT-TYPE ::= { mplsStdMIB 18 }
SYNTAX MplsGlobalId
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object allows the operator or service provider to
assign a unique operator identifier also called MPLS-TP
Global_ID.
If this value is used in mplsTunnelExtNodeConfigGlobalId
for mapping Global_ID::Node_ID with the local identifier
then this object value MUST NOT be changed."
::= { mplsIdObjects 1 }
mplsIdNodeId OBJECT-TYPE -- notifications
SYNTAX MplsNodeId mplsIdNotifications OBJECT IDENTIFIER ::= { mplsIdStdMIB 0 }
MAX-ACCESS read-write -- tables, scalars
STATUS current mplsIdObjects OBJECT IDENTIFIER ::= { mplsIdStdMIB 1 }
DESCRIPTION -- conformance
"This object allows the operator or service provider to mplsIdConformance OBJECT IDENTIFIER ::= { mplsIdStdMIB 2 }
assign a unique MPLS-TP Node_ID. The Node_ID is assigned
within the scope of the Global_ID/ICC_Operator_ID.
If this value is used in mplsTunnelExtNodeConfigNodeId
for mapping Global_ID::Node_ID with the local identifier
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 MUST NOT be changed."
::= { mplsIdObjects 2 }
mplsIdCc OBJECT-TYPE -- MPLS common objects
SYNTAX MplsCcId
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object allows the operator or service provider to
assign a Country Code (CC) to the node. Global
uniqueness of ICC is assured by concatenating the ICC
with a Country Code (CC).
If this value is used in mplsTunnelExtNodeConfigCcId
for mapping ICC_Operator_ID::Node_ID with the local
identifier then this object value MUST NOT be changed."
REFERENCE
"MPLS-TP Identifiers Following ITU-T Conventions,
[RFC6923] Section 3"
::= { mplsIdObjects 3 }
mplsIdIcc OBJECT-TYPE mplsIdGlobalId OBJECT-TYPE
SYNTAX MplsIccId SYNTAX MplsGlobalId
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 operator identifier, also called the MPLS-TP
the node. Together, the CC and the ICC form Global_ID.
the ICC_Operator_ID as CC::ICC. If this value is used in mplsTunnelExtNodeConfigGlobalId
If this value is used in mplsTunnelExtNodeConfigIccId for mapping Global_ID::Node_ID with the local identifier,
for mapping ICC_Operator_ID::Node_ID with the local then this object value MUST NOT be changed."
identifier then this object value MUST NOT be changed." ::= { mplsIdObjects 1 }
REFERENCE
"MPLS-TP Identifiers Following ITU-T Conventions,
[RFC6923] Section 3"
::= { mplsIdObjects 4 } mplsIdNodeId OBJECT-TYPE
SYNTAX MplsNodeId
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object allows the operator or service provider to
assign a unique MPLS-TP Node_ID. The Node_ID is assigned
within the scope of the Global_ID/ICC_Operator_ID.
If this value is used in mplsTunnelExtNodeConfigNodeId
for mapping Global_ID::Node_ID with the local identifier,
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 MUST NOT be changed."
::= { mplsIdObjects 2 }
-- Module compliance. mplsIdCc OBJECT-TYPE
SYNTAX MplsCcId
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object allows the operator or service provider to
assign a Country Code (CC) to the node. Global
uniqueness of ICC is assured by concatenating the ICC
with a Country Code (CC).
If this value is used in mplsTunnelExtNodeConfigCcId
for mapping ICC_Operator_ID::Node_ID with the local
identifier, then this object value MUST NOT be changed."
REFERENCE
"MPLS-TP Identifiers Following ITU-T Conventions,
RFC 6923, Section 3"
::= { mplsIdObjects 3 }
mplsIdCompliances mplsIdIcc OBJECT-TYPE
OBJECT IDENTIFIER ::= { mplsIdConformance 1 } SYNTAX MplsIccId
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object allows the operator or service provider to
assign a unique MPLS-TP ITU-T Carrier Code (ICC) to
the node. Together, the CC and the ICC form
the ICC_Operator_ID as CC::ICC.
If this value is used in mplsTunnelExtNodeConfigIccId
for mapping ICC_Operator_ID::Node_ID with the local
identifier, then this object value MUST NOT be changed."
REFERENCE
"MPLS-TP Identifiers Following ITU-T Conventions,
RFC 6923, Section 3"
mplsIdGroups ::= { mplsIdObjects 4 }
OBJECT IDENTIFIER ::= { mplsIdConformance 2 }
-- Compliance requirement for fully compliant implementations. -- Module compliance.
mplsIdModuleFullCompliance MODULE-COMPLIANCE mplsIdCompliances
STATUS current OBJECT IDENTIFIER ::= { mplsIdConformance 1 }
DESCRIPTION
"Compliance statement for agents that provide full
support of the MPLS-ID-STD-MIB module."
MODULE -- this module mplsIdGroups
OBJECT IDENTIFIER ::= { mplsIdConformance 2 }
-- The mandatory group has to be implemented by all LSRs that -- Compliance requirement for fully compliant implementations.
-- originate, terminate, or act as transit for MPLS-TP tunnels.
GROUP mplsIdIpOperatorGroup mplsIdModuleFullCompliance MODULE-COMPLIANCE
DESCRIPTION STATUS current
"This group is mandatory for devices which support DESCRIPTION
IP based identifier configuration." "Compliance statement for agents that provide full
support of the MPLS-ID-STD-MIB module."
GROUP mplsIdIccOperatorGroup MODULE -- this module
DESCRIPTION
"This group is mandatory for devices which support
ICC based identifier configuration."
::= { mplsIdCompliances 1 } -- The mandatory group has to be implemented by all LSRs that
-- originate, terminate, or act as transit for MPLS-TP Tunnels.
-- Compliance requirement for read-only implementations. GROUP mplsIdIpOperatorGroup
DESCRIPTION
"This group is mandatory for devices that support
IP-based identifier configuration."
mplsIdModuleReadOnlyCompliance MODULE-COMPLIANCE GROUP mplsIdIccOperatorGroup
STATUS current DESCRIPTION
DESCRIPTION "This group is mandatory for devices that support
"Compliance statement for agents that only provide ICC-based identifier configuration."
read-only support for the MPLS-ID-STD-MIB module."
MODULE -- this module ::= { mplsIdCompliances 1 }
GROUP mplsIdIpOperatorGroup -- Compliance requirement for read-only implementations.
DESCRIPTION
"This group is mandatory for devices which support
IP based identifier configuration."
GROUP mplsIdIccOperatorGroup mplsIdModuleReadOnlyCompliance MODULE-COMPLIANCE
DESCRIPTION STATUS current
"This group is mandatory for devices which support DESCRIPTION
ICC based identifier configuration." "Compliance statement for agents that only provide
read-only support for the MPLS-ID-STD-MIB module."
OBJECT mplsIdGlobalId MODULE -- this module
MIN-ACCESS read-only GROUP mplsIdIpOperatorGroup
DESCRIPTION DESCRIPTION
"Write access is not required." "This group is mandatory for devices that support
IP-based identifier configuration."
OBJECT mplsIdNodeId GROUP mplsIdIccOperatorGroup
MIN-ACCESS read-only DESCRIPTION
DESCRIPTION "This group is mandatory for devices that support
"Write access is not required." ICC-based identifier configuration."
OBJECT mplsIdCc OBJECT mplsIdGlobalId
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsIdIcc OBJECT mplsIdNodeId
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
::= { mplsIdCompliances 2 } OBJECT mplsIdCc
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
-- Units of conformance. OBJECT mplsIdIcc
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
mplsIdIpOperatorGroup OBJECT-GROUP ::= { mplsIdCompliances 2 }
OBJECTS { mplsIdGlobalId,
mplsIdNodeId
}
STATUS current
DESCRIPTION
"The objects in this group are optional for ICC based
node."
::= { mplsIdGroups 1 }
mplsIdIccOperatorGroup OBJECT-GROUP -- Units of conformance.
OBJECTS { mplsIdNodeId,
mplsIdCc,
mplsIdIcc
} mplsIdIpOperatorGroup OBJECT-GROUP
STATUS current OBJECTS { mplsIdGlobalId,
DESCRIPTION mplsIdNodeId
"The objects in this group are optional for IP based }
node." STATUS current
::= { mplsIdGroups 2 } DESCRIPTION
"The objects in this group are optional for an
ICC-based node."
::= { mplsIdGroups 1 }
-- MPLS-ID-STD-MIB module ends mplsIdIccOperatorGroup OBJECT-GROUP
END OBJECTS { mplsIdNodeId,
mplsIdCc,
mplsIdIcc
}
STATUS current
DESCRIPTION
"The objects in this group are optional for an
IP-based node."
::= { mplsIdGroups 2 }
12. MPLS LSR Extension MIB definitions -- MPLS-ID-STD-MIB module ends
END
12. MPLS LSR Extension MIB Definitions
MPLS-LSR-EXT-STD-MIB DEFINITIONS ::= BEGIN MPLS-LSR-EXT-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE MODULE-IDENTITY, OBJECT-TYPE
FROM SNMPv2-SMI -- [RFC2578] FROM SNMPv2-SMI -- RFC 2578
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF -- [RFC2580] FROM SNMPv2-CONF -- RFC 2580
mplsStdMIB mplsStdMIB
FROM MPLS-TC-STD-MIB -- [RFC3811] FROM MPLS-TC-STD-MIB -- RFC 3811
RowPointer RowPointer
FROM SNMPv2-TC -- [RFC2579] FROM SNMPv2-TC -- RFC 2579
mplsXCIndex, mplsXCInSegmentIndex, mplsXCOutSegmentIndex, mplsXCIndex, mplsXCInSegmentIndex, mplsXCOutSegmentIndex,
mplsInterfaceGroup, mplsInSegmentGroup, mplsOutSegmentGroup, mplsInterfaceGroup, mplsInSegmentGroup, mplsOutSegmentGroup,
mplsXCGroup, mplsLsrNotificationGroup mplsXCGroup, mplsLsrNotificationGroup
FROM MPLS-LSR-STD-MIB; -- [RFC3813] FROM MPLS-LSR-STD-MIB; -- RFC 3813
mplsLsrExtStdMIB MODULE-IDENTITY mplsLsrExtStdMIB MODULE-IDENTITY
LAST-UPDATED LAST-UPDATED
"201412120000Z" -- December 12, 2014 "201502020000Z" -- February 2, 2015
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
Kannan KV Sampath Kannan KV Sampath
Redeem, Redeem,
India India
Email: kannankvs@gmail.com Email: kannankvs@gmail.com
Sam Aldrin Sam Aldrin
Huawei Technologies Huawei Technologies
2330 Central Express Way, 2330 Central Express Way,
Santa Clara, CA 95051, USA Santa Clara, CA 95051, USA
Email: aldrin.ietf@gmail.com Email: aldrin.ietf@gmail.com
Thomas D. Nadeau Thomas D. Nadeau
Email: tnadeau@lucidvision.com Email: tnadeau@lucidvision.com
" "
DESCRIPTION DESCRIPTION
"Copyright (c) 2014 IETF Trust and the persons identified "This MIB module contains generic object definitions for
as the document authors. All rights reserved. MPLS LSRs in transport networks.
This MIB module contains generic object definitions for Copyright (c) 2015 IETF Trust and the persons identified as
MPLS LSR in transport networks." authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject to
the license terms contained in, the Simplified BSD License set
forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents
(http://trustee.ietf.org/license-info)."
-- Revision history. -- Revision history.
REVISION REVISION
"201412120000Z" -- December 12, 2014 "201502020000Z" -- February 2, 2015
DESCRIPTION DESCRIPTION
"MPLS LSR specific MIB objects extension" "MPLS LSR-specific MIB objects extension"
::= { mplsStdMIB yyy } -- yyy to be replaced with correct value ::= { mplsStdMIB 19 }
-- notifications -- notifications
mplsLsrExtNotifications OBJECT IDENTIFIER ::= { mplsLsrExtStdMIB 0 } mplsLsrExtNotifications OBJECT IDENTIFIER ::= { mplsLsrExtStdMIB 0 }
-- tables, scalars -- tables, scalars
mplsLsrExtObjects OBJECT IDENTIFIER mplsLsrExtObjects OBJECT IDENTIFIER
::= { mplsLsrExtStdMIB 1 } ::= { mplsLsrExtStdMIB 1 }
-- conformance -- conformance
mplsLsrExtConformance OBJECT IDENTIFIER mplsLsrExtConformance OBJECT IDENTIFIER
::= { mplsLsrExtStdMIB 2 } ::= { 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 (RFC 3813) to provide MPLS-TP-specific
information about associated tunnel information" information about associated tunnel information"
REFERENCE REFERENCE
"1. Multiprotocol Label Switching (MPLS) Label Switching "Multiprotocol Label Switching (MPLS) Label Switching
Router (LSR) Management Information Base (MIB), RFC 3813." Router (LSR) Management Information Base (MIB), RFC 3813."
::= { mplsLsrExtObjects 1 } ::= { mplsLsrExtObjects 1 }
mplsXCExtEntry OBJECT-TYPE mplsXCExtEntry OBJECT-TYPE
SYNTAX MplsXCExtEntry SYNTAX MplsXCExtEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table sparsely extends the cross-connect
"An entry in this table sparsely extends the cross connect
information represented by an entry in information represented by an entry in
the mplsXCTable in MPLS-LSR-STD-MIB [RFC3813] through the mplsXCTable in MPLS-LSR-STD-MIB (RFC 3813) through
a sparse augmentation. An entry can be created by a sparse augmentation. An entry can be created by
a network operator via SNMP SET commands, or in a network operator via SNMP SET commands or in
response to signaling protocol events." response to signaling protocol events."
REFERENCE REFERENCE
"1. Multiprotocol Label Switching (MPLS) Label Switching "Multiprotocol Label Switching (MPLS) Label Switching
Router (LSR) Management Information Base (MIB), RFC 3813." Router (LSR) Management Information Base (MIB), RFC 3813."
INDEX { mplsXCIndex, mplsXCInSegmentIndex, INDEX { mplsXCIndex, mplsXCInSegmentIndex,
mplsXCOutSegmentIndex } mplsXCOutSegmentIndex }
::= { mplsXCExtTable 1 } ::= { mplsXCExtTable 1 }
MplsXCExtEntry ::= SEQUENCE { MplsXCExtEntry ::= SEQUENCE {
mplsXCExtTunnelPointer RowPointer, mplsXCExtTunnelPointer RowPointer,
mplsXCExtOppositeDirXCPtr RowPointer mplsXCExtOppositeDirXCPtr RowPointer
} }
skipping to change at page 36, line 39 skipping to change at page 37, line 4
mplsXCExtTunnelPointer OBJECT-TYPE mplsXCExtTunnelPointer OBJECT-TYPE
SYNTAX RowPointer SYNTAX RowPointer
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This read-only object indicates the back pointer to "This read-only object indicates the back pointer to
the tunnel entry segment. the tunnel entry segment.
The only valid value for Tunnel Pointer is The only valid value for Tunnel Pointer is
mplsTunnelTable entry." mplsTunnelTable entry."
REFERENCE REFERENCE
"1. Multiprotocol Label Switching (MPLS) Label Switching "Multiprotocol Label Switching (MPLS) Label Switching
Router (LSR) Management Information Base (MIB), RFC 3813." Router (LSR) Management Information Base (MIB), RFC 3813."
::= { mplsXCExtEntry 1 } ::= { mplsXCExtEntry 1 }
mplsXCExtOppositeDirXCPtr OBJECT-TYPE mplsXCExtOppositeDirXCPtr OBJECT-TYPE
SYNTAX RowPointer SYNTAX RowPointer
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the pointer to the opposite "This object indicates the pointer to the opposite-
direction XC entry. This object cannot be modified if direction XC entry. This object cannot be modified if
mplsXCRowStatus for the corresponding entry in the mplsXCRowStatus for the corresponding entry in the
mplsXCTable is active(1). If this pointer is not set or mplsXCTable is active(1). If this pointer is not set or
removed, mplsXCOperStatus should be set to down(2)." removed, mplsXCOperStatus should be set to down(2)."
REFERENCE REFERENCE
"1. Multiprotocol Label Switching (MPLS) Label Switching "Multiprotocol Label Switching (MPLS) Label Switching
Router (LSR) Management Information Base (MIB), RFC 3813." Router (LSR) Management Information Base (MIB), RFC 3813."
::= { mplsXCExtEntry 2 } ::= { mplsXCExtEntry 2 }
mplsLsrExtCompliances mplsLsrExtCompliances
OBJECT IDENTIFIER ::= { mplsLsrExtConformance 1 } OBJECT IDENTIFIER ::= { mplsLsrExtConformance 1 }
mplsLsrExtGroups mplsLsrExtGroups
OBJECT IDENTIFIER ::= { mplsLsrExtConformance 2 } OBJECT IDENTIFIER ::= { mplsLsrExtConformance 2 }
-- Compliance requirement for fully compliant implementations. -- Compliance requirement for fully compliant implementations.
skipping to change at page 37, line 31 skipping to change at page 37, line 44
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Compliance statement for agents that provide full support "Compliance statement for agents that provide full support
for MPLS-LSR-EXT-STD-MIB. for MPLS-LSR-EXT-STD-MIB.
The mandatory group has to be implemented by all LSRs The mandatory group has to be implemented by all LSRs
that originate, terminate, or act as transit for that originate, terminate, or act as transit for
TE-LSPs/tunnels. TE-LSPs/tunnels.
In addition, depending on the type of tunnels supported, In addition, depending on the type of tunnels supported,
other groups become mandatory as explained below." other groups become mandatory as explained below."
MODULE MPLS-LSR-STD-MIB -- The MPLS-LSR-STD-MIB, RFC3813 MODULE MPLS-LSR-STD-MIB -- The MPLS-LSR-STD-MIB, RFC 3813
MANDATORY-GROUPS { MANDATORY-GROUPS {
mplsInSegmentGroup, mplsInSegmentGroup,
mplsOutSegmentGroup, mplsOutSegmentGroup,
mplsXCGroup, mplsXCGroup,
mplsLsrNotificationGroup mplsLsrNotificationGroup
} }
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
mplsXCExtGroup mplsXCExtGroup
} }
::= { mplsLsrExtCompliances 1 } ::= { mplsLsrExtCompliances 1 }
-- Compliance requirement for implementations that provide -- Compliance requirement for implementations that provide
-- read-only access. -- read-only access.
skipping to change at page 38, line 26 skipping to change at page 38, line 35
MANDATORY-GROUPS { MANDATORY-GROUPS {
mplsInterfaceGroup, mplsInterfaceGroup,
mplsInSegmentGroup, mplsInSegmentGroup,
mplsOutSegmentGroup mplsOutSegmentGroup
} }
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 that 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 the XC entry."
::= { mplsLsrExtGroups 1 } ::= { mplsLsrExtGroups 1 }
mplsXCExtReadOnlyObjectsGroup OBJECT-GROUP mplsXCExtReadOnlyObjectsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
mplsXCExtTunnelPointer, mplsXCExtTunnelPointer,
mplsXCExtOppositeDirXCPtr 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
MPLS-TE-EXT-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS This MIB module imports from [RFC2578], [RFC2579], [RFC2580],
MODULE-IDENTITY, OBJECT-TYPE [RFC3289], [RFC3811], and [RFC3812].
FROM SNMPv2-SMI -- [RFC2578]
MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF -- [RFC2580]
TruthValue, RowStatus, RowPointer, StorageType
FROM SNMPv2-TC -- [RFC2579]
IndexIntegerNextFree
FROM DIFFSERV-MIB -- [RFC3289]
MplsGlobalId, MplsNodeId, MplsCcId, MplsIccId
FROM MPLS-TC-EXT-STD-MIB
mplsStdMIB, MplsTunnelIndex, MplsTunnelInstanceIndex,
MplsExtendedTunnelId
FROM MPLS-TC-STD-MIB -- [RFC3811]
mplsTunnelIndex, mplsTunnelInstance, mplsTunnelIngressLSRId,
mplsTunnelEgressLSRId
FROM MPLS-TE-STD-MIB -- [RFC3812]
;
mplsTeExtStdMIB MODULE-IDENTITY MPLS-TE-EXT-STD-MIB DEFINITIONS ::= BEGIN
LAST-UPDATED
"201412120000Z" -- December 12, 2014
ORGANIZATION
"Multiprotocol Label Switching (MPLS) Working Group"
CONTACT-INFO
"
Venkatesan Mahalingam
Dell Inc,
5450 Great America Parkway,
Santa Clara, CA 95054, USA
Email: venkat.mahalingams@gmail.com
Kannan KV Sampath IMPORTS
Redeem, MODULE-IDENTITY, OBJECT-TYPE
India FROM SNMPv2-SMI -- RFC 2578
Email: kannankvs@gmail.com MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF -- RFC 2580
TruthValue, RowStatus, RowPointer, StorageType
FROM SNMPv2-TC -- RFC 2579
IndexIntegerNextFree
FROM DIFFSERV-MIB -- RFC 3289
MplsGlobalId, MplsNodeId, MplsCcId, MplsIccId
FROM MPLS-TC-EXT-STD-MIB
mplsStdMIB, MplsTunnelIndex, MplsTunnelInstanceIndex,
MplsExtendedTunnelId
FROM MPLS-TC-STD-MIB -- RFC 3811
mplsTunnelIndex, mplsTunnelInstance, mplsTunnelIngressLSRId,
mplsTunnelEgressLSRId
FROM MPLS-TE-STD-MIB -- RFC 3812
;
Sam Aldrin mplsTeExtStdMIB MODULE-IDENTITY
Huawei Technologies LAST-UPDATED
2330 Central Express Way, "201502020000Z" -- February 2, 2015
Santa Clara, CA 95051, USA ORGANIZATION
Email: aldrin.ietf@gmail.com "Multiprotocol Label Switching (MPLS) Working Group"
CONTACT-INFO
"
Venkatesan Mahalingam
Dell Inc,
5450 Great America Parkway,
Santa Clara, CA 95054, USA
Email: venkat.mahalingams@gmail.com
Thomas D. Nadeau Kannan KV Sampath
Email: tnadeau@lucidvision.com Redeem,
" India
DESCRIPTION Email: kannankvs@gmail.com
"Copyright (c) 2014 IETF Trust and the persons identified
as the document authors. All rights reserved.
This MIB module contains generic object definitions for Sam Aldrin
MPLS Traffic Engineering in transport networks." Huawei Technologies
2330 Central Express Way,
Santa Clara, CA 95051, USA
Email: aldrin.ietf@gmail.com
-- Revision history. Thomas D. Nadeau
Email: tnadeau@lucidvision.com
"
DESCRIPTION
"This MIB module contains generic object definitions for
extending the MPLS Traffic Engineering tunnels in transport
networks.
REVISION Copyright (c) 2015 IETF Trust and the persons identified as
"201412120000Z" -- December 12, 2014 authors of the code. All rights reserved.
DESCRIPTION Redistribution and use in source and binary forms, with or
"MPLS TE MIB objects extension" without modification, is permitted pursuant to, and subject to
the license terms contained in, the Simplified BSD License set
forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents
(http://trustee.ietf.org/license-info)."
::= { mplsStdMIB zzz } -- zzz to be replaced -- Revision history.
-- with correct value
-- Top level components of this MIB module. REVISION
"201502020000Z" -- February 2, 2015
-- tables, scalars DESCRIPTION
mplsTeExtObjects OBJECT IDENTIFIER "MPLS TE MIB objects extension"
::= { mplsTeExtStdMIB 0 }
-- conformance
mplsTeExtConformance OBJECT IDENTIFIER
::= { mplsTeExtStdMIB 1 }
-- Start of MPLS Transport Profile Node configuration table ::= { mplsStdMIB 20 }
mplsTunnelExtNodeConfigLocalIdNext OBJECT-TYPE
SYNTAX IndexIntegerNextFree (0..16777215)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object contains an unused value for
mplsTunnelExtNodeConfigLocalId, or a zero to indicate
that none exist. Negative values are not allowed,
as they do not correspond to valid values of
mplsTunnelExtNodeConfigLocalId."
::= { mplsTeExtObjects 1 }
mplsTunnelExtNodeConfigTable OBJECT-TYPE -- Top-level components of this MIB module.
SYNTAX SEQUENCE OF MplsTunnelExtNodeConfigEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table allows the operator to map a node or
LSR Identifier (IP compatible [Global_ID::Node_ID] or
ICC based [ICC_Operator_ID::Node_ID]) with a local
identifier.
This table is created to reuse the existing -- tables, scalars
mplsTunnelTable for MPLS based transport network mplsTeExtObjects OBJECT IDENTIFIER
tunnels also. ::= { mplsTeExtStdMIB 0 }
-- conformance
mplsTeExtConformance OBJECT IDENTIFIER
::= { mplsTeExtStdMIB 1 }
Since the MPLS tunnel's Ingress/Egress LSR identifiers' -- Start of MPLS Transport Profile Node configuration table
size (Unsigned32) value is not compatible for
MPLS-TP tunnel i.e. Global_ID::Node_ID of size 8 bytes and
ICC_Operator_ID::Node_ID of size 12 bytes, there exists a
need to map the Global_ID::Node_ID or ICC_Operator_ID::Node_ID
with the local identifier of size 4 bytes (Unsigned32) value
in order to index (Ingress/Egress LSR identifier)
the existing mplsTunnelTable."
::= { mplsTeExtObjects 2 } mplsTunnelExtNodeConfigLocalIdNext OBJECT-TYPE
SYNTAX IndexIntegerNextFree (0..16777215)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object contains an unused value for
mplsTunnelExtNodeConfigLocalId, or a zero to indicate
that none exist. Negative values are not allowed,
as they do not correspond to valid values of
mplsTunnelExtNodeConfigLocalId."
::= { mplsTeExtObjects 1 }
mplsTunnelExtNodeConfigEntry OBJECT-TYPE mplsTunnelExtNodeConfigTable OBJECT-TYPE
SYNTAX MplsTunnelExtNodeConfigEntry SYNTAX SEQUENCE OF MplsTunnelExtNodeConfigEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table represents a mapping "This table allows the operator to map a node or
identification for the operator or service provider LSR identifier (IP-compatible [Global_ID::Node_ID] or
with node or LSR. ICC-based [ICC_Operator_ID::Node_ID]) with a local
identifier.
As per [RFC6370], IP compatible mapping is represented This table is created to reuse the existing
as Global_ID::Node_ID. mplsTunnelTable for MPLS-based transport network
tunnels also.
As per [RFC6923], the CC and the ICC form the ICC_Operator_ID Since the MPLS tunnel's Ingress/Egress LSR identifiers'
as CC::ICC and ICC compatible mapping is represented size (Unsigned32) value is not compatible for
as ICC_Operator_ID::Node_ID. MPLS-TP Tunnel, i.e., Global_ID::Node_ID of size 8 bytes and
ICC_Operator_ID::Node_ID of size 12 bytes, there exists a
need to map the Global_ID::Node_ID or ICC_Operator_ID::Node_ID
with the local identifier of size 4 bytes (Unsigned32) value
in order to index (Ingress/Egress LSR identifier)
the existing mplsTunnelTable."
Note: Each entry in this table should have a unique ::= { mplsTeExtObjects 2 }
[Global_ID and Node_ID] or [CC::ICC and Node_ID] combination."
INDEX { mplsTunnelExtNodeConfigLocalId }
::= { mplsTunnelExtNodeConfigTable 1 }
MplsTunnelExtNodeConfigEntry ::= SEQUENCE { mplsTunnelExtNodeConfigEntry OBJECT-TYPE
mplsTunnelExtNodeConfigLocalId MplsExtendedTunnelId, SYNTAX MplsTunnelExtNodeConfigEntry
mplsTunnelExtNodeConfigGlobalId MplsGlobalId, MAX-ACCESS not-accessible
mplsTunnelExtNodeConfigCcId MplsCcId, STATUS current
mplsTunnelExtNodeConfigIccId MplsIccId, DESCRIPTION
mplsTunnelExtNodeConfigNodeId MplsNodeId, "An entry in this table represents a mapping
mplsTunnelExtNodeConfigIccValid TruthValue, identification for the operator or service provider
mplsTunnelExtNodeConfigStorageType StorageType, to a node or an LSR.
mplsTunnelExtNodeConfigRowStatus RowStatus
} As per RFC 6370, IP-compatible mapping is represented
as Global_ID::Node_ID.
mplsTunnelExtNodeConfigLocalId OBJECT-TYPE As per RFC 6923, the CC and the ICC form the ICC_Operator_ID
SYNTAX MplsExtendedTunnelId as CC::ICC, and ICC-compatible mapping is represented
MAX-ACCESS not-accessible as ICC_Operator_ID::Node_ID.
STATUS current
DESCRIPTION
"This object is used in accommodating the bigger
size Global_ID::Node_ID and/or the ICC_Operator_ID::Node_ID
with lower size LSR identifier in order to index
the mplsTunnelTable.
The Local Identifier is configured between 0 and 16777215, Note: Each entry in this table should have a unique
as valid IP address range starts from 16777216(01.00.00.00). [Global_ID and Node_ID] or [CC::ICC and Node_ID] combination."
This range is chosen to determine whether the INDEX { mplsTunnelExtNodeConfigLocalId }
mplsTunnelTable's Ingress/Egress LSR-id is an IP address or ::= { mplsTunnelExtNodeConfigTable 1 }
Local identifier. If the configured range is not an
IP address, the operator is expected to retrieve the
complete information (Global_ID::Node_ID or
ICC_Operator_ID::Node_ID) from
mplsTunnelExtNodeConfigTable.
This way, existing mplsTunnelTable is reused for
bidirectional tunnel extensions for MPLS based transport
networks.
The Local Identifier allows the operator to assign MplsTunnelExtNodeConfigEntry ::= SEQUENCE {
a unique identifier to map Global_ID::Node_ID and/or mplsTunnelExtNodeConfigLocalId MplsExtendedTunnelId,
ICC_Operator_ID::Node_ID. As this Local Identifier is unique mplsTunnelExtNodeConfigGlobalId MplsGlobalId,
within the node and the same syntax of this object can be mplsTunnelExtNodeConfigCcId MplsCcId,
used for MPLS-TE tunnel also, it is up to the operator/local mplsTunnelExtNodeConfigIccId MplsIccId,
management entity to choose non-conflicting value for mplsTunnelExtNodeConfigNodeId MplsNodeId,
indexing the MPLS and MPLS-TP tunnel entries." mplsTunnelExtNodeConfigIccValid TruthValue,
::= { mplsTunnelExtNodeConfigEntry 1 } mplsTunnelExtNodeConfigStorageType StorageType,
mplsTunnelExtNodeConfigRowStatus RowStatus
mplsTunnelExtNodeConfigGlobalId OBJECT-TYPE }
SYNTAX MplsGlobalId
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object indicates the Global Operator Identifier.
This object has no meaning when
mplsTunnelExtNodeConfigIccValid is set true."
REFERENCE
"MPLS Transport Profile (MPLS-TP) Identifiers [RFC6370]
Section 3."
::= { mplsTunnelExtNodeConfigEntry 2 }
mplsTunnelExtNodeConfigCcId OBJECT-TYPE mplsTunnelExtNodeConfigLocalId OBJECT-TYPE
SYNTAX MplsCcId SYNTAX MplsExtendedTunnelId
MAX-ACCESS read-create MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object allows the operator or service provider to "This object is used in accommodating the bigger-
configure a unique MPLS-TP ITU-T Country Code (CC) size Global_ID::Node_ID and/or the ICC_Operator_ID::Node_ID
either for Ingress ID or Egress ID. with the smaller-size LSR identifier in order to index
the mplsTunnelTable.
This object has no meaning when The local identifier is configured between 0 and 16777215,
mplsTunnelExtNodeConfigIccValid is set false." as the valid IP address range starts from
REFERENCE 16777216(01.00.00.00).
"MPLS-TP Identifiers Following ITU-T Conventions, This range is chosen to determine whether the
[RFC6923] Section 3" mplsTunnelTable's Ingress/Egress LSR ID is an IP address or
::= { mplsTunnelExtNodeConfigEntry 3 } local identifier. If the configured range is not an
IP address, the operator is expected to retrieve the
complete information (Global_ID::Node_ID or
ICC_Operator_ID::Node_ID) from mplsTunnelExtNodeConfigTable.
This way, the existing mplsTunnelTable is reused for
bidirectional tunnel extensions for MPLS-based transport
networks.
mplsTunnelExtNodeConfigIccId OBJECT-TYPE The local identifier allows the operator to assign
SYNTAX MplsIccId a unique identifier to map Global_ID::Node_ID and/or
MAX-ACCESS read-create ICC_Operator_ID::Node_ID. As this local identifier is unique
STATUS current within the node and the same syntax of this object can be
DESCRIPTION used for MPLS-TE tunnel also, it is up to the operator/local
"This object allows the operator or service provider to management entity to choose a non-conflicting value for
configure a unique MPLS-TP ITU-T Carrier Code (ICC) indexing the MPLS and MPLS-TP tunnel entries."
either for Ingress ID or Egress ID. ::= { mplsTunnelExtNodeConfigEntry 1 }
This object has no meaning when mplsTunnelExtNodeConfigGlobalId OBJECT-TYPE
mplsTunnelExtNodeConfigIccValid is set false." SYNTAX MplsGlobalId
REFERENCE MAX-ACCESS read-create
"MPLS-TP Identifiers Following ITU-T Conventions, STATUS current
DESCRIPTION
"This object indicates the Global Operator Identifier.
This object has no meaning when
mplsTunnelExtNodeConfigIccValid is set true."
REFERENCE
"MPLS Transport Profile (MPLS-TP) Identifiers, RFC 6370,
Section 3."
::= { mplsTunnelExtNodeConfigEntry 2 }
[RFC6923] Section 3" mplsTunnelExtNodeConfigCcId OBJECT-TYPE
::= { mplsTunnelExtNodeConfigEntry 4 } SYNTAX MplsCcId
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object allows the operator or service provider to
configure a unique MPLS-TP ITU-T Country Code (CC)
either for Ingress ID or Egress ID.
mplsTunnelExtNodeConfigNodeId OBJECT-TYPE This object has no meaning when
SYNTAX MplsNodeId mplsTunnelExtNodeConfigIccValid is set to false."
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 REFERENCE
"MPLS Transport Profile (MPLS-TP) Identifiers [RFC6370] "MPLS-TP Identifiers Following ITU-T Conventions,
Section 4." RFC 6923, Section 3"
::= { mplsTunnelExtNodeConfigEntry 5 } ::= { mplsTunnelExtNodeConfigEntry 3 }
mplsTunnelExtNodeConfigIccValid OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Denotes whether or not this entry uses
mplsTunnelExtNodeConfigCcId,
mplsTunnelExtNodeConfigIccId and
mplsTunnelExtNodeConfigNodeId for mapping
the ICC based identifiers with the local identifier.
Note that if this variable is set to false then the
mplsTunnelExtNodeConfigGlobalId and
mplsTunnelExtNodeConfigNodeId objects should have
the valid information."
DEFVAL { false }
::= { mplsTunnelExtNodeConfigEntry 6 }
mplsTunnelExtNodeConfigStorageType OBJECT-TYPE mplsTunnelExtNodeConfigIccId OBJECT-TYPE
SYNTAX StorageType SYNTAX MplsIccId
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable indicates the storage type for this "This object allows the operator or service provider to
object. configure a unique MPLS-TP ITU-T Carrier Code (ICC)
Conceptual rows having the value 'permanent' either for Ingress ID or Egress ID.
need not allow write-access to any columnar
objects in the row."
DEFVAL { volatile }
::= { mplsTunnelExtNodeConfigEntry 7 }
mplsTunnelExtNodeConfigRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object allows the operator to create, modify,
and/or delete a row in this table."
::= { mplsTunnelExtNodeConfigEntry 8 }
-- End of MPLS Transport Profile Node configuration table
-- Start of MPLS Transport Profile Node IP compatible
-- mapping table
mplsTunnelExtNodeIpMapTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsTunnelExtNodeIpMapEntry
MAX-ACCESS not-accessible This object has no meaning when
STATUS current mplsTunnelExtNodeConfigIccValid is set to false."
DESCRIPTION REFERENCE
"This read-only table allows the operator to retrieve "MPLS-TP Identifiers Following ITU-T Conventions,
the local identifier for a given Global_ID::Node_ID in an IP RFC 6923, Section 3"
compatible operator environment. ::= { mplsTunnelExtNodeConfigEntry 4 }
This table MAY be used in on-demand and/or proactive 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, RFC 6370,
Section 4."
::= { mplsTunnelExtNodeConfigEntry 5 }
OAM operations to get the Ingress/Egress LSR identifier mplsTunnelExtNodeConfigIccValid OBJECT-TYPE
(Local Identifier) from Src-Global_Node_ID SYNTAX TruthValue
or Dst-Global_Node_ID. The Ingress and Egress LSR MAX-ACCESS read-create
identifiers are used to retrieve the tunnel entry. STATUS current
DESCRIPTION
"Denotes whether or not this entry uses
mplsTunnelExtNodeConfigCcId,
mplsTunnelExtNodeConfigIccId, and
mplsTunnelExtNodeConfigNodeId for mapping
the ICC-based identifiers with the local identifier.
Note that if this variable is set to false, then the
mplsTunnelExtNodeConfigGlobalId and
mplsTunnelExtNodeConfigNodeId objects should have
the valid information."
DEFVAL { false }
::= { mplsTunnelExtNodeConfigEntry 6 }
This table returns nothing when the associated entry mplsTunnelExtNodeConfigStorageType OBJECT-TYPE
is not defined in mplsTunnelExtNodeConfigTable." SYNTAX StorageType
::= { mplsTeExtObjects 3 } 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 }
mplsTunnelExtNodeIpMapEntry OBJECT-TYPE mplsTunnelExtNodeConfigRowStatus OBJECT-TYPE
SYNTAX MplsTunnelExtNodeIpMapEntry SYNTAX RowStatus
MAX-ACCESS not-accessible MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table represents a mapping of "This object allows the operator to create, modify,
Global_ID::Node_ID with the local identifier. and/or delete a row in this table."
::= { mplsTunnelExtNodeConfigEntry 8 }
An entry in this table is created automatically when -- End of MPLS Transport Profile Node configuration table
the Local identifier is associated with Global_ID and
Node_Id in the mplsTunnelExtNodeConfigTable.
Note: Each entry in this table should have a unique -- Start of MPLS Transport Profile Node IP-compatible
Global_ID and Node_ID combination." -- mapping table
INDEX { mplsTunnelExtNodeIpMapGlobalId,
mplsTunnelExtNodeIpMapNodeId
}
::= { mplsTunnelExtNodeIpMapTable 1 }
MplsTunnelExtNodeIpMapEntry ::= SEQUENCE { mplsTunnelExtNodeIpMapTable OBJECT-TYPE
mplsTunnelExtNodeIpMapGlobalId MplsGlobalId, SYNTAX SEQUENCE OF MplsTunnelExtNodeIpMapEntry
mplsTunnelExtNodeIpMapNodeId MplsNodeId,
mplsTunnelExtNodeIpMapLocalId MplsExtendedTunnelId
}
mplsTunnelExtNodeIpMapGlobalId OBJECT-TYPE MAX-ACCESS not-accessible
SYNTAX MplsGlobalId STATUS current
MAX-ACCESS not-accessible DESCRIPTION
STATUS current "This read-only table allows the operator to retrieve
DESCRIPTION the local identifier for a given Global_ID::Node_ID in an
"This object indicates the Global_ID." IP-compatible operator environment.
::= { mplsTunnelExtNodeIpMapEntry 1 } This table MAY be used in on-demand and/or proactive
OAM operations to get the Ingress/Egress LSR identifier
(local identifier) from Src-Global_Node_ID
or Dst-Global_Node_ID. The Ingress and Egress LSR
identifiers are used to retrieve the tunnel entry.
mplsTunnelExtNodeIpMapNodeId OBJECT-TYPE This table returns nothing when the associated entry
SYNTAX MplsNodeId is not defined in mplsTunnelExtNodeConfigTable."
MAX-ACCESS not-accessible ::= { mplsTeExtObjects 3 }
STATUS current
DESCRIPTION
"This object indicates the Node_ID within the
operator." mplsTunnelExtNodeIpMapEntry OBJECT-TYPE
::= { mplsTunnelExtNodeIpMapEntry 2 } SYNTAX MplsTunnelExtNodeIpMapEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in this table represents a mapping of
Global_ID::Node_ID with the local identifier.
mplsTunnelExtNodeIpMapLocalId OBJECT-TYPE An entry in this table is created automatically when
SYNTAX MplsExtendedTunnelId the local identifier is associated with Global_ID and
MAX-ACCESS read-only Node_Id in the mplsTunnelExtNodeConfigTable.
STATUS current
DESCRIPTION
"This object contains an IP compatible local identifier
which is defined in mplsTunnelExtNodeConfigTable."
::= { mplsTunnelExtNodeIpMapEntry 3 }
-- End MPLS Transport Profile Node IP compatible table Note: Each entry in this table should have a unique
Global_ID and Node_ID combination."
INDEX { mplsTunnelExtNodeIpMapGlobalId,
mplsTunnelExtNodeIpMapNodeId
}
::= { mplsTunnelExtNodeIpMapTable 1 }
-- Start of MPLS Transport Profile Node ICC based table MplsTunnelExtNodeIpMapEntry ::= SEQUENCE {
mplsTunnelExtNodeIpMapGlobalId MplsGlobalId,
mplsTunnelExtNodeIpMapNodeId MplsNodeId,
mplsTunnelExtNodeIpMapLocalId MplsExtendedTunnelId
}
mplsTunnelExtNodeIccMapTable OBJECT-TYPE mplsTunnelExtNodeIpMapGlobalId OBJECT-TYPE
SYNTAX SEQUENCE OF MplsTunnelExtNodeIccMapEntry SYNTAX MplsGlobalId
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This read-only table allows the operator to retrieve "This object indicates the Global_ID."
the local identifier for a given ICC_Operator_ID::Node_ID ::= { mplsTunnelExtNodeIpMapEntry 1 }
in an ICC operator environment.
This table MAY be used in on-demand and/or proactive
OAM operations to get the Ingress/Egress LSR
identifier (Local Identifier) from Src-ICC
or Dst-ICC. The Ingress and Egress LSR
identifiers are used to retrieve the tunnel entry.
This table returns nothing when the associated entry
is not defined in mplsTunnelExtNodeConfigTable."
::= { mplsTeExtObjects 4 }
mplsTunnelExtNodeIccMapEntry OBJECT-TYPE mplsTunnelExtNodeIpMapNodeId OBJECT-TYPE
SYNTAX MplsTunnelExtNodeIccMapEntry SYNTAX MplsNodeId
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table represents a mapping of "This object indicates the Node_ID within the
ICC_Operator_ID::Node_ID with the local identifier. operator."
::= { mplsTunnelExtNodeIpMapEntry 2 }
An entry in this table is created automatically when mplsTunnelExtNodeIpMapLocalId OBJECT-TYPE
the Local identifier is associated with SYNTAX MplsExtendedTunnelId
ICC_Operator_ID::Node_ID in MAX-ACCESS read-only
the mplsTunnelExtNodeConfigTable." STATUS current
INDEX { mplsTunnelExtNodeIccMapCcId, DESCRIPTION
mplsTunnelExtNodeIccMapIccId, "This object contains an IP-compatible local identifier
mplsTunnelExtNodeIccMapNodeId } that is defined in mplsTunnelExtNodeConfigTable."
::= { mplsTunnelExtNodeIccMapTable 1 } ::= { mplsTunnelExtNodeIpMapEntry 3 }
MplsTunnelExtNodeIccMapEntry ::= SEQUENCE { -- End MPLS Transport Profile Node IP compatible table
mplsTunnelExtNodeIccMapCcId MplsCcId,
mplsTunnelExtNodeIccMapIccId MplsIccId,
mplsTunnelExtNodeIccMapNodeId MplsNodeId,
mplsTunnelExtNodeIccMapLocalId MplsExtendedTunnelId
}
mplsTunnelExtNodeIccMapCcId OBJECT-TYPE -- Start of MPLS Transport Profile Node ICC based table
SYNTAX MplsCcId
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This object allows the operator or service provider to
configure a unique MPLS-TP ITU-T Country Code (CC)
either for Ingress or Egress LSR ID.
The CC is a string of two alphabetic characters mplsTunnelExtNodeIccMapTable OBJECT-TYPE
represented with upper case letters (i.e., A-Z)." SYNTAX SEQUENCE OF MplsTunnelExtNodeIccMapEntry
::= { mplsTunnelExtNodeIccMapEntry 1 } MAX-ACCESS not-accessible
mplsTunnelExtNodeIccMapIccId OBJECT-TYPE STATUS current
SYNTAX MplsIccId DESCRIPTION
MAX-ACCESS not-accessible "This read-only table allows the operator to retrieve
STATUS current the local identifier for a given ICC_Operator_ID::Node_ID
DESCRIPTION in an ICC operator environment.
"This object allows the operator or service provider
to configure a unique MPLS-TP ITU-T Carrier
Code (ICC) either for Ingress or Egress LSR ID.
The ICC is a string of one to six characters, each This table MAY be used in on-demand and/or proactive
character being either alphabetic (i.e. A-Z) or OAM operations to get the Ingress/Egress LSR
numeric (i.e. 0-9) characters. Alphabetic characters identifier (local identifier) from Src-ICC
in the ICC should be represented with upper case or Dst-ICC. The Ingress and Egress LSR
letters." identifiers are used to retrieve the tunnel entry.
::= { mplsTunnelExtNodeIccMapEntry 2 } This table returns nothing when the associated entry
is not defined in mplsTunnelExtNodeConfigTable."
::= { mplsTeExtObjects 4 }
mplsTunnelExtNodeIccMapNodeId OBJECT-TYPE mplsTunnelExtNodeIccMapEntry OBJECT-TYPE
SYNTAX MplsNodeId SYNTAX MplsTunnelExtNodeIccMapEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the Node_ID within the "An entry in this table represents a mapping of
ICC based operator." ICC_Operator_ID::Node_ID with the local identifier.
::= { mplsTunnelExtNodeIccMapEntry 3}
mplsTunnelExtNodeIccMapLocalId OBJECT-TYPE An entry in this table is created automatically when
SYNTAX MplsExtendedTunnelId the local identifier is associated with
MAX-ACCESS read-only ICC_Operator_ID::Node_ID in
STATUS current the mplsTunnelExtNodeConfigTable."
INDEX { mplsTunnelExtNodeIccMapCcId,
mplsTunnelExtNodeIccMapIccId,
mplsTunnelExtNodeIccMapNodeId }
::= { mplsTunnelExtNodeIccMapTable 1 }
MplsTunnelExtNodeIccMapEntry ::= SEQUENCE {
mplsTunnelExtNodeIccMapCcId MplsCcId,
mplsTunnelExtNodeIccMapIccId MplsIccId,
mplsTunnelExtNodeIccMapNodeId MplsNodeId,
mplsTunnelExtNodeIccMapLocalId MplsExtendedTunnelId
}
mplsTunnelExtNodeIccMapCcId OBJECT-TYPE
SYNTAX MplsCcId
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION DESCRIPTION
"This object contains an ICC based local identifier "This object allows the operator or service provider to
which is defined in mplsTunnelExtNodeConfigTable." configure a unique MPLS-TP ITU-T Country Code (CC)
::= { mplsTunnelExtNodeIccMapEntry 4 } either for Ingress or Egress LSR ID.
-- End MPLS Transport Profile Node ICC based table The CC is a string of two alphabetic characters
represented with uppercase letters (i.e., A-Z)."
::= { mplsTunnelExtNodeIccMapEntry 1 }
-- Start of MPLS Tunnel table extension mplsTunnelExtNodeIccMapIccId OBJECT-TYPE
SYNTAX MplsIccId
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This object allows the operator or service provider
to configure a unique MPLS-TP ITU-T Carrier
Code (ICC) either for Ingress or Egress LSR ID.
mplsTunnelExtTable OBJECT-TYPE The ICC is a string of one to six characters, each
SYNTAX SEQUENCE OF MplsTunnelExtEntry character being either alphabetic (i.e., A-Z) or
MAX-ACCESS not-accessible numeric (i.e., 0-9) characters. Alphabetic characters
in the ICC should be represented with uppercase
letters."
::= { 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
SYNTAX MplsExtendedTunnelId
MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table represents extensions to mplsTunnelTable "This object contains an ICC-based local identifier
in order to support MPLS-TP tunnels. that is defined in mplsTunnelExtNodeConfigTable."
::= { mplsTunnelExtNodeIccMapEntry 4 }
As per MPLS-TP Identifiers [RFC6370], LSP_ID for IP based -- End MPLS Transport Profile Node ICC-based table
co-routed bidirectional tunnel,
A1-{Global_ID::Node_ID::Tunnel_Num}::Z9-{Global_ID::
Node_ID::Tunnel_Num}::LSP_Num
LSP_ID for IP based associated bidirectional tunnel, -- Start of MPLS Tunnel table extension
A1-{Global_ID::Node_ID::Tunnel_Num::LSP_Num}::
Z9-{Global_ID::Node_ID::Tunnel_Num::LSP_Num}
mplsTunnelTable is reused for forming the LSP_ID mplsTunnelExtTable OBJECT-TYPE
as follows, SYNTAX SEQUENCE OF MplsTunnelExtEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table represents extensions to mplsTunnelTable
in order to support MPLS-TP Tunnels.
Source Tunnel_Num is mapped with mplsTunnelIndex, As per MPLS-TP Identifiers (RFC 6370), LSP_ID for IP-based
Source Node_ID is mapped with co-routed bidirectional tunnel:
mplsTunnelIngressLSRId, Destination Node_ID is
mapped with mplsTunnelEgressLSRId LSP_Num is mapped with
mplsTunnelInstance.
Source Global_ID::Node_ID and/or ICC_Operator_ID::Node_ID and A1-{Global_ID::Node_ID::Tunnel_Num}::Z9-{Global_ID::
Destination Global_ID::Node_ID and/or ICC_Operator_ID::Node-ID Node_ID::Tunnel_Num}::LSP_Num
are maintained in the mplsTunnelExtNodeConfigTable and
mplsTunnelExtNodeConfigLocalId is used to create an entry
in mplsTunnelTable."
REFERENCE
"MPLS Transport Profile (MPLS-TP) Identifiers [RFC6370]."
::= { mplsTeExtObjects 5 }
mplsTunnelExtEntry OBJECT-TYPE LSP_ID for IP based associated bidirectional tunnel:
SYNTAX MplsTunnelExtEntry A1-{Global_ID::Node_ID::Tunnel_Num::LSP_Num}::
MAX-ACCESS not-accessible Z9-{Global_ID::Node_ID::Tunnel_Num::LSP_Num}
STATUS current
DESCRIPTION
"An entry in this table represents MPLS-TP
specific additional tunnel configurations."
INDEX {
mplsTunnelIndex,
mplsTunnelInstance,
mplsTunnelIngressLSRId,
mplsTunnelEgressLSRId
}
::= { mplsTunnelExtTable 1 }
MplsTunnelExtEntry ::= SEQUENCE { mplsTunnelTable is reused for forming the LSP_ID
mplsTunnelExtOppositeDirPtr RowPointer, as follows:
mplsTunnelExtOppositeDirTnlValid TruthValue,
mplsTunnelExtDestTnlIndex MplsTunnelIndex,
mplsTunnelExtDestTnlLspIndex MplsTunnelInstanceIndex,
mplsTunnelExtDestTnlValid TruthValue,
mplsTunnelExtIngressLSRLocalIdValid TruthValue,
mplsTunnelExtEgressLSRLocalIdValid TruthValue
} Source Tunnel_Num is mapped with mplsTunnelIndex,
Source Node_ID is mapped with
mplsTunnelIngressLSRId, Destination Node_ID is
mapped with mplsTunnelEgressLSRId, and LSP_Num is mapped with
mplsTunnelInstance.
mplsTunnelExtOppositeDirPtr OBJECT-TYPE Source Global_ID::Node_ID and/or ICC_Operator_ID::Node_ID and
SYNTAX RowPointer Destination Global_ID::Node_ID and/or ICC_Operator_ID::Node-ID
MAX-ACCESS read-create are maintained in the mplsTunnelExtNodeConfigTable.
STATUS current mplsTunnelExtNodeConfigLocalId is used to create an entry
DESCRIPTION in mplsTunnelTable."
"This object points to the opposite direction tunnel entry."
::= { mplsTunnelExtEntry 1 }
mplsTunnelExtOppositeDirTnlValid OBJECT-TYPE REFERENCE
SYNTAX TruthValue "MPLS Transport Profile (MPLS-TP) Identifiers, RFC 6370."
MAX-ACCESS read-create ::= { mplsTeExtObjects 5 }
STATUS current
DESCRIPTION
"Denotes whether or not this tunnel uses
mplsTunnelExtOppositeDirPtr for identifying the opposite
direction tunnel information. Note that if this variable
is set to true then the mplsTunnelExtOppositeDirPtr should
point to the first accessible row of the valid opposite
direction tunnel."
DEFVAL { false }
::= { mplsTunnelExtEntry 2 }
mplsTunnelExtDestTnlIndex OBJECT-TYPE mplsTunnelExtEntry OBJECT-TYPE
SYNTAX MplsTunnelIndex SYNTAX MplsTunnelExtEntry
MAX-ACCESS read-create MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is applicable only for the bidirectional "An entry in this table represents additional MPLS-TP-
tunnel that has the forward and reverse LSPs in the specific tunnel configurations."
different tunnel entries. INDEX {
mplsTunnelIndex,
mplsTunnelInstance,
mplsTunnelIngressLSRId,
mplsTunnelEgressLSRId
}
::= { mplsTunnelExtTable 1 }
The values of this object and the MplsTunnelExtEntry ::= SEQUENCE {
mplsTunnelExtDestTnlLspIndex object together can be used mplsTunnelExtOppositeDirPtr RowPointer,
to identify an opposite direction LSP i.e. if the mplsTunnelExtOppositeDirTnlValid TruthValue,
mplsTunnelIndex and mplsTunnelInstance hold the value mplsTunnelExtDestTnlIndex MplsTunnelIndex,
for forward LSP, this object and mplsTunnelExtDestTnlLspIndex MplsTunnelInstanceIndex,
mplsTunnelExtDestTnlLspIndex can be used to retrieve mplsTunnelExtDestTnlValid TruthValue,
the reverse direction LSP and vice versa. mplsTunnelExtIngressLSRLocalIdValid TruthValue,
mplsTunnelExtEgressLSRLocalIdValid TruthValue
}
This object and mplsTunnelExtDestTnlLspIndex values mplsTunnelExtOppositeDirPtr OBJECT-TYPE
provide the first two indices of tunnel entry and SYNTAX RowPointer
the remaining indices can be derived as follows, MAX-ACCESS read-create
the Ingress and Egress Identifiers should be STATUS current
swapped in order to index the other direction tunnel." DESCRIPTION
::= { mplsTunnelExtEntry 3 } "This object points to the opposite-direction tunnel entry."
::= { mplsTunnelExtEntry 1 }
mplsTunnelExtDestTnlLspIndex OBJECT-TYPE mplsTunnelExtOppositeDirTnlValid OBJECT-TYPE
SYNTAX MplsTunnelInstanceIndex SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is applicable only for the bidirectional "Denotes whether or not this tunnel uses
tunnel that has the forward and reverse LSPs in the mplsTunnelExtOppositeDirPtr for identifying the opposite-
different tunnel entries. This object holds direction tunnel information. Note that if this variable
the instance index of the opposite direction tunnel." is set to true, then the mplsTunnelExtOppositeDirPtr should
::= { mplsTunnelExtEntry 4 } point to the first accessible row of the valid opposite-
direction tunnel."
mplsTunnelExtDestTnlValid OBJECT-TYPE DEFVAL { false }
SYNTAX TruthValue ::= { mplsTunnelExtEntry 2 }
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Denotes whether or not this tunnel uses
mplsTunnelExtDestTnlIndex and
mplsTunnelExtDestTnlLspIndex for identifying
the opposite direction tunnel information. Note that if
this variable is set to true then the
mplsTunnelExtDestTnlIndex and
mplsTunnelExtDestTnlLspIndex objects should have
the valid opposite direction tunnel indices."
DEFVAL { false }
::= { mplsTunnelExtEntry 5 }
mplsTunnelExtIngressLSRLocalIdValid OBJECT-TYPE mplsTunnelExtDestTnlIndex OBJECT-TYPE
SYNTAX TruthValue SYNTAX MplsTunnelIndex
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object denotes whether the mplsTunnelIngressLSRId "This object is applicable only for the bidirectional
contains the local value, which is used to reference tunnel that has the forward and reverse LSPs in the
the complete Ingress Global_ID::Node_ID or ICC_Operator_ID different tunnel entries.
from the mplsTunnelExtNodeConfigTable.
If this object is set to FALSE, mplsTunnelExtNodeConfigTable The values of this object and the
will not contain an entry to reference local identifier with mplsTunnelExtDestTnlLspIndex object together can be used
Global_ID::Node_ID or ICC_Operator_ID::Node_ID value. to identify an opposite-direction LSP, i.e., if the
mplsTunnelIndex and mplsTunnelInstance hold the value
for forward LSP, this object and
mplsTunnelExtDestTnlLspIndex can be used to retrieve
the reverse-direction LSP and vice versa.
This object is set to FALSE for legacy implementations like This object and mplsTunnelExtDestTnlLspIndex values
MPLS TE tunnels where mplsTunnelIngressId itself provides provide the first two indices of tunnel entry, and
complete Ingress LSRId." the remaining indices can be derived as follows:
REFERENCE the Ingress and Egress Identifiers should be
"MPLS-TE-STD-MIB [RFC3812], Section 11. swapped in order to index the other direction tunnel."
mplsTunnelIngressLSRId object in mplsTunnelTable." ::= { mplsTunnelExtEntry 3 }
DEFVAL { false }
::= { mplsTunnelExtEntry 6 }
mplsTunnelExtEgressLSRLocalIdValid OBJECT-TYPE mplsTunnelExtDestTnlLspIndex OBJECT-TYPE
SYNTAX TruthValue SYNTAX MplsTunnelInstanceIndex
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object denotes whether the mplsTunnelEgressLSRId "This object is applicable only for the bidirectional
contains the local value, which is used to reference tunnel that has the forward and reverse LSPs in the
the complete Egress Global_ID::Node_ID or different tunnel entries. This object holds
ICC_Operator_ID::Node_ID from the instance index of the opposite-direction tunnel."
the mplsTunnelExtNodeConfigTable. ::= { mplsTunnelExtEntry 4 }
If this object is set to FALSE, mplsTunnelExtNodeConfigTable mplsTunnelExtDestTnlValid OBJECT-TYPE
will not contain an entry to reference local identifier with SYNTAX TruthValue
Global_ID::Node_ID or ICC_Operator_ID::Node_ID value. MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Denotes whether or not this tunnel uses
mplsTunnelExtDestTnlIndex and
mplsTunnelExtDestTnlLspIndex for identifying
the opposite-direction tunnel information. Note that if
this variable is set to true, then the
mplsTunnelExtDestTnlIndex and
mplsTunnelExtDestTnlLspIndex objects should have
the valid opposite-direction tunnel indices."
DEFVAL { false }
::= { mplsTunnelExtEntry 5 }
This object is set to FALSE for legacy implementations like mplsTunnelExtIngressLSRLocalIdValid OBJECT-TYPE
MPLS TE tunnels where mplsTunnelEgressId itself provides SYNTAX TruthValue
complete Egress LSRId." MAX-ACCESS read-create
REFERENCE STATUS current
"MPLS-TE-STD-MIB [RFC3812], Section 11. DESCRIPTION
mplsTunnelEgressLSRId object in mplsTunnelTable." "This object denotes whether the mplsTunnelIngressLSRId
DEFVAL { false } contains the local value that is used to reference
::= { mplsTunnelExtEntry 7 } the complete Ingress Global_ID::Node_ID or ICC_Operator_ID
from the mplsTunnelExtNodeConfigTable.
-- End of MPLS Tunnel table extension If this object is set to FALSE, mplsTunnelExtNodeConfigTable
will not contain an entry to reference the local identifier
with Global_ID::Node_ID or ICC_Operator_ID::Node_ID value.
-- Module compliance. This object is set to FALSE for legacy implementations like
MPLS TE tunnels where mplsTunnelIngressId itself provides
the complete Ingress LSR ID."
REFERENCE
"MPLS-TE-STD-MIB (RFC 3812), Section 11.
mplsTunnelIngressLSRId object in mplsTunnelTable."
DEFVAL { false }
::= { mplsTunnelExtEntry 6 }
mplsTeExtCompliances mplsTunnelExtEgressLSRLocalIdValid OBJECT-TYPE
OBJECT IDENTIFIER ::= { mplsTeExtConformance 1 } SYNTAX TruthValue
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object denotes whether the mplsTunnelEgressLSRId
contains the local value, which is used to reference
the complete Egress Global_ID::Node_ID or
ICC_Operator_ID::Node_ID from
the mplsTunnelExtNodeConfigTable.
mplsTeExtGroups If this object is set to FALSE, mplsTunnelExtNodeConfigTable
OBJECT IDENTIFIER ::= { mplsTeExtConformance 2 } will not contain an entry to reference the local identifier
with Global_ID::Node_ID or ICC_Operator_ID::Node_ID value.
-- Compliance requirement for fully compliant implementations. This object is set to FALSE for legacy implementations like
MPLS TE tunnels where mplsTunnelEgressId itself provides
the complete Egress LSR ID."
mplsTeExtModuleFullCompliance MODULE-COMPLIANCE REFERENCE
STATUS current "MPLS-TE-STD-MIB (RFC 3812), Section 11.
DESCRIPTION mplsTunnelEgressLSRId object in mplsTunnelTable."
"Compliance statement for agents that provide full DEFVAL { false }
support the MPLS-TE-EXT-STD-MIB module." ::= { mplsTunnelExtEntry 7 }
MODULE -- this module -- End of MPLS Tunnel table extension
-- The mandatory group has to be implemented by all -- Module compliance.
-- LSRs that originate/terminate MPLS-TP tunnels.
-- In addition, depending on the type of tunnels mplsTeExtCompliances
-- supported, other groups become mandatory as OBJECT IDENTIFIER ::= { mplsTeExtConformance 1 }
-- explained below. mplsTeExtGroups
OBJECT IDENTIFIER ::= { mplsTeExtConformance 2 }
MANDATORY-GROUPS { -- Compliance requirement for fully compliant implementations.
mplsTunnelExtGroup
}
GROUP mplsTunnelExtIpOperatorGroup mplsTeExtModuleFullCompliance MODULE-COMPLIANCE
DESCRIPTION STATUS current
"This group is mandatory for devices which support DESCRIPTION
configuration of IP based identifier tunnels." "Compliance statement for agents that provide full
support the MPLS-TE-EXT-STD-MIB module."
GROUP mplsTunnelExtIccOperatorGroup MODULE -- this module
DESCRIPTION
"This group is mandatory for devices which support
configuration of ICC based tunnels."
::= { mplsTeExtCompliances 1 } -- The mandatory group has to be implemented by all
-- LSRs that originate/terminate MPLS-TP Tunnels.
-- In addition, depending on the type of tunnels
-- supported, other groups become mandatory as
-- explained below.
-- Compliance requirement for read-only implementations. MANDATORY-GROUPS {
mplsTunnelExtGroup
}
mplsTeExtModuleReadOnlyCompliance MODULE-COMPLIANCE GROUP mplsTunnelExtIpOperatorGroup
STATUS current DESCRIPTION
DESCRIPTION "This group is mandatory for devices that support
"Compliance statement for agents that only provide configuration of IP-based identifier tunnels."
read-only support for MPLS-TE-EXT-STD-MIB module."
MODULE -- this module GROUP mplsTunnelExtIccOperatorGroup
DESCRIPTION
"This group is mandatory for devices that support
configuration of ICC based tunnels."
MANDATORY-GROUPS { ::= { mplsTeExtCompliances 1 }
mplsTunnelExtGroup
}
GROUP mplsTunnelExtIpOperatorGroup -- Compliance requirement for read-only implementations.
DESCRIPTION
"This group is mandatory for devices which support
configuration of IP based identifier tunnels."
GROUP mplsTunnelExtIccOperatorGroup mplsTeExtModuleReadOnlyCompliance MODULE-COMPLIANCE
DESCRIPTION STATUS current
"This group is mandatory for devices which support DESCRIPTION
configuration of ICC based tunnels." "Compliance statement for agents that only provide
read-only support for the MPLS-TE-EXT-STD-MIB module."
-- mplsTunnelExtTable MODULE -- this module
OBJECT mplsTunnelExtOppositeDirPtr MANDATORY-GROUPS {
MIN-ACCESS read-only mplsTunnelExtGroup
DESCRIPTION }
"Write access is not required."
OBJECT mplsTunnelExtOppositeDirTnlValid GROUP mplsTunnelExtIpOperatorGroup
MIN-ACCESS read-only DESCRIPTION
DESCRIPTION "This group is mandatory for devices that support
"Write access is not required." configuration of IP-based identifier tunnels."
OBJECT mplsTunnelExtDestTnlIndex GROUP mplsTunnelExtIccOperatorGroup
MIN-ACCESS read-only DESCRIPTION
DESCRIPTION "This group is mandatory for devices that support
"Write access is not required." configuration of ICC-based tunnels."
OBJECT mplsTunnelExtDestTnlLspIndex -- mplsTunnelExtTable
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT mplsTunnelExtDestTnlValid OBJECT mplsTunnelExtOppositeDirPtr
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsTunnelExtIngressLSRLocalIdValid OBJECT mplsTunnelExtOppositeDirTnlValid
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsTunnelExtEgressLSRLocalIdValid OBJECT mplsTunnelExtDestTnlIndex
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsTunnelExtNodeConfigGlobalId OBJECT mplsTunnelExtDestTnlLspIndex
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsTunnelExtNodeConfigNodeId OBJECT mplsTunnelExtDestTnlValid
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsTunnelExtNodeConfigStorageType OBJECT mplsTunnelExtIngressLSRLocalIdValid
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsTunnelExtNodeConfigRowStatus OBJECT mplsTunnelExtEgressLSRLocalIdValid
SYNTAX RowStatus { active(1) } MIN-ACCESS read-only
MIN-ACCESS read-only DESCRIPTION
DESCRIPTION "Write access is not required."
"Write access is not required."
OBJECT mplsTunnelExtNodeConfigCcId OBJECT mplsTunnelExtNodeConfigGlobalId
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsTunnelExtNodeConfigIccId OBJECT mplsTunnelExtNodeConfigNodeId
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsTunnelExtNodeConfigIccValid OBJECT mplsTunnelExtNodeConfigStorageType
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
::= { mplsTeExtCompliances 2 } OBJECT mplsTunnelExtNodeConfigRowStatus
SYNTAX RowStatus { active(1) }
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
-- Units of conformance. OBJECT mplsTunnelExtNodeConfigCcId
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
mplsTunnelExtGroup OBJECT-GROUP OBJECT mplsTunnelExtNodeConfigIccId
OBJECTS { MIN-ACCESS read-only
mplsTunnelExtOppositeDirPtr, DESCRIPTION
mplsTunnelExtOppositeDirTnlValid, "Write access is not required."
mplsTunnelExtDestTnlIndex,
mplsTunnelExtDestTnlLspIndex,
mplsTunnelExtDestTnlValid,
mplsTunnelExtIngressLSRLocalIdValid,
mplsTunnelExtEgressLSRLocalIdValid
}
STATUS current OBJECT mplsTunnelExtNodeConfigIccValid
DESCRIPTION MIN-ACCESS read-only
"Necessary, but not sufficient, set of objects to DESCRIPTION
implement tunnels. In addition, depending on the "Write access is not required."
operating environment, the following groups are
mandatory."
::= { mplsTeExtGroups 1 }
mplsTunnelExtIpOperatorGroup OBJECT-GROUP ::= { mplsTeExtCompliances 2 }
OBJECTS { mplsTunnelExtNodeConfigLocalIdNext,
mplsTunnelExtNodeConfigGlobalId,
mplsTunnelExtNodeConfigNodeId,
mplsTunnelExtNodeIpMapLocalId,
mplsTunnelExtNodeConfigStorageType,
mplsTunnelExtNodeConfigRowStatus
}
STATUS current
DESCRIPTION
"Object(s) needed to implement IP compatible tunnels."
::= { mplsTeExtGroups 2 }
mplsTunnelExtIccOperatorGroup OBJECT-GROUP -- Units of conformance.
OBJECTS { mplsTunnelExtNodeConfigLocalIdNext,
mplsTunnelExtNodeConfigCcId,
mplsTunnelExtNodeConfigIccId,
mplsTunnelExtNodeConfigNodeId,
mplsTunnelExtNodeConfigIccValid,
mplsTunnelExtNodeIccMapLocalId,
mplsTunnelExtNodeConfigStorageType,
mplsTunnelExtNodeConfigRowStatus
}
STATUS current
DESCRIPTION
"Object(s) needed to implement ICC based tunnels."
::= { mplsTeExtGroups 3 }
-- MPLS-TE-EXT-STD-MIB module ends mplsTunnelExtGroup OBJECT-GROUP
END OBJECTS {
mplsTunnelExtOppositeDirPtr,
mplsTunnelExtOppositeDirTnlValid,
mplsTunnelExtDestTnlIndex,
mplsTunnelExtDestTnlLspIndex,
mplsTunnelExtDestTnlValid,
mplsTunnelExtIngressLSRLocalIdValid,
mplsTunnelExtEgressLSRLocalIdValid
}
14. Security Consideration STATUS current
DESCRIPTION
"Necessary, but not sufficient, set of objects to
implement tunnels. In addition, depending on the
operating environment, the following groups are
mandatory."
::= { mplsTeExtGroups 1 }
This document follows the security consideration mentioned in the mplsTunnelExtIpOperatorGroup OBJECT-GROUP
section 12 of [RFC3812]. These security considerations are also OBJECTS { mplsTunnelExtNodeConfigLocalIdNext,
applicable to the MIB objects and tables defined in this draft, which mplsTunnelExtNodeConfigGlobalId,
are identified as below. mplsTunnelExtNodeConfigNodeId,
mplsTunnelExtNodeIpMapLocalId,
mplsTunnelExtNodeConfigStorageType,
mplsTunnelExtNodeConfigRowStatus
}
STATUS current
DESCRIPTION
"Object(s) needed to implement IP-compatible tunnels."
::= { mplsTeExtGroups 2 }
- The common objects mplsIdGlobalId, mplsIdNodeId, mplsIdCc, and mplsTunnelExtIccOperatorGroup OBJECT-GROUP
mplsIdIcc are used to define the identity of an MPLS-TP node for OBJECTS { mplsTunnelExtNodeConfigLocalIdNext,
OAM purposes. If write-access is allowed to these objects it mplsTunnelExtNodeConfigCcId,
offers the possibility for incorrect values to be entered that mplsTunnelExtNodeConfigIccId,
will confuse the information returned by OAM functions and mplsTunnelExtNodeConfigNodeId,
possibly prevent OAM from operating correctly. Furthermore, mplsTunnelExtNodeConfigIccValid,
there is the possibility of inducing one node to impersonate mplsTunnelExtNodeIccMapLocalId,
another with confusing results. mplsTunnelExtNodeConfigStorageType,
mplsTunnelExtNodeConfigRowStatus
}
STATUS current
DESCRIPTION
"Object(s) needed to implement ICC-based tunnels."
::= { mplsTeExtGroups 3 }
- mplsTunnelExtNodeConfigTable, mplsTunnelExtTable and -- MPLS-TE-EXT-STD-MIB module ends
mplsXCExtTable collectively contain objects to provision MPLS-TP END
tunnels, tunnel hops, and tunnel resources.
14. Security Considerations
This document follows the security considerations mentioned in
Section 12 of [RFC3812]. These security considerations are also
applicable to the MIB objects and tables defined in this document,
which are identified as below.
- The common objects mplsIdGlobalId, mplsIdNodeId, mplsIdCc, and
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
mplsXCExtTable collectively contain objects to provision MPLS-TP
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. It is thus important to vulnerable in some network environments. It is thus important to
control even GET and/or NOTIFY access to these objects and possibly control even GET and/or NOTIFY access to these objects and possibly
to even encrypt the values of these objects when sending them over to even encrypt the values of these objects when sending them over
the network via SNMP. These are the tables and objects and their the network via SNMP. These are the tables and objects and their
sensitivity/vulnerability: sensitivity/vulnerability:
- mplsTunnelExtNodeConfigTable, mplsTunnelExtTable, - mplsTunnelExtNodeConfigTable, mplsTunnelExtTable, and
and mplsXCExtTable collectively show the MPLS-TP tunnel network mplsXCExtTable collectively show the characteristics of the
topology characteristics. If an Administrator does not want to MPLS-TP tunnel network topology. If an Administrator does not
reveal this information, then these tables should be considered want to reveal this information, then these tables should be
sensitive/vulnerable. considered sensitive/vulnerable.
SNMP versions prior to SNMPv3 did not include adequate security. Even SNMP versions prior to SNMPv3 did not include adequate security.
if the network itself is secure (for example by using IPsec), there Even if the network itself is secure (for example by using IPsec),
is no control as to who on the secure network is allowed to access there is no control as to who on the secure network is allowed to
and GET/SET (read/change/create/delete) the objects in this MIB access and GET/SET (read/change/create/delete) the objects in this
module. MIB module.
Implementations SHOULD provide the security features described by the Implementations SHOULD provide the security features described by the
SNMPv3 framework (see [RFC3410]), and implementations claiming SNMPv3 framework (see [RFC3410]), and implementations claiming
compliance to the SNMPv3 standard MUST include full support for compliance to the SNMPv3 standard MUST include full support for
authentication and privacy via the User-based Security Model (USM) authentication and privacy via the User-based Security Model (USM)
[RFC3414] with the AES cipher algorithm [RFC3826]. Implementations [RFC3414] with the AES cipher algorithm [RFC3826]. Implementations
MAY also provide support for the Transport Security Model (TSM) MAY also provide support for the Transport Security Model (TSM)
[RFC5591] in combination with a secure transport such as SSH [RFC5591] in combination with a secure transport such as SSH
[RFC5592] or TLS/DTLS [RFC6353]. [RFC5592] or TLS/DTLS [RFC6353].
Further, deployment of SNMP versions prior to SNMPv3 is NOT Further, deployment of SNMP versions prior to SNMPv3 is NOT
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 access to instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them. 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] and [RFC6639], and as requested in the
STD-MIB [RFC3811], MPLS related standards track MIB modules should be MPLS-TC-STD-MIB [RFC3811], MPLS-related Standards Track MIB modules
rooted under the mplsStdMIB subtree. There are 4 MPLS MIB Modules should be rooted under the mplsStdMIB subtree. There are four MPLS
contained in this document, each of the following "IANA MIB modules contained in this document; each of the following
Considerations" subsections requests IANA for a new assignment under subsections lists a new assignment made by IANA under the mplsStdMIB
the mplsStdMIB subtree. New assignments can only be made via a subtree. New assignments can only be made via a Standards Action as
Standards Action as specified in [RFC5226]. 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 has assigned the OID { mplsStdMIB 17 } to the
EXT-STD-MIB module specified in this document. MPLS-TC-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 OID } to the MPLS-ID-
STD-MIB module specified in this document.
15.3. IANA Considerations for MPLS-LSR-EXT-STD-MIB IANA has assigned the OID { mplsStdMIB 18 } to the MPLS-ID-STD-MIB
module specified in this document.
IANA is requested to assign an OID { mplsStdMIB OID } to the MPLS- 15.3. IANA Considerations for MPLS-LSR-EXT-STD-MIB
LSR-EXT-STD-MIB module specified in this document.
15.4. IANA Considerations for MPLS-TE-EXT-STD-MIB IANA has assigned the OID { mplsStdMIB 19 } to the
MPLS-LSR-EXT-STD-MIB module specified in this document.
IANA is requested to assign an OID { mplsStdMIB OID } to the MPLS-TE- 15.4. IANA Considerations for MPLS-TE-EXT-STD-MIB
EXT-STD-MIB module specified in this document.
16. References IANA has assigned the OID { mplsStdMIB 20 } to the
MPLS-TE-EXT-STD-MIB module specified in this document.
16.1. Normative References 16. References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 16.1. Normative References
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder, [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
"Structure of Management Information Version 2 (SMIv2)", Requirement Levels", BCP 14, RFC 2119, March 1997,
STD 58, RFC 2578, April 1999. <http://www.rfc-editor.org/info/rfc2119>.
[RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder, [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
"Textual Conventions for SMIv2", STD 58, RFC 2579, April Schoenwaelder, Ed., "Structure of Management Information
1999. Version 2 (SMIv2)", STD 58, RFC 2578, April 1999,
<http://www.rfc-editor.org/info/rfc2578>.
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.
"Conformance Statements for SMIv2", STD 58, RFC 2580, Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD
April 1999. 58, RFC 2579, April 1999,
<http://www.rfc-editor.org/info/rfc2579>.
[RFC3031] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol [RFC2580] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Label Switching Architecture", RFC 3031, January 2001. Schoenwaelder, Ed., "Conformance Statements for SMIv2",
STD 58, RFC 2580, April 1999,
<http://www.rfc-editor.org/info/rfc2580>.
[RFC3289] Baker, F., Chan, K., and A. Smith, "Management [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol
Information Base for the Differentiated Services Label Switching Architecture", RFC 3031, January 2001,
Architecture", RFC 3289, May 2002. <http://www.rfc-editor.org/info/rfc3031>.
[RFC3811] Nadeau, T., Ed., and J. Cucchiara, Ed., "Definitions of [RFC3289] Baker, F., Chan, K., and A. Smith, "Management Information
Base for the Differentiated Services Architecture", RFC
3289, May 2002, <http://www.rfc-editor.org/info/rfc3289>.
[RFC3811] Nadeau, T., Ed., and J. Cucchiara, Ed., "Definitions of
Textual Conventions (TCs) for Multiprotocol Label Textual Conventions (TCs) for Multiprotocol Label
Switching (MPLS) Management", RFC 3811, June 2004. Switching (MPLS) Management", RFC 3811, June 2004,
<http://www.rfc-editor.org/info/rfc3811>.
[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, <http://www.rfc-editor.org/info/rfc3812>.
[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, Router (LSR) Management Information Base (MIB)", RFC 3813,
June 2004. June 2004, <http://www.rfc-editor.org/info/rfc3813>.
[RFC4802] Nadeau, T., Ed., and A. Farrel, Ed., "Generalized [RFC4802] Nadeau, T., Ed., and A. Farrel, Ed., "Generalized
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,
<http://www.rfc-editor.org/info/rfc4802>.
[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,
<http://www.rfc-editor.org/info/rfc6370>.
[RFC6923] Winter, R., Gray, E., Helvoort, H., and M. Betts, "MPLS-TP [RFC6923] Winter, R., Gray, E., van Helvoort, H., and M. Betts,
Identifiers Following ITU-T Conventions", RFC 6923, May "MPLS Transport Profile (MPLS-TP) Identifiers Following
2013 ITU-T Conventions", RFC 6923, May 2013,
<http://www.rfc-editor.org/info/rfc6923>.
[T.50] "International Reference Alphabet (IRA) (Formerly [T.50] ITU-T, "International Reference Alphabet (IRA) (Formerly
International Alphabet No. 5 or IA5) - Information International Alphabet No. 5 or IA5) - Information
technology - 7-bit coded character set for information technology - 7-bit coded character set for information
exchange", ITU-T Recommendation T.50, September 1992. 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] Case, J., Mundy, R., Partain, D., and B. Stewart,
and Applicability Statement for Internet Standard "Introduction and Applicability Statements for Internet-
Management Framework", RFC 3410, December 2002. Standard Management Framework", RFC 3410, December 2002,
<http://www.rfc-editor.org/info/rfc3410>.
[RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model [RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model
(USM) for version 3 of the Simple Network Management (USM) for version 3 of the Simple Network Management
Protocol (SNMPv3)", STD 62, RFC 3414, December 2002. Protocol (SNMPv3)", STD 62, RFC 3414, December 2002,
<http://www.rfc-editor.org/info/rfc3414>.
[RFC3826] Blumenthal, U., F. Maino and K. McCloghrie, "The Advanced [RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, "The
Encryption Standard (AES) Cipher Algorithm in the SNMP Advanced Encryption Standard (AES) Cipher Algorithm in the
User-based Security Model", RFC 3826, June 2004. SNMP User-based Security Model", RFC 3826, June 2004,
<http://www.rfc-editor.org/info/rfc3826>.
[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, <http://www.rfc-editor.org/info/rfc4221>.
[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, <http://www.rfc-editor.org/info/rfc5226>.
[RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model [RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model
for the Simple Network Management Protocol (SNMP)", for the Simple Network Management Protocol (SNMP)", STD
RFC 5591, June 2009. 78, RFC 5591, June 2009,
<http://www.rfc-editor.org/info/rfc5591>.
[RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure [RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure
Shell Transport Model for the Simple Network Management Shell Transport Model for the Simple Network Management
Protocol (SNMP)", RFC 5592, June 2009. Protocol (SNMP)", RFC 5592, June 2009,
<http://www.rfc-editor.org/info/rfc5592>.
[RFC5654] Niven-Jenkins, B., Ed., Brungard, D., Ed., Betts, M., [RFC5654] Niven-Jenkins, B., Ed., Brungard, D., Ed., Betts, M., Ed.,
Ed.,Sprecher, N., and S. Ueno, "Requirements of an MPLS Sprecher, N., and S. Ueno, "Requirements of an MPLS
Transport Profile", RFC 5654, September 2009. Transport Profile", RFC 5654, September 2009,
<http://www.rfc-editor.org/info/rfc5654>.
[RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport [RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport
Model for the Simple Network Management Protocol (SNMP)", Model for the Simple Network Management Protocol (SNMP)",
STD 78, RFC 6353, July 2011. STD 78, RFC 6353, July 2011,
<http://www.rfc-editor.org/info/rfc6353>.
[RFC6639] Venkatesan, M., King, D., "Multiprotocol Label Switching [RFC6639] King, D., Ed., and M. Venkatesan, Ed., "Multiprotocol
Transport Profile (MPLS-TP) MIB-Based Management Label Switching Transport Profile (MPLS-TP) MIB-Based
Overview", RFC 6639, June 2012 Management Overview", RFC 6639, June 2012,
<http://www.rfc-editor.org/info/rfc6639>.
17. Acknowledgments 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, Elwyn Agrahara Kiran Koushik, Metrri Jain, Muly Ilan, Randy Presuhn, Elwyn
Davies, Tom Taylor and Pete Resnick for their valuable review and Davies, Tom Taylor, and Pete Resnick for their valuable reviews and
comments. A special thanks to Joan Cucchiara and Adrian Farrel for comments. A special thanks to Joan Cucchiara and Adrian Farrel for
really getting the MIB modules into shape. really getting the MIB modules into shape.
18. Authors' Addresses 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
Email: venkat.mahalingams@gmail.com United States
EMail: venkat.mahalingams@gmail.com
Sam Aldrin Sam Aldrin
Huawei Technologies Huawei Technologies
2330 Central Express Way, 2330 Central Express Way,
Santa Clara, CA 95051, USA Santa Clara, CA 95051
Email: aldrin.ietf@gmail.com United States
EMail: aldrin.ietf@gmail.com
Thomas D. Nadeau Thomas D. Nadeau
Brocade Brocade
Email: tnadeau@lucidvision.com EMail: tnadeau@lucidvision.com
Kannan KV Sampath Kannan KV Sampath
Redeem Redeem
India India
Email: kannankvs@gmail.com EMail: kannankvs@gmail.com
 End of changes. 477 change blocks. 
1561 lines changed or deleted 1596 lines changed or added

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