draft-ietf-mpls-tp-mib-management-overview-03.txt   draft-ietf-mpls-tp-mib-management-overview-04.txt 
Network Working Group D. King (Editor) Network Working Group D. King (Editor)
Internet-Draft Old Dog Consulting Internet-Draft Old Dog Consulting
Intended status: Informational M. Venkatesan (Editor) Intended status: Informational M. Venkatesan (Editor)
Expires: August 14, 2011 Aricent Expires: November 12, 2011 Aricent
March 14, 2011 June 12, 2011
Multiprotocol Label Switching Transport Profile (MPLS-TP) Multiprotocol Label Switching Transport Profile (MPLS-TP)
MIB-based Management Overview MIB-based Management Overview
draft-ietf-mpls-tp-mib-management-overview-03.txt draft-ietf-mpls-tp-mib-management-overview-04.txt
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 management architecture for This document describes the MIB-based architecture for MPLS-TP,
MPLS-TP, indicates the interrelationships between different and indicates the interrelationships between different existing MIB
existing MIB modules that can be leveraged for MPLS-TP network modules that can be leveraged for MPLS-TP network management and
management and identifies areas where additional MIB modules would be identifies areas where additional MIB modules would be required.
required.
This document is a product of a joint Internet Engineering Task Force
(IETF) / International Telecommunication Union Telecommunication
Standardization Sector (ITU-T) effort to include an MPLS Transport
Profile within the IETF MPLS and PWE3 architectures to support the
capabilities and functionalities of a packet transport network as
defined by the ITU-T.
This Informational Internet-Draft is aimed at achieving IETF
Consensus before publication as an RFC and will be subject to an IETF
Last Call.
[RFC Editor, please remove this note before publication as an RFC and
insert the correct Streams Boilerplate to indicate that the published
RFC has IETF Consensus.]
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 2, line 26 skipping to change at page 1, line 50
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on August 14, 2011. This Internet-Draft will expire on June 12, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction.................................................4 1. Introduction.................................................3
1.1 MPLS-TP Management Function.................................4
2. Terminology..................................................4 2. Terminology..................................................4
3. The SNMP Management Framework................................4 3. The SNMP Management Framework................................4
4. Summary of MPLS-TP Management Function.......................5 4. Overview of Existing Work....................................5
5. Overview of Existing Work....................................5 4.1. MPLS Management Overview and Requirements...............5
5.1. MPLS Management Overview and Requirements...............5 4.2. An Introduction to the MPLS and Pseudowire MIB Modules..5
5.2. An Introduction to the MPLS and Pseudowire MIB Modules..6 4.2.1. Structure of the MPLS MIB OID Tree...............5
5.2.1. Structure of the MPLS MIB OID Tree...............6 4.2.2. Textual Convention Modules.......................6
5.2.2. Textual Convention Modules.......................7 4.2.3. Label Edge Router (LER) Modules..................7
5.2.3. Mapping Data to LSPs.............................7 4.2.4. Label Switching Router Modules...................7
5.2.4. Label Switching Router Modules...................8 4.2.5. Label Switched Path Modules......................7
5.2.5. Label Switched Path Modules......................8 4.2.6. Pseudowire Modules...............................8
5.2.6. Pseudowire Modules...............................8 4.2.7. Routing and Traffic Engineering..................9
5.2.7. Routing and Traffic Engineering..................10 4.2.8. Resiliency.......................................9
5.2.8. Resiliency.......................................10 4.2.9. Fault Management and Performance Management......10
5.2.9. Fault Management and Performance Management......11 4.2.10. MIB Module Interdependencies....................11
5.2.10. MIB Module Interdependencies....................12 4.2.11. Dependencies on External MIB Modules............13
5.2.11. Dependencies on External MIB Modules............14 5. Applicability of MPLS MIB modules to MPLS-TP.................14
6. Applicability of MPLS MIB modules to MPLS-TP.................14 5.1 MPLS-TP Tunnel...........................................14
6.1 Gap Analysis............................................15 5.1.1 Gap Analysis.......................................14
6.1.1 MPLS-TP Tunnel....................................15 5.1.2 Recommendations....................................15
6.1.2 MPLS-TP Pseudowire................................15 5.2 MPLS-TP Pseudowire.......................................15
6.1.3 MPLS-TP Sections..................................15 5.2.1 Gap Analysis.......................................15
6.1.4 MPLS-TP OAM.......................................15 5.2.2 Recommendations....................................15
6.1.5 MPLS-TP Protection Switching......................16 5.3 MPLS-TP Sections.........................................15
7. Interfaces...................................................16 5.3.1 Gap Analysis.......................................15
7.1. MPLS Tunnels as Interfaces..............................17 5.3.2 Recommendations....................................15
7.2. Application of the Interfaces Group to TE Links.........17 5.4 MPLS-TP OAM..............................................16
7.3. References to Interface Objects from MPLS MIB Modules...17 5.4.1 Gap Analysis.......................................16
8. New MIB Modules Required for MPLS-TP.........................18 5.4.2 Recommendations....................................16
8.1 MPLS Extension MIB Modules...............................19
8.1.1 The MPLS Extension MIB OID Tree...................19
8.1.2 MPLS-TC-EXT-STD-MIB...............................19
8.1.3 MPLS-LSR-EXT-STD-MIB..............................19
8.1.4 MPLS-TE-EXT-STD-MIB...............................20
8.2 PWE3 Extension MIB Modules...............................20
8.2.1 Structure of the PWE3 Extension MIB OID Tree......20
8.2.2 PW-TC-EXT-STD-MIB.................................20
8.2.3 PW-EXT-STD-MIB....................................21
8.2.4 PW-MPLS-EXT-STD-MIB...............................21
8.3 OAM MIB Modules..........................................21
8.3.1 Structure of the OAM Extension MIB OID Tree.......21
8.3.2 MPLS-LSPPING-STD-MIB..............................21
8.3.3 MPLS-BFD-STD-MIB..................................22
8.3.4 MPLS-OAM-STD-MIB..................................22
8.4. Protection Switching MIB Modules........................22 5.5 MPLS-TP Protection Switching and Recovery................16
8.4.1 Structure of the MPLS Extension MIB OID Tree......22 5.5.1 Gap Analysis.......................................16
8.4.2 MPLS-LPS-STD-MIB..................................22 5.5.2 Recommendations....................................16
8.4.3 MPLS-RPS-STD-MIB..................................23 5.6 MPLS-TP Interfaces.......................................16
8.4.4 MPLS-MPS-STD-MIB..................................23 5.6.1 Gap Analysis.......................................16
9. Management Options...........................................23 5.6.2 Recommendations....................................17
10. Security Considerations.....................................23 6. An Introduction to the MPLS-TP MIB Modules...................17
11. IANA Considerations.........................................24 6.1 MPLS-TP MIB Modules......................................17
12. Acknowledgements............................................24 6.1.1 Structure of the MPLS-TP MIB OID Tree.............17
13. References..................................................24 6.1.2 Textual Conventions for MPLS-TP...................18
13.1. Normative References...................................24 6.1.3 Identifiers for MPLS-TP...........................18
13.2. Informational References...............................25 6.1.4 LSR MIB Extensions for MPLS-TP....................18
14. Authors' Addresses..........................................27 6.1.5 Tunnel Extensions for MPLS-TP.....................18
6.2 PWE3 MIB Modules for MPLS-TP.............................18
6.2.1 Structure of the PWE3 MIB OID Tree for MPLS-TP....19
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 Structure of the OAM MIB OID Tree for MPLS-TP.....19
6.3.2 LSP Ping MIB module...............................20
6.3.3 BFD MIB module....................................20
6.3.4 Common OAM MIB modules............................20
6.4. Protection Switching and Recovery MIB Modules
for MPLS-TP.............................................20
6.4.1 Structure of the Protection Switching
and Recovery MIB OID Tree for MPLS-TP.............21
6.4.2 Linear Protection Switching MIB module............21
6.4.3 Ring Protection Switching MIB module..............21
6.4.4 Mesh Protection Switching MIB module..............21
7. Management Options...........................................21
8. Security Considerations......................................21
9. IANA Considerations..........................................22
10. Acknowledgements............................................22
11. References..................................................22
11.1. Normative References...................................22
11.2. Informational References...............................24
12. Authors' Addresses..........................................26
1. Introduction 1. Introduction
The MPLS Transport Profile (MPLS-TP) is a packet transport The MPLS Transport Profile (MPLS-TP) is a packet transport
technology based on a profile of the MPLS functionality specific technology based on a profile of the MPLS functionality specific
to the construction of packet-switched transport networks. to the construction of packet-switched transport networks.
MPLS is described in [RFC3031] and requirements for MPLS-TP are MPLS is described in [RFC3031] and requirements for MPLS-TP are
specified in [RFC5654]. specified in [RFC5654].
A range of Management Information Base (MIB) modules has been A range of Management Information Base (MIB) modules has been
skipping to change at page 4, line 40 skipping to change at page 4, line 18
are defined in separate documents that focus on the specific areas of are 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.
An MPLS-TP network can be operated via static provisioning of An MPLS-TP network can be operated via static provisioning of
transport paths, or the elective use of a Generalized MPLS (GMPLS) transport paths, or the elective use of a Generalized MPLS (GMPLS)
control plane to support dynamic provisioning of transport paths. control plane to support dynamic provisioning of transport paths.
This document describes the MIB-based management architecture for This document describes the MIB-based management architecture for
MPLS-TP and indicates the interrelationships between different MPLS-TP and indicates the interrelationships between different
existing MIB modules that should be leveraged for MPLS-TP network existing MIB modules that should be leveraged for MPLS-TP network
management and identifies areas where additional MIB modules would be management, if SNMP is used for the management interface and
required. identifies areas where additional MIB modules would be required. Note
that [RFC5951] does not specify a preferred management interface
protocol to be used as the standard protocol for managing MPLS-TP
networks.
This document is a product of a joint Internet Engineering Task Force 1.1 MPLS-TP Management Function
(IETF) / International Telecommunication Union Telecommunication
Standardization Sector (ITU-T) effort to include an MPLS Transport The management of the MPLS-TP networks is inseparable from that of
Profile within the IETF MPLS and PWE3 architectures to support the its client networks so that the same means of management can be used
capabilities and functionalities of a packet transport network. regardless of the client. The management functions of MPLS-TP
includes fault management, configuration management, performance
monitoring, and security management.
The purpose of the management function is to provide control and
monitoring over the protocol mechanisms and procedures that
constitute the building blocks for a transport profile of MPLS.
The requirements for the network management functionality are
found in [RFC5951]. A description of the network and element
management architectures that can be applied to the 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] and the following MPLS related MIB modules: document [RFC3031] and the following MPLS related MIB modules:
MPLS TC MIB [RFC3811], MPLS LSR MIB [RFC3813], MPLS TE MIB [RFC3812], MPLS TC MIB [RFC3811], MPLS LSR MIB [RFC3813], MPLS TE MIB [RFC3812],
MPLS LDP MIB [RFC3815], MPLS FTN MIB [RFC3814] and TE LINK MIB MPLS LDP MIB [RFC3815], MPLS FTN MIB [RFC3814] and TE LINK MIB
[RFC4220]. [RFC4220].
3. The SNMP Management Framework 3. The SNMP Management Framework
skipping to change at page 5, line 28 skipping to change at page 5, line 12
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
RFC 3410 [RFC3410]. RFC 3410 [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. Summary of MPLS-TP Management Function 4. Overview of Existing Work
The management of the MPLS-TP networks is separable from that of its
client networks so that the same means of management can be used
regardless of the client. The management functions of MPLS-TP
includes fault management, configuration management, performance
monitoring, and security management.
5. Overview of Existing Work
This section describes the existing tools and techniques for This section describes the existing tools and techniques for
managing and modeling MPLS networks, devices, and protocols. It does managing and modeling MPLS networks, devices, and protocols. It is
not focus on MPLS-TP, but is intended to provide a description of the intended to provide a description of the tool kit that is already
tool kit that is already available. available.
The following section (Section 6. Applicability of MPLS MIB modules Section 5 of this document outlines the applicability of existing
to MPLS-TP) of this document outlines the existing MPLS MIB modules MPLS MIB modules to MPLS-TP, describes the optional use of GMPLS MIB
and optional use of GMPLS MIB modules to MPLS-TP and examines the modules in MPLS-TP networks, and examines the additional MIB modules
additional MIB modules and objects that would be required for and objects that would be required for managing an MPLS-TP network.
managing an MPLS-TP network.
5.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 and Management (OAM) requirements outlined in
[RFC4377] and how it is applied to the management functions of fault, [RFC4377] and how it is applied to the management functions of fault,
configuration, accounting, performance, and security (commonly known configuration, accounting, performance, and security (commonly known
as FCAPS) for MPLS networks. 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].
5.2. An Introduction to the MPLS and Pseudowire MIB Modules 4.2. An Introduction to the MPLS and Pseudowire MIB Modules
5.2.1. Structure of the MPLS MIB OID Tree 4.2.1. Structure of the MPLS MIB OID Tree
The MPLS MIB OID tree has the following structure compatible for
MPLS-TP. The MPLS MIB OID tree has the following structure. It is based on the
tree originally set out in section 4.1 of [RFC4221] and has been
enhanced to include other relevant MIB 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]
| | | | | |
| | +- mplsLsrStdMIB -- MPLS-LSR-STD-MIB [RFC3813] | | +- mplsLsrStdMIB -- MPLS-LSR-STD-MIB [RFC3813]
| | | | | |
| | +- mplsTeStdMIB -- MPLS-TE-STD-MIB [RFC3812] | | +- mplsTeStdMIB -- MPLS-TE-STD-MIB [RFC3812]
| | | | | |
| | +- mplsLdpStdMIB -- MPLS-LDP-STD-MIB [RFC3815] | | +- mplsLdpStdMIB -- MPLS-LDP-STD-MIB [RFC3815]
| | | | | |
| | +- mplsLdpGenericStdMIB -- MPLS-LDP-GENERIC-STD-MIB | | +- mplsLdpGenericStdMIB
| | | -- MPLS-LDP-GENERIC-STD-MIB [RFC3815]
| | | | | |
| | +- mplsFTNStdMIB -- MPLS-FTN-STD-MIB [RFC3814] | | +- mplsFTNStdMIB -- MPLS-FTN-STD-MIB [RFC3814]
| | | | | |
| | +- gmplsTCStdMIB -- GMPLS-TC-STD-MIB [RFC4801] | | +- gmplsTCStdMIB -- GMPLS-TC-STD-MIB [RFC4801]
| | | | | |
| | +- gmplsTeStdMIB -- GMPLS-TE-STD-MIB [RFC4802] | | +- gmplsTeStdMIB -- GMPLS-TE-STD-MIB [RFC4802]
| | | | | |
| | +- gmplsLsrStdMIB -- GMPLS-LSR-STD-MIB [RFC4803] | | +- gmplsLsrStdMIB -- GMPLS-LSR-STD-MIB [RFC4803]
| | | | | |
| | +- gmplsLabelStdMIB -- GMPLS-LABEL-STD-MIB [RFC4803] | | +- gmplsLabelStdMIB -- GMPLS-LABEL-STD-MIB [RFC4803]
skipping to change at page 8, line 5 skipping to change at page 6, line 51
| |
+- 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.
5.2.2. Textual Convention Modules 4.2.2. Textual Convention Modules
MPLS-TC-STD-MIB [RFC3811], GMPLS-TC-STD-MIB [RFC4801],
MPLS-TC-STD-MIB [RFC3811] and GMPLS-TC-STD-MIB [RFC4801] contains the IANA-GMPLS-TC-MIB [RFC4802] and PW-TC-STD-MIB [RFC5542] contains 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 which manage MPLS
and GMPLS networks. and GMPLS networks. Section 3.2.11. highlights dependencies on
additional external MIB modules
5.2.3. Mapping Data to LSPs
MPLS is a packet switching protocol that operates between the
Network layer and the data link layer in the OSI model.
There is a clean separation between the control and forwarding
planes in the MPLS protocol. This helps in easy portability and
extensibility to the forwarding functions.
A router which performs MPLS forwarding is known as a "Label
Switching Router. An LSR implements the control and forwarding
plane of MPLS.
The LSR "control plane" provides information in terms of label
bindings which are part of the information used to populate
forwarding tables in an LSR. An LSR determines which label bindings
to seek and retain based on configuration and other information.
The LSR forwarding plane then uses an index which is the incoming
interface and label (usually of 20-bit length) to forward the
packet.
Each entry in this forwarding table corresponds to a forwarding
equivalence class (FEC). This can be loosely defined as the set of
characteristics that are being shared by the packets which will be
forwarded in a similar fashion and may share the same label.
MPLS packets are encapsulated by one more label entries referred to
as the label stack. Each label stack entry consists of a label, the
3 TC-bits for classifying the Traffic Class, the bottom of stack bit,
and TTL.
The ingress and the egress devices of the MPLS network are called
Label Edge Routers (LER). At the LER a label is pushed onto an
incoming packet and popped to remove it.
At the ingress when an unlabeled packet enters, one or more label
stack entries are (each label stack with one or more labels) is
prefixed to this packet based on its FEC as discussed above. In
addition, the "MPLS-specific" L2 encapsulation (including, for 4.2.3. Label Edge Router (LER) Modules
instance, the MPLS PID) is also added at the ingress. Then the packet
is sent to the next-hop router for further processing. The next-hop
router examines the topmost label in the label stack and then does a
swap, 'push' or 'pop' operations based on the contents.
A label stack entry can be 'popped' or removed from the top of the Label Edge Router (LER) Module helps in mapping data to LSP's
label stack or a label stack entry is 'pushed' or inserted into the based on the network layer header. The ingress device of the MPLS
top of the stack based on the FEC information. network is called Label Edge Routers (LER).
When a 'swap' operation is executed, the topmost label stack entry is At the LER when an unlabelled packet enters the ingress interface,
replaced with a different one and the depth of the label stack network layer header is parsed to classify the packet to a forwarding
remains the same. After the swap the packet is forwarded based on the equivalence class (FEC). Each FEC is mapped to an LFIB entry to
new entry. encapsulate the unlabelled packet with one or more label entries
referred to as the label stack. Each label stack entry consists of a
label, the 3 TC-bits for classifying the Traffic Class, the bottom of
stack bit, and TTL.
MPLS-FTN-STD-MIB [RFC3814] describes the managed objects for mapping MPLS-FTN-STD-MIB [RFC3814] describes the managed objects for mapping
FEC's to label bindings. FEC's to label bindings.
5.2.4. Label Switching Router Modules 4.2.4. Label Switching Router Modules
A router which performs MPLS forwarding is known as an LSR. An LSR
receives a labelled packet and performs forwarding action based on
the label received.
LSR maintains a mapping of an incoming label and incoming interface
to one or more outgoing label and outgoing interfaces in its
forwarding database. When a labelled packet is received, LSR examines
the topmost label in the label stack and then does 'swap', 'push' or
'pop' operation based on the contents.
MPLS-LSR-STD-MIB [RFC3813] describes the managed objects for modeling MPLS-LSR-STD-MIB [RFC3813] describes the managed objects for modeling
a Multiprotocol Label Switching (MPLS) [RFC3031] LSR. a Multiprotocol Label Switching (MPLS) [RFC3031] LSR.
MPLS-LSR-STD-MIB [RFC3813] contains the managed objects to maintain
mapping of in-segments to out-segments.
MPLS-TP is specific to the use of MPLS in transport networks. 4.2.5. Label Switched Path Modules
According to [RFC5654] multipoint-to-point LSPs do not form part of
MPLS-TP, so multipoint-to-point cross-connects are out of scope for
this document.
5.2.5. Label Switched Path Modules
The path taken through the MPLS domain by a packet is referred to as The path taken through the MPLS domain by a packet is referred to as
a label switched path (LSP). It is possible that this path may not be a label switched path (LSP). It is possible that this path may not be
understood or completely stored in one LSR within the MPLS domain. understood or completely stored in any one LSR within the MPLS
domain.
MPLS-LSR-STD-MIB [RFC3813] defines the required objects for setting
up an LSP. It defines the conceptual object MPLS cross-connect that
is used to map incoming labels to outgoing labels on a MPLS enabled
interfaces. This is referenced by other MIB modules in order to refer
to an underlying MPLS LSP.
This label switched path can be programmed using a variety of MPLS-LSR-STD-MIB [RFC3813] describes the required objects to define
mechanisms. These include manual programming and using a signalling the LSP.
protocol.
RSVP-TE (Resource reservation protocol for Traffic Engineering) is 4.2.6. Pseudowire Modules
normally used for signalling LSPs used for Traffic Engineering.
5.2.6. Pseudowire Modules The PW (Pseudowire) MIB architecture provides a layered
modular model into which any supported emulated service such as Frame
Relay, ATM, Ethernet, TDM and SONET/SDH can be connected to any
supported packet switched network (PSN) type. This MIB architecture
is modeled based on PW3 architecture [RFC3985].
The PW (Pseudowire) MIB modules architecture provides a layered
modular model into which any supported emulated service can be
connected to any supported packet switched network (PSN) type.
Emulated Service Layer, Generic PW Layer and PSN VC Layer constitute Emulated Service Layer, Generic PW Layer and PSN VC Layer constitute
the different layers of the model. A combination of the MIB modules the different layers of the model. A combination of the MIB modules
belonging to each layer provides the glue for mapping the emulated belonging to each layer provides the glue for mapping the emulated
service onto the native PSN service. At least three MIB modules each service onto the native PSN service. At least three MIB modules each
belonging to a different layer is required to define a PW emulated belonging to a different layer are required to define a PW emulated
service. service.
Starting from the emulated Service Layer, the first is a o Service-Specific module is dependent on the emulated signal type
service-specific module that is dependent on the emulated signal and helps in modeling emulated service layer.
type.
The second is the PW-STD-MIB module, which configures general PW-ENET-STD-MIB [RFC5603] describes a model for managing Ethernet
parameters of the PW that are common to all types of emulated pseudowire services for transmission over a PSN. This MIB module is
services and PSN types. generic and common to all types of PSNs supported in the Pseudowire
Emulation Edge-to-Edge (PWE3) architecture [RFC3985], which describes
the transport and encapsulation of L1 and L2 services over supported
PSN types.
The third is a PSN-specific module. There is a different module for In particular, the MIB module associates a port or specific VLANs on
each type of PSN. These modules associate the PW with one or more top of a physical Ethernet port or a virtual Ethernet interface (for
"tunnels" that carry the service over the PSN. These modules are Virtual Private LAN Service (VPLS)) to a point-to-point PW. It is
defined in other documents. complementary to the PW-STD-MIB [RFC5601], which manages the generic
PW parameters common to all services, including all supported PSN
types.
PW-TC-STD-MIB [RFC5542] contains the textual conventions required PW-TDM-MIB [RFC5604] describes a model for managing TDM pseudowires,
for PW MIB modules. i.e., TDM data encapsulated for transmission over a Packet Switched
Network (PSN). The term TDM in this document is limited to the
scope of Plesiochronous Digital Hierarchy (PDH). It is currently
specified to carry any TDM Signals in either Structure Agnostic
Transport mode (E1, T1, E3, and T3) or in Structure Aware
Transport mode (E1, T1, and NxDS0) as defined in the Pseudowire
Emulation Edge-to-Edge (PWE3) TDM Requirements document [RFC4197].
o Generic PW Module configures general parameters of the PW that are
common to all types of emulated services and PSN types.
PW-STD-MIB [RFC5601] defines a MIB module that can be PW-STD-MIB [RFC5601] defines a MIB module that can be
used to manage pseudowire (PW) services for transmission over a used to manage pseudowire (PW) services for transmission over a
Packet Switched Network (PSN) [RFC3931] [RFC4447]. This MIB module Packet Switched Network (PSN) [RFC3931] [RFC4447]. This MIB module
provides generic management of PWs that is common to all types of provides generic management of PWs that is common to all types of
PSN and PW services defined by the IETF PWE3 Working Group. PSN and PW services defined by the IETF PWE3 Working Group.
o PSN-specific module associate the PW with one or more "tunnels"
that carry the service over the PSN. There is a different module
for each type of PSN.
PW-MPLS-STD-MIB [RFC5602] describes a model for managing pseudowire PW-MPLS-STD-MIB [RFC5602] describes a model for managing pseudowire
services for transmission over different flavors of MPLS tunnels. services for transmission over different flavors of MPLS tunnels.
The general PW MIB module [RFC5601] defines the parameters global to The general PW MIB module [RFC5601] defines the parameters global to
the PW regardless of the underlying Packet Switched Network (PSN) the PW regardless of the underlying Packet Switched Network (PSN)
and emulated service. This document is applicable for PWs that use and emulated service. This document is applicable for PWs that use
MPLS PSN type in the PW-STD-MIB. Additionally this document describes MPLS PSN type in the PW-STD-MIB. Additionally this document describes
the MIB objects that define pseudowire association to the MPLS PSN, the MIB objects that define pseudowire association to the MPLS PSN,
that is not specific to the carried service. that is not specific to the carried service.
Together, [RFC3811], [RFC3812] and [RFC3813] describe the modeling of Together, [RFC3811], [RFC3812] and [RFC3813] describe the modeling of
an MPLS tunnel, and a tunnel's underlying cross-connects. This MIB 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-TE PSN, non-TE MPLS PSN (an outer tunnel created
by the Label Distribution Protocol (LDP) or manually), and MPLS PW by the Label Distribution Protocol (LDP) or manually), and MPLS PW
label only (no outer tunnel). label only (no outer tunnel).
PW-ENET-STD-MIB [RFC5603] describes a model for managing Ethernet 4.2.7. Routing and Traffic Engineering
pseudowire services for transmission over a PSN. This MIB module is
generic and common to all types of PSNs supported in the Pseudowire
Emulation Edge-to-Edge (PWE3) architecture [RFC3985], which describes
the transport and encapsulation of L1 and L2 services over supported
PSN types.
In particular, the MIB module associates a port or specific VLANs on
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
complementary to the PW-STD-MIB [RFC5601], which manages the generic
PW parameters common to all services, including all supported PSN
types.
PW-TDM-MIB [RFC5604] describes a model for managing TDM pseudowires,
i.e., TDM data encapsulated for transmission over a Packet Switched
Network (PSN). The term TDM in this document is limited to the
scope of Plesiochronous Digital Hierarchy (PDH). It is currently
specified to carry any TDM Signals in either Structure Agnostic
Transport mode (E1, T1, E3, and T3) or in Structure Aware
Transport mode (E1, T1, and NxDS0) as defined in the Pseudowire
Emulation Edge-to-Edge (PWE3) TDM Requirements document [RFC4197].
5.2.7. Routing and Traffic Engineering
In MPLS traffic engineering, its 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. some specific data can be routed around network hot spots. TE LSPs
can be setup through a management plane or a control plane.
MPLS-TE-STD-MIB [RFC3812] describes managed objects for modeling a MPLS-TE-STD-MIB [RFC3812] describes managed objects for modeling a
Multiprotocol Label Switching (MPLS) [RFC3031] based traffic Multiprotocol Label Switching (MPLS) [RFC3031] based traffic
engineering. This MIB module should be used in conjunction with the engineering. This MIB module should be used in conjunction with the
companion document [RFC3813] for MPLS based traffic engineering companion document [RFC3813] for MPLS based traffic engineering
configuration and management. configuration and management.
5.2.8. Resiliency 4.2.8. Resiliency
MPLS Fast Reroute is a restoration network resiliency mechanism used An MPLS resiliency is to make sure that there is no interruption to
in MPLS TE to redirect the traffic onto the backup LSP's in 10s of traffic when the failure occurs within the system or network.
milliseconds in case of link or node failure across the LSP. Two
different modes of local protection are described in the [RFC4090] to
protect LSP.
o One-to-One Backup Various components of MPLS resiliency solutions are,
o Facility Backup 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
Facility backup uses label stacking to reroute multiple protected TE The below modules only support the SNMP based mib management
LSPs using a single backup TE LSP. One-to-one backup does not use for MPLS resiliency.
label stacking, and every protected TE LSP requires a dedicated
backup TE LSP. MPLS Fast Reroute is a restoration network resiliency mechanism used
in MPLS TE to redirect the traffic onto the backup LSP's in 10s of
milliseconds in case of link or node failure across the LSP.
MPLS-FRR-GENERAL-STD-MIB [draft-ietf-mpls-fastreroute-mib-14] MPLS-FRR-GENERAL-STD-MIB [draft-ietf-mpls-fastreroute-mib-14]
contains objects that apply to any MPLS LSR implementing MPLS TE fast contains objects that apply to any MPLS LSR implementing MPLS TE fast
reroute functionality. reroute functionality.
MPLS-FRR-ONE2ONE-STD-MIB [draft-ietf-mpls-fastreroute-mib-14] MPLS-FRR-ONE2ONE-STD-MIB [draft-ietf-mpls-fastreroute-mib-14]
contains objects that apply to one-to-one backup method. contains objects that apply to one-to-one backup method.
MPLS-FRR-FACILITY-STD-MIB [draft-ietf-mpls-fastreroute-mib-14] MPLS-FRR-FACILITY-STD-MIB [draft-ietf-mpls-fastreroute-mib-14]
contains objects that apply to facility backup method. contains objects that apply to facility backup method.
5.2.9. Fault Management and Performance Management Protection Switching mechanisms have been designed to provide network
resiliency for MPLS network. Different types of protection switching
mechanisms such as 1:1, 1:N, 1+1 have been designed.
4.2.9. Fault Management and Performance Management
MPLS manages the LSP and pseudowire faults through the use of LSP MPLS manages the LSP and pseudowire faults through the use of LSP
ping [RFC4379], VCCV [RFC5085], BFD for LSPs [RFC5884] and BFD for ping [RFC4379], VCCV [RFC5085], BFD for LSPs [RFC5884] and BFD for
VCCV [RFC5885] tools. VCCV [RFC5885] tools.
Current MPLS focuses on the in and/or out packet counters, Current MPLS focuses on the in and/or out packet counters,
errored packets, discontinuity time. errored packets, discontinuity time.
Some of the MPLS and Pseudowire performance tables used for Some of the MPLS and Pseudowire performance tables used for
performance management are given below. performance management are given below.
skipping to change at page 11, line 97 skipping to change at page 11, line 7
mplsFTNPerfTable contains performance information for the specified mplsFTNPerfTable contains performance information for the specified
interface and an FTN entry mapped to this interface. interface and an FTN entry mapped to this interface.
mplsLdpEntityStatsTable and mplsLdpSessionStatsTable contain mplsLdpEntityStatsTable and mplsLdpSessionStatsTable contain
statistical information (session attempts, errored packets, statistical information (session attempts, errored packets,
notifications) about an LDP entity. notifications) about an LDP entity.
pwPerfCurrentTable, pwPerfIntervalTable, pwPerf1DayIntervalTable pwPerfCurrentTable, pwPerfIntervalTable, pwPerf1DayIntervalTable
provides pseudowire performance information (in and/or out packets) provides pseudowire performance information (in and/or out packets)
based on time (current interval, each interval, 1day interval). based on time (current interval, preconfigured specific interval,
1day interval).
pwEnetStatsTable contains statistical counters specific for Ethernet pwEnetStatsTable contains statistical counters specific for Ethernet
PW. PW.
pwTDMPerfCurrentTable, pwTDMPerfIntervalTable and pwTDMPerfCurrentTable, pwTDMPerfIntervalTable and
pwTDMPerf1DayIntervalTable contain statistical informations pwTDMPerf1DayIntervalTable contain statistical informations
accumulated per 15-minute, 24 hour, 1 day respectively. accumulated per 15-minute, 24 hour, 1 day respectively.
gmplsTunnelErrorTable and gmplsTunnelReversePerfTable provides gmplsTunnelErrorTable and gmplsTunnelReversePerfTable provides
information about performance errored packets and in/out packet information about performance errored packets and in/out packet
counters. counters.
5.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 the MPLS MIB module interdependencies,
this section also highlights the GMPLS and PW MIB modules this section also highlights the GMPLS and PW MIB modules
interdependencies. interdependencies.
The relationship "A --> B" means A depends on B and that MIB module The relationship "A --> B" means A depends on B and that MIB module
skipping to change at page 15, line 22 skipping to change at page 13, line 22
- GMPLS-TE-STD-MIB contains references to objects in - GMPLS-TE-STD-MIB contains references to objects in
IANA-GMPLS-TC-MIB. IANA-GMPLS-TC-MIB.
- GMPLS-LSR-STD-MIB contains references to objects in - GMPLS-LSR-STD-MIB contains references to objects in
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. MPLS-LSR-STD-MIB that is imported by MPLS-LDP-STD-MIB.
5.2.11. Dependencies on External MIB Modules 4.2.11. Dependencies on External MIB Modules
MPLS MIB modules have dependencies with the TE-LINK-STD-MIB With the exception of MPLS-TC-STD-MIB, all the MPLS MIB modules have
dependencies on the Interfaces MIB [RFC2863]. MPLS-FTN-STD-MIB
references IP-capable interfaces on which received traffic is to be
classified using indexes in the Interface Table (ifTable) of IF-MIB
[RFC2863]. The other MPLS MIB modules reference MPLS-capable
interfaces in ifTable.
The Interfaces Group of IF-MIB [RFC2863] defines generic managed
objects for managing interfaces. The MPLS MIB modules contain
media-specific extensions to the Interfaces Group for managing MPLS
interfaces.
The MPLS MIB modules assume the interpretation of the Interfaces
Group to be in accordance with [RFC2863], which states that ifTable
contains information on the managed resource's interfaces and that
each sub-layer below the internetwork layer of a network interface is
considered an interface. Thus, the MPLS interface is represented as
an entry in ifTable.
The interrelation of entries in ifTable is defined by the Interfaces
Stack Group defined in [RFC2863].
The MPLS MIB modules have dependencies with the TE-LINK-STD-MIB
for maintaining the traffic engineering information. for maintaining the traffic engineering information.
MPLS MIB modules depend on the CSPF module to get the paths for MPLS The MPLS MIB modules depend on the constrained shortest path first
tunnel to traverse to reach the end point of the tunnel and BFD (CSPF) module to obtain the path required for an MPLS tunnel to reach
module to verify the data-plane failures of LSPs and PWs. the end point of the tunnel and BFD module to verify the 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.
This is business as usual for a MIB module and is not discussed 5. Applicability of MPLS MIB modules to MPLS-TP
further in this document.
6. Applicability of MPLS MIB modules to MPLS-TP
In addition to the MPLS management overview [RFC4221] This section and its sub sections focus on the possible gaps that
section 4.12 (Dependencies on External MIB Modules), some of the exist in the MPLS MIB modules to extend its use to MPLS-TP networks.
existing MPLS MIBs, PW MIBs and GMPLS MIBs are re-used with
extensions for achieving the MPLS-TP functionality.
[RFC5951] specifies the requirements for the management of [RFC5951] specifies the requirements for the management of
equipment used in networks supporting an MPLS-TP. It also details the equipment used in networks supporting an MPLS-TP. It also details the
essential network management capabilities for operating networks essential network management capabilities for operating networks
consisting of MPLS-TP equipment. consisting of MPLS-TP equipment.
[RFC5950] provides the network management framework for [RFC5950] provides the network management framework for
MPLS-TP. The document explains how network elements and networks that MPLS-TP. The document explains how network elements and networks that
support MPLS-TP can be managed using solutions that satisfy the support MPLS-TP can be managed using solutions that satisfy the
requirements defined in [RFC5951]. The relationship between requirements defined in [RFC5951]. The relationship between
MPLS-TP management and OAM is described in the MPLS-TP framework MPLS-TP management and OAM is described in the MPLS-TP framework
[RFC5950] document. [RFC5950] document.
The MPLS mib modules MPLS-TE-STD-MIB [RFC3812], PW-STD-MIB [RFC5601]
and MPLS-LSR-STD-MIB [RFC3813] and their associated mib 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
Operations, Administration, and Maintenance (OAM) function. MPLS-TP Operations, Administration, and Maintenance (OAM) function. MPLS-TP
OAM is described in [MPLS-TP-OAM-FWK]. OAM is described in [MPLS-TP-OAM-FWK].
[Editors note - A seperate draft will provide an MPLS-TP abstract A seperate draft will provide an MPLS-TP abstract model and use a
model and use a formal language to define the terminology, the formal language to define the terminology, the information that
information that must be retrieved and method for storing. The draft must be retrieved and method for storing.
will also list the new MPLS-TP MIB modules identified in this
document]
6.1 Gap Analysis 5.1 MPLS-TP Tunnel
6.1.1 MPLS-TP Tunnel 5.1.1 Gap Analysis
o An MPLS tunnel may not be compatible for non-IP environments. MPLS-TP tunnel can be operated over IP and/or ICC environments,
i.e., the tunnel ingress and egress identifiers are not always below points capture the gaps in existing MPLS mib modules
identified via an IP address, rather identification is achieved for managing the MPLS-TP networks.
using local numbers to operate in a non-IP environment.
o Next-hop IP address in MPLS XC table is not compatible for non-IP
environment.
o Bidirectional LSPs are not introduced until the GMPLS MIB modules,
tunnel table should be enhanced to provide static and signalling
corouted/associated bidirectional connectivity.
6.1.2 MPLS-TP Pseudowire o IP based environment
i. MPLS-TE-STD-MIB [RFC3812] does not support
tunnel LSR identifier based on Global_ID and Node_ID.
ii. MPLS-TE-STD-MIB [RFC3812] does not support
corouted/associated bidirectional tunnel configurations.
o MPLS pseudowire may not be compatible for non-IP environments. o ICC based environment
i.e., pseudowire source and destination identifiers are not always i. MPLS-TE-STD-MIB [RFC3812] does not support
identified via an IP address, rather identification is achieved tunnel LSR identifier based on ICC.
using local numbers to operate in a non-IP environment. ii. MPLS tunnel does not support forwarding other
o Pseudowire mib modules should be enhanced to operate over than the nexthop IP address.
5.1.2 Recommendations
o New MIB definitions can be created for Global_Node_ID and/or
ICC configurations.
o MPLS-LSR-STD-MIB [RFC3813] mib module can be enhanced to identify
the nexthop based on MAC address for IP-less environment.
o MPLS-TE-STD-MIB [RFC3812] and MPLS-LSR-STD-MIB should be
enhanced to provide static and signalling mib module
extensions for corouted/associated bidirectional LSPs.
5.2 MPLS-TP Pseudowire
5.2.1 Gap Analysis
MPLS-TP Pseudowire can be operated over IP and/or ICC environments,
below points capture the gaps in existing PW mib modules
for managing the MPLS-TP networks.
o 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 opeation over corouted/associated bidirectional tunnels.
o ICC based environment
i. PW-STD-MIB [RFC5601] does not support
PW end point identifier based on ICC.
ii. Pseudowire does not support forwarding other
than the nexthop IP address.
5.2.2 Recommendations
o PW-MPLS-STD-MIB [RFC5602] can be enhanced to operate over
corouted/associated bi-directional tunnel. corouted/associated bi-directional tunnel.
o Pseudowire 129 FEC type-2 should be used in non-IP and IP o Pseudowire 129 FEC type-2 can be used in non-IP and IP
environments with the required changes. environments with the required changes.
6.1.3 MPLS-TP Sections 5.3 MPLS-TP Sections
There is no gap in the existing MPLS MIB modules as this MPLS-TP 5.3.1 Gap Analysis
section will be defined as the new term for MPLS-TP.
6.1.4 MPLS-TP OAM The existing MPLS MIB modules does not support MPLS-TP sections.
5.3.2 Recommendations
Link specific and/or path/segment specific sections can be achieved
by enhancing the IF-MIB [RFC2863], MPLS-TE-STD-MIB [RFC3812] and
PW-STD-MIB [RFC5601] mib modules.
5.4 MPLS-TP OAM
5.4.1 Gap Analysis
MPLS manages the LSP and pseudowire faults through LSP ping MPLS manages the LSP and pseudowire faults through LSP ping
[RFC4379], VCCV [RFC5085], BFD for LSPs [RFC5884] and BFD for VCCV [RFC4379], VCCV [RFC5085], BFD for LSPs [RFC5884] and BFD for VCCV
[RFC5885] tools. [RFC5885] tools.
There is no MIB management model currently available for the above The MPLS mib modules do not support the below MPLS-TP OAM functions,
fault management tools. o Continuity Check and Connectivity Verification
o Remote Defect Indication
o Route Tracing
o Alarm Reporting
o Lock Reporting
o Lock Instruct
o Client Failure Indication
o Packet Loss Measurement
o Packet Delay Measurement
There is no performance management tool currently available for MPLS 5.4.2 Recommendations
except the statistics information.
6.1.5 MPLS-TP Protection Switching New mib modules for BFD and LSP Ping can be created to address
all the gaps mentioned in the 5.4.1 Gap Analysis section.
5.5 MPLS-TP Protection Switching and Recovery
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 described as the substitution of a protection or standby can be described as the substitution of a protection or standby
facility for a working or primary facility. An MPLS-TP protection facility for a working or primary facility.
switching can be managed with the following parameters:
o Topology (linear, ring, mesh)
o Protection architecture (1+1, 1:1, or others as defined in
different topologies)
o Switching type (unidirectional, bidirectional)
o Operation mode (revertive, non-revertive)
o Automatic protection channel
o Protection state
o Position of the switch
o Timer values (hold-off, Wait-to-Restore)
o Failure of protocol
Among the parameters described above for protection switching, it is
the topology itself which has the most significant influence.
Therefore, three MIB modules are to be defined to model and
manage protection switching for each of three different topologies
(linear, ring and mesh) availible.
7. Interfaces
MPLS-TP can be carried over the existing and evolving physical
transport technologies such as SONET/SDH, OTN/WDM, and Ethernet.
The Interfaces Group of IF-MIB [RFC2863] defines generic managed
objects for managing interfaces. The MPLS-TP MIB modules make
references to interfaces so that it can be clearly determined where
the procedures managed by the MIB modules should be performed.
Additionally, the MPLS-TP MIB modules (notably MPLS-TE-STD-MIB and
TE-LINK-STD-MIB, PW-STD-MIB) utilize interface stacking within the
Interface Group.
Please refer to section 4. (Node and Interface Identifiers) in
[MPLS-TP-IDENTIFIERS] for more information on MPLS-TP specific
interfaces.
7.1. MPLS Tunnels as Interfaces
An extension to mplsTunnelTable should address the tunnel The MPLS mib modules do not provide support for protection switching
requirements specific to MPLS-TP. and recovery of three different topologies (linear, ring and mesh)
available.
MPLS Tunnel logical interfaces can be stacked over 5.5.2 Recommendations
PDH/SDH/OTH/Ethernet physical interfaces. For more information on
Tunnel interfaces, refer section 11.1 (MPLS Tunnels as Interfaces) of
RFC-4221.
7.2. Application of the Interfaces Group to TE Links New mib modules can be created to address all the gaps mentioned
in the 5.5.1 Gap Analysis section.
TE links can be formed over PDH/SDH/OTH/Ethernet physical interfaces. 5.6 MPLS-TP Interfaces
For more information on TE links, Refer section 11.2. Application of
the Interfaces Group to TE Links of RFC-4221.
7.3. References to Interface Objects from MPLS MIB Modules 5.6.1 Gap Analysis
As per [MPLS-TP-IDENTIFIERS], 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.
MPLSTP-STD-MIB includes the extensions of Tunnel table, PW table The MPLS mib modules do not provide support for configuring
for MPLS-TP. the interfaces within the context of an operator.
More information on Tunnel interfaces can be found in the RFC-3812, 5.6.2 Recommendations
section 8. (Application of the Interface Group to MPLS Tunnels)
The PW in general is not an ifIndex on its own, for agent New mib defintions can be created to address the gaps mentioned
scalability reasons. The PW is typically associated via in the 5.6.1 Gap Analysis section.
the PWE3 MIB modules to an ifIndex (physical entity) the PW is
emulating. Some implementations may manage the PW as an ifIndex in the
ifTable. A special ifType to represent a PW virtual interface (246)
will be used in the ifTable in this case. More information on PW
interfaces can be found in the RFC-5601, section 8 (PW relations to
the IF-MIB).
8. New MIB Modules Required for MPLS-TP 6. An Introduction to the MPLS-TP MIB Modules
This section highlights the new MIB modules that have been identified This section highlights new MIB modules that have been identified
in Section 6.1 (Gap Analysis) and are required for MPLS-TP. This as being required for MPLS-TP. This section also provides an overview
section also provides an overview of the following: of the following:
- the MPLS Object Identifier (OID) tree structure and the position - the MPLS Object Identifier (OID) tree structure and the position
of different MPLS related MIB modules on this tree; of different MPLS related MIB modules on this tree;
- the purpose of each of the MIB modules within the MIB documents, - the purpose of each of the MIB modules within the MIB documents,
what it can be used for, and how it relates to the other MIB what it can be used for, and how it relates to the other MIB
modules. modules.
Note that each new MIB document should contain one or more compliance Note that each new MIB module (apart from Textual Conventions
statements for the modules and objects that it defines. Therefore, modules) will contain one or more Compliance Statements to indicate
the support for the different MIB modules and objects is beyond the which objects must be suppor in what manner to claim a specific level
scope of this document, although some recommendations are included in of compliance. Additional text, either in the documents that define
the sections that follow. the MIB modules or in separate Applicability Statements, will define
which Compliance Statements need tbe conformed to in order to provide
specific MPLS-TP function. This document does not set any
requirements in that respect although some recommendations are
included in the sections that follow.
8.1 MPLS Extension MIB Modules 6.1 MPLS-TP MIB Modules
8.1.1 The MPLS Extension MIB OID Tree 6.1.1 Structure of the MPLS-TP MIB OID Tree
The MPLS Extension MIB OID tree has the following structure. The MPLS-TP MIB OID tree has the following structure.
transmission -- RFC 2578 [RFC2578] transmission -- RFC 2578 [RFC2578]
| |
+- mplsStdMIB +- mplsStdMIB
| |
+- mplsTCExtStdMIB -- MPLS-TC-EXT-STD-MIB +- Textual Conventions for MPLS-TP
| |
+- mplsLsrExrStdMIB -- MPLS-LSR-EXT-STD-MIB +- Identifiers for MPLS-TP
| |
+- mplsTeExtStdMIB -- MPLS-TE-EXT-STD-MIB +- LSR MIB Extensions for MPLS-TP
|
+- TE MIB Extensions for MPLS-TP
Note that the mib modules mentioned here are applicable
for MPLS operations as well.
Note: The OIDs for MIB modules are yet to be assigned and managed by Note: The OIDs for MIB modules are yet to be assigned and managed by
IANA. IANA.
8.1.2 MPLS-TC-EXT-STD-MIB 6.1.2 Textual Conventions for MPLS-TP
MPLS-TC-STD-MIB defines textual conventions [RFC2579] that may be New textual convention mib module defines textual
common to MPLS-related MIB modules. These conventions allow multiple conventions [RFC2579] for MPLS-TP related MIB modules.
MIB modules to use the same syntax and format for a concept that is These conventions allow multiple MIB modules to use the
shared between the MIB modules. This MIB is extended to support new same syntax and format for a concept that is shared between
textual definitions supporting MPLS-TP networks. the MIB modules.
For example, MEP identifier is used to identify maintainence end For example, MEP identifier is used to identify maintenance entity
point within MPLS-TP networks. The textual convention representing group end point within MPLS-TP networks. The textual convention
the MEP identifier is defined in MPLS-TC-EXT-STD-MIB, representing the MEP identifier is defined in new textual convention
which is an extension to MPLS-TC-STD-MIB mib module.
All new extensions related to MPLS-TP are defined in this 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.
8.1.3 MPLS-LSR-EXT-STD-MIB 6.1.3 Identifiers for MPLS-TP
New Identifiers describe managed objects that are used to model
common MPLS-TP identifiers [MPLS-TP-IDENTIFIERS].
6.1.4 LSR MIB Extensions for MPLS-TP
MPLS-LSR-STD-MIB describes managed objects for modeling an MPLS Label MPLS-LSR-STD-MIB describes managed objects for modeling an MPLS Label
Switching Router (LSR). This puts it at the heart of the management Switching Router (LSR). This puts it at the heart of the management
architecture for MPLS. architecture for MPLS.
MPLS-LSR-STD-MIB MIB module is used to model and manage the basic
label switching behavior of an MPLS LSR. It represents the label
forwarding information base (LFIB) of the LSR and provides a view of
the LSPs that are being switched by the LSR in question.
Since basic MPLS label switching is common to all MPLS applications,
this MIB module is referenced by many of the other MPLS MIB modules.
In general, MPLS-LSR-STD-MIB provides a model of incoming labels on
MPLS-enabled interfaces being mapped to outgoing labels on MPLS-
enabled interfaces via a conceptual object called an MPLS cross-
connect. MPLS cross-connect entries and their properties are
represented in MPLS-LSR-STD-MIB and are typically referenced by
other MIB modules in order to refer to the underlying MPLS LSP.
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 bidirectional and co-routed or the MPLS-TP LSP's, which are corouted or associated bidirectional.
associated. This extended MIB, MPLS-LSR-EXT-STD-MIB all models of This extended MIB is also applicable for modeling MPLS-TP tunnels.
MPLS-TP tunnels.
8.1.4 MPLS-TE-EXT-STD-MIB 6.1.5 Tunnel Extensions for MPLS-TP
MPLS-TE-STD-MIB describes managed objects that are used to model and MPLS-TE-STD-MIB describes managed objects that are used to model and
manage MPLS Traffic Engineered (TE) Tunnels. manage MPLS Traffic Engineered (TE) Tunnels.
This MIB module is based on a table that represents TE tunnels that
either originate from, traverse via, or terminate on the LSR in
question. The MIB module provides configuration and statistics
objects needed for TE tunnels.
MPLS-TP tunnels are much similar to MPLS-TE tunnels, but are MPLS-TP tunnels are much similar to MPLS-TE tunnels, but are
bidirectional and could be associated or co-routed. The bidirectional and could be co-routed or associated.
MPLS-TE-EXT-STD-MIB contains the extensions to support the MPLS-TP The MPLS-TE-STD-MIB is extended to support the MPLS-TP specific
specific attributed for the tunnel. attributes for the tunnel.
8.2 PWE3 Extension MIB Modules
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 to meet the MPLS based transport network requirements. modules to meet the MPLS based transport network requirements.
8.2.1 Structure of the PWE3 Extension MIB OID Tree 6.2.1 Structure of the PWE3 MIB OID Tree for MPLS-TP
mib-2 -- RFC 2578 [RFC2578] mib-2 -- RFC 2578 [RFC2578]
| |
+-transmission +-transmission
| | | |
| +- pwExtStdMIB -- PW-EXT-STD-MIB | +- Pseudowire Extensions for MPLS-TP
| |
+- pwMplsExtStdMIB -- PW-MPLS-EXT-STD-MIB +- Pseudowire MPLS Extensions for MPLS-TP
| |
+- pwTcExtStdMIB -- PW-TC-EXT-STD-MIB +- Pseudowire Textual Conventions for MPLS-TP
Note: The OIDs for MIB modules are yet to be assigned and managed by Note: The OIDs for MIB modules are yet to be assigned and managed by
IANA. IANA.
8.2.2 PW-TC-EXT-STD-MIB 6.2.2 Pseudowire Textual Conventions for MPLS-TP
PW-TC-STD-MIB MIB defines textual conventions used for pseudowire PW-TC-STD-MIB MIB defines textual conventions used for pseudowire
(PW) technology and for Pseudowire Edge-to-Edge Emulation (PWE3) MIB (PW) technology and for Pseudowire Edge-to-Edge Emulation (PWE3) MIB
Modules. PW-TC-EXT-STD-MIB add extensions to PW-TC-STD-MIB to support Modules. New textual convention mib module defines textual
textual definitions for MPLS-TP specific Pseudowire attributes. definitions for MPLS-TP specific Pseudowire attributes.
8.2.3 PW-EXT-STD-MIB 6.2.3 Pseudowire Extensions for MPLS-TP
PW-STD-MIB describes managed objects for modeling of Pseudowire PW-STD-MIB describes managed objects for modeling of Pseudowire
Edge-to-Edge services carried over a general Packet Switched Network. Edge-to-Edge services carried over a general Packet Switched Network.
This MIB module is extended as PW-EXT-STD-MIB to support This MIB module is extended to support MPLS-TP specific attributes
MPLS-TP specific attributes related to Pseudowires. related to Pseudowires.
8.2.4 PW-MPLS-EXT-STD-MIB 6.2.4 Pseudowire MPLS Extensions for MPLS-TP
PW-MPLS-STD-MIB defines the managed objects for Pseudowire PW-MPLS-STD-MIB defines the managed objects for Pseudowire
operations over MPLS LSR's. This MIB supports both, operations over MPLS LSR's. This MIB supports both,
manual and dynamically signaled PW's, point-to-point connections, manual and dynamically signaled PW's, point-to-point connections,
enables the use of any emulated service, MPLS-TE as outer tunnel enables the use of any emulated service, MPLS-TE as outer tunnel
and no outer tunnel as MPLS-TE. and no outer tunnel as MPLS-TE.
The newly extended MIB, PW-MPLS-EXT-STD-MIB defines the managed The newly extended MIB defines the managed objects,
objects, extending PW-MPLS-STD-MIB, by supporting with or without extending PW-MPLS-STD-MIB, by supporting with or without
MPLS-TP as outer tunnel. MPLS-TP as outer tunnel.
8.3 OAM MIB Modules 6.3 OAM MIB Modules for MPLS-TP
This section provides an overview of Operations, Administration, This section provides an overview of Operations, Administration,
and Maintenance (OAM) mib modules for MPLS LSPs and Pseudowires. and Maintenance (OAM) mib modules for MPLS LSPs and Pseudowires.
8.3.1 Structure of the OAM Extension MIB OID Tree 6.3.1 Structure of the OAM MIB OID Tree for MPLS-TP
mib-2 -- RFC 2578 [RFC2578] mib-2 -- RFC 2578 [RFC2578]
| |
+-transmission +-transmission
| |
+- mplsLspPingStdMIB -- MPLS-LSPPING-STD-MIB +- LSP Ping MIB module
| |
+- mplsBfdStdMIB -- MPLS-BFD-STD-MIB +- BFD MIB module
| |
+- mplsOamStdMIB -- MPLS-OAM-STD-MIB +- OAM MIB module
Note: The OIDs for MIB modules are yet to be assigned and managed by Note: The OIDs for MIB modules are yet to be assigned and managed by
IANA. IANA.
8.3.2 MPLS-LSPPING-STD-MIB 6.3.2 LSP Ping MIB module
LSP ping is defined in RFC4379 to validate data plane consistency of LSP ping is defined in [RFC4379] to validate data plane consistency
MPLS LSP's. It defines how LSP ping and Trace could be performed of MPLS LSP's. It defines how LSP ping and Trace Route could be
across MPLS networks to identify and diagnose faults within MPLS performed across MPLS networks to identify and diagnose faults
networks. This OAM functionality is performed on demand basis for within MPLS networks. This OAM functionality is performed on demand
verification purposes. basis for verification purposes.
MPLS-LSPPING-STD-MIB defines managed objects for modeling LSP ping New mib module defines managed objects for modeling LSP ping
protocol. It allows user to perform on demand operations based on protocol. It allows user to perform on demand operations based on
RFC4379. The managed objects to support LSP ping for MPLS-TP is [RFC4379].
based on draft-ietf-mpls-tp-lsp-ping-bfd-procedures-01.
For example, a MPLS-TP tunnel LSP is to be pinged, a SNMP request For example, a MPLS-TP tunnel LSP is to be pinged, a SNMP request
issued using the MIB for the tunnel in test. The results for the issued using the MIB for the tunnel in test. The results for the
operation could be queried using the managed objects defined in the operation could be queried using the managed objects defined in the
MIB module. MIB module.
8.3.3 MPLS-BFD-STD-MIB 6.3.3 BFD MIB module
BFD-STD-MIB defines managed objects for performing BFD operation in BFD-STD-MIB defines managed objects for performing BFD operation in
IP networks. This MIB is modeled to support BFD protocol RFC5880. IP networks. This MIB is modeled to support BFD protocol [RFC5880].
MPLS-BFD-STD-MIB is an extension to BFD-STD-MIB managed objects New mib module is an extension to BFD-STD-MIB managed objects
to support BFD operations on MPLS LSP's. The new MPLS-TP managed to support BFD operations on MPLS LSPs and PWs.
objects for BFD are based on
draft-ietf-mpls-tp-lsp-ping-bfd-procedures-01.
8.3.4 MPLS-OAM-STD-MIB 6.3.4 Common OAM MIB modules
MPLS-OAM-STD-MIB defined managed objects for OAM maintenance New mib module defines managed objects for OAM maintenance
identifiers i.e. Maintenance Entity Group Identifiers (MEG), identifiers i.e. Maintenance Entity Group Identifiers (MEG),
Maintenance Entity Group End-point (MEP), Maintenance Entity Group Maintenance Entity Group End-point (MEP), Maintenance Entity Group
Intermediate Point (MIP). Maintenance points are uniquely Intermediate Point (MIP). Maintenance points are uniquely
associated with a MEG. Within the context of a MEG, MEPs and MIPs associated with a MEG. Within the context of a MEG, MEPs and MIPs
must be uniquely identified. must be uniquely identified.
8.4. Protection Switching MIB Modules 6.4. Protection Switching and Recovery MIB Modules for MPLS-TP
This section provides an overview of protection switching mib modules This section provides an overview of protection switching and
for MPLS LSPs and Pseudowires. recovery MIB modules for MPLS LSPs and Pseudowires.
8.4.1 Structure of the MPLS Protection Switching MIB OID Tree 6.4.1 Structure of the MPLS Protection Switching and Recovery MIB OID
Tree for MPLS-TP
mib-2 -- RFC 2578 [RFC2578] mib-2 -- RFC 2578 [RFC2578]
| |
+-transmission +-transmission
| |
+- mplsLpsStdMIB -- MPLS-LPS-STD-MIB +- Linear Protection Switching MIB module
| |
+- mplsRpsStdMIB -- MPLS-RPS-STD-MIB +- Ring Protection Switching MIB module
| |
+- mplsMpsStdMIB -- MPLS-MPS-STD-MIB +- Mesh Protection Swithcing MIB module
Note: The OIDs for MIB modules are yet to be assigned and managed by Note: The OIDs for MIB modules are yet to be assigned and managed by
IANA. IANA.
8.4.2 MPLS-LPS-STD-MIB 6.4.2 Linear Protection Switching MIB module
MPLS-LPS-STD-MIB defined managed objects for linear protection
New mib module defines managed objects for linear protection
switching of MPLS LSPs and Pseudowires. switching of MPLS LSPs and Pseudowires.
8.4.3 MPLS-RPS-STD-MIB 6.4.3 Ring Protection Switching MIB module
MPLS-RPS-STD-MIB defined managed objects for ring protection New mib module defines managed objects for ring protection
switching of MPLS LSPs and Pseudowires. switching of MPLS LSPs and Pseudowires.
8.4.4 MPLS-MPS-STD-MIB 6.4.4 Mesh Protection Switching MIB module
MPLS-MPS-STD-MIB defined managed objects for Mesh protection New mib module defines managed objects for Mesh protection
switching of MPLS LSPs and Pseudowires. switching of MPLS LSPs and Pseudowires.
9. Management Options 7. Management Options
It is not the intention of this document to provide instructions or This document applies only to scenarios where MIB modules are used to
advice to implementers of management systems, management agents, or manage the MPLS-TP network. It is not the intention of this document
managed entities. It is, however, useful to make some observations to provide instructions or advice to implementers of management
about how the MIB modules described above might be used to manage systems, management agents, or managed entities. It is, however,
MPLS systems. 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
management interface.
For MPLS specific management options, refer [RFC4221] Section 12 For MPLS specific management options, refer [RFC4221] Section 12
(Management Options). (Management Options).
[Editors Note: MPLS-TP specific management gaps and options will be 8. Security Considerations
documented in this document and will be referenced here.]
10. 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
skipping to change at page 24, line 10 skipping to change at page 22, line 29
provided by the SNMPv3 framework. Specifically, the use of the provided by the SNMPv3 framework. Specifically, the use of the
User-based Security Model STD 62, RFC3414 [RFC3414], and the User-based Security Model STD 62, RFC3414 [RFC3414], and the
View-based Access Control Model STD 62, RFC 3415 [RFC3415], View-based Access Control Model STD 62, RFC 3415 [RFC3415],
is recommended. is 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.
11. IANA Considerations 9. IANA Considerations
This document makes no requests for IANA action. This document makes no requests for IANA action.
12. 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, Sam Aldrin and Saravanan Narasimhan for their Niven-Jenkins and Saravanan Narasimhan for their valuable comments.
valuable comments.
13. References This document benefited from review by participants in ITU-T Study
Group 15.
13.1 Normative References 11. References
11.1 Normative References
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
MIB using SMIv2", RFC 2863, June 2000. MIB using SMIv2", RFC 2863, June 2000.
[RFC3811] Nadeau, T. and J. Cucchiara, "Definition of Textual [RFC3811] Nadeau, T. and J. Cucchiara, "Definition of Textual
Conventions and for Multiprotocol Label Switching (MPLS) Conventions and for Multiprotocol Label Switching (MPLS)
Management", RFC 3811, June 2004. Management", RFC 3811, June 2004.
[RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau, [RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau,
"Multiprotocol Label Switching (MPLS) Traffic "Multiprotocol Label Switching (MPLS) Traffic
skipping to change at page 25, line 44 skipping to change at page 24, line 13
July 2009. July 2009.
[RFC5603] Zelig, D., Ed., and T. Nadeau, Ed., "Ethernet Pseudowire [RFC5603] Zelig, D., Ed., and T. Nadeau, Ed., "Ethernet Pseudowire
(PW) Management Information Base (MIB)", RFC 5603, (PW) Management Information Base (MIB)", RFC 5603,
July 2009. July 2009.
[RFC5604] Nicklass, O., "Managed Objects for Time Division [RFC5604] Nicklass, O., "Managed Objects for Time Division
Multiplexing (TDM) over Packet Switched Networks (PSNs)", Multiplexing (TDM) over Packet Switched Networks (PSNs)",
RFC5604, July 2009. RFC5604, July 2009.
13.2 Informative References 11.2 Informative References
[RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder, [RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Structure of Management Information Version 2 "Structure of Management Information Version 2
(SMIv2)", STD 58, RFC 2578, April 1999. (SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder, [RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Textual Conventions for SMIv2", STD 58, RFC 2579, "Textual Conventions for SMIv2", STD 58, RFC 2579,
April 1999. April 1999.
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
skipping to change at page 26, line 28 skipping to change at page 24, line 46
[RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security [RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security
Model (USM) for version 3 of the Simple Network Model (USM) for version 3 of the Simple Network
Management Protocol (SNMPv3)", STD 62, RFC 3414, Management Protocol (SNMPv3)", STD 62, RFC 3414,
December 2002. December 2002.
[RFC3415] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based [RFC3415] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based
Access Control Model (VACM) for the Simple Network Access Control Model (VACM) for the Simple Network
Management Protocol (SNMP)", STD 62, RFC 3415, December Management Protocol (SNMP)", STD 62, RFC 3415, December
2002. 2002.
[RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau,
"Multiprotocol Label Switching (MPLS) Traffic Engineering
(TE) Management Information Base (MIB)", RFC 3812, June
2004.
[RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau,
"Multiprotocol Label Switching (MPLS) Label Switching
Router (LSR) Management Information Base (MIB)", RFC 3813,
June 2004.
[RFC3931] Lau, J., Townsley, M., and I. Goyret, "Layer Two Tunneling [RFC3931] Lau, J., Townsley, M., and I. Goyret, "Layer Two Tunneling
Protocol - Version 3 (L2TPv3)", RFC 3931, March 2005. Protocol - Version 3 (L2TPv3)", RFC 3931, March 2005.
[RFC3945] Mannie, E. et.al., "Generalized Multi-Protocol Label [RFC3945] Mannie, E. et.al., "Generalized Multi-Protocol Label
Switching (GMPLS) Architecture", IETF RFC 3945, October Switching (GMPLS) Architecture", IETF RFC 3945, October
2004. 2004.
[RFC3985] Bryant, S. and P. Pate, "Pseudo Wire Emulation Edge-to- [RFC3985] Bryant, S. and P. Pate, "Pseudo Wire Emulation Edge-to-
Edge (PWE3) Architecture", RFC 3985, March 2005. Edge (PWE3) Architecture", RFC 3985, March 2005.
[RFC4090] Pan, P., Ed., Swallow, G., Ed., and A. Atlas, Ed., "Fast
Reroute Extensions to RSVP-TE for LSP Tunnels", RFC 4090,
May 2005.
[RFC4197] Riegel, M., "Requirements for Edge-to-Edge Emulation of [RFC4197] Riegel, M., "Requirements for Edge-to-Edge Emulation of
Time Division Multiplexed (TDM) Circuits over Packet Time Division Multiplexed (TDM) Circuits over Packet
Switching Networks", RFC4197, October 2005. Switching Networks", RFC4197, October 2005.
[RFC4377] Nadeau, T., Morrow, M., Swallow, G., Allan, D., and S. [RFC4377] Nadeau, T., Morrow, M., Swallow, G., Allan, D., and S.
Matsushima, "Operations and Management (OAM) Requirements Matsushima, "Operations and Management (OAM) Requirements
for Multi-Protocol Label Switched (MPLS) Networks", for Multi-Protocol Label Switched (MPLS) Networks",
RFC 4377, March 2006. RFC 4377, March 2006.
[RFC4378] Allan, D. and T. Nadeau, "A Framework for Multi-Protocol [RFC4378] Allan, D. and T. Nadeau, "A Framework for Multi-Protocol
skipping to change at page 27, line 18 skipping to change at page 25, line 41
[RFC4447] Martini, L., Rosen, E., El-Aawar, N., Smith, T., and [RFC4447] Martini, L., Rosen, E., El-Aawar, N., Smith, T., and
G. Heron, "Pseudowire Setup and Maintenance Using the G. Heron, "Pseudowire Setup and Maintenance Using the
Label Distribution Protocol (LDP)", RFC 4447, Label Distribution Protocol (LDP)", RFC 4447,
April 2006. April 2006.
[RFC5085] Nadeau, T. and C. Pignataro, "Pseudowire Virtual [RFC5085] Nadeau, T. and C. Pignataro, "Pseudowire Virtual
Circuit Connectivity Verification (VCCV): A Control Circuit Connectivity Verification (VCCV): A Control
Channel for Pseudowires", RFC 5085, December 2007. Channel for Pseudowires", RFC 5085, December 2007.
[RFC5601] Nadeau, T., Ed. and D. Zelig, Ed. "Pseudowire (PW)
Management Information Base (MIB)", RFC 5601, July 2009.
[RFC5602] Zelig, D., Ed., and T. Nadeau, Ed., "Pseudowire (PW) over
MPLS PSN Management Information Base (MIB)", RFC 5602,
July 2009.
[RFC5654] Niven-Jenkins, B., et al, "MPLS-TP Requirements", [RFC5654] Niven-Jenkins, B., et al, "MPLS-TP Requirements",
RFC5654, September 2009. RFC5654, September 2009.
[RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding
Detection", RFC 5880, June 2010.
[RFC5884] Aggarwal, R., Kompella, K., Nadeau, T., and G. Swallow, [RFC5884] Aggarwal, R., Kompella, K., Nadeau, T., and G. Swallow,
"Bidirectional Forwarding Detection (BFD) For MPLS "Bidirectional Forwarding Detection (BFD) For MPLS
Label Switched Paths (LSPs)", RFC 5884, June 2010. Label Switched Paths (LSPs)", RFC 5884, June 2010.
[RFC5885] Nadeau, T. and C. Pignataro, "Bidirectional [RFC5885] Nadeau, T. and C. Pignataro, "Bidirectional
Forwarding Detection (BFD) for the Pseudowire Forwarding Detection (BFD) for the Pseudowire
Virtual Circuit Connectivity Verification (VCCV)", Virtual Circuit Connectivity Verification (VCCV)",
RFC5885, June 2010. RFC5885, June 2010.
[RFC5950] Gray, E., Mansfield, S., Lam, K., [RFC5950] Gray, E., Mansfield, S., Lam, K.,
skipping to change at page 27, line 45 skipping to change at page 26, line 29
Network Management Requirements", RFC 5951, September Network Management Requirements", RFC 5951, September
2010. 2010.
[MPLS-TP-IDENTIFIERS] Bocci, M., Swallow, G., "MPLS-TP Identifiers" [MPLS-TP-IDENTIFIERS] Bocci, M., Swallow, G., "MPLS-TP Identifiers"
draft-ietf-mpls-tp-identifiers-04, March 2011. draft-ietf-mpls-tp-identifiers-04, March 2011.
[MPLS-TP-OAM-FWK] Busi, I. and B. Niven-Jenkins, "MPLS-TP OAM [MPLS-TP-OAM-FWK] Busi, I. and B. Niven-Jenkins, "MPLS-TP OAM
Framework and Overview", 2009, Framework and Overview", 2009,
<draft-ietf-mpls-tp-oam-framework>. <draft-ietf-mpls-tp-oam-framework>.
14. Authors' Addresses 12. Authors' Addresses
Adrian Farrel Adrian Farrel
Old Dog Consulting Old Dog Consulting
UK UK
Email: adrian@olddog.co.uk Email: adrian@olddog.co.uk
Daniel King Daniel King
Old Dog Consulting Old Dog Consulting
UK UK
Email: daniel@olddog.co.uk Email: daniel@olddog.co.uk
 End of changes. 143 change blocks. 
479 lines changed or deleted 478 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/