--- 1/draft-ietf-mpls-tp-mib-management-overview-00.txt 2011-01-05 15:23:19.000000000 +0100 +++ 2/draft-ietf-mpls-tp-mib-management-overview-01.txt 2011-01-05 15:23:19.000000000 +0100 @@ -1,43 +1,38 @@ -Network Working Group A.Farrel -Internet-Draft D. King -Intended status: Informational Old Dog Consulting -Expires: April 7, 2011 M.Venkatesan - Aricent - J. Ryoo - ETRI - S. Mansfield - Ericsson - K. Koushik - Cisco Systems, Inc. - November 7, 2010 +Network Working Group D. King (Editor) +Internet-Draft Old Dog Consulting +Intended status: Informational M. Venkatesan (Editor) +Expires: June 5, 2011 Aricent + January 5, 2011 Multiprotocol Label Switching Transport Profile (MPLS-TP) MIB-based Management Overview - draft-ietf-mpls-tp-mib-management-overview-00.txt + draft-ietf-mpls-tp-mib-management-overview-01.txt Abstract A range of Management Information Base (MIB) modules has been developed to help model and manage the various aspects of Multiprotocol Label Switching (MPLS) networks. These MIB modules are defined in separate documents that focus on the specific areas of responsibility of the modules that they describe. The MPLS Transport Profile (MPLS-TP) is a profile of MPLS functionality specific to the construction of packet-switched transport networks. This document describes the MIB-based management architecture for - MPLS-TP and indicates the interrelationships between the different - MIB modules used for MPLS-TP network management. + MPLS-TP, indicates the interrelationships between different + existing MIB modules that can be leveraged for MPLS-TP network + management and identifies areas where additional MIB modules would be + 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 @@ -61,100 +56,99 @@ and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. - This Internet-Draft will expire on March 21, 2011. + This Internet-Draft will expire on June 5, 2011. Copyright Notice - Copyright (c) 2010 IETF Trust and the persons identified as the + Copyright (c) 2011 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents - 1. Introduction.................................................3 + 1. Introduction.................................................4 2. Terminology..................................................4 3. The SNMP Management Framework................................4 - 4. Summary of MPLS-TP Management Function.......................4 - 5. Overview of Existing Work....................................4 + 4. Summary of MPLS-TP Management Function.......................5 + 5. Overview of Existing Work....................................5 5.1. MPLS Management Overview and Requirements...............5 - 5.2. An Introduction to the MPLS and Pseudowire MIB Modules..5 - 5.2.1. Structure of the MPLS MIB OID Tree...............5 - 5.2.2. Textual Convention Modules.......................6 + 5.2. An Introduction to the MPLS and Pseudowire MIB Modules..6 + 5.2.1. Structure of the MPLS MIB OID Tree...............6 + 5.2.2. Textual Convention Modules.......................7 5.2.3. Mapping Data to LSPs.............................7 5.2.4. Label Switching Router Modules...................8 5.2.5. Label Switched Path Modules......................8 5.2.6. Pseudowire Modules...............................8 5.2.7. Routing and Traffic Engineering..................10 5.2.8. Resiliency.......................................10 - 5.2.9. Fault Management and Performance Management......10 - 5.2.10. MIB Module Interdependencies....................11 - 5.2.11. Dependencies on External MIB Modules............12 - 6. Applicability of MPLS MIB modules to MPLS-TP.................13 - 6.1 Gap Analysis............................................13 - 6.1.1 MPLS-TP Tunnel....................................13 - 6.1.2 MPLS-TP Pseudowire................................13 - 6.1.3 MPLS-TP Sections..................................13 - 6.1.4 MPLS-TP OAM.......................................13 - 6.1.5 MPLS-TP Protection Switching......................14 - 6.1.6 MIB Module Interdependencies......................15 - 7. Interfaces...................................................17 + 5.2.9. Fault Management and Performance Management......11 + 5.2.10. MIB Module Interdependencies....................12 + 5.2.11. Dependencies on External MIB Modules............14 + 6. Applicability of MPLS MIB modules to MPLS-TP.................14 + 6.1 Gap Analysis............................................15 + 6.1.1 MPLS-TP Tunnel....................................15 + 6.1.2 MPLS-TP Pseudowire................................15 + 6.1.3 MPLS-TP Sections..................................15 + 6.1.4 MPLS-TP OAM.......................................15 + 6.1.5 MPLS-TP Protection Switching......................16 + 7. Interfaces...................................................16 7.1. MPLS Tunnels as Interfaces..............................17 7.2. Application of the Interfaces Group to TE Links.........17 7.3. References to Interface Objects from MPLS MIB Modules...17 - 8. Management Options...........................................18 + 8. Management Options...........................................17 9. Security Considerations......................................18 10. IANA Considerations.........................................18 11. Acknowledgements............................................18 - 12. Normative References........................................19 - 13. Informational References....................................19 - 14. Authors' Addresses..........................................20 + 12. References..................................................18 + 12.1. Normative References..................................18 + 12.2. Informational References..............................20 + 14. Authors' Addresses..........................................22 1. Introduction The MPLS Transport Profile (MPLS-TP) is a packet transport technology based on a profile of the MPLS functionality specific to the construction of packet-switched transport networks. MPLS is described in [RFC3031] and requirements for MPLS-TP are specified in [RFC5654]. A range of Management Information Base (MIB) modules has been developed to help model and manage the various aspects of Multiprotocol Label Switching (MPLS) networks. These MIB modules are defined in separate documents that focus on the specific areas of responsibility of the modules that they describe. An MPLS-TP network can be operated via static provisioning of transport paths, or the elective use of a Generalized MPLS (GMPLS) control plane to support dynamic provisioning of transport paths. This document describes the MIB-based management architecture for - MPLS-TP and indicates the interrelationships between the existing - MIB modules used for MPLS-TP network management. The document also - indentifies areas where additional MIB modules would be required to - support an MPLS-TP network. + MPLS-TP and indicates the interrelationships between different + existing MIB modules that should be leveraged for MPLS-TP network + management. 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. 2. Terminology This document also uses terminology from the MPLS architecture @@ -187,21 +181,21 @@ monitoring, and security management. 5. Overview of Existing Work This section describes the existing tools and techniques for managing and modeling MPLS networks, devices, and protocols. It does not focus on MPLS-TP, but is intended to provide a description of the tool kit that is already available. The following section (Section 6. Applicability of MPLS MIB modules - to MPLS-TP) of this document describes the applicability of the MPLS + to MPLS-TP) of this document outlines the existing MPLS MIB modules and optional use of GMPLS MIB modules to MPLS-TP and examines the additional MIB modules and objects that would be required for managing an MPLS-TP network. 5.1. MPLS Management Overview and Requirements [RFC4378] outlines how data plane protocols can assist in providing the Operations and Management (OAM) requirements outlined in [RFC4377] and how it is applied to the management functions of fault, configuration, accounting, performance, and security (commonly known @@ -267,24 +261,24 @@ | +- pwTDMMIB -- PW-TDM-MIB [RFC5604] | +- pwTcStdMIB -- PW-TC-STD-MIB [RFC5542] Note: The OIDs for MIB modules are assigned and managed by IANA. They can be found in the referenced MIB documents. 5.2.2. Textual Convention Modules - MPLS-TC-STD-MIB [RFC3811] contains the Textual Conventions for - Multiprotocol Label Switching (MPLS) networks. These Textual + MPLS-TC-STD-MIB [RFC3811] and GMPLS-TC-STD-MIB [RFC4801] contains the + Textual Conventions for MPLS and GMPLS networks. These Textual Conventions should be imported by MIB modules which manage MPLS - networks. + and GMPLS networks. 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. @@ -298,24 +292,24 @@ 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 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 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. These routers "Push" an MPLS label into an incoming packet and "pop" off the MPLS label from an outgoing packet respectively. 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 @@ -333,58 +327,66 @@ remains the same. After the swap the packet is forwarded based on the new entry. 5.2.4. Label Switching Router Modules MPLS-LSR-STD-MIB [RFC3813] describes the managed objects for modeling a Multiprotocol Label Switching (MPLS) [RFC3031] LSR. MPLS-TP is specific to the use of MPLS in transport networks. According to [RFC5654] multipoint-to-point LSPs do not form part of - MPLS-TP, so multipoint-to-point cross connects are not configured in - this MIB module for use in MPLS-TP. + 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 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. + 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 mechanisms. These include manual programming and using a signalling protocol. RSVP-TE (Resource reservation protocol for Traffic Engineering) is normally used for signalling LSPs used for Traffic Engineering. 5.2.6. Pseudowire Modules 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. This - specific MIB module provides the glue for mapping between the - emulated service onto the native PSN service. As such, the defining - of a PW emulated service requires the use of at least three types of - MIB modules. + connected to any supported packet switched network (PSN) type. + Emulated Service Layer, Generic PW Layer and PSN VC Layer constitute + the different layers of the model. A combination of the MIB modules + belonging to each layer provides the glue for mapping the emulated + service onto the native PSN service. At least three MIB modules each + belonging to a different layer is required to define a PW emulated + service. - Starting from the emulated service, the first type is a service- - specific module, which is dependent on the emulated signal type. - These modules are defined in other documents. + Starting from the emulated Service Layer, the first is a + service-specific module that is dependent on the emulated signal + type. - The second type is this module, the PW-STD-MIB module, which - configures general parameters of the PW that are common to all types - of emulated services and PSN types. + The second is the PW-STD-MIB module, which configures general + parameters of the PW that are common to all types of emulated + services and PSN types. - The third type of module is a PSN-specific module. There is a - different module for each type of PSN. These modules associate the - PW with one or more "tunnels" that carry the service over the PSN. - These modules are defined in other documents. + The third is a PSN-specific module. There is a different module for + each type of PSN. These modules associate the PW with one or more + "tunnels" that carry the service over the PSN. These modules are + defined in other documents. PW-STD-MIB [RFC5601] defines a MIB module that can be used to manage pseudowire (PW) services for transmission over a Packet Switched Network (PSN) [RFC3931] [RFC4447]. This MIB module provides generic management of PWs that is common to all types of PSN and PW services defined by the IETF PWE3 Working Group. PW-MPLS-STD-MIB [RFC5602] describes a model for managing pseudowire services for transmission over different flavors of MPLS tunnels. The general PW MIB module [RFC5601] defines the parameters global to @@ -418,27 +420,20 @@ 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]. - The PW MIB modules architecture provides a layered modular model - into which any supported emulated service can be connected to any - supported PSN type. This specific MIB module provides the glue for - mapping between the emulated service onto the native PSN service. As - such, the defining of a PW emulated service requires the use of at - least three types of MIB modules. - 5.2.7. Routing and Traffic Engineering In MPLS traffic engineering, its possible to specify explicit routes or choose routes based on QOS metrics in setting up a path such that some specific data can be routed around network hot spots. MPLS-TE-STD-MIB [RFC3812] describes managed objects for modeling a Multiprotocol Label Switching (MPLS) [RFC3031] based traffic engineering. This MIB module should be used in conjunction with the companion document [RFC3813] for MPLS based traffic engineering @@ -463,35 +458,79 @@ reroute functionality. MPLS-FRR-ONE2ONE-STD-MIB [draft-ietf-mpls-fastreroute-mib-14] contains objects that apply to one-to-one backup method. MPLS-FRR-FACILITY-STD-MIB [draft-ietf-mpls-fastreroute-mib-14] contains objects that apply to facility backup method. 5.2.9. Fault Management and Performance Management - MPLS manages the LSP and Pseudowire faults through LSP ping - [RFC4379], VCCV [RFC5085], BFD for LSPs [RFC5884] and BFD for VCCV - [RFC5885] tools. + MPLS manages the LSP and pseudowire faults through the use of LSP + ping [RFC4379], VCCV [RFC5085], BFD for LSPs [RFC5884] and BFD for + VCCV [RFC5885] tools. - There is no MIB management model currently available for the above - fault management tools. + Current MPLS focuses on the in and/or out packet counters, + errored packets, discontinuity time. - There is no performance management tool currently available for MPLS. + Some of the MPLS and Pseudowire performance tables used for + performance management are given below. + + mplsTunnelPerfTable provides several counters (packets forwarded, + packets dropped because of errors) to measure the performance of + the MPLS tunnels. + + mplsInterfacePerfTable provides performance information (incoming and + outgoing labels in use and lookup failures) on a per-interface basis. + + mplsInSegmentPerfTable contains statistical information (total + packets received by the insegment, total errored packets received, + total packets discarded, discontinuity time) for incoming MPLS + segments to an LSR. + + mplsOutSegmentPerfTable contains statistical information (total + packets received, total errored packets received, total packets + discarded, discontinuity time) for outgoing MPLS segments from an + LSR. + + mplsFTNPerfTable contains performance information for the specified + interface and an FTN entry mapped to this interface. + + mplsLdpEntityStatsTable and mplsLdpSessionStatsTable contain + statistical information (session attempts, errored packets, + notifications) about an LDP entity. + + pwPerfCurrentTable, pwPerfIntervalTable, pwPerf1DayIntervalTable + provides pseudowire performance information (in and/or out packets) + based on time (current interval, each interval, 1day interval). + + pwEnetStatsTable contains statistical counters specific for Ethernet + PW. + + pwTDMPerfCurrentTable, pwTDMPerfIntervalTable and + pwTDMPerf1DayIntervalTable contain statistical informations + accumulated per 15-minute, 24 hour, 1 day respectively. + + gmplsTunnelErrorTable and gmplsTunnelReversePerfTable provides + information about performance errored packets and in/out packet + counters. 5.2.10. MIB Module Interdependencies This section provides an overview of the relationship between the MPLS MIB modules for managing MPLS networks. More details of these relationships are given below. + [RFC4221] mainly focuses on the MPLS MIB module interdependencies, + this section also highlights the GMPLS and PW MIB modules + interdependencies. + The relationship "A --> B" means A depends on B and that MIB module A uses an object, object identifier, or textual convention defined in MIB module B, or that MIB module A contains a pointer (index or RowPointer) to an object in MIB module B. +-------> MPLS-TC-STD-MIB <-----------------------------------------+ | ^ | | | | | MPLS-LSR-STD-MIB <--------------------------------+ | | | | @@ -552,130 +591,104 @@ IANA-GMPLS-TC-MIB. - GMPLS-LSR-STD-MIB contains references to objects in GMPLS-LABEL-STD-MIB. Note that there is a textual convention (MplsIndexType) defined in MPLS-LSR-STD-MIB that is imported by MPLS-LDP-STD-MIB. 5.2.11. Dependencies on External MIB Modules - In addition to the MPLS management overview [RFC4221] - section 4.12 (Dependencies on External MIB Modules), some of the - existing MPLS MIBs, PW MIBs and GMPLS MIBs are re-used with - extensions for achieving the MPLS-TP functionality. - MPLS MIB modules have dependencies with the TE-LINK-STD-MIB for maintaining the traffic engineering information. MPLS MIB modules depend on the CSPF module to get the paths for MPLS tunnel to traverse to reach 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 such as integers, strings, timestamps, etc., from the MIB modules in which they are defined. This is business as usual for a MIB module and is not discussed further in this document. 6. Applicability of MPLS MIB modules to MPLS-TP + In addition to the MPLS management overview [RFC4221] + section 4.12 (Dependencies on External MIB Modules), some of the + 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 equipment used in networks supporting an MPLS-TP. It also details the essential network management capabilities for operating networks consisting of MPLS-TP equipment. [RFC5950] provides the network management framework for MPLS-TP. The document explains how network elements and networks that support MPLS-TP can be managed using solutions that satisfy the requirements defined in [RFC5951]. The relationship between MPLS-TP management and OAM is described in the MPLS-TP framework [RFC5950] document. Fault management and performance management form key parts of Operations, Administration, and Maintenance (OAM) function. MPLS-TP OAM is described in [MPLS-TP-OAM-FWK]. - This section also provides the information about the extensions of - existing MPLS MIB modules for MPLS-TP and the new MPLS-TP MIB - modules. + [Editors note - A seperate draft will provide an MPLS-TP abstract + model and use a formal language to define the terminology, the + information that must be retrieved and method for storing. The draft + will also list the new MPLS-TP MIB modules identified in this + document] 6.1 Gap Analysis 6.1.1 MPLS-TP Tunnel - MPLS-TP tunnel table MPLSTP-STD-MIB is an extension of - MPLS tunnel table [RFC3812] to support MPLS-TP requirements. - Tunnel identifiers are defined based on [MPLS-TP-IDENTIFIERS]. + o An MPLS tunnel may not compatible for non-IP environments. + i.e., the tunnel ingress and egress identifiers are not always + identified via an IP address, rather identification is achieved + 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 - MPLS-TP Pseudowire table MPLSTP-STD-MIB is an extension of - Pseudowire table MPLS-PW-STD-MIB to support MPLS-TP requirements. - Pseudowire identifiers are defined based on [MPLS-TP-IDENTIFIERS]. + o MPLS pseudowire may not be compatible for non-IP environments. + i.e., pseudowire source and destination identifiers are not always + identified via an IP address, rather identification is achieved + using local numbers to operate in a non-IP environment. + o Pseudowire mib modules should be enhanced to operate over + corouted/associated bi-directional tunnel. + o Pseudowire 129 FEC type-2 should be used in non-IP and IP + environments with the required changes. 6.1.3 MPLS-TP Sections - This section needs to be updated with the section layer network - managed objects based on the draft-ietf-mpls-tp-data-plane-04.txt - (Section 3.2.) draft. + There is no gap in the existing MPLS MIB modules as this MPLS-TP + section will be defined as the new term for MPLS-TP. 6.1.4 MPLS-TP OAM - MPLS-LSP-PING-STD-MIB describes managed objects used to model and - manage the MPLS LSP ping [RFC4379]. LSP ping is used for - connectivity verification and fault isolation in an MPLS LSPs. - - PW-VCCV-STD-MIB describes managed objects used to model and manage - the VCCV [RFC5085]. VCCV used for end-to-end fault detection and - diagnostics for a Pseudowire. - - BFD-MPLS-STD-MIB describes the managed objects for modeling the - BFD for MPLS LSPs [RFC5884]. BFD for LSPs used for detecting - MPLS LSP data plane failures. - - BFD-PW-VCCV-STD-MIB describes the managed objects for modeling - the BFD for Pseudowires [RFC5885]. BFD for Pseudowires used for - detecting data plane failures. - - MPLS-LSP-PING-STD-MIB, PW-VCCV-STD-MIB, BFD-MPLS-STD-MIB and - BFD-PW-VCCV-STD-MIB are newly defined for MPLS. The new MPLS-TP - managed objects for LSP ping and BFD are based on - draft-ietf-mpls-tp-lsp-ping-bfd-procedures-00. - - All MPLS-TP managed for OAM is defined in the MPLSTP-OAM-STD-MIB. - - MPLSTP-TC-STD-MIB describes the textual conventions used for MPLS-TP. - - MPLSTP-STD-MIB describes managed objects used to model and manage - the new extensions for LSPs, section and Pseudowires for IP and - non-IP packet based MPLS-TP transport networks. - - The following MPLS-TP OAM functionalities can be achieved using the - MPLSTP-OAM-STD-MIB mib extensions: - - o Continuity Check and Connectivity Verification, - o Alarm Reporting, Diagnostic, - o Route Tracing, - o Loopback tool, - o Lock Instruct, - o Lock Reporting Remote Defect Indication, - o Client Failure Indication, - o Packet Loss Measurement and - o Packet Delay Measurement + MPLS manages the LSP and pseudowire faults through LSP ping + [RFC4379], VCCV [RFC5085], BFD for LSPs [RFC5884] and BFD for VCCV + [RFC5885] tools. - MPLS-TP OAM managed objects are defined based on the drafts: + There is no MIB management model currently available for the above + fault management tools. - o draft-ietf-mpls-tp-oam-requirements-06, - o draft-ietf-mpls-tp-oam-framework-06 and - o draft-ietf-mpls-tp-identifiers-01 + There is no performance management tool currently available for MPLS + except the statistics information. 6.1.5 MPLS-TP Protection Switching An important aspect that MPLS-TP technology provides is protection switching. In general, the mechanism of protection switching can be described as the substitution of a protection or standby facility for a working or primary facility. An MPLS-TP protection switching can be managed with the following parameters: o Topology (linear, ring, mesh) @@ -689,112 +702,41 @@ o Timer values (hold-off, Wait-to-Restore) o Failure of protocol Among those parameters for protection switching, the topology on that a protection switching applies has the most significant 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 manage each of three different topologies protection switching. - MPLSTP-LPS-STD-MIB describes managed objects used to model and - manage the linear protection switching. - - MPLSTP-RPS-STD-MIB describes managed objects used to model and - manage the ring protection switching. - - MPLSTP-MPS-STD-MIB describes managed objects used to model and - manage the mesh protection switching. - -6.1.6 MIB Module Interdependencies - - This section provides an overview of the relationship between - the MPLS-TP MIB modules. More details of these relationships - are given below. - - The arrows in the following diagram show a 'depends on' - relationship. A relationship "MIB module A depends on MIB module - B" means that MIB module A uses an object, object identifier, or - textual convention defined in MIB module B, or that MIB module A - contains a pointer (index or RowPointer) to an object in MIB - module B. - - +-------------->MPLSTP-TC-STD-MIB <--------------------------+ - | | - | MPLS-TE-STD-MIB PW-STD-MIB | - | ^ ^ | - | | | | - +<----------- MPLSTP-STD-MIB <-------------------------------+ - | ^ | - | | +---------> MPLS-LSP-PING-STD-MIB | - | | ^ ^ ^ | - | | | | | | - | | | PW-VCCV-STD-MIB | | - | | | ^ ^ | | - | | | | | | | - | | BFD-MPLS-STD-MIB | | | - | | ^ +----------+ | | - | | | ^ | | - | | | | | | - +<----------- MPLSTP-OAM-STD-MIB ------------->+ | - ^ | - | | - +- MPLSTP-LPS-STD-MIB -------------------->+ - | | - +- MPLSTP-RPS-STD-MIB -------------------->+ - | | - +- MPLSTP-MPS-STD-MIB -------------------->+ - - Thus: - - - All the MPLS-TP MIB modules depend on MPLSTP-TC-STD-MIB. - - - MPLSTP-OAM-STD-MIB and MPLSTP-PS-STD-MIB contain references to - objects in MPLSTP-STD-MIB. - - - MPLSTP-PS-STD-MIB contains references to objects in - MPLSTP-OAM-STD-MIB. - - - MPLSTP-STD-MIB contains references to objects in - MPLS-TE-STD-MIB and PW-STD-MIB. - - - MPLSTP-OAM-STD-MIB contains references to objects in - MPLS-LSP-PING-STD-MIB, and - PW-VCCV-STD-MIB and BFD-MPLS-STD-MIB. - - - BFD-MPLS-STD-MIB contains references to objects in - MPLS-LSP-PING-STD-MIB and PW-VCCV-STD-MIB. - - - PW-VCCV-STD-MIB contains references to objects in - MPLS-LSP-PING-STD-MIB. - 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 - mplstpTunnelTable is extended from mplsTunnelTable for achieving the - MPLS-TP tunnel requirements. + An extension to mplsTunnelTable should address the tunnel + requirements specific to MPLS-TP. MPLS Tunnel logical interfaces can be stacked over 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 TE links can be formed over PDH/SDH/OTH/Ethernet physical interfaces. For more information on TE links, Refer section 11.2. Application of @@ -857,22 +799,23 @@ entity giving access to an instance of each MIB module is properly configured to give access to only those objects, and to those principals (users) that have legitimate rights to access them. 10. IANA Considerations This document makes no requests for IANA action. 11. Acknowledgements - The authors would like to thank Eric Gray, Thomas Nadeau and Benjamin - Niven-Jenkins for their valuable comments. + The authors would like to thank Eric Gray, Thomas Nadeau, Benjamin + Niven-Jenkins, Sam Aldrin and Anirban Karmakar for their valuable + comments. 12. References 12.1 Normative References [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB using SMIv2", RFC 2863, June 2000. [RFC3811] Nadeau, T. and J. Cucchiara, "Definition of Textual Conventions and for Multiprotocol Label Switching (MPLS) @@ -1049,24 +992,27 @@ UK Email: daniel@olddog.co.uk Venkatesan Mahalingam Aricent India Email: venkatesan.mahalingam@aricent.com Scott Mansfield Ericsson - 300 Holger Way - San Jose, CA 95134 - US + 300 Holger Way, San Jose, CA 95134, US Phone: +1 724 931 9316 Email: scott.mansfield@ericsson.com Jeong-dong Ryoo ETRI 161 Gajeong, Yuseong, Daejeon, 305-700, South Korea Phone: +82 42 860 5384 Email: ryoo@etri.re.kr + A S Kiran Koushik Cisco Systems Inc. Email: kkoushik@cisco.com + + A. Karmakar + Cisco Systems Inc. + Email: akarmaka@cisco.com