draft-ietf-mpls-tp-mib-management-overview-02.txt   draft-ietf-mpls-tp-mib-management-overview-03.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: June 26, 2011 Aricent Expires: August 14, 2011 Aricent
January 26, 2011 March 14, 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-02.txt draft-ietf-mpls-tp-mib-management-overview-03.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
skipping to change at page 2, line 26 skipping to change at page 2, line 26
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on June 26, 2011. This Internet-Draft will expire on August 14, 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
skipping to change at page 3, line 36 skipping to change at page 3, line 36
6.1 Gap Analysis............................................15 6.1 Gap Analysis............................................15
6.1.1 MPLS-TP Tunnel....................................15 6.1.1 MPLS-TP Tunnel....................................15
6.1.2 MPLS-TP Pseudowire................................15 6.1.2 MPLS-TP Pseudowire................................15
6.1.3 MPLS-TP Sections..................................15 6.1.3 MPLS-TP Sections..................................15
6.1.4 MPLS-TP OAM.......................................15 6.1.4 MPLS-TP OAM.......................................15
6.1.5 MPLS-TP Protection Switching......................16 6.1.5 MPLS-TP Protection Switching......................16
7. Interfaces...................................................16 7. Interfaces...................................................16
7.1. MPLS Tunnels as Interfaces..............................17 7.1. MPLS Tunnels as Interfaces..............................17
7.2. Application of the Interfaces Group to TE Links.........17 7.2. Application of the Interfaces Group to TE Links.........17
7.3. References to Interface Objects from MPLS MIB Modules...17 7.3. References to Interface Objects from MPLS MIB Modules...17
8. Management Options...........................................17 8. New MIB Modules Required for MPLS-TP.........................18
9. Security Considerations......................................18 8.1 MPLS Extension MIB Modules...............................19
10. IANA Considerations.........................................18 8.1.1 The MPLS Extension MIB OID Tree...................19
11. Acknowledgements............................................18 8.1.2 MPLS-TC-EXT-STD-MIB...............................19
12. References..................................................18 8.1.3 MPLS-LSR-EXT-STD-MIB..............................19
12.1. Normative References..................................18 8.1.4 MPLS-TE-EXT-STD-MIB...............................20
12.2. Informational References..............................20 8.2 PWE3 Extension MIB Modules...............................20
14. Authors' Addresses..........................................22 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
8.4.1 Structure of the MPLS Extension MIB OID Tree......22
8.4.2 MPLS-LPS-STD-MIB..................................22
8.4.3 MPLS-RPS-STD-MIB..................................23
8.4.4 MPLS-MPS-STD-MIB..................................23
9. Management Options...........................................23
10. Security Considerations.....................................23
11. IANA Considerations.........................................24
12. Acknowledgements............................................24
13. References..................................................24
13.1. Normative References...................................24
13.2. Informational References...............................25
14. Authors' Addresses..........................................27
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 26 skipping to change at page 4, line 40
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. management and identifies areas where additional MIB modules would be
required.
This document is a product of a joint Internet Engineering Task Force This document is a product of a joint Internet Engineering Task Force
(IETF) / International Telecommunication Union Telecommunication (IETF) / International Telecommunication Union Telecommunication
Standardization Sector (ITU-T) effort to include an MPLS Transport Standardization Sector (ITU-T) effort to include an MPLS Transport
Profile within the IETF MPLS and PWE3 architectures to support the Profile within the IETF MPLS and PWE3 architectures to support the
capabilities and functionalities of a packet transport network. capabilities and functionalities of a packet transport network.
2. Terminology 2. Terminology
This document also uses terminology from the MPLS architecture This document also uses terminology from the MPLS architecture
skipping to change at page 7, line 24 skipping to change at page 8, line 21
5.2.3. Mapping Data to LSPs 5.2.3. Mapping Data to LSPs
MPLS is a packet switching protocol that operates between the MPLS is a packet switching protocol that operates between the
Network layer and the data link layer in the OSI model. Network layer and the data link layer in the OSI model.
There is a clean separation between the control and forwarding There is a clean separation between the control and forwarding
planes in the MPLS protocol. This helps in easy portability and planes in the MPLS protocol. This helps in easy portability and
extensibility to the forwarding functions. extensibility to the forwarding functions.
A router which supports MPLS is known as a "Label Switching Router", A router which performs MPLS forwarding is known as a "Label
or LSR. An LSR implements the control and forwarding plane of MPLS. Switching Router. An LSR implements the control and forwarding
plane of MPLS.
The LSR "control plane" provides information in terms of label The LSR "control plane" provides information in terms of label
bindings which are part of the information used to populate bindings which are part of the information used to populate
forwarding tables in an LSR. An LSR determines which label bindings forwarding tables in an LSR. An LSR determines which label bindings
to seek and retain based on configuration and other information. to seek and retain based on configuration and other information.
The LSR forwarding plane then uses an index which is the incoming The LSR forwarding plane then uses an index which is the incoming
interface and label (usually of 20-bit length) to forward the interface and label (usually of 20-bit length) to forward the
packet. packet.
skipping to change at page 7, line 47 skipping to change at page 8, line 45
equivalence class (FEC). This can be loosely defined as the set of equivalence class (FEC). This can be loosely defined as the set of
characteristics that are being shared by the packets which will be characteristics that are being shared by the packets which will be
forwarded in a similar fashion and may share the same label. forwarded in a similar fashion and may share the same label.
MPLS packets are encapsulated by one more label entries referred to MPLS packets are encapsulated by one more label entries referred to
as the label stack. Each label stack entry consists of a label, the 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, 3 TC-bits for classifying the Traffic Class, the bottom of stack bit,
and TTL. and TTL.
The ingress and the egress devices of the MPLS network are called The ingress and the egress devices of the MPLS network are called
Label Edge routers. These routers "Push" an MPLS label into an Label Edge Routers (LER). At the LER a label is pushed onto an
incoming packet and "pop" off the MPLS label from an outgoing packet incoming packet and popped to remove it.
respectively.
At the ingress when an unlabeled packet enters, one or more label At the ingress when an unlabeled packet enters, one or more label
stack entries are (each label stack with one or more labels) is stack entries are (each label stack with one or more labels) is
prefixed to this packet based on its FEC as discussed above. In prefixed to this packet based on its FEC as discussed above. In
addition, the "MPLS-specific" L2 encapsulation (including, for addition, the "MPLS-specific" L2 encapsulation (including, for
instance, the MPLS PID) is also added at the ingress. Then the packet 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 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 router examines the topmost label in the label stack and then does a
swap, 'push' or 'pop' operations based on the contents. swap, 'push' or 'pop' operations based on the contents.
A label stack entry can be 'popped' or removed from the top of the A label stack entry can be 'popped' or removed from the top of the
label stack or a label stack entry is 'pushed' or inserted into the label stack or a label stack entry is 'pushed' or inserted into the
top of the stack based on the FEC information. top of the stack based on the FEC information.
skipping to change at page 9, line 40 skipping to change at page 10, line 37
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.
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. MPLS PSN type in the PW-STD-MIB. Additionally this document describes
the MIB objects that define pseudowire association to the MPLS PSN,
This document describes the MIB objects that define pseudowire that is not specific to the carried service.
association to the MPLS PSN, in a way 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 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 Pseudowire
skipping to change at page 16, line 30 skipping to change at page 17, line 27
o Protection architecture (1+1, 1:1, or others as defined in o Protection architecture (1+1, 1:1, or others as defined in
different topologies) different topologies)
o Switching type (unidirectional, bidirectional) o Switching type (unidirectional, bidirectional)
o Operation mode (revertive, non-revertive) o Operation mode (revertive, non-revertive)
o Automatic protection channel o Automatic protection channel
o Protection state o Protection state
o Position of the switch o Position of the switch
o Timer values (hold-off, Wait-to-Restore) o Timer values (hold-off, Wait-to-Restore)
o Failure of protocol o Failure of protocol
Among those parameters for protection switching, the topology on Among the parameters described above for protection switching, it is
that a protection switching applies has the most significant the topology itself which has the most significant influence.
influence on the other parameters. Besides, the mechanism of a
particular protection switching heavily depends on its topology.
Therefore, three MIB modules are to be defined to model and Therefore, three MIB modules are to be defined to model and
manage each of three different topologies protection switching. manage protection switching for each of three different topologies
(linear, ring and mesh) availible.
7. Interfaces 7. Interfaces
MPLS-TP can be carried over the existing and evolving physical MPLS-TP can be carried over the existing and evolving physical
transport technologies such as SONET/SDH, OTN/WDM, and Ethernet. transport technologies such as SONET/SDH, OTN/WDM, and Ethernet.
The Interfaces Group of IF-MIB [RFC2863] defines generic managed The Interfaces Group of IF-MIB [RFC2863] defines generic managed
objects for managing interfaces. The MPLS-TP MIB modules make objects for managing interfaces. The MPLS-TP MIB modules make
references to interfaces so that it can be clearly determined where references to interfaces so that it can be clearly determined where
the procedures managed by the MIB modules should be performed. the procedures managed by the MIB modules should be performed.
Additionally, the MPLS-TP MIB modules (notably MPLS-TE-STD-MIB and Additionally, the MPLS-TP MIB modules (notably MPLS-TE-STD-MIB and
TE-LINK-STD-MIB, PW-STD-MIB) utilize interface stacking within the TE-LINK-STD-MIB, PW-STD-MIB) utilize interface stacking within the
Interface Group. Interface Group.
Please refer to section 4. (Node and Interface Identifiers) in Please refer to section 4. (Node and Interface Identifiers) in
[MPLS-TP-IDENTIFIERS] for more information on MPLS-TP specific [MPLS-TP-IDENTIFIERS] for more information on MPLS-TP specific
interfaces. interfaces.
7.1. MPLS Tunnels as Interfaces 7.1. MPLS Tunnels as Interfaces
An extension to mplsTunnelTable should address the tunnel An extension to mplsTunnelTable should address the tunnel
requirements specific to MPLS-TP. requirements specific to MPLS-TP.
MPLS Tunnel logical interfaces can be stacked over MPLS Tunnel logical interfaces can be stacked over
PDH/SDH/OTH/Ethernet physical interfaces. For more information on PDH/SDH/OTH/Ethernet physical interfaces. For more information on
Tunnel interfaces, refer section 11.1 (MPLS Tunnels as Interfaces) of Tunnel interfaces, refer section 11.1 (MPLS Tunnels as Interfaces) of
RFC-4221. RFC-4221.
skipping to change at page 17, line 38 skipping to change at page 18, line 33
The PW in general is not an ifIndex on its own, for agent The PW in general is not an ifIndex on its own, for agent
scalability reasons. The PW is typically associated via scalability reasons. The PW is typically associated via
the PWE3 MIB modules to an ifIndex (physical entity) the PW is the PWE3 MIB modules to an ifIndex (physical entity) the PW is
emulating. Some implementations may manage the PW as an ifIndex in the emulating. Some implementations may manage the PW as an ifIndex in the
ifTable. A special ifType to represent a PW virtual interface (246) ifTable. A special ifType to represent a PW virtual interface (246)
will be used in the ifTable in this case. More information on PW 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 interfaces can be found in the RFC-5601, section 8 (PW relations to
the IF-MIB). the IF-MIB).
8. Management Options 8. New MIB Modules Required for MPLS-TP
This section highlights the new MIB modules that have been identified
in Section 6.1 (Gap Analysis) and are required for MPLS-TP. This
section also provides an overview of the following:
- the MPLS Object Identifier (OID) tree structure and the position
of different MPLS related MIB modules on this tree;
- 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
modules.
Note that each new MIB document should contain one or more compliance
statements for the modules and objects that it defines. Therefore,
the support for the different MIB modules and objects is beyond the
scope of this document, although some recommendations are included in
the sections that follow.
8.1 MPLS Extension MIB Modules
8.1.1 The MPLS Extension MIB OID Tree
The MPLS Extension MIB OID tree has the following structure.
transmission -- RFC 2578 [RFC2578]
|
+- mplsStdMIB
|
+- mplsTCExtStdMIB -- MPLS-TC-EXT-STD-MIB
|
+- mplsLsrExrStdMIB -- MPLS-LSR-EXT-STD-MIB
|
+- mplsTeExtStdMIB -- MPLS-TE-EXT-STD-MIB
Note: The OIDs for MIB modules are yet to be assigned and managed by
IANA.
8.1.2 MPLS-TC-EXT-STD-MIB
MPLS-TC-STD-MIB defines textual conventions [RFC2579] that may be
common to MPLS-related MIB modules. These conventions allow multiple
MIB modules to use the same syntax and format for a concept that is
shared between the MIB modules. This MIB is extended to support new
textual definitions supporting MPLS-TP networks.
For example, MEP identifier is used to identify maintainence end
point within MPLS-TP networks. The textual convention representing
the MEP identifier is defined in MPLS-TC-EXT-STD-MIB,
which is an extension to MPLS-TC-STD-MIB
All new extensions related to MPLS-TP are defined in this MIB module
and will be referenced by other MIB modules to support MPLS-TP.
8.1.3 MPLS-LSR-EXT-STD-MIB
MPLS-LSR-STD-MIB describes managed objects for modeling an MPLS Label
Switching Router (LSR). This puts it at the heart of the management
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
the MPLS-TP LSP's, which are bidirectional and co-routed or
associated. This extended MIB, MPLS-LSR-EXT-STD-MIB all models of
MPLS-TP tunnels.
8.1.4 MPLS-TE-EXT-STD-MIB
MPLS-TE-STD-MIB describes managed objects that are used to model and
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
bidirectional and could be associated or co-routed. The
MPLS-TE-EXT-STD-MIB contains the extensions to support the MPLS-TP
specific attributed for the tunnel.
8.2 PWE3 Extension MIB Modules
This section provides an overview of Pseudowire extension mib
modules to meet the MPLS based transport network requirements.
8.2.1 Structure of the PWE3 Extension MIB OID Tree
mib-2 -- RFC 2578 [RFC2578]
|
+-transmission
| |
| +- pwExtStdMIB -- PW-EXT-STD-MIB
|
+- pwMplsExtStdMIB -- PW-MPLS-EXT-STD-MIB
|
+- pwTcExtStdMIB -- PW-TC-EXT-STD-MIB
Note: The OIDs for MIB modules are yet to be assigned and managed by
IANA.
8.2.2 PW-TC-EXT-STD-MIB
PW-TC-STD-MIB MIB defines textual conventions used for pseudowire
(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
textual definitions for MPLS-TP specific Pseudowire attributes.
8.2.3 PW-EXT-STD-MIB
PW-STD-MIB describes managed objects for modeling of Pseudowire
Edge-to-Edge services carried over a general Packet Switched Network.
This MIB module is extended as PW-EXT-STD-MIB to support
MPLS-TP specific attributes related to Pseudowires.
8.2.4 PW-MPLS-EXT-STD-MIB
PW-MPLS-STD-MIB defines the managed objects for Pseudowire
operations over MPLS LSR's. This MIB supports both,
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, PW-MPLS-EXT-STD-MIB defines the managed
objects, extending PW-MPLS-STD-MIB, by supporting with or without
MPLS-TP as outer tunnel.
8.3 OAM MIB Modules
This section provides an overview of Operations, Administration,
and Maintenance (OAM) mib modules for MPLS LSPs and Pseudowires.
8.3.1 Structure of the OAM Extension MIB OID Tree
mib-2 -- RFC 2578 [RFC2578]
|
+-transmission
|
+- mplsLspPingStdMIB -- MPLS-LSPPING-STD-MIB
|
+- mplsBfdStdMIB -- MPLS-BFD-STD-MIB
|
+- mplsOamStdMIB -- MPLS-OAM-STD-MIB
Note: The OIDs for MIB modules are yet to be assigned and managed by
IANA.
8.3.2 MPLS-LSPPING-STD-MIB
LSP ping is defined in RFC4379 to validate data plane consistency of
MPLS LSP's. It defines how LSP ping and Trace could be performed
across MPLS networks to identify and diagnose faults within MPLS
networks. This OAM functionality is performed on demand basis for
verification purposes.
MPLS-LSPPING-STD-MIB defines managed objects for modeling LSP ping
protocol. It allows user to perform on demand operations based on
RFC4379. The managed objects to support LSP ping for MPLS-TP is
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
issued using the MIB for the tunnel in test. The results for the
operation could be queried using the managed objects defined in the
MIB module.
8.3.3 MPLS-BFD-STD-MIB
BFD-STD-MIB defines managed objects for performing BFD operation in
IP networks. This MIB is modeled to support BFD protocol RFC5880.
MPLS-BFD-STD-MIB is an extension to BFD-STD-MIB managed objects
to support BFD operations on MPLS LSP's. The new MPLS-TP managed
objects for BFD are based on
draft-ietf-mpls-tp-lsp-ping-bfd-procedures-01.
8.3.4 MPLS-OAM-STD-MIB
MPLS-OAM-STD-MIB defined managed objects for OAM maintenance
identifiers i.e. Maintenance Entity Group Identifiers (MEG),
Maintenance Entity Group End-point (MEP), Maintenance Entity Group
Intermediate Point (MIP). Maintenance points are uniquely
associated with a MEG. Within the context of a MEG, MEPs and MIPs
must be uniquely identified.
8.4. Protection Switching MIB Modules
This section provides an overview of protection switching mib modules
for MPLS LSPs and Pseudowires.
8.4.1 Structure of the MPLS Protection Switching MIB OID Tree
mib-2 -- RFC 2578 [RFC2578]
|
+-transmission
|
+- mplsLpsStdMIB -- MPLS-LPS-STD-MIB
|
+- mplsRpsStdMIB -- MPLS-RPS-STD-MIB
|
+- mplsMpsStdMIB -- MPLS-MPS-STD-MIB
Note: The OIDs for MIB modules are yet to be assigned and managed by
IANA.
8.4.2 MPLS-LPS-STD-MIB
MPLS-LPS-STD-MIB defined managed objects for linear protection
switching of MPLS LSPs and Pseudowires.
8.4.3 MPLS-RPS-STD-MIB
MPLS-RPS-STD-MIB defined managed objects for ring protection
switching of MPLS LSPs and Pseudowires.
8.4.4 MPLS-MPS-STD-MIB
MPLS-MPS-STD-MIB defined managed objects for Mesh protection
switching of MPLS LSPs and Pseudowires.
9. Management Options
It is not the intention of this document to provide instructions or It is not the intention of this document to provide instructions or
advice to implementers of management systems, management agents, or advice to implementers of management systems, management agents, or
managed entities. It is, however, useful to make some observations managed entities. It is, however, useful to make some observations
about how the MIB modules described above might be used to manage about how the MIB modules described above might be used to manage
MPLS systems. MPLS systems.
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 [Editors Note: MPLS-TP specific management gaps and options will be
documented in this document and will be referenced here.] documented in this document and will be referenced here.]
9. Security Considerations 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
skipping to change at page 18, line 32 skipping to change at page 24, line 10
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.
10. IANA Considerations 11. IANA Considerations
This document makes no requests for IANA action. This document makes no requests for IANA action.
11. Acknowledgements 12. 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, Sam Aldrin and Saravanan Narasimhan for their
valuable comments. valuable comments.
12. References 13. References
12.1 Normative References 13.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 20, line 20 skipping to change at page 25, line 44
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.
12.2 Informative References 13.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,
"Conformance Statements for SMIv2", STD 58, RFC 2580, "Conformance Statements for SMIv2", STD 58, RFC 2580,
April 1999. April 1999.
[RFC3031] Rosen, E., Viswanathan, A., and R. Callon, [RFC3031] Rosen, E., Viswanathan, A., and R. Callon,
"Multiprotocol Label Switching Architecture", RFC 3031, "Multiprotocol Label Switching Architecture", RFC 3031,
January 2001. March 2001.
[RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart,
"Introduction and Applicability Statements for "Introduction and Applicability Statements for
Internet-Standard Management Framework", RFC 3410, Internet-Standard Management Framework", RFC 3410,
December 2002. December 2002.
[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.
skipping to change at page 21, line 26 skipping to change at page 26, line 49
Reroute Extensions to RSVP-TE for LSP Tunnels", RFC 4090, Reroute Extensions to RSVP-TE for LSP Tunnels", RFC 4090,
May 2005. 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, February 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
Label Switching (MPLS) Operations and Management (OAM)", Label Switching (MPLS) Operations and Management (OAM)",
RFC 4378, February 2006. RFC 4378, March 2006.
[RFC4379] Kompella, K. and G. Swallow, "Detecting Multi-Protocol [RFC4379] Kompella, K. and G. Swallow, "Detecting Multi-Protocol
Label Switched (MPLS) Data Plane Failures", RFC 4379, Label Switched (MPLS) Data Plane Failures", RFC 4379,
February 2006. March 2006.
[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.
skipping to change at page 22, line 14 skipping to change at page 27, line 39
[RFC5950] Gray, E., Mansfield, S., Lam, K., [RFC5950] Gray, E., Mansfield, S., Lam, K.,
"MPLS-TP Network Management Framework", RFC 5950, "MPLS-TP Network Management Framework", RFC 5950,
September 2010. September 2010.
[RFC5951] Gray, E., Mansfield, S., Lam, K., "MPLS TP [RFC5951] Gray, E., Mansfield, S., Lam, K., "MPLS TP
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-03, October 2010. 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 14. Authors' Addresses
Adrian Farrel Adrian Farrel
Old Dog Consulting Old Dog Consulting
UK UK
skipping to change at line 1026 skipping to change at page 28, line 28
Phone: +82 42 860 5384 Phone: +82 42 860 5384
Email: ryoo@etri.re.kr Email: ryoo@etri.re.kr
A S Kiran Koushik A S Kiran Koushik
Cisco Systems Inc. Cisco Systems Inc.
Email: kkoushik@cisco.com Email: kkoushik@cisco.com
A. Karmakar A. Karmakar
Cisco Systems Inc. Cisco Systems Inc.
Email: akarmaka@cisco.com Email: akarmaka@cisco.com
Sam Aldrin
Huawei Technologies, co.
2330 Central Express Way,
Santa Clara, CA 95051, USA
Email: aldrin.ietf@gmail.com
 End of changes. 27 change blocks. 
52 lines changed or deleted 303 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/