draft-ietf-mpls-tp-mib-management-overview-08.txt   rfc6639.txt 
Network Working Group D. King (Editor)
Internet-Draft Old Dog Consulting
Intended status: Informational M. Venkatesan (Editor)
Expires: Secptember 13, 2012 Aricent
April 13, 2012
Multiprotocol Label Switching Transport Profile (MPLS-TP) Internet Engineering Task Force (IETF) D. King, Ed.
MIB-based Management Overview Request for Comments: 6639 Old Dog Consulting
draft-ietf-mpls-tp-mib-management-overview-08.txt Category: Informational M. Venkatesan, Ed.
ISSN: 2070-1721 Aricent
June 2012
Multiprotocol Label Switching Transport Profile (MPLS-TP)
MIB-Based Management Overview
Abstract Abstract
A range of Management Information Base (MIB) modules has been A range of Management Information Base (MIB) modules has been
developed to help model and manage the various aspects of developed to help model and manage the various aspects of
Multiprotocol Label Switching (MPLS) networks. These MIB modules are Multiprotocol Label Switching (MPLS) networks. These MIB modules are
defined in separate documents that focus on the specific areas of defined in separate documents that focus on the specific areas of
responsibility of the modules that they describe. responsibility of the modules that they describe.
The MPLS Transport Profile (MPLS-TP) is a profile of MPLS The MPLS Transport Profile (MPLS-TP) is a profile of MPLS
functionality specific to the construction of packet-switched functionality specific to the construction of packet-switched
transport networks. transport networks.
This document describes the MIB-based architecture for MPLS-TP, This document describes the MIB-based architecture for MPLS-TP,
and indicates the interrelationships between different existing MIB indicates the interrelationships between different existing MIB
modules that can be leveraged for MPLS-TP network management and modules that can be leveraged for MPLS-TP network management, and
identifies areas where additional MIB modules are required. identifies areas where additional MIB modules are required.
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 document is not an Internet Standards Track specification; it is
http://www.ietf.org/ietf/1id-abstracts.txt. published for informational purposes.
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). Not all documents
approved by the IESG are a candidate for any level of Internet
Standard; see Section 2 of RFC 5741.
This Internet-Draft will expire on September 13, 2012. 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/rfc6639.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 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.................................................3 1. Introduction ....................................................4
1.1 MPLS-TP Management Function.................................4 1.1. MPLS-TP Management Function ................................5
2. Terminology..................................................4 2. Terminology .....................................................5
3. The SNMP Management Framework................................4 3. The SNMP Management Framework ...................................5
4. Overview of Existing Work....................................5 4. Overview of Existing Work .......................................6
4.1. MPLS Management Overview and Requirements...............5 4.1. MPLS Management Overview and Requirements ..................6
4.2. An Introduction to the MPLS and Pseudowire MIB Modules..5 4.2. An Introduction to the MPLS and Pseudowire MIB Modules .....6
4.2.1. Structure of the MPLS MIB OID Tree...............5 4.2.1. Structure of the MPLS MIB OID Tree ..................6
4.2.2. Textual Convention Modules.......................7 4.2.2. Textual Convention Modules ..........................8
4.2.3. Label Switched Path (LSP) Modules................7 4.2.3. Label Switched Path (LSP) Modules ...................8
4.2.4. Label Edge Router (LER) Modules..................7 4.2.4. Label Edge Router (LER) Modules .....................8
4.2.5. Label Switching Router (LSR) Modules.............7 4.2.5. Label Switching Router (LSR) Modules ................9
4.2.6. Pseudowire Modules...............................8 4.2.6. Pseudowire Modules ..................................9
4.2.7. Routing and Traffic Engineering..................9 4.2.7. Routing and Traffic Engineering ....................10
4.2.8. Resiliency.......................................9 4.2.8. Resiliency .........................................11
4.2.9. Fault Management and Performance Management......10 4.2.9. Fault Management and Performance Management ........11
4.2.10. MIB Module Interdependencies....................11 4.2.10. MIB Module Interdependencies ......................13
4.2.11. Dependencies on External MIB Modules............13 4.2.11. Dependencies on External MIB Modules ..............15
5. Applicability of MPLS MIB modules to MPLS-TP.................14 5. Applicability of MPLS MIB Modules to MPLS-TP ...................16
5.1 MPLS-TP Tunnel...........................................14 5.1. MPLS-TP Tunnel ............................................17
5.1.1 Gap Analysis.......................................14 5.1.1. Gap Analysis .......................................17
5.1.2 Recommendations....................................15 5.1.2. Recommendations ....................................17
5.2 MPLS-TP Pseudowire.......................................15 5.2. MPLS-TP Pseudowire ........................................17
5.2.1 Gap Analysis.......................................15 5.2.1. Gap Analysis .......................................17
5.2.2 Recommendations....................................15 5.2.2. Recommendations ....................................18
5.3 MPLS-TP Sections.........................................15 5.3. MPLS-TP Sections ..........................................18
5.3.1 Gap Analysis.......................................15 5.3.1. Gap Analysis .......................................18
5.3.2 Recommendations....................................15 5.3.2. Recommendations ....................................18
5.4 MPLS-TP OAM..............................................16 5.4. MPLS-TP OAM ...............................................18
5.4.1 Gap Analysis.......................................16 5.4.1. Gap Analysis .......................................18
5.4.2 Recommendations....................................16 5.4.2. Recommendations ....................................19
5.5 MPLS-TP Protection Switching and Recovery................16 5.5. MPLS-TP Protection Switching and Recovery .................19
5.5.1 Gap Analysis.......................................16 5.5.1. Gap Analysis .......................................19
5.5.2 Recommendations....................................16 5.5.2. Recommendations ....................................19
5.6 MPLS-TP Interfaces.......................................16 5.6. MPLS-TP Interfaces ........................................19
5.6.1 Gap Analysis.......................................16 5.6.1. Gap Analysis .......................................19
5.6.2 Recommendations....................................17 5.6.2. Recommendations ....................................19
6. An Introduction to the MPLS-TP MIB Modules...................17
6.1 MPLS-TP MIB Modules......................................17
6.1.1 NEW MIB Modules for MPLS-TP.......................17
6.1.2 Textual Conventions for MPLS-TP...................18
6.1.3 Identifiers for MPLS-TP...........................18
6.1.4 LSR MIB Extensions for MPLS-TP....................18
6.1.5 Tunnel Extensions for MPLS-TP.....................18
6.2 PWE3 MIB Modules for MPLS-TP.............................18
6.2.1 New MIB Modules for MPLS-TP Pseudowires...........18
6.2.2 Pseudowire Textual Conventions for MPLS-TP........19
6.2.3 Pseudowire Extensions for MPLS-TP.................19
6.2.4 Pseudowire MPLS Extensions for MPLS-TP............19
6.3 OAM MIB Modules for MPLS-TP..............................19
6.3.1 New MIB Modules for OAM for MPLS-TP...............19
6.3.2 BFD MIB module....................................19
6.3.3 Common OAM MIB modules............................20
6.4. Protection Switching and Recovery MIB Modules
for MPLS-TP.............................................20
6.4.1 New MIB Modules for MPLS Protection Switching
and Recovery............................................20
6.4.2 Linear Protection Switching MIB module............20
6.4.3 Ring Protection Switching MIB module..............20
6.4.4 Mesh Protection Switching MIB module..............20
7. Management Options...........................................20
8. Security Considerations......................................21
9. IANA Considerations..........................................21
10. Acknowledgements............................................21
11. References..................................................22
11.1. Normative References...................................22
11.2. Informational References...............................23
12. Authors' Addresses..........................................27
1. Introduction 6. An Introduction to the MPLS-TP MIB Modules .....................20
6.1. MPLS-TP MIB Modules .......................................20
6.1.1. New MIB Modules for MPLS-TP ........................20
6.1.2. Textual Conventions for MPLS-TP ....................20
6.1.3. Identifiers for MPLS-TP ............................21
6.1.4. LSR MIB Extensions for MPLS-TP .....................21
6.1.5. Tunnel Extensions for MPLS-TP ......................21
6.2. PWE3 MIB Modules for MPLS-TP ..............................21
6.2.1. New MIB Modules for MPLS-TP Pseudowires ............21
6.2.2. Pseudowire Textual Conventions for MPLS-TP .........21
6.2.3. Pseudowire Extensions for MPLS-TP ..................22
6.2.4. Pseudowire MPLS Extensions for MPLS-TP .............22
6.3. OAM MIB Modules for MPLS-TP ...............................22
6.3.1. New MIB Modules for OAM for MPLS-TP ................22
6.3.2. BFD MIB Module .....................................22
6.3.3. OAM MIB Module .....................................23
6.4. Protection Switching and Recovery MIB Modules for MPLS-TP .23
6.4.1. New MIB Modules for MPLS Protection
Switching and Recovery .............................23
6.4.2. Linear Protection Switching MIB Module .............23
6.4.3. Ring Protection Switching MIB Module ...............23
6.4.4. Mesh Protection Switching MIB Module ...............23
7. Management Options .............................................23
8. Security Considerations ........................................24
9. IANA Considerations ............................................24
10. Acknowledgements ..............................................24
11. Contributors' Addresses .......................................25
12. References ....................................................26
12.1. Normative References .....................................26
12.2. Informative References ...................................27
The MPLS Transport Profile (MPLS-TP) is a packet transport 1. Introduction
technology based on a profile of the MPLS functionality specific
to the construction of packet-switched transport networks. The MPLS Transport Profile (MPLS-TP) is a packet transport technology
MPLS is described in [RFC3031] and requirements for MPLS-TP are based on a profile of the MPLS functionality specific to the
specified in [RFC5654]. construction of packet-switched transport networks. MPLS is
described in [RFC3031], and requirements for MPLS-TP are specified in
[RFC5654].
A range of Management Information Base (MIB) modules has been A range of Management Information Base (MIB) modules has been
developed to help model and manage the various aspects of developed to help model and manage the various aspects of
Multiprotocol Label Switching (MPLS) networks. These MIB modules Multiprotocol Label Switching (MPLS) networks. These MIB modules are
are defined in separate documents that focus on the specific areas of defined in separate documents that focus on the specific areas of
responsibility for the modules that they describe. responsibility for the modules that they describe.
An MPLS-TP network can be operated via static provisioning of An MPLS-TP network can be operated via static provisioning of
transport paths, Label Switched Paths (LSPs) and Pseudowires (PW). transport paths, Label Switched Paths (LSPs) and pseudowires (PWs),
Or the elective use of a Generalized MPLS (GMPLS) control plane to or the elective use of a Generalized MPLS (GMPLS) control plane to
support dynamic provisioning of transport paths, LSPs and PWs. support dynamic provisioning of transport paths, LSPs, and PWs.
This document describes the MIB-based management architecture for This document describes the MIB-based management architecture for
MPLS, as extended for MPLS-TP. The document also indicates the MPLS, as extended for MPLS-TP. The document also indicates the
interrelationships between existing MIB modules that should be interrelationships between existing MIB modules that should be
leveraged for MPLS-TP network management and identifies areas where leveraged for MPLS-TP network management and identifies areas where
additional MIB modules are required. additional MIB modules are required.
Note that [RFC5951] does not specify a preferred management interface Note that [RFC5951] does not specify a preferred management interface
protocol to be used as the standard protocol for managing MPLS-TP protocol to be used as the standard protocol for managing MPLS-TP
networks. networks.
1.1 MPLS-TP Management Function 1.1. MPLS-TP Management Function
The management of the MPLS-TP networks is separable from that of The management of the MPLS-TP networks is separable from that of its
its client networks so that the same means of management can be used client networks so that the same means of management can be used
regardless of the client. The management function of MPLS-TP regardless of the client. The management function of MPLS-TP
includes fault management, configuration management, performance includes fault management, configuration management, performance
monitoring, and security management. monitoring, and security management.
The purpose of the management function is to provide control and The purpose of the management function is to provide control and
monitoring of the MPLS transport profile protocol mechanisms and monitoring of the MPLS transport profile protocol mechanisms and
procedures. The requirements for the network management procedures. The requirements for the network management
functionality are found in [RFC5951]. A description of the network functionality are found in [RFC5951]. A description of the network
and element management architectures that can be applied to the and element management architectures that can be applied to the
management of MPLS-based transport networks is found in [RFC5950]. management of MPLS-based transport networks is found in [RFC5950].
2. Terminology 2. Terminology
This document also uses terminology from the MPLS architecture This document also uses terminology from the MPLS architecture
document [RFC3031], PWE3 architecture [RFC4805], and the following document [RFC3031], Pseudowire Emulation Edge-to-Edge (PWE3)
MPLS related MIB modules: MPLS TC MIB [RFC3811], MPLS LSR MIB architecture [RFC3985], and the following MPLS-related MIB modules:
[RFC3813], MPLS TE MIB [RFC3812], MPLS LDP MIB [RFC3815], MPLS FTN the MPLS-TC-STD-MIB [RFC3811], MPLS-LSR-STD-MIB [RFC3813],
MIB [RFC3814] and TE LINK MIB [RFC4220]. MPLS-TE-STD-MIB [RFC3812], MPLS-LDP-STD-MIB [RFC3815],
MPLS-FTN-STD-MIB [RFC3814], and TE-LINK-STD-MIB [RFC4220].
3. The SNMP Management Framework 3. The SNMP Management Framework
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). Structure of Management Information (SMI).
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 Internet-Standard Management Framework, please refer to Section 7 of
[RFC3410]. [RFC3410].
This document discusses MIB modules that are compliant to the SMIv2, This document discusses MIB modules that are compliant to the SMIv2,
which is described in [RFC2578], [RFC2579] and [RFC2580]. which is described in [RFC2578], [RFC2579], and [RFC2580].
4. Overview of Existing Work 4. Overview of Existing Work
This section describes the existing tools and techniques for This section describes the existing tools and techniques for managing
managing and modeling MPLS networks, devices, and protocols. It is and modeling MPLS networks, devices, and protocols. It is intended
intended to provide a description of the tool kit that is already to provide a description of the tool kit that is already available.
available.
Section 5 of this document outlines the applicability of existing Section 5 of this document outlines the applicability of existing
MPLS MIB modules to MPLS-TP, describes the optional use of GMPLS MIB MPLS MIB modules to MPLS-TP, describes the optional use of GMPLS MIB
modules in MPLS-TP networks, and examines the additional MIB modules modules in MPLS-TP networks, and examines the additional MIB modules
and objects that would be required for managing an MPLS-TP network. and objects that would be required for managing an MPLS-TP network.
4.1. MPLS Management Overview and Requirements 4.1. MPLS Management Overview and Requirements
[RFC4378] outlines how data plane protocols can assist in providing [RFC4378] outlines how data-plane protocols can assist in providing
the Operations and Management (OAM) requirements outlined in the Operations, Administration, and Maintenance (OAM) requirements
[RFC4377] and how it is applied to the management functions of fault, outlined in [RFC4377] and how it is applied to the management
configuration, accounting, performance, and security (commonly known functions of fault, configuration, accounting, performance, and
as FCAPS) for MPLS networks. security (commonly known as FCAPS) for MPLS networks.
[RFC4221] describes the management architecture for MPLS. In [RFC4221] describes the management architecture for MPLS. In
particular, it describes how the managed objects defined in various particular, it describes how the managed objects defined in various
MPLS-related MIB modules model different aspects of MPLS, as well as MPLS-related MIB modules model different aspects of MPLS, as well as
the interactions and dependencies between each of these MIB modules. the interactions and dependencies between each of these MIB modules.
[RFC4377] describes the requirements for user and data plane OAM and [RFC4377] describes the requirements for user- and data-plane OAM and
applications for MPLS. applications for MPLS.
[RFC5654] describes the requirements for the optional use of a [RFC5654] describes the requirements for the optional use of a
control plane to support dynamic provisioning of MPLS-TP transport control plane to support dynamic provisioning of MPLS-TP transport
paths. The MPLS-TP LSP control plane is based on GMPLS and is paths. The MPLS-TP LSP control plane is based on GMPLS and is
described in [RFC3945]. described in [RFC3945].
4.2. An Introduction to the MPLS and Pseudowire MIB Modules 4.2. An Introduction to the MPLS and Pseudowire MIB Modules
4.2.1. Structure of the MPLS MIB OID Tree 4.2.1. Structure of the MPLS MIB OID Tree
The MPLS MIB Object Identifiers (OID) tree has the following The MPLS MIB Object Identifier (OID) tree has the following
structure. It is based on the tree originally set out in section structure. It is based on the tree originally set out in Section 4.1
4.1 of [RFC4221] and has been enhanced to include other relevant MIB of [RFC4221] and has been enhanced to include other relevant MIB
modules. modules.
mib-2 -- RFC 2578 [RFC2578] mib-2 -- RFC 2578 [RFC2578]
| |
+-transmission +-transmission
| | | |
| +- mplsStdMIB | +- mplsStdMIB
| | | | | |
| | +- mplsTCStdMIB -- MPLS-TC-STD-MIB [RFC3811] | | +- mplsTCStdMIB -- MPLS-TC-STD-MIB [RFC3811]
| | | | | |
skipping to change at page 7, line 5 skipping to change at page 8, line 5
| |
+- pwMplsStdMIB -- PW-MPLS-STD-MIB [RFC5602] +- pwMplsStdMIB -- PW-MPLS-STD-MIB [RFC5602]
| |
+- pwTDMMIB -- PW-TDM-MIB [RFC5604] +- pwTDMMIB -- PW-TDM-MIB [RFC5604]
| |
+- pwTcStdMIB -- PW-TC-STD-MIB [RFC5542] +- pwTcStdMIB -- PW-TC-STD-MIB [RFC5542]
Note: The OIDs for MIB modules are assigned and managed by IANA. Note: The OIDs for MIB modules are assigned and managed by IANA.
They can be found in the referenced MIB documents. They can be found in the referenced MIB documents.
4.2.2. Textual Convention Modules 4.2.2. Textual Convention Modules
MPLS-TC-STD-MIB [RFC3811], GMPLS-TC-STD-MIB [RFC4801], The MPLS-TC-STD-MIB [RFC3811], GMPLS-TC-STD-MIB [RFC4801],
IANA-GMPLS-TC-MIB [RFC4802] and PW-TC-STD-MIB [RFC5542] contains the IANA-GMPLS-TC-MIB [RFC4802], and PW-TC-STD-MIB [RFC5542] contain the
Textual Conventions for MPLS and GMPLS networks. These Textual Textual Conventions for MPLS and GMPLS networks. These Textual
Conventions should be imported by MIB modules which manage MPLS Conventions should be imported by MIB modules that manage MPLS and
and GMPLS networks. Section 4.2.11. highlights dependencies on GMPLS networks. Section 4.2.11 highlights dependencies on additional
additional external MIB modules external MIB modules.
4.2.3. Label Switched Path (LSP) Modules 4.2.3. Label Switched Path (LSP) Modules
An LSP is a path over which a labeled packet travels across the An LSP is a path over which a labeled packet travels across the
sequence of LSRs for a given Forward Equivalence Class (FEC). When a sequence of Label Switching Routers (LSRs) for a given Forward
packet, with or without label, arrives at an ingress LER of an LSP, Equivalence Class (FEC). When a packet, with or without a label,
it is encapsulated with the label corresponding to the FEC and sent arrives at an ingress Label Edge Router (LER) of an LSP, it is
across the LSP. The labeled packet traverses across the LSRs and encapsulated with the label corresponding to the FEC and sent across
arrives at the egress LER of the LSP, where, it gets forwarded the LSP. The labeled packet traverses the LSRs and arrives at the
depending on the packet type it came with. LSPs could be nested using egress LER of the LSP, where it gets forwarded, depending on the
label stacking, such that, an LSP could traverse over another LSP. A packet type it came with. LSPs could be nested using label stacking,
further description of an LSP can be found in [RFC3031]. such that an LSP could traverse another LSP. A more detailed
description of an LSP can be found in [RFC3031].
MPLS-LSR-STD-MIB [RFC3813] describes the required objects to define The MPLS-LSR-STD-MIB [RFC3813] describes the objects required to
the LSP. define the LSP.
4.2.4. Label Edge Router (LER) Modules 4.2.4. Label Edge Router (LER) Modules
Ingress and Egress LSRs of an LSP are known as Label Edge Routers Ingress and egress LSRs of an LSP are known as Label Edge Routers
(LER). An ingress LER takes the incoming unlabeled or labeled packets (LERs). An ingress LER takes each incoming unlabeled or labeled
and encapsulates it with the corresponding label of the LSP it packet and encapsulates it with the corresponding label of the LSP it
represents, and forwards it, over to the adjacent LSR of the LSP. represents, and then forwards it to the adjacent LSR of the LSP.
Each FEC is mapped to a label forwarding entry, so that packet could Each FEC is mapped to a label-forwarding entry, so that a packet
be encapsulated with one or more label entries, referred as label could be encapsulated with one or more label entries; this is
stack. referred to as a label stack.
The packet traverses across the LSP, and upon reaching the Egress The packet traverses the LSP. Upon reaching the egress LER, further
LER, further action will be taken to handle the packet, depending on action will be taken to handle the packet, depending on the type of
the packet it received. MPLS Architecture [RFC3031] details packet received. MPLS Architecture [RFC3031] details the
the functionality of an Ingress and Egress LERs. functionality of ingress and egress LERs.
MPLS-FTN-STD-MIB [RFC3814] describes the managed objects for mapping The MPLS-FTN-STD-MIB [RFC3814] describes the managed objects for
FEC to label bindings. mapping FEC to label bindings.
4.2.5. Label Switching Router (LSR) Modules 4.2.5. Label Switching Router (LSR) Modules
A router which performs MPLS forwarding is known as an LSR. An LSR A router that performs MPLS forwarding is known as an LSR. An LSR
receives a labelled packet and performs forwarding action based on receives a labeled packet and performs forwarding action based on the
the label received. label received.
LSR maintains a mapping of an incoming label and incoming interface The LSR maintains a mapping of an incoming label and incoming
to one or more outgoing label and outgoing interfaces in its interface to one or more outgoing labels and outgoing interfaces in
forwarding database. When a labelled packet is received, LSR examines its forwarding database. When a labeled packet is received, the LSR
the topmost label in the label stack and then does 'swap', 'push' or examines the topmost label in the label stack and then does a 'swap',
'pop' operation based on the contents. 'push', or 'pop' operation based on the contents.
MPLS-LSR-STD-MIB [RFC3813] describes the managed objects for modeling The MPLS-LSR-STD-MIB [RFC3813] describes the managed objects for
a Multiprotocol Label Switching (MPLS) [RFC3031] LSR. modeling an MPLS [RFC3031] LSR. The MPLS-LSR-STD-MIB [RFC3813]
MPLS-LSR-STD-MIB [RFC3813] contains the managed objects to maintain contains the managed objects to maintain mapping of in-segments to
mapping of in-segments to out-segments. out-segments.
4.2.6. Pseudowire Modules 4.2.6. Pseudowire Modules
The PW (Pseudowire) MIB architecture provides a layered modular model The pseudowire (PW) MIB architecture provides a layered modular model
into which any supported emulated service such as Frame Relay, ATM, into which any supported emulated service such as Frame Relay, ATM,
Ethernet, TDM and SONET/SDH can be connected to any supported Packet Ethernet, Time-Division Multiplexing (TDM), and Synchronous Optical
Switched Network (PSN) type. This MIB architecture is modeled based Network/Synchronous Digital Hierarchy (SONET/SDH) can be connected to
on PW3 architecture [RFC3985]. any supported Packet Switched Network (PSN) type. This MIB
architecture is modeled based on PW3 architecture [RFC3985].
Emulated Service Layer, Generic PW Layer and PSN VC Layer constitute The emulated service layer, generic PW layer, and PSN Virtual Circuit
the different layers of the model. A combination of the MIB modules (VC) layer constitute the different layers of the model. A
belonging to each layer provides the glue for mapping the emulated combination of the MIB modules belonging to each layer provides the
service onto the native PSN service. At least three MIB modules each glue for mapping the emulated service onto the native PSN service.
belonging to a different layer are required to define a PW emulated At least three MIB modules, each belonging to a different layer, are
service. required to define a PW emulated service.
- Service-Specific module is dependent on the emulated signal type - The service-specific module is dependent on the emulated signal
and helps in modeling emulated service layer. type and helps in modeling the emulated service layer.
PW-ENET-STD-MIB [RFC5603] describes a model for managing Ethernet The PW-ENET-STD-MIB [RFC5603] describes a model for managing Ethernet
pseudowire services for transmission over a PSN. This MIB module is pseudowire services for transmission over a PSN. This MIB module is
generic and common to all types of PSNs supported in the Pseudowire generic and common to all types of PSNs supported in the PWE3
Emulation Edge-to-Edge (PWE3) Architecture [RFC3985], which describes Architecture [RFC3985], which describes the transport and
the transport and encapsulation of L1 and L2 services over supported encapsulation of L1 and L2 services over supported PSN types.
PSN types.
In particular, the MIB module associates a port or specific VLANs on In particular, the MIB module associates a port or specific VLANs on
top of a physical Ethernet port or a virtual Ethernet interface (for top of a physical Ethernet port or a virtual Ethernet interface (for
Virtual Private LAN Service (VPLS)) to a point-to-point PW. It is the Virtual Private LAN Service (VPLS)) to a point-to-point PW. It
complementary to the PW-STD-MIB [RFC5601], which manages the generic is complementary to the PW-STD-MIB [RFC5601], which manages the
PW parameters common to all services, including all supported PSN generic PW parameters common to all services, including all supported
types. PSN types.
PW-TDM-MIB [RFC5604] describes a model for managing TDM pseudowires, The PW-TDM-MIB [RFC5604] describes a model for managing TDM
i.e., TDM data encapsulated for transmission over a Packet Switched pseudowires, i.e., TDM data encapsulated for transmission over a PSN.
Network (PSN). The term TDM in this document is limited to the The term "TDM" in this document is limited to the scope of
scope of Plesiochronous Digital Hierarchy (PDH). It is currently Plesiochronous Digital Hierarchy (PDH). It is currently specified to
specified to carry any TDM Signals in either Structure Agnostic carry any TDM signals in either Structure Agnostic Transport mode
Transport mode (E1, T1, E3, and T3) or in Structure Aware (E1, T1, E3, and T3) or Structure Aware Transport mode (E1, T1, and
Transport mode (E1, T1, and NxDS0) as defined in the Pseudowire NxDS0) as defined in the PWE3 TDM Requirements document [RFC4197].
Emulation Edge-to-Edge (PWE3) TDM Requirements document [RFC4197].
- Generic PW Module configures general parameters of the PW that are - The generic PW module configures general parameters of the PW that
common to all types of emulated services and PSN types. are common to all types of emulated services and PSN types.
PW-STD-MIB [RFC5601] defines a MIB module that can be The PW-STD-MIB [RFC5601] defines a MIB module that can be used to
used to manage pseudowire (PW) services for transmission over a manage PW services for transmission over a PSN [RFC3931] [RFC4447].
Packet Switched Network (PSN) [RFC3931] [RFC4447]. This MIB module This MIB module provides generic management of PWs that is common to
provides generic management of PWs that is common to all types of all types of PSN and PW services defined by the IETF PWE3 Working
PSN and PW services defined by the IETF PWE3 Working Group. Group.
- PSN-specific module associate the PW with one or more "tunnels" - The PSN-specific module associates the PW with one or more
that carry the service over the PSN. There is a different module "tunnels" that carry the service over the PSN. There is a
for each type of PSN. different module for each type of PSN.
PW-MPLS-STD-MIB [RFC5602] describes a model for managing pseudowire The PW-MPLS-STD-MIB [RFC5602] describes a model for managing
services for transmission over different flavors of MPLS tunnels. pseudowire services for transmission over different flavors of MPLS
The general PW MIB module [RFC5601] defines the parameters global to tunnels. The generic PW MIB module [RFC5601] defines the parameters
the PW regardless of the underlying Packet Switched Network (PSN) global to the PW, regardless of the underlying PSN and emulated
and emulated service. This document is applicable for PWs that use service. This document is applicable for PWs that use the MPLS PSN
MPLS PSN type in the PW-STD-MIB. Additionally this document describes type in the PW-STD-MIB. Additionally, this document describes the
the MIB objects that define pseudowire association to the MPLS PSN, MIB objects that define pseudowire association to the MPLS PSN that
that is not specific to the carried service. is not specific to the carried service.
Together, [RFC3811], [RFC3812] and [RFC3813] describe the modeling of Together, [RFC3811], [RFC3812], and [RFC3813] describe the modeling
an MPLS tunnel, and a tunnel's underlying cross-connects. This MIB of an MPLS tunnel and a tunnel's underlying cross-connects. This MIB
module supports MPLS-TE PSN, non-TE MPLS PSN (an outer tunnel created module supports MPLS Traffic Engineering (MPLS-TE) PSNs, non-TE MPLS
by the Label Distribution Protocol (LDP) or manually), and MPLS PW PSNs (an outer tunnel created by the Label Distribution Protocol
label only (no outer tunnel). (LDP) or manually), and MPLS PW labels only (no outer tunnel).
4.2.7. Routing and Traffic Engineering 4.2.7. Routing and Traffic Engineering
In MPLS traffic engineering, it's possible to specify explicit routes In MPLS traffic engineering, it's possible to specify explicit routes
or choose routes based on QOS metrics in setting up a path such that or choose routes based on QoS metrics in setting up a path such that
some specific data can be routed around network hot spots. TE LSPs some specific data can be routed around network hot spots. TE LSPs
can be setup through a management plane or a control plane. can be set up through a management plane or a control plane.
MPLS-TE-STD-MIB [RFC3812] describes managed objects for modeling a The MPLS-TE-STD-MIB [RFC3812] describes managed objects for modeling
Multiprotocol Label Switching (MPLS) [RFC3031] based traffic MPLS [RFC3031]-based traffic engineering. This MIB module should be
engineering. This MIB module should be used in conjunction with the used in conjunction with the companion document [RFC3813] for MPLS-
companion document [RFC3813] for MPLS based traffic engineering based traffic engineering configuration and management.
configuration and management.
4.2.8. Resiliency 4.2.8. Resiliency
The purpose of MPLS resiliency is to ensure minimal interruption to The purpose of MPLS resiliency is to ensure minimal interruption to
traffic when the failure occurs within the system or network. traffic when a failure occurs within the system or network.
Various components of MPLS resiliency solutions are; Various components of MPLS resiliency solutions are as follows:
1) Graceful restart in LDP and RSVP-TE modules,
2) Make Before Break,
3) Protection Switching for LSPs,
4) Fast ReRoute for LSPs,
5) PW redundancy.
The MIB modules below only support MIB based management for MPLS 1) Graceful restart in LDP and RSVP-TE modules
2) Make before break
3) Protection switching for LSPs
4) Fast reroute for LSPs
5) PW redundancy
The MIB modules below only support MIB-based management for MPLS
resiliency. resiliency.
MPLS Fast Reroute (FRR) is a restoration network resiliency mechanism MPLS Fast Reroute (FRR) is a restoration network resiliency mechanism
used in MPLS TE to redirect the traffic onto the backup LSP's in 10s used in MPLS TE to redirect traffic onto the backup LSPs in tens of
of milliseconds in case of link or node failure across the LSP. milliseconds in case of link or node failure across the LSP.
MPLS-FRR-GENERAL-STD-MIB [draft-ietf-mpls-fastreroute-mib-14] The MPLS-FRR-GENERAL-STD-MIB [RFC6445] contains objects that apply to
contains objects that apply to any MPLS LSR implementing MPLS TE fast any MPLS LSR implementing MPLS TE fast-reroute functionality.
reroute functionality.
MPLS-FRR-ONE2ONE-STD-MIB [draft-ietf-mpls-fastreroute-mib-14] The MPLS-FRR-ONE2ONE-STD-MIB [RFC6445] contains objects that apply to
contains objects that apply to one-to-one backup method. the one-to-one backup method.
MPLS-FRR-FACILITY-STD-MIB [draft-ietf-mpls-fastreroute-mib-14]
contains objects that apply to facility backup method.
Protection Switching mechanisms have been designed to provide network The MPLS-FRR-FACILITY-STD-MIB [RFC6445] contains objects that apply
resiliency for MPLS network. Different types of protection switching to the facility backup method.
mechanisms such as 1:1, 1:N, 1+1 have been designed.
4.2.9. Fault Management and Performance Management Protection switching mechanisms have been designed to provide network
resiliency for MPLS networks. Different types of protection
switching mechanisms, such as 1:1, 1:N, and 1+1, have been designed.
MPLS manages the LSP and pseudowire faults through the use of LSP 4.2.9. Fault Management and Performance Management
ping [RFC4379], VCCV [RFC5085], BFD for LSPs [RFC5884] and BFD for
VCCV [RFC5885] tools.
Current MPLS focuses on the in and/or out packet counters, MPLS manages LSP and pseudowire faults through the use of LSP ping
errored packets, discontinuity time. [RFC4379], Virtual Circuit Connectivity Verification (VCCV)
[RFC5085], Bidirectional Forwarding Detection (BFD) for LSPs
[RFC5884], and BFD for VCCV [RFC5885] tools.
Some of the MPLS and Pseudowire performance tables used for MPLS currently focuses on in and/or out packet counters, errored
packets, and discontinuity time.
Some of the MPLS and pseudowire performance tables used for
performance management are given below. performance management are given below.
mplsTunnelPerfTable [RFC3812] provides several counters (packets The mplsTunnelPerfTable [RFC3812] provides several counters (e.g.,
forwarded, packets dropped because of errors) to measure the packets forwarded, packets dropped because of errors) to measure the
performance of the MPLS tunnels. performance of the MPLS tunnels.
mplsInterfacePerfTable [RFC3813] provides performance information The mplsInterfacePerfTable [RFC3813] provides performance information
(incoming and outgoing labels in use and lookup failures) on a (incoming and outgoing labels in use, and lookup failures) on a
per-interface basis. per-interface basis.
mplsInSegmentPerfTable [RFC3813] contains statistical information The mplsInSegmentPerfTable [RFC3813] contains statistical information
(total packets received by the insegment, total errored packets (total packets received by the in-segment, total errored packets
received, total packets discarded, discontinuity time) for incoming received, total packets discarded, discontinuity time) for incoming
MPLS segments to an LSR. MPLS segments to an LSR.
mplsOutSegmentPerfTable [RFC3813] contains statistical information The mplsOutSegmentPerfTable [RFC3813] contains statistical
(total packets received, total errored packets received, total information (total packets received, total errored packets received,
packets discarded, discontinuity time) for outgoing MPLS segments total packets discarded, discontinuity time) for outgoing MPLS
from an LSR. segments from an LSR.
mplsFTNPerfTable [RFC3814] contains performance information for the The mplsFTNPerfTable [RFC3814] contains performance information for
specified interface and an FTN entry mapped to this interface. the specified interface and an FTN entry mapped to this interface.
mplsLdpEntityStatsTable [RFC3815] and mplsLdpSessionStatsTable The mplsLdpEntityStatsTable [RFC3815] and mplsLdpSessionStatsTable
[RFC3815] contain statistical information (session attempts, errored [RFC3815] contain statistical information (session attempts, errored
packets, notifications) about an LDP entity. packets, notifications) about an LDP entity.
pwPerfCurrentTable [RFC5601], pwPerfIntervalTable [RFC5601], The pwPerfCurrentTable [RFC5601], pwPerfIntervalTable [RFC5601], and
pwPerf1DayIntervalTable [RFC5601] provides pseudowire performance pwPerf1DayIntervalTable [RFC5601] provide pseudowire performance
information (in and/or out packets) based on time (current interval, information (in and/or out packets) based on time (current interval,
preconfigured specific interval, 1day interval). preconfigured specific interval, 1-day interval).
pwEnetStatsTable [RFC5603] contains statistical counters specific for The pwEnetStatsTable [RFC5603] contains statistical counters specific
Ethernet PW. for Ethernet PW.
pwTDMPerfCurrentTable [RFC5604], pwTDMPerfIntervalTable [RFC5604] and The pwTDMPerfCurrentTable [RFC5604], pwTDMPerfIntervalTable
pwTDMPerf1DayIntervalTable [RFC5604] contain statistical informations [RFC5604], and pwTDMPerf1DayIntervalTable [RFC5604] contain
accumulated per 15-minute, 24 hour, 1 day respectively. statistical information accumulated per 15-minute, 24-hour, and 1-day
periods, respectively.
gmplsTunnelErrorTable [RFC4802] and gmplsTunnelReversePerfTable The gmplsTunnelErrorTable [RFC4802] and gmplsTunnelReversePerfTable
[RFC4802] provides information about performance errored packets and [RFC4802] provide information about performance, errored packets, and
in/out packet counters. in/out packet counters.
4.2.10. MIB Module Interdependencies 4.2.10. MIB Module Interdependencies
This section provides an overview of the relationship between the This section provides an overview of the relationship between the
MPLS MIB modules for managing MPLS networks. More details of these MPLS MIB modules for managing MPLS networks. More details of these
relationships are given below. relationships are given below.
[RFC4221] mainly focuses on the MPLS MIB module interdependencies, [RFC4221] mainly focuses on MPLS MIB module interdependencies. This
this section also highlights the GMPLS and PW MIB modules section also highlights GMPLS and PW MIB module interdependencies.
interdependencies.
The relationship "A --> B" means A depends on B and that MIB module The relationship "A --> B" means that A depends on B and that MIB
A uses an object, object identifier, or textual convention defined module A uses an object, object identifier, or Textual Convention
in MIB module B, or that MIB module A contains a pointer (index or defined in MIB module B, or that MIB module A contains a pointer
RowPointer) to an object in MIB module B. (index or RowPointer) to an object in MIB module B.
+-------> MPLS-TC-STD-MIB <-----------------------------------------+ +-------> MPLS-TC-STD-MIB <-----------------------------------------+
^ ^ ^ ^ ^ ^
| | | | | |
| MPLS-LSR-STD-MIB <--------------------------------+ | | MPLS-LSR-STD-MIB <--------------------------------+ |
| ^ | | ^ |
| | | | | |
+<----------------------- MPLS-LDP-STD-MIB ---------------->+ | +<----------------------- MPLS-LDP-STD-MIB ---------------->+ |
^ ^ ^ | ^ ^ ^ |
| | | | | | | |
skipping to change at page 12, line 44 skipping to change at page 14, line 44
| | ^ ^ | | ^ ^
+<--- PW-STD-MIB <------+ | | +<--- PW-STD-MIB <------+ | |
^ ^ | | ^ ^ | |
| | | | | | | |
+<--- PW-ENET-STD-MIB ->+ | | +<--- PW-ENET-STD-MIB ->+ | |
^ ^ | | ^ ^ | |
| | | | | | | |
| | | | | | | |
+<---------------- PW-MPLS-STD-MIB--------------------------------->+ +<---------------- PW-MPLS-STD-MIB--------------------------------->+
Thus: Thus,
- All the MPLS MIB modules depend on MPLS-TC-STD-MIB. - All the MPLS MIB modules depend on the MPLS-TC-STD-MIB.
- All the GMPLS MIB modules depend on GMPLS-TC-STD-MIB. - All the GMPLS MIB modules depend on the GMPLS-TC-STD-MIB.
- All the PW MIB modules depend on PW-TC-STD-MIB. - All the PW MIB modules depend on the PW-TC-STD-MIB.
- MPLS-LDP-STD-MIB, MPLS-TE-STD-MIB, MPLS-FTN-STD-MIB, - The MPLS-LDP-STD-MIB, MPLS-TE-STD-MIB, MPLS-FTN-STD-MIB,
GMPLS-LSR-STD-MIB, and PW-MPLS-STD-MIB contain references to GMPLS-LSR-STD-MIB, and PW-MPLS-STD-MIB contain references to
objects in MPLS-LSR-STD-MIB. objects in the MPLS-LSR-STD-MIB.
- MPLS-LDP-GENERIC-STD-MIB contains references to objects in - The MPLS-LDP-GENERIC-STD-MIB contains references to objects in the
MPLS-LDP-STD-MIB. MPLS-LDP-STD-MIB.
- MPLS-FTN-STD-MIB, PW-MPLS-STD-MIB, and GMPLS-TE-STD-MIB contain - The MPLS-FTN-STD-MIB, PW-MPLS-STD-MIB, and GMPLS-TE-STD-MIB
references to objects in MPLS-TE-STD-MIB. contain references to objects in the MPLS-TE-STD-MIB.
- PW-MPLS-STD-MIB, and PW-ENET-STD-MIB contains references to - The PW-MPLS-STD-MIB and PW-ENET-STD-MIB contain references to
objects in PW-STD-MIB. objects in the PW-STD-MIB.
- PW-STD-MIB contains references to objects in IANA-PWE3-MIB. - The PW-STD-MIB contains references to objects in the
IANA-PWE3-MIB.
- GMPLS-TE-STD-MIB contains references to objects in - The GMPLS-TE-STD-MIB contains references to objects in the
IANA-GMPLS-TC-MIB. IANA-GMPLS-TC-MIB.
- GMPLS-LSR-STD-MIB contains references to objects in - The GMPLS-LSR-STD-MIB contains references to objects in the
GMPLS-LABEL-STD-MIB. GMPLS-LABEL-STD-MIB.
Note that there is a textual convention (MplsIndexType) defined in Note that there is a Textual Convention (MplsIndexType) defined in
MPLS-LSR-STD-MIB that is imported by MPLS-LDP-STD-MIB. the MPLS-LSR-STD-MIB that is imported by the MPLS-LDP-STD-MIB.
4.2.11. Dependencies on External MIB Modules 4.2.11. Dependencies on External MIB Modules
With the exception of MPLS-TC-STD-MIB, all the MPLS MIB modules have With the exception of the MPLS-TC-STD-MIB, all the MPLS MIB modules
dependencies on the Interfaces MIB [RFC2863]. MPLS-FTN-STD-MIB have dependencies on the Interfaces MIB (also called the Interfaces
references IP-capable interfaces on which received traffic is to be Group MIB or the IF-MIB) [RFC2863]. The MPLS-FTN-STD-MIB references
classified using indexes in the Interface Table (ifTable) of IF-MIB IP-capable interfaces on which received traffic is to be classified
using indexes in the Interfaces Table (ifTable) of the IF-MIB
[RFC2863]. The other MPLS MIB modules reference MPLS-capable [RFC2863]. The other MPLS MIB modules reference MPLS-capable
interfaces in ifTable. interfaces in the ifTable.
The Interfaces Group of IF-MIB [RFC2863] defines generic managed The IF-MIB [RFC2863] defines generic managed objects for managing
objects for managing interfaces. The MPLS MIB modules contain interfaces. The MPLS MIB modules contain media-specific extensions
media-specific extensions to the Interfaces Group for managing MPLS to the Interfaces Group for managing MPLS interfaces.
interfaces.
The MPLS MIB modules assume the interpretation of the Interfaces The MPLS MIB modules assume the interpretation of the Interfaces
Group to be in accordance with [RFC2863], which states that ifTable Group to be in accordance with [RFC2863], which states that the
contains information on the managed resource's interfaces and that ifTable contains information on the managed resource's interfaces and
each sub-layer below the internetwork layer of a network interface is that each sub-layer below the internetwork layer of a network
considered an interface. Thus, the MPLS interface is represented as interface is considered an interface. Thus, the MPLS interface is
an entry in ifTable. represented as an entry in the ifTable.
The interrelation of entries in ifTable is defined by the Interfaces The interrelation of entries in the ifTable is defined by the
Stack Group defined in [RFC2863]. Interface Stack Group defined in [RFC2863].
The MPLS MIB modules have dependencies with the TE-LINK-STD-MIB The MPLS MIB modules have dependencies on the TE-LINK-STD-MIB for
for maintaining the traffic engineering information. maintaining traffic engineering information.
The MPLS MIB modules depend on the constrained shortest path first The MPLS MIB modules depend on the Constrained Shortest Path First
(CSPF) module to obtain the path required for an MPLS tunnel to reach (CSPF) component to obtain the path required for an MPLS tunnel to
the end point of the tunnel and Bidirectional Forwarding Detection reach the end point of the tunnel, and on the BFD component to verify
(BFD) module to verify the data-plane failures of LSPs and PWs. data-plane failures of LSPs and PWs.
Finally, all of the MIB modules import standard textual conventions Finally, all of the MIB modules import standard Textual Conventions
such as integers, strings, timestamps, etc., from the MIB modules in such as integers, strings, timestamps, etc., from the MIB modules in
which they are defined. which they are defined.
5. Applicability of MPLS MIB modules to MPLS-TP 5. Applicability of MPLS MIB Modules to MPLS-TP
This section highlights gaps in existing MPLS MIB modules in This section highlights gaps in existing MPLS MIB modules in order to
order to determine extensions or additional MIB modules that are determine extensions or additional MIB modules that are required to
required to support MPLS-TP in MPLS networks support MPLS-TP in MPLS networks.
[RFC5951] specifies the requirements for the management of equipment [RFC5951] specifies the requirements for the management of equipment
used in networks supporting an MPLS-TP. It also details the used in networks supporting MPLS-TP. It also details the essential
essential network management capabilities for operating networks network management capabilities for operating networks consisting of
consisting of MPLS-TP equipment. MPLS-TP equipment.
[RFC5950] provides the network management framework for MPLS-TP. The [RFC5950] provides the network management framework for MPLS-TP. The
document explains how network elements and networks that support document explains how network elements and networks that support
MPLS-TP can be managed using solutions that satisfy the MPLS-TP can be managed using solutions that satisfy the requirements
requirements defined in [RFC5951]. The relationship between MPLS-TP defined in [RFC5951]. The relationship between MPLS-TP management
management and OAM is described in the MPLS-TP framework [RFC5950] and OAM is described in the MPLS-TP framework document [RFC5950].
document.
The MPLS MIB modules MPLS-TE-STD-MIB [RFC3812], PW-STD-MIB [RFC5601] The MPLS MIB documents MPLS-TE-STD-MIB [RFC3812], PW-STD-MIB
and MPLS-LSR-STD-MIB [RFC3813] and their associated MIB modules are [RFC5601], and MPLS-LSR-STD-MIB [RFC3813], and their associated MIB
reused for MPLS based transport network management. modules, are reused for MPLS-based transport network management.
Fault management and performance management form key parts of Fault management and performance management form key parts of the OAM
the Operations, Administration, and Maintenance (OAM) function. function. MPLS-TP OAM is described in [RFC6371].
MPLS-TP OAM is described in [MPLS-TP-OAM-FWK].
5.1 MPLS-TP Tunnel 5.1. MPLS-TP Tunnel
5.1.1 Gap Analysis 5.1.1. Gap Analysis
MPLS-TP tunnel can be operated over IP and/or ITU-T Carrier Code An MPLS-TP tunnel can be operated over IP and/or ITU-T Carrier Code
(ICC) environments, below points capture the gaps in existing MPLS (ICC) environments. The points below capture the gaps in existing
MIB modules for managing the MPLS-TP networks. MPLS MIB modules for managing MPLS-TP networks.
- IP based environment - IP-based environment
i. MPLS-TE-STD-MIB [RFC3812] does not support tunnel
Ingress/Egress identifier based on Global_ID and Node_ID i. The MPLS-TE-STD-MIB [RFC3812] does not support the tunnel
[RFC6370]. Ingress/Egress identifier based on Global_ID and Node_ID
ii. MPLS-TE-STD-MIB [RFC3812] does not support [RFC6370].
ii. The MPLS-TE-STD-MIB [RFC3812] does not support
co-routed/associated bidirectional tunnel configurations. co-routed/associated bidirectional tunnel configurations.
- ICC based environment - ICC-based environment
i. MPLS-TE-STD-MIB [RFC3812] does not support tunnel LSR
identifier based on ICC.
5.1.2 Recommendations i. The MPLS-TE-STD-MIB [RFC3812] does not support the tunnel LSR
identifier based on ICC.
- New MIB definitions may be created for Global_Node_ID and/or 5.1.2. Recommendations
ICC configurations.
- MPLS-LSR-STD-MIB [RFC3813] MIB modules may be enhanced to identify - New MIB definitions may be created for Global_Node_ID and/or ICC
the nexthop based on MAC address for IP-less environments. configurations.
OutSegment may be extended to hold the MAC-address also for
IP-less environments.
- MPLS-TE-STD-MIB [RFC3812] and MPLS-LSR-STD-MIB may be - The MPLS-LSR-STD-MIB [RFC3813] module may be enhanced to identify
enhanced to provide static and signalling MIB module the next hop based on a Media Access Control (MAC) address for
extensions for co-routed/associated bidirectional LSPs. environments that do not use IP. The mplsOutSegmentTable may be
extended to hold the MAC address.
5.2 MPLS-TP Pseudowire - The MPLS-TE-STD-MIB [RFC3812] and MPLS-LSR-STD-MIB may be enhanced
to provide static and signaling MIB module extensions for
co-routed/associated bidirectional LSPs.
5.2.1 Gap Analysis 5.2. MPLS-TP Pseudowire
MPLS-TP Pseudowire can be operated over IP and/or ICC environments, 5.2.1. Gap Analysis
below points capture the gaps in existing PW MIB modules
for managing the MPLS-TP networks.
[RFC6370] specifies an initial set of identifiers to be MPLS-TP pseudowire can be operated over IP and/or ICC environments.
used in MPLS-TP. These identifiers were chosen to be compatible with The points below capture the gaps in existing PW MIB modules for
managing MPLS-TP networks.
[RFC6370] specifies an initial set of identifiers to be used in
MPLS-TP. These identifiers were chosen to be compatible with
existing MPLS, GMPLS, and PW definitions. existing MPLS, GMPLS, and PW definitions.
- IP based environment - IP-based environment
i. PW-STD-MIB [RFC5601] does not support
PW end point identifier based on Global_ID and Node_ID.
ii. PW-MPLS-STD-MIB [RFC5602] does not support
its operation over co-routed/associated bidirectional tunnels.
- ICC based environment i. The PW-STD-MIB [RFC5601] does not support the PW end point
i. PW-STD-MIB [RFC5601] does not support identifier based on Global_ID and Node_ID.
PW end point identifier based on ICC.
5.2.2 Recommendations ii. The PW-MPLS-STD-MIB [RFC5602] does not support operation over
co-routed/associated bidirectional tunnels.
- PW-MPLS-STD-MIB [RFC5602] can be enhanced to operate over - ICC-based environment
co-routed/associated bi-directional tunnel.
5.3 MPLS-TP Sections i. The PW-STD-MIB [RFC5601] does not support the PW end point
identifier based on ICC.
5.3.1 Gap Analysis 5.2.2. Recommendations
- The PW-MPLS-STD-MIB [RFC5602] can be enhanced to operate over
co-routed/associated bidirectional tunnels.
5.3. MPLS-TP Sections
5.3.1. Gap Analysis
The existing MPLS MIB modules do not support MPLS-TP sections. The existing MPLS MIB modules do not support MPLS-TP sections.
5.3.2 Recommendations 5.3.2. Recommendations
Link specific and/or path/segment specific sections can be supported
by enhancing the IF-MIB [RFC2863], MPLS-TE-STD-MIB [RFC3812] and Link-specific and/or path/segment-specific sections can be supported
by enhancing the IF-MIB [RFC2863], MPLS-TE-STD-MIB [RFC3812], and
PW-STD-MIB [RFC5601] MIB modules. PW-STD-MIB [RFC5601] MIB modules.
5.4 MPLS-TP OAM 5.4. MPLS-TP OAM
5.4.1 Gap Analysis 5.4.1. Gap Analysis
MPLS manages the LSP and pseudowire faults through LSP ping MPLS manages LSP and pseudowire faults through LSP ping [RFC4379],
[RFC4379], VCCV [RFC5085], BFD for LSPs [RFC5884] and BFD for VCCV VCCV [RFC5085], BFD for LSPs [RFC5884], and BFD for VCCV [RFC5885]
[RFC5885] tools. tools.
The MPLS MIB modules do not support the below MPLS-TP OAM functions: The MPLS MIB modules do not support the following MPLS-TP OAM
functions:
o Continuity Check and Connectivity Verification o Continuity Check and Connectivity Verification
o Remote Defect Indication
o Alarm Reporting
o Lock Reporting
o Lock Instruct
o Client Failure Indication
o Packet Loss Measurement
o Packet Delay Measurement
5.4.2 Recommendations o Remote Defect Indication
o Alarm Reporting
o Lock Reporting
o Lock Instruct
o Client Failure Indication
o Packet Loss Measurement
o Packet Delay Measurement
5.4.2. Recommendations
New MIB module for BFD can be created to address all the gaps New MIB module for BFD can be created to address all the gaps
mentioned in Section 5.4.1. (Gap Analysis). mentioned in Section 5.4.1.
5.5 MPLS-TP Protection Switching and Recovery 5.5. MPLS-TP Protection Switching and Recovery
5.5.1 Gap Analysis 5.5.1. Gap Analysis
An important aspect that MPLS-TP technology provides is protection An important aspect that MPLS-TP technology provides is protection
switching. In general, the mechanism of protection switching switching. In general, the mechanism of protection switching can be
can be described as the substitution of a protection or standby described as the substitution of a protection or standby facility for
facility for a working or primary facility. a working or primary facility.
The MPLS MIB modules do not provide support for protection switching The MPLS MIB modules do not provide support for protection switching
and recovery of three different topologies (linear, ring and mesh) and recovery in the following three topologies: linear, ring, and
available. mesh.
5.5.2 Recommendations 5.5.2. Recommendations
New MIB modules can be created to address all the gaps mentioned New MIB modules can be created to address all the gaps mentioned in
in the 5.5.1 Gap Analysis section. Section 5.5.1.
5.6 MPLS-TP Interfaces 5.6. MPLS-TP Interfaces
5.6.1 Gap Analysis 5.6.1. Gap Analysis
As per [RFC6370], an LSR requires identification of the
node itself and of its interfaces. An interface is the attachment
point to a server layer MPLS-TP section or MPLS-TP tunnel.
The MPLS MIB modules do not provide support for configuring As per [RFC6370], an LSR requires identification of the node itself
the interfaces within the context of an operator. and of its interfaces. An interface is the attachment point to a
server layer MPLS-TP section or MPLS-TP tunnel.
5.6.2 Recommendations The MPLS MIB modules do not provide support for configuring the
interfaces within the context of an operator.
New MIB definitions can be created to address the gaps mentioned 5.6.2. Recommendations
in the 5.6.1 Gap Analysis section.
6. An Introduction to the MPLS-TP MIB Modules New MIB definitions can be created to address the gaps mentioned in
Section 5.6.1.
This section highlights new MIB modules that have been identified 6. An Introduction to the MPLS-TP MIB Modules
as being required for MPLS-TP. This section also provides an overview
the purpose of each of the MIB modules within the MIB documents, what This section highlights new MIB modules that have been identified as
it can be used for, and how it relates to the other MIB modules. being required for MPLS-TP. This section also provides an overview
of the purpose of each MIB module within the MIB documents, what it
can be used for, and how it relates to the other MIB modules.
Note that each new MIB module (apart from Textual Conventions Note that each new MIB module (apart from Textual Conventions
modules) will contain one or more Compliance Statements to indicate modules) will contain one or more Compliance Statements to indicate
which objects must be supported in what manner to claim a specific which objects must be supported in what manner to claim a specific
level of compliance. Additional text, either in the documents that level of compliance. Additional text, either in the documents that
define the MIB modules or in separate Applicability Statements, will define the MIB modules or in separate Applicability Statements, will
define which Compliance Statements need to be conformed to in order define which Compliance Statements need to be conformed to in order
to provide specific MPLS-TP function. This document does not set any to provide specific MPLS-TP functionality. This document does not
requirements in that respect although some recommendations are set any requirements in that respect, although some recommendations
included in the sections that follow. are included in the sections that follow.
6.1 MPLS-TP MIB Modules 6.1. MPLS-TP MIB Modules
6.1.1 NEW MIB Modules for MPLS-TP 6.1.1. New MIB Modules for MPLS-TP
Four new MIB modules are identified as follows: Four new MIB modules are identified as follows:
- Textual Conventions for MPLS-TP - Textual Conventions for MPLS-TP
- Identifiers for MPLS-TP - Identifiers for MPLS-TP
- LSR MIB Extensions for MPLS-TP - LSR MIB Extensions for MPLS-TP
- TE MIB Extensions for MPLS-TP - Tunnel Extensions for MPLS-TP
Note that the MIB modules mentioned here are applicable for MPLS Note that the MIB modules mentioned here are applicable for MPLS
operations as well. operations as well.
6.1.2 Textual Conventions for MPLS-TP 6.1.2. Textual Conventions for MPLS-TP
A new MIB module needs to be written that will define textual A new MIB module needs to be written that will define Textual
conventions [RFC2579] for MPLS-TP related MIB modules. These Conventions [RFC2579] for MPLS-TP-related MIB modules. These
conventions allow multiple MIB modules to use the same syntax and conventions allow multiple MIB modules to use the same syntax and
format for a concept that is shared between the MIB modules. format to provide a concept that is shared between the MIB modules.
For example, MEP identifier is used to identify maintenance entity For example, a Maintenance Entity Group End Point (MEP) identifier is
group end point within MPLS-TP networks. The textual convention used to identify a maintenance entity group end point within MPLS-TP
representing the MEP identifier should be defined in a new textual networks. The Textual Convention representing the MEP identifier
convention MIB module. should be defined in a new Textual Convention MIB module.
All new extensions related to MPLS-TP are defined in the MIB module All new extensions related to MPLS-TP are defined in the MIB module
and will be referenced by other MIB modules to support MPLS-TP. and will be referenced by other MIB modules to support MPLS-TP.
6.1.3 Identifiers for MPLS-TP 6.1.3. Identifiers for MPLS-TP
New Identifiers describe managed objects that are used to model New identifiers describe managed objects that are used to model
common MPLS-TP identifiers [RFC6370]. common MPLS-TP identifiers [RFC6370].
6.1.4 LSR MIB Extensions for MPLS-TP 6.1.4. LSR MIB Extensions for MPLS-TP
MPLS-LSR-STD-MIB describes managed objects for modeling an MPLS Label The MPLS-LSR-STD-MIB describes managed objects for modeling an MPLS
Switching Router (LSR). This puts it at the heart of the management LSR. This puts it at the heart of the management architecture for
architecture for MPLS. MPLS.
In the case of MPLS-TP, the MPLS-LSR-STD-MIB is extended to support In the case of MPLS-TP, the MPLS-LSR-STD-MIB is extended to support
the MPLS-TP LSP's, which are co-routed or associated bidirectional. MPLS-TP LSPs, which are co-routed or associated bidirectionally.
This extended MIB is also applicable for modeling MPLS-TP tunnels. This extended MIB is also applicable for modeling MPLS-TP tunnels.
6.1.5 Tunnel Extensions for MPLS-TP 6.1.5. Tunnel Extensions for MPLS-TP
MPLS-TE-STD-MIB describes managed objects that are used to model and The MPLS-TE-STD-MIB describes managed objects that are used to model
manage MPLS Traffic Engineered (TE) Tunnels. and manage MPLS-TE tunnels.
MPLS-TP tunnels are very similar to MPLS-TE tunnels, but are MPLS-TP tunnels are very similar to MPLS-TE tunnels but are co-routed
co-routed or associated bidirectionally. or associated bidirectionally.
The MPLS-TE-STD-MIB must be extended to support the MPLS-TP specific The MPLS-TE-STD-MIB must be extended to support the MPLS-TP-specific
attributes for the tunnel. attributes for the tunnel.
6.2 PWE3 MIB Modules for MPLS-TP 6.2. PWE3 MIB Modules for MPLS-TP
This section provides an overview of Pseudowire extension MIB This section provides an overview of pseudowire-extension MIB modules
modules to meet the MPLS based transport network requirements. used to meet MPLS-based transport network requirements.
6.2.1 New MIB Modules for MPLS-TP Pseudowires 6.2.1. New MIB Modules for MPLS-TP Pseudowires
Three new MIB modules are identified as follows: Three new MIB modules are identified as follows:
- Pseudowire Extensions for MPLS-TP - Pseudowire Textual Conventions for MPLS-TP
- Pseudowire MPLS Extensions for MPLS-TP - Pseudowire Extensions for MPLS-TP
- Pseudowire Textual Conventions for MPLS-TP - Pseudowire MPLS Extensions for MPLS-TP
6.2.2 Pseudowire Textual Conventions for MPLS-TP 6.2.2. Pseudowire Textual Conventions for MPLS-TP
PW-TC-STD-MIB MIB defines textual conventions used for pseudowire The PW-TC-STD-MIB defines Textual Conventions used for PW technology
(PW) technology and for Pseudowire Edge-to-Edge Emulation (PWE3) MIB and for PWE3 MIB modules. A new Textual Convention MIB module is
Modules. A new textual convention MIB module is required to define required to define textual definitions for MPLS-TP-specific
textual definitions for MPLS-TP specific Pseudowire attributes. pseudowire attributes.
6.2.3 Pseudowire Extensions for MPLS-TP 6.2.3. Pseudowire Extensions for MPLS-TP
PW-STD-MIB describes managed objects for modeling of Pseudowire The PW-STD-MIB describes managed objects for the modeling of
Edge-to-Edge services carried over a general Packet Switched Network. pseudowire edge-to-edge services carried over a general PSN. This
This MIB module is extended to support MPLS-TP specific attributes MIB module is extended to support MPLS-TP-specific attributes related
related to Pseudowires. to pseudowires.
6.2.4 Pseudowire MPLS Extensions for MPLS-TP 6.2.4. Pseudowire MPLS Extensions for MPLS-TP
PW-MPLS-STD-MIB defines the managed objects for Pseudowire The PW-MPLS-STD-MIB defines the managed objects for pseudowire
operations over MPLS LSR's. This MIB supports both, operations over MPLS LSRs. This MIB module supports
manual and dynamically signaled PW's, point-to-point connections,
enables the use of any emulated service, MPLS-TE as outer tunnel
and no outer tunnel as MPLS-TE.
The newly extended MIB defines the managed objects, extending - manually and dynamically signaled PWs
PW-MPLS-STD-MIB, by supporting with or without MPLS-TP as outer
tunnel.
6.3 OAM MIB Modules for MPLS-TP - point-to-point connections
This section provides an overview of Operations, Administration, - the use of any emulated service
and Maintenance (OAM) MIB modules for MPLS LSPs and Pseudowires.
6.3.1 New MIB Modules for OAM for MPLS-TP - outer tunnels provisioned using MPLS-TE
- PWs with no outer tunnel
An extended MIB module would define additional objects, extending the
PW-MPLS-STD-MIB by continuing to support configurations that operate
with or without an outer tunnel.
6.3. OAM MIB Modules for MPLS-TP
This section provides an overview of Operations, Administration, and
Maintenance (OAM) MIB modules for MPLS LSPs and pseudowires.
6.3.1. New MIB Modules for OAM for MPLS-TP
Two new MIB modules are identified as follows: Two new MIB modules are identified as follows:
- BFD MIB module - BFD MIB module
- OAM MIB module - OAM MIB module
6.3.2 BFD MIB module 6.3.2. BFD MIB Module
BFD-STD-MIB defines managed objects for performing BFD operation in The BFD-STD-MIB defines managed objects for performing BFD operations
IP networks. This MIB is modeled to support BFD protocol [RFC5880]. in IP networks. This MIB module is modeled to support the BFD
protocol [RFC5880].
A new MIB module needs to be written that will be an extension to A new MIB module needs to be written that will be an extension to
BFD-STD-MIB managed objects to support BFD operations on MPLS LSPs BFD-STD-MIB managed objects to support BFD operations on MPLS LSPs
and PWs. and PWs.
6.3.3 Common OAM MIB modules 6.3.3. OAM MIB Module
A new MIB module needs to be written that will define managed objects A new MIB module needs to be written that will define managed objects
for OAM maintenance identifiers i.e. Maintenance Entity Group for OAM maintenance identifiers, i.e., Maintenance Entity Group (MEG)
Identifiers (MEG), Maintenance Entity Group End-point (MEP), identifiers, the MEP, and the Maintenance Entity Group Intermediate
Maintenance Entity Group Intermediate Point (MIP). Maintenance points Point (MIP). Maintenance points are uniquely associated with a MEG.
are uniquely associated with a MEG. Within the context of a MEG, MEPs Within the context of a MEG, MEPs and MIPs must be uniquely
and MIPs must be uniquely identified. identified.
6.4. Protection Switching and Recovery MIB Modules for MPLS-TP 6.4. Protection Switching and Recovery MIB Modules for MPLS-TP
This section provides an overview of protection switching and This section provides an overview of protection switching and
recovery MIB modules for MPLS LSPs and Pseudowires. recovery MIB modules for MPLS LSPs and pseudowires.
6.4.1 New MIB Modules for MPLS Protection Switching and Recovery 6.4.1. New MIB Modules for MPLS Protection Switching and Recovery
Three new MIB modules are identified as follows: Three new MIB modules are identified as follows:
- Linear Protection Switching MIB module - Linear Protection Switching MIB module
- Ring Protection Switching MIB module - Ring Protection Switching MIB module
- Mesh Protection Switching MIB module - Mesh Protection Switching MIB module
6.4.2 Linear Protection Switching MIB module 6.4.2. Linear Protection Switching MIB Module
A new MIB module needs to be written that will define managed objects A new MIB module needs to be written that will define managed objects
for linear protection switching of MPLS LSPs and Pseudowires. for linear protection switching of MPLS LSPs and pseudowires.
6.4.3 Ring Protection Switching MIB module 6.4.3. Ring Protection Switching MIB Module
A new MIB module will define managed objects for ring protection A new MIB module needs to be written that will define managed objects
switching of MPLS LSPs and Pseudowires. for ring protection switching of MPLS LSPs and pseudowires.
6.4.4 Mesh Protection Switching MIB module 6.4.4. Mesh Protection Switching MIB Module
A new MIB module needs to be written that will define managed objects A new MIB module needs to be written that will define managed objects
for Mesh protection switching of MPLS LSPs and Pseudowires. for mesh protection switching of MPLS LSPs and pseudowires.
7. Management Options 7. Management Options
This document applies only to scenarios where MIB modules are used to This document applies only to scenarios where MIB modules are used to
manage the MPLS-TP network. It is not the intention of this document manage the MPLS-TP network. It is not the intention of this document
to provide instructions or advice to implementers of management to provide instructions or advice to implementers of management
systems, management agents, or managed entities. It is, however, systems, management agents, or managed entities. It is, however,
useful to make some observations about how the MIB modules described useful to make some observations about how the MIB modules described
above might be used to manage MPLS systems, if SNMP is used in the above might be used to manage MPLS systems, if SNMP is used in the
management interface. management interface.
For MPLS specific management options, refer to [RFC4221] Section 12. For MPLS-specific management options, refer to [RFC4221] Section 12
(Management Options). ("Management Options").
8. Security Considerations 8. Security Considerations
This document describes the interrelationships amongst the different This document describes the interrelationships amongst the different
MIB modules relevant to MPLS-TP management and as such does not have MIB modules relevant to MPLS-TP management and as such does not have
any security implications in and of itself. any security implications in and of itself.
Each IETF MIB document that specifies MIB objects for MPLS-TP must Each IETF MIB document that specifies MIB objects for MPLS-TP must
provide a proper security considerations section that explains the provide a proper Security Considerations section that explains the
security aspects of those objects. security aspects of those objects.
The attention of readers is particularly drawn to the security The attention of readers is particularly drawn to the security
implications of making MIB objects available for create or write implications of making MIB objects available for create or write
access through an access protocol such as SNMP. SNMPv1 by itself is access through an access protocol such as SNMP. SNMPv1 by itself is
an insecure environment. Even if the network itself is made secure an insecure environment. Even if the network itself is made secure
(for example, by using IPSec), there is no control over who on the (for example, by using IPsec), there is no control over who on the
secure network is allowed to access the objects in this MIB. It is secure network is allowed to access the objects in the MIB module.
recommended that the implementers consider the security features as It is recommended that the implementers consider the security
provided by the SNMPv3 framework. Specifically, the use of the features as provided by the SNMPv3 framework. Specifically, the use
User-based Security Model STD 62, RFC3414 [RFC3414], and the of the User-based Security Model STD 62, RFC 3414 [RFC3414], and the
View-based Access Control Model STD 62, RFC 3415 [RFC3415], View-based Access Control Model STD 62, RFC 3415 [RFC3415], is
is recommended. recommended.
It is then a customer/user responsibility to ensure that the SNMP It is then a customer/user responsibility to ensure that the SNMP
entity giving access to an instance of each MIB module is properly entity giving access to an instance of each MIB module is properly
configured to give access to only those objects, and to those configured to give access to only those objects, and to those
principals (users) that have legitimate rights to access them. principals (users) that have legitimate rights to access them.
9. IANA Considerations 9. IANA Considerations
This document has identified areas where additional MIB modules are This document has identified areas where additional MIB modules are
neccessary for MPLS-TP. The new MIB modules recommended by this necessary for MPLS-TP. The new MIB modules recommended by this
document will require OID assignments from IANA. However, this document will require OID assignments from IANA. However, this
document makes no specific request for IANA action. document makes no specific request for IANA action.
10. Acknowledgements 10. Acknowledgements
The authors would like to thank Eric Gray, Thomas Nadeau, Benjamin The authors would like to thank Eric Gray, Thomas Nadeau, Benjamin
Niven-Jenkins, Saravanan Narasimhan, Joel Halpern, David Harrington, Niven-Jenkins, Saravanan Narasimhan, Joel Halpern, David Harrington,
and Stephen Farrell for their valuable comments. and Stephen Farrell for their valuable comments.
This document also benefited from review by participants in ITU-T This document also benefited from review by participants in ITU-T
Study Group 15. Study Group 15.
11. References 11. Contributors' Addresses
11.1 Normative References Adrian Farrel
Old Dog Consulting
UK
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group EMail: adrian@olddog.co.uk
MIB using SMIv2", RFC 2863, June 2000.
[RFC3811] Nadeau, T. and J. Cucchiara, "Definition of Textual Scott Mansfield
Conventions and for Multiprotocol Label Switching (MPLS) Ericsson
Management", RFC 3811, June 2004. 300 Holger Way
San Jose, CA 95134
US
[RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau, Phone: +1 724 931 9316
"Multiprotocol Label Switching (MPLS) Traffic EMail: scott.mansfield@ericsson.com
Engineering (TE) Management Information Base (MIB)",
RFC 3812, June 2004.
[RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau, Jeong-dong Ryoo
"Multiprotocol Label Switching (MPLS) Label Switching ETRI
(LSR) Router Management Information Base (MIB)", RFC 3813, 161 Gajeong, Yuseong
June 2004. Daejeon, 305-700
South Korea
[RFC3814] Nadeau, T., Srinivasan, C., and A. Viswanathan, Phone: +82 42 860 5384
"Multiprotocol Label Switching (MPLS) FEC-To-NHLFE EMail: ryoo@etri.re.kr
(FTN) Management Information Base", RFC3814, June
2004.
[RFC3815] Cucchiara, J., Sjostrand, H., and Luciani, J., A S Kiran Koushik
"Definitions of Managed Objects for the Cisco Systems Inc.
Multiprotocol Label Switching (MPLS), Label
Distribution Protocol (LDP)", RFC 3815, June 2004.
[RFC4220] Dubuc, M., Nadeau, T., and J. Lang, "Traffic EMail: kkoushik@cisco.com
Engineering Link Management Information Base", RFC
4220, November 2005.
[RFC4221] Nadeau, T., Srinivasan, C., and A. Farrel, A. Karmakar
"Multiprotocol Label Switching (MPLS) Management Cisco Systems Inc.
Overview", RFC 4221, November 2005.
[RFC4801] T. Nadeau and A. Farrel, Ed., "Definitions of Textual EMail: akarmaka@cisco.com
Conventions for Generalized Multiprotocol Label Switching
(GMPLS) Management", RFC4801, Feb. 2007.
[RFC4802] T. D. Nadeau and A. Farrel, "Generalized Multiprotocol Sam Aldrin
Label Switching (GMPLS) Traffic Engineering Management Huawei Technologies Co.
Information Base", RFC4802, Feb., 2007. 2330 Central Expressway
Santa Clara, CA 95051
USA
[RFC4803] T. D. Nadeau and A. Farrel, "Generalized Multiprotocol EMail: aldrin.ietf@gmail.com
Label Switching (GMPLS) Label Switching Router (LSR)
Management Information Base", RFC4803, Feb., 2007.
[RFC5542] Nadeau, T., Ed., Zelig, D., Ed., and O. Nicklass, Ed., 12. References
"Definitions of Textual Conventions for Pseudowire (PW)
Management", RFC 5542, May 2009.
[RFC5601] Nadeau, T., Ed. and D. Zelig, Ed. "Pseudowire (PW) 12.1. Normative References
Management Information Base (MIB)", RFC 5601, July 2009.
[RFC5602] Zelig, D., Ed., and T. Nadeau, Ed., "Pseudowire (PW) over [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
MPLS PSN Management Information Base (MIB)", RFC 5602, MIB", RFC 2863, June 2000.
July 2009.
[RFC5603] Zelig, D., Ed., and T. Nadeau, Ed., "Ethernet Pseudowire [RFC3811] Nadeau, T., Ed., and J. Cucchiara, Ed., "Definitions of
(PW) Management Information Base (MIB)", RFC 5603, Textual Conventions (TCs) for Multiprotocol Label
July 2009. Switching (MPLS) Management", RFC 3811, June 2004.
[RFC5604] Nicklass, O., "Managed Objects for Time Division [RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau,
Multiplexing (TDM) over Packet Switched Networks (PSNs)", "Multiprotocol Label Switching (MPLS) Traffic Engineering
RFC5604, July 2009. (TE) Management Information Base (MIB)", RFC 3812,
June 2004.
11.2 Informative References [RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau,
"Multiprotocol Label Switching (MPLS) Label Switching
Router (LSR) Management Information Base (MIB)",
RFC 3813, June 2004.
[RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder, [RFC3814] Nadeau, T., Srinivasan, C., and A. Viswanathan,
"Structure of Management Information Version 2 "Multiprotocol Label Switching (MPLS) Forwarding
(SMIv2)", STD 58, RFC 2578, April 1999. Equivalence Class To Next Hop Label Forwarding Entry
(FEC-To-NHLFE) Management Information Base (MIB)",
RFC 3814, June 2004.
[RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder, [RFC3815] Cucchiara, J., Sjostrand, H., and J. Luciani,
"Textual Conventions for SMIv2", STD 58, RFC 2579, "Definitions of Managed Objects for the Multiprotocol
April 1999. Label Switching (MPLS), Label Distribution Protocol
(LDP)", RFC 3815, June 2004.
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, [RFC4220] Dubuc, M., Nadeau, T., and J. Lang, "Traffic Engineering
"Conformance Statements for SMIv2", STD 58, RFC 2580, Link Management Information Base", RFC 4220,
April 1999. November 2005.
[RFC3031] Rosen, E., Viswanathan, A., and R. Callon, [RFC4221] Nadeau, T., Srinivasan, C., and A. Farrel, "Multiprotocol
"Multiprotocol Label Switching Architecture", RFC 3031, Label Switching (MPLS) Management Overview", RFC 4221,
March 2001. November 2005.
[RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, [RFC4801] Nadeau, T., Ed., and A. Farrel, Ed., "Definitions of
"Introduction and Applicability Statements for Textual Conventions for Generalized Multiprotocol Label
Internet-Standard Management Framework", RFC 3410, Switching (GMPLS) Management", RFC 4801, February 2007.
December 2002.
[RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security [RFC4802] Nadeau, T., Ed., and A. Farrel, Ed., "Generalized
Model (USM) for version 3 of the Simple Network Multiprotocol Label Switching (GMPLS) Traffic Engineering
Management Protocol (SNMPv3)", STD 62, RFC 3414, Management Information Base", RFC 4802, February 2007.
December 2002.
[RFC3415] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based [RFC4803] Nadeau, T., Ed., and A. Farrel, Ed., "Generalized
Access Control Model (VACM) for the Simple Network Multiprotocol Label Switching (GMPLS) Label Switching
Management Protocol (SNMP)", STD 62, RFC 3415, December Router (LSR) Management Information Base", RFC 4803,
2002. February 2007.
[RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau, [RFC5542] Nadeau, T., Ed., Zelig, D., Ed., and O. Nicklass, Ed.,
"Multiprotocol Label Switching (MPLS) Traffic Engineering "Definitions of Textual Conventions for Pseudowire (PW)
(TE) Management Information Base (MIB)", RFC 3812, June Management", RFC 5542, May 2009.
2004.
[RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau, [RFC5601] Nadeau, T., Ed., and D. Zelig, Ed., "Pseudowire (PW)
"Multiprotocol Label Switching (MPLS) Label Switching Management Information Base (MIB)", RFC 5601, July 2009.
Router (LSR) Management Information Base (MIB)", RFC 3813,
June 2004.
[RFC3931] Lau, J., Townsley, M., and I. Goyret, "Layer Two Tunneling [RFC5602] Zelig, D., Ed., and T. Nadeau, Ed., "Pseudowire (PW) over
Protocol - Version 3 (L2TPv3)", RFC 3931, March 2005. MPLS PSN Management Information Base (MIB)", RFC 5602,
July 2009.
[RFC3945] Mannie, E. et.al., "Generalized Multi-Protocol Label [RFC5603] Zelig, D., Ed., and T. Nadeau, Ed., "Ethernet Pseudowire
Switching (GMPLS) Architecture", IETF RFC 3945, October (PW) Management Information Base (MIB)", RFC 5603,
2004. July 2009.
[RFC3985] Bryant, S. and P. Pate, "Pseudo Wire Emulation Edge-to- [RFC5604] Nicklass, O., "Managed Objects for Time Division
Edge (PWE3) Architecture", RFC 3985, March 2005. Multiplexing (TDM) over Packet Switched Networks (PSNs)",
RFC 5604, July 2009.
[RFC4197] Riegel, M., "Requirements for Edge-to-Edge Emulation of 12.2. Informative References
Time Division Multiplexed (TDM) Circuits over Packet
Switching Networks", RFC4197, October 2005.
[RFC4377] Nadeau, T., Morrow, M., Swallow, G., Allan, D., and S. [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Matsushima, "Operations and Management (OAM) Requirements Schoenwaelder, Ed., "Structure of Management Information
for Multi-Protocol Label Switched (MPLS) Networks", Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
RFC 4377, March 2006.
[RFC4378] Allan, D. and T. Nadeau, "A Framework for Multi-Protocol [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Label Switching (MPLS) Operations and Management (OAM)", Schoenwaelder, Ed., "Textual Conventions for SMIv2",
RFC 4378, March 2006. STD 58, RFC 2579, April 1999.
[RFC4379] Kompella, K. and G. Swallow, "Detecting Multi-Protocol [RFC2580] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Label Switched (MPLS) Data Plane Failures", RFC 4379, Schoenwaelder, Ed., "Conformance Statements for SMIv2",
March 2006. STD 58, RFC 2580, April 1999.
[RFC4447] Martini, L., Rosen, E., El-Aawar, N., Smith, T., and [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol
G. Heron, "Pseudowire Setup and Maintenance Using the Label Switching Architecture", RFC 3031, January 2001.
Label Distribution Protocol (LDP)", RFC 4447,
April 2006.
[RFC4805] Nicklass, O., Ed., "Definitions of Managed Objects for the [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
DS1, J1, E1, DS2, and E2 Interface Types", RFC 4805, March "Introduction and Applicability Statements for Internet-
2007. Standard Management Framework", RFC 3410, December 2002.
[RFC5085] Nadeau, T. and C. Pignataro, "Pseudowire Virtual [RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model
Circuit Connectivity Verification (VCCV): A Control (USM) for version 3 of the Simple Network Management
Channel for Pseudowires", RFC 5085, December 2007. Protocol (SNMPv3)", STD 62, RFC 3414, December 2002.
[RFC5601] Nadeau, T., Ed. and D. Zelig, Ed. "Pseudowire (PW) [RFC3415] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based
Management Information Base (MIB)", RFC 5601, July 2009. Access Control Model (VACM) for the Simple Network
Management Protocol (SNMP)", STD 62, RFC 3415,
December 2002.
[RFC5602] Zelig, D., Ed., and T. Nadeau, Ed., "Pseudowire (PW) over [RFC3931] Lau, J., Ed., Townsley, M., Ed., and I. Goyret, Ed.,
MPLS PSN Management Information Base (MIB)", RFC 5602, "Layer Two Tunneling Protocol - Version 3 (L2TPv3)",
July 2009. RFC 3931, March 2005.
[RFC5654] Niven-Jenkins, B., et al, "MPLS-TP Requirements", [RFC3945] Mannie, E., Ed., "Generalized Multi-Protocol Label
RFC5654, September 2009. Switching (GMPLS) Architecture", RFC 3945, October 2004.
[RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding [RFC3985] Bryant, S., Ed., and P. Pate, Ed., "Pseudo Wire Emulation
Detection", RFC 5880, June 2010. Edge-to-Edge (PWE3) Architecture", RFC 3985, March 2005.
[RFC5884] Aggarwal, R., Kompella, K., Nadeau, T., and G. Swallow, [RFC4197] Riegel, M., Ed., "Requirements for Edge-to-Edge Emulation
"Bidirectional Forwarding Detection (BFD) For MPLS of Time Division Multiplexed (TDM) Circuits over Packet
Label Switched Paths (LSPs)", RFC 5884, June 2010. Switching Networks", RFC 4197, October 2005.
[RFC5885] Nadeau, T. and C. Pignataro, "Bidirectional [RFC4377] Nadeau, T., Morrow, M., Swallow, G., Allan, D., and S.
Forwarding Detection (BFD) for the Pseudowire Matsushima, "Operations and Management (OAM) Requirements
Virtual Circuit Connectivity Verification (VCCV)", for Multi-Protocol Label Switched (MPLS) Networks",
RFC5885, June 2010. RFC 4377, February 2006.
[RFC5950] Gray, E., Mansfield, S., Lam, K., [RFC4378] Allan, D., Ed., and T. Nadeau, Ed., "A Framework for
"MPLS-TP Network Management Framework", RFC 5950, Multi-Protocol Label Switching (MPLS) Operations and
September 2010. Management (OAM)", RFC 4378, February 2006.
[RFC5951] Gray, E., Mansfield, S., Lam, K., "MPLS TP [RFC4379] Kompella, K. and G. Swallow, "Detecting Multi-Protocol
Network Management Requirements", RFC 5951, September Label Switched (MPLS) Data Plane Failures", RFC 4379,
2010. February 2006.
[RFC6370] Bocci, M., Swallow, G., and E. Gray, "MPLS Transport [RFC4447] Martini, L., Ed., Rosen, E., El-Aawar, N., Smith, T., and
Profile (MPLS-TP) Identifiers", RFC 6370, September 2011. G. Heron, "Pseudowire Setup and Maintenance Using the
Label Distribution Protocol (LDP)", RFC 4447, April 2006.
[MPLS-TP-OAM-FWK] Busi, I. and B. Niven-Jenkins, "MPLS-TP OAM [RFC5085] Nadeau, T., Ed., and C. Pignataro, Ed., "Pseudowire
Framework and Overview", 2009, Virtual Circuit Connectivity Verification (VCCV): A
<draft-ietf-mpls-tp-oam-framework>. Control Channel for Pseudowires", RFC 5085,
December 2007.
12. Authors' Addresses [RFC5654] Niven-Jenkins, B., Ed., Brungard, D., Ed., Betts, M.,
Ed., Sprecher, N., and S. Ueno, "Requirements of an MPLS
Transport Profile", RFC 5654, September 2009.
Daniel King [RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding Detection
Old Dog Consulting (BFD)", RFC 5880, June 2010.
UK
Email: daniel@olddog.co.uk
Venkatesan Mahalingam [RFC5884] Aggarwal, R., Kompella, K., Nadeau, T., and G. Swallow,
Aricent "Bidirectional Forwarding Detection (BFD) for MPLS Label
India Switched Paths (LSPs)", RFC 5884, June 2010.
Email: venkat.mahalingams@gmail.com
Adrian Farrel [RFC5885] Nadeau, T., Ed., and C. Pignataro, Ed., "Bidirectional
Old Dog Consulting Forwarding Detection (BFD) for the Pseudowire Virtual
UK Circuit Connectivity Verification (VCCV)", RFC 5885,
Email: adrian@olddog.co.uk June 2010.
Scott Mansfield [RFC5950] Mansfield, S., Ed., Gray, E., Ed., and K. Lam, Ed.,
Ericsson "Network Management Framework for MPLS-based Transport
300 Holger Way, San Jose, CA 95134, US Networks", RFC 5950, September 2010.
Phone: +1 724 931 9316
Email: scott.mansfield@ericsson.com
Jeong-dong Ryoo [RFC5951] Lam, K., Mansfield, S., and E. Gray, "Network Management
ETRI Requirements for MPLS-based Transport Networks",
161 Gajeong, Yuseong, Daejeon, 305-700, South Korea RFC 5951, September 2010.
Phone: +82 42 860 5384
Email: ryoo@etri.re.kr
A S Kiran Koushik [RFC6370] Bocci, M., Swallow, G., and E. Gray, "MPLS Transport
Cisco Systems Inc. Profile (MPLS-TP) Identifiers", RFC 6370, September 2011.
Email: kkoushik@cisco.com
A. Karmakar [RFC6371] Busi, I., Ed., and D. Allan, Ed., "Operations,
Cisco Systems Inc. Administration, and Maintenance Framework for MPLS-Based
Email: akarmaka@cisco.com Transport Networks", RFC 6371, September 2011.
Sam Aldrin [RFC6445] Nadeau, T., Ed., Koushik, A., Ed., and R. Cetin, Ed.,
Huawei Technologies, co. "Multiprotocol Label Switching (MPLS) Traffic Engineering
2330 Central Express Way, Management Information Base for Fast Reroute", RFC 6445,
Santa Clara, CA 95051, USA November 2011.
Email: aldrin.ietf@gmail.com
Authors' Addresses
Daniel King (editor)
Old Dog Consulting
UK
EMail: daniel@olddog.co.uk
Venkatesan Mahalingam (editor)
Aricent
India
EMail: venkat.mahalingams@gmail.com
 End of changes. 281 change blocks. 
729 lines changed or deleted 735 lines changed or added

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