idnits 2.17.00 (12 Aug 2021) /tmp/idnits32132/draft-ietf-mpls-tp-mib-management-overview-08.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (April 13, 2012) is 3683 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- -- Obsolete informational reference (is this intentional?): RFC 4379 (Obsoleted by RFC 8029) -- Obsolete informational reference (is this intentional?): RFC 4447 (Obsoleted by RFC 8077) Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group D. King (Editor) 2 Internet-Draft Old Dog Consulting 3 Intended status: Informational M. Venkatesan (Editor) 4 Expires: Secptember 13, 2012 Aricent 5 April 13, 2012 7 Multiprotocol Label Switching Transport Profile (MPLS-TP) 8 MIB-based Management Overview 9 draft-ietf-mpls-tp-mib-management-overview-08.txt 11 Abstract 13 A range of Management Information Base (MIB) modules has been 14 developed to help model and manage the various aspects of 15 Multiprotocol Label Switching (MPLS) networks. These MIB modules are 16 defined in separate documents that focus on the specific areas of 17 responsibility of the modules that they describe. 19 The MPLS Transport Profile (MPLS-TP) is a profile of MPLS 20 functionality specific to the construction of packet-switched 21 transport networks. 23 This document describes the MIB-based architecture for MPLS-TP, 24 and indicates the interrelationships between different existing MIB 25 modules that can be leveraged for MPLS-TP network management and 26 identifies areas where additional MIB modules are required. 28 Status of this Memo 30 This Internet-Draft is submitted to IETF in full conformance with the 31 provisions of BCP 78 and BCP 79. 33 Internet-Drafts are working documents of the Internet Engineering 34 Task Force (IETF), its areas, and its working groups. Note that 35 other groups may also distribute working documents as Internet- 36 Drafts. 38 Internet-Drafts are draft documents valid for a maximum of six months 39 and may be updated, replaced, or obsoleted by other documents at any 40 time. It is inappropriate to use Internet-Drafts as reference 41 material or to cite them other than as "work in progress." 43 The list of current Internet-Drafts can be accessed at 44 http://www.ietf.org/ietf/1id-abstracts.txt. 46 The list of Internet-Draft Shadow Directories can be accessed at 47 http://www.ietf.org/shadow.html. 49 This Internet-Draft will expire on September 13, 2012. 51 Copyright Notice 53 Copyright (c) 2012 IETF Trust and the persons identified as the 54 document authors. All rights reserved. 56 This document is subject to BCP 78 and the IETF Trust's Legal 57 Provisions Relating to IETF Documents 58 (http://trustee.ietf.org/license-info) in effect on the date of 59 publication of this document. Please review these documents 60 carefully, as they describe your rights and restrictions with respect 61 to this document. Code Components extracted from this document must 62 include Simplified BSD License text as described in Section 4.e of 63 the Trust Legal Provisions and are provided without warranty as 64 described in the Simplified BSD License. 66 Table of Contents 68 1. Introduction.................................................3 69 1.1 MPLS-TP Management Function.................................4 70 2. Terminology..................................................4 71 3. The SNMP Management Framework................................4 72 4. Overview of Existing Work....................................5 73 4.1. MPLS Management Overview and Requirements...............5 74 4.2. An Introduction to the MPLS and Pseudowire MIB Modules..5 75 4.2.1. Structure of the MPLS MIB OID Tree...............5 76 4.2.2. Textual Convention Modules.......................7 77 4.2.3. Label Switched Path (LSP) Modules................7 78 4.2.4. Label Edge Router (LER) Modules..................7 79 4.2.5. Label Switching Router (LSR) Modules.............7 80 4.2.6. Pseudowire Modules...............................8 81 4.2.7. Routing and Traffic Engineering..................9 82 4.2.8. Resiliency.......................................9 83 4.2.9. Fault Management and Performance Management......10 84 4.2.10. MIB Module Interdependencies....................11 85 4.2.11. Dependencies on External MIB Modules............13 86 5. Applicability of MPLS MIB modules to MPLS-TP.................14 87 5.1 MPLS-TP Tunnel...........................................14 88 5.1.1 Gap Analysis.......................................14 89 5.1.2 Recommendations....................................15 90 5.2 MPLS-TP Pseudowire.......................................15 91 5.2.1 Gap Analysis.......................................15 92 5.2.2 Recommendations....................................15 93 5.3 MPLS-TP Sections.........................................15 94 5.3.1 Gap Analysis.......................................15 95 5.3.2 Recommendations....................................15 96 5.4 MPLS-TP OAM..............................................16 97 5.4.1 Gap Analysis.......................................16 98 5.4.2 Recommendations....................................16 99 5.5 MPLS-TP Protection Switching and Recovery................16 100 5.5.1 Gap Analysis.......................................16 101 5.5.2 Recommendations....................................16 102 5.6 MPLS-TP Interfaces.......................................16 103 5.6.1 Gap Analysis.......................................16 104 5.6.2 Recommendations....................................17 105 6. An Introduction to the MPLS-TP MIB Modules...................17 106 6.1 MPLS-TP MIB Modules......................................17 107 6.1.1 NEW MIB Modules for MPLS-TP.......................17 108 6.1.2 Textual Conventions for MPLS-TP...................18 109 6.1.3 Identifiers for MPLS-TP...........................18 110 6.1.4 LSR MIB Extensions for MPLS-TP....................18 111 6.1.5 Tunnel Extensions for MPLS-TP.....................18 112 6.2 PWE3 MIB Modules for MPLS-TP.............................18 113 6.2.1 New MIB Modules for MPLS-TP Pseudowires...........18 114 6.2.2 Pseudowire Textual Conventions for MPLS-TP........19 115 6.2.3 Pseudowire Extensions for MPLS-TP.................19 116 6.2.4 Pseudowire MPLS Extensions for MPLS-TP............19 117 6.3 OAM MIB Modules for MPLS-TP..............................19 118 6.3.1 New MIB Modules for OAM for MPLS-TP...............19 119 6.3.2 BFD MIB module....................................19 120 6.3.3 Common OAM MIB modules............................20 121 6.4. Protection Switching and Recovery MIB Modules 122 for MPLS-TP.............................................20 123 6.4.1 New MIB Modules for MPLS Protection Switching 124 and Recovery............................................20 125 6.4.2 Linear Protection Switching MIB module............20 126 6.4.3 Ring Protection Switching MIB module..............20 127 6.4.4 Mesh Protection Switching MIB module..............20 128 7. Management Options...........................................20 129 8. Security Considerations......................................21 130 9. IANA Considerations..........................................21 131 10. Acknowledgements............................................21 132 11. References..................................................22 133 11.1. Normative References...................................22 134 11.2. Informational References...............................23 135 12. Authors' Addresses..........................................27 137 1. Introduction 139 The MPLS Transport Profile (MPLS-TP) is a packet transport 140 technology based on a profile of the MPLS functionality specific 141 to the construction of packet-switched transport networks. 142 MPLS is described in [RFC3031] and requirements for MPLS-TP are 143 specified in [RFC5654]. 145 A range of Management Information Base (MIB) modules has been 146 developed to help model and manage the various aspects of 147 Multiprotocol Label Switching (MPLS) networks. These MIB modules 148 are defined in separate documents that focus on the specific areas of 149 responsibility for the modules that they describe. 151 An MPLS-TP network can be operated via static provisioning of 152 transport paths, Label Switched Paths (LSPs) and Pseudowires (PW). 153 Or the elective use of a Generalized MPLS (GMPLS) control plane to 154 support dynamic provisioning of transport paths, LSPs and PWs. 156 This document describes the MIB-based management architecture for 157 MPLS, as extended for MPLS-TP. The document also indicates the 158 interrelationships between existing MIB modules that should be 159 leveraged for MPLS-TP network management and identifies areas where 160 additional MIB modules are required. 162 Note that [RFC5951] does not specify a preferred management interface 163 protocol to be used as the standard protocol for managing MPLS-TP 164 networks. 166 1.1 MPLS-TP Management Function 168 The management of the MPLS-TP networks is separable from that of 169 its client networks so that the same means of management can be used 170 regardless of the client. The management function of MPLS-TP 171 includes fault management, configuration management, performance 172 monitoring, and security management. 174 The purpose of the management function is to provide control and 175 monitoring of the MPLS transport profile protocol mechanisms and 176 procedures. The requirements for the network management 177 functionality are found in [RFC5951]. A description of the network 178 and element management architectures that can be applied to the 179 management of MPLS-based transport networks is found in [RFC5950]. 181 2. Terminology 183 This document also uses terminology from the MPLS architecture 184 document [RFC3031], PWE3 architecture [RFC4805], and the following 185 MPLS related MIB modules: MPLS TC MIB [RFC3811], MPLS LSR MIB 186 [RFC3813], MPLS TE MIB [RFC3812], MPLS LDP MIB [RFC3815], MPLS FTN 187 MIB [RFC3814] and TE LINK MIB [RFC4220]. 189 3. The SNMP Management Framework 191 Managed objects are accessed via a virtual information store, termed 192 the Management Information Base or MIB. MIB objects are generally 193 accessed through the Simple Network Management Protocol (SNMP). 195 Objects in the MIB are defined using the mechanisms defined in the 196 Structure of Management Information (SMI). 198 For a detailed overview of the documents that describe the current 199 Internet-Standard Management Framework, please refer to Section 7. of 200 [RFC3410]. 202 This document discusses MIB modules that are compliant to the SMIv2, 203 which is described in [RFC2578], [RFC2579] and [RFC2580]. 205 4. Overview of Existing Work 207 This section describes the existing tools and techniques for 208 managing and modeling MPLS networks, devices, and protocols. It is 209 intended to provide a description of the tool kit that is already 210 available. 212 Section 5 of this document outlines the applicability of existing 213 MPLS MIB modules to MPLS-TP, describes the optional use of GMPLS MIB 214 modules in MPLS-TP networks, and examines the additional MIB modules 215 and objects that would be required for managing an MPLS-TP network. 217 4.1. MPLS Management Overview and Requirements 219 [RFC4378] outlines how data plane protocols can assist in providing 220 the Operations and Management (OAM) requirements outlined in 221 [RFC4377] and how it is applied to the management functions of fault, 222 configuration, accounting, performance, and security (commonly known 223 as FCAPS) for MPLS networks. 225 [RFC4221] describes the management architecture for MPLS. In 226 particular, it describes how the managed objects defined in various 227 MPLS-related MIB modules model different aspects of MPLS, as well as 228 the interactions and dependencies between each of these MIB modules. 230 [RFC4377] describes the requirements for user and data plane OAM and 231 applications for MPLS. 233 [RFC5654] describes the requirements for the optional use of a 234 control plane to support dynamic provisioning of MPLS-TP transport 235 paths. The MPLS-TP LSP control plane is based on GMPLS and is 236 described in [RFC3945]. 238 4.2. An Introduction to the MPLS and Pseudowire MIB Modules 240 4.2.1. Structure of the MPLS MIB OID Tree 242 The MPLS MIB Object Identifiers (OID) tree has the following 243 structure. It is based on the tree originally set out in section 244 4.1 of [RFC4221] and has been enhanced to include other relevant MIB 245 modules. 247 mib-2 -- RFC 2578 [RFC2578] 248 | 249 +-transmission 250 | | 251 | +- mplsStdMIB 252 | | | 253 | | +- mplsTCStdMIB -- MPLS-TC-STD-MIB [RFC3811] 254 | | | 255 | | +- mplsLsrStdMIB -- MPLS-LSR-STD-MIB [RFC3813] 256 | | | 257 | | +- mplsTeStdMIB -- MPLS-TE-STD-MIB [RFC3812] 258 | | | 259 | | +- mplsLdpStdMIB -- MPLS-LDP-STD-MIB [RFC3815] 260 | | | 261 | | +- mplsLdpGenericStdMIB 262 | | | -- MPLS-LDP-GENERIC-STD-MIB [RFC3815] 263 | | | 264 | | +- mplsFTNStdMIB -- MPLS-FTN-STD-MIB [RFC3814] 265 | | | 266 | | +- gmplsTCStdMIB -- GMPLS-TC-STD-MIB [RFC4801] 267 | | | 268 | | +- gmplsTeStdMIB -- GMPLS-TE-STD-MIB [RFC4802] 269 | | | 270 | | +- gmplsLsrStdMIB -- GMPLS-LSR-STD-MIB [RFC4803] 271 | | | 272 | | +- gmplsLabelStdMIB -- GMPLS-LABEL-STD-MIB [RFC4803] 273 | | 274 | +- teLinkStdMIB -- TE-LINK-STD-MIB [RFC4220] 275 | | 276 | +- pwStdMIB -- PW-STD-MIB [RFC5601] 277 | 278 +- ianaGmpls -- IANA-GMPLS-TC-MIB [RFC4802] 279 | 280 +- ianaPwe3MIB -- IANA-PWE3-MIB [RFC5601] 281 | 282 +- pwEnetStdMIB -- PW-ENET-STD-MIB [RFC5603] 283 | 284 +- pwMplsStdMIB -- PW-MPLS-STD-MIB [RFC5602] 285 | 286 +- pwTDMMIB -- PW-TDM-MIB [RFC5604] 287 | 288 +- pwTcStdMIB -- PW-TC-STD-MIB [RFC5542] 290 Note: The OIDs for MIB modules are assigned and managed by IANA. 291 They can be found in the referenced MIB documents. 293 4.2.2. Textual Convention Modules 295 MPLS-TC-STD-MIB [RFC3811], GMPLS-TC-STD-MIB [RFC4801], 296 IANA-GMPLS-TC-MIB [RFC4802] and PW-TC-STD-MIB [RFC5542] contains the 297 Textual Conventions for MPLS and GMPLS networks. These Textual 298 Conventions should be imported by MIB modules which manage MPLS 299 and GMPLS networks. Section 4.2.11. highlights dependencies on 300 additional external MIB modules 302 4.2.3. Label Switched Path (LSP) Modules 304 An LSP is a path over which a labeled packet travels across the 305 sequence of LSRs for a given Forward Equivalence Class (FEC). When a 306 packet, with or without label, arrives at an ingress LER of an LSP, 307 it is encapsulated with the label corresponding to the FEC and sent 308 across the LSP. The labeled packet traverses across the LSRs and 309 arrives at the egress LER of the LSP, where, it gets forwarded 310 depending on the packet type it came with. LSPs could be nested using 311 label stacking, such that, an LSP could traverse over another LSP. A 312 further description of an LSP can be found in [RFC3031]. 314 MPLS-LSR-STD-MIB [RFC3813] describes the required objects to define 315 the LSP. 317 4.2.4. Label Edge Router (LER) Modules 319 Ingress and Egress LSRs of an LSP are known as Label Edge Routers 320 (LER). An ingress LER takes the incoming unlabeled or labeled packets 321 and encapsulates it with the corresponding label of the LSP it 322 represents, and forwards it, over to the adjacent LSR of the LSP. 323 Each FEC is mapped to a label forwarding entry, so that packet could 324 be encapsulated with one or more label entries, referred as label 325 stack. 327 The packet traverses across the LSP, and upon reaching the Egress 328 LER, further action will be taken to handle the packet, depending on 329 the packet it received. MPLS Architecture [RFC3031] details 330 the functionality of an Ingress and Egress LERs. 332 MPLS-FTN-STD-MIB [RFC3814] describes the managed objects for mapping 333 FEC to label bindings. 335 4.2.5. Label Switching Router (LSR) Modules 337 A router which performs MPLS forwarding is known as an LSR. An LSR 338 receives a labelled packet and performs forwarding action based on 339 the label received. 341 LSR maintains a mapping of an incoming label and incoming interface 342 to one or more outgoing label and outgoing interfaces in its 343 forwarding database. When a labelled packet is received, LSR examines 344 the topmost label in the label stack and then does 'swap', 'push' or 345 'pop' operation based on the contents. 347 MPLS-LSR-STD-MIB [RFC3813] describes the managed objects for modeling 348 a Multiprotocol Label Switching (MPLS) [RFC3031] LSR. 349 MPLS-LSR-STD-MIB [RFC3813] contains the managed objects to maintain 350 mapping of in-segments to out-segments. 352 4.2.6. Pseudowire Modules 354 The PW (Pseudowire) MIB architecture provides a layered modular model 355 into which any supported emulated service such as Frame Relay, ATM, 356 Ethernet, TDM and SONET/SDH can be connected to any supported Packet 357 Switched Network (PSN) type. This MIB architecture is modeled based 358 on PW3 architecture [RFC3985]. 360 Emulated Service Layer, Generic PW Layer and PSN VC Layer constitute 361 the different layers of the model. A combination of the MIB modules 362 belonging to each layer provides the glue for mapping the emulated 363 service onto the native PSN service. At least three MIB modules each 364 belonging to a different layer are required to define a PW emulated 365 service. 367 - Service-Specific module is dependent on the emulated signal type 368 and helps in modeling emulated service layer. 370 PW-ENET-STD-MIB [RFC5603] describes a model for managing Ethernet 371 pseudowire services for transmission over a PSN. This MIB module is 372 generic and common to all types of PSNs supported in the Pseudowire 373 Emulation Edge-to-Edge (PWE3) Architecture [RFC3985], which describes 374 the transport and encapsulation of L1 and L2 services over supported 375 PSN types. 377 In particular, the MIB module associates a port or specific VLANs on 378 top of a physical Ethernet port or a virtual Ethernet interface (for 379 Virtual Private LAN Service (VPLS)) to a point-to-point PW. It is 380 complementary to the PW-STD-MIB [RFC5601], which manages the generic 381 PW parameters common to all services, including all supported PSN 382 types. 384 PW-TDM-MIB [RFC5604] describes a model for managing TDM pseudowires, 385 i.e., TDM data encapsulated for transmission over a Packet Switched 386 Network (PSN). The term TDM in this document is limited to the 387 scope of Plesiochronous Digital Hierarchy (PDH). It is currently 388 specified to carry any TDM Signals in either Structure Agnostic 389 Transport mode (E1, T1, E3, and T3) or in Structure Aware 390 Transport mode (E1, T1, and NxDS0) as defined in the Pseudowire 391 Emulation Edge-to-Edge (PWE3) TDM Requirements document [RFC4197]. 393 - Generic PW Module configures general parameters of the PW that are 394 common to all types of emulated services and PSN types. 396 PW-STD-MIB [RFC5601] defines a MIB module that can be 397 used to manage pseudowire (PW) services for transmission over a 398 Packet Switched Network (PSN) [RFC3931] [RFC4447]. This MIB module 399 provides generic management of PWs that is common to all types of 400 PSN and PW services defined by the IETF PWE3 Working Group. 402 - PSN-specific module associate the PW with one or more "tunnels" 403 that carry the service over the PSN. There is a different module 404 for each type of PSN. 406 PW-MPLS-STD-MIB [RFC5602] describes a model for managing pseudowire 407 services for transmission over different flavors of MPLS tunnels. 408 The general PW MIB module [RFC5601] defines the parameters global to 409 the PW regardless of the underlying Packet Switched Network (PSN) 410 and emulated service. This document is applicable for PWs that use 411 MPLS PSN type in the PW-STD-MIB. Additionally this document describes 412 the MIB objects that define pseudowire association to the MPLS PSN, 413 that is not specific to the carried service. 415 Together, [RFC3811], [RFC3812] and [RFC3813] describe the modeling of 416 an MPLS tunnel, and a tunnel's underlying cross-connects. This MIB 417 module supports MPLS-TE PSN, non-TE MPLS PSN (an outer tunnel created 418 by the Label Distribution Protocol (LDP) or manually), and MPLS PW 419 label only (no outer tunnel). 421 4.2.7. Routing and Traffic Engineering 423 In MPLS traffic engineering, it's possible to specify explicit routes 424 or choose routes based on QOS metrics in setting up a path such that 425 some specific data can be routed around network hot spots. TE LSPs 426 can be setup through a management plane or a control plane. 428 MPLS-TE-STD-MIB [RFC3812] describes managed objects for modeling a 429 Multiprotocol Label Switching (MPLS) [RFC3031] based traffic 430 engineering. This MIB module should be used in conjunction with the 431 companion document [RFC3813] for MPLS based traffic engineering 432 configuration and management. 434 4.2.8. Resiliency 436 The purpose of MPLS resiliency is to ensure minimal interruption to 437 traffic when the failure occurs within the system or network. 439 Various components of MPLS resiliency solutions are; 440 1) Graceful restart in LDP and RSVP-TE modules, 441 2) Make Before Break, 442 3) Protection Switching for LSPs, 443 4) Fast ReRoute for LSPs, 444 5) PW redundancy. 446 The MIB modules below only support MIB based management for MPLS 447 resiliency. 449 MPLS Fast Reroute (FRR) is a restoration network resiliency mechanism 450 used in MPLS TE to redirect the traffic onto the backup LSP's in 10s 451 of milliseconds in case of link or node failure across the LSP. 453 MPLS-FRR-GENERAL-STD-MIB [draft-ietf-mpls-fastreroute-mib-14] 454 contains objects that apply to any MPLS LSR implementing MPLS TE fast 455 reroute functionality. 457 MPLS-FRR-ONE2ONE-STD-MIB [draft-ietf-mpls-fastreroute-mib-14] 458 contains objects that apply to one-to-one backup method. 459 MPLS-FRR-FACILITY-STD-MIB [draft-ietf-mpls-fastreroute-mib-14] 460 contains objects that apply to facility backup method. 462 Protection Switching mechanisms have been designed to provide network 463 resiliency for MPLS network. Different types of protection switching 464 mechanisms such as 1:1, 1:N, 1+1 have been designed. 466 4.2.9. Fault Management and Performance Management 468 MPLS manages the LSP and pseudowire faults through the use of LSP 469 ping [RFC4379], VCCV [RFC5085], BFD for LSPs [RFC5884] and BFD for 470 VCCV [RFC5885] tools. 472 Current MPLS focuses on the in and/or out packet counters, 473 errored packets, discontinuity time. 475 Some of the MPLS and Pseudowire performance tables used for 476 performance management are given below. 478 mplsTunnelPerfTable [RFC3812] provides several counters (packets 479 forwarded, packets dropped because of errors) to measure the 480 performance of the MPLS tunnels. 482 mplsInterfacePerfTable [RFC3813] provides performance information 483 (incoming and outgoing labels in use and lookup failures) on a 484 per-interface basis. 486 mplsInSegmentPerfTable [RFC3813] contains statistical information 487 (total packets received by the insegment, total errored packets 488 received, total packets discarded, discontinuity time) for incoming 489 MPLS segments to an LSR. 491 mplsOutSegmentPerfTable [RFC3813] contains statistical information 492 (total packets received, total errored packets received, total 493 packets discarded, discontinuity time) for outgoing MPLS segments 494 from an LSR. 496 mplsFTNPerfTable [RFC3814] contains performance information for the 497 specified interface and an FTN entry mapped to this interface. 499 mplsLdpEntityStatsTable [RFC3815] and mplsLdpSessionStatsTable 500 [RFC3815] contain statistical information (session attempts, errored 501 packets, notifications) about an LDP entity. 503 pwPerfCurrentTable [RFC5601], pwPerfIntervalTable [RFC5601], 504 pwPerf1DayIntervalTable [RFC5601] provides pseudowire performance 505 information (in and/or out packets) based on time (current interval, 506 preconfigured specific interval, 1day interval). 508 pwEnetStatsTable [RFC5603] contains statistical counters specific for 509 Ethernet PW. 511 pwTDMPerfCurrentTable [RFC5604], pwTDMPerfIntervalTable [RFC5604] and 512 pwTDMPerf1DayIntervalTable [RFC5604] contain statistical informations 513 accumulated per 15-minute, 24 hour, 1 day respectively. 515 gmplsTunnelErrorTable [RFC4802] and gmplsTunnelReversePerfTable 516 [RFC4802] provides information about performance errored packets and 517 in/out packet counters. 519 4.2.10. MIB Module Interdependencies 521 This section provides an overview of the relationship between the 522 MPLS MIB modules for managing MPLS networks. More details of these 523 relationships are given below. 525 [RFC4221] mainly focuses on the MPLS MIB module interdependencies, 526 this section also highlights the GMPLS and PW MIB modules 527 interdependencies. 529 The relationship "A --> B" means A depends on B and that MIB module 530 A uses an object, object identifier, or textual convention defined 531 in MIB module B, or that MIB module A contains a pointer (index or 532 RowPointer) to an object in MIB module B. 534 +-------> MPLS-TC-STD-MIB <-----------------------------------------+ 535 ^ ^ ^ 536 | | | 537 | MPLS-LSR-STD-MIB <--------------------------------+ | 538 | ^ | 539 | | | 540 +<----------------------- MPLS-LDP-STD-MIB ---------------->+ | 541 ^ ^ ^ | 542 | | | | 543 +<-- MPLS-LDP-GENERIC-STD-MIB ------>+ | | 544 ^ | | 545 | | | 546 +<------ MPLS-FTN-STD-MIB --------------------------------->+ | 547 ^ | ^ | 548 | V | | 549 +<------------- MPLS-TE-STD-MIB -->+----------------------->+ | 550 ^ GMPLS-TC-STD-MIB ------------>+ 551 | ^ ^ 552 | | | 553 +---+ +<-- GMPLS-LABEL-STD-MIB -->+ 554 ^ ^ ^ ^ ^ 555 | | | | | 556 +----> PW-TC-STD-MIB | GMPLS-LSR-STD-MIB --------------->+ 557 ^ | ^ ^ ^ 558 | | | | | 559 | IANA-PWE3-MIB | | | IANA-GMPLS-TC-MIB | 560 | ^ | | | ^ | 561 | | | | | | | 562 | | +<--- GMPLS-TE-STD-MIB ------------->+ 563 | | ^ ^ 564 +<--- PW-STD-MIB <------+ | | 565 ^ ^ | | 566 | | | | 567 +<--- PW-ENET-STD-MIB ->+ | | 568 ^ ^ | | 569 | | | | 570 | | | | 571 +<---------------- PW-MPLS-STD-MIB--------------------------------->+ 573 Thus: 575 - All the MPLS MIB modules depend on MPLS-TC-STD-MIB. 577 - All the GMPLS MIB modules depend on GMPLS-TC-STD-MIB. 579 - All the PW MIB modules depend on PW-TC-STD-MIB. 581 - MPLS-LDP-STD-MIB, MPLS-TE-STD-MIB, MPLS-FTN-STD-MIB, 582 GMPLS-LSR-STD-MIB, and PW-MPLS-STD-MIB contain references to 583 objects in MPLS-LSR-STD-MIB. 585 - MPLS-LDP-GENERIC-STD-MIB contains references to objects in 586 MPLS-LDP-STD-MIB. 588 - MPLS-FTN-STD-MIB, PW-MPLS-STD-MIB, and GMPLS-TE-STD-MIB contain 589 references to objects in MPLS-TE-STD-MIB. 591 - PW-MPLS-STD-MIB, and PW-ENET-STD-MIB contains references to 592 objects in PW-STD-MIB. 594 - PW-STD-MIB contains references to objects in IANA-PWE3-MIB. 596 - GMPLS-TE-STD-MIB contains references to objects in 597 IANA-GMPLS-TC-MIB. 599 - GMPLS-LSR-STD-MIB contains references to objects in 600 GMPLS-LABEL-STD-MIB. 602 Note that there is a textual convention (MplsIndexType) defined in 603 MPLS-LSR-STD-MIB that is imported by MPLS-LDP-STD-MIB. 605 4.2.11. Dependencies on External MIB Modules 607 With the exception of MPLS-TC-STD-MIB, all the MPLS MIB modules have 608 dependencies on the Interfaces MIB [RFC2863]. MPLS-FTN-STD-MIB 609 references IP-capable interfaces on which received traffic is to be 610 classified using indexes in the Interface Table (ifTable) of IF-MIB 611 [RFC2863]. The other MPLS MIB modules reference MPLS-capable 612 interfaces in ifTable. 614 The Interfaces Group of IF-MIB [RFC2863] defines generic managed 615 objects for managing interfaces. The MPLS MIB modules contain 616 media-specific extensions to the Interfaces Group for managing MPLS 617 interfaces. 619 The MPLS MIB modules assume the interpretation of the Interfaces 620 Group to be in accordance with [RFC2863], which states that ifTable 621 contains information on the managed resource's interfaces and that 622 each sub-layer below the internetwork layer of a network interface is 623 considered an interface. Thus, the MPLS interface is represented as 624 an entry in ifTable. 626 The interrelation of entries in ifTable is defined by the Interfaces 627 Stack Group defined in [RFC2863]. 629 The MPLS MIB modules have dependencies with the TE-LINK-STD-MIB 630 for maintaining the traffic engineering information. 632 The MPLS MIB modules depend on the constrained shortest path first 633 (CSPF) module to obtain the path required for an MPLS tunnel to reach 634 the end point of the tunnel and Bidirectional Forwarding Detection 635 (BFD) module to verify the data-plane failures of LSPs and PWs. 637 Finally, all of the MIB modules import standard textual conventions 638 such as integers, strings, timestamps, etc., from the MIB modules in 639 which they are defined. 641 5. Applicability of MPLS MIB modules to MPLS-TP 643 This section highlights gaps in existing MPLS MIB modules in 644 order to determine extensions or additional MIB modules that are 645 required to support MPLS-TP in MPLS networks 647 [RFC5951] specifies the requirements for the management of equipment 648 used in networks supporting an MPLS-TP. It also details the 649 essential network management capabilities for operating networks 650 consisting of MPLS-TP equipment. 652 [RFC5950] provides the network management framework for MPLS-TP. The 653 document explains how network elements and networks that support 654 MPLS-TP can be managed using solutions that satisfy the 655 requirements defined in [RFC5951]. The relationship between MPLS-TP 656 management and OAM is described in the MPLS-TP framework [RFC5950] 657 document. 659 The MPLS MIB modules MPLS-TE-STD-MIB [RFC3812], PW-STD-MIB [RFC5601] 660 and MPLS-LSR-STD-MIB [RFC3813] and their associated MIB modules are 661 reused for MPLS based transport network management. 663 Fault management and performance management form key parts of 664 the Operations, Administration, and Maintenance (OAM) function. 665 MPLS-TP OAM is described in [MPLS-TP-OAM-FWK]. 667 5.1 MPLS-TP Tunnel 669 5.1.1 Gap Analysis 671 MPLS-TP tunnel can be operated over IP and/or ITU-T Carrier Code 672 (ICC) environments, below points capture the gaps in existing MPLS 673 MIB modules for managing the MPLS-TP networks. 675 - IP based environment 676 i. MPLS-TE-STD-MIB [RFC3812] does not support tunnel 677 Ingress/Egress identifier based on Global_ID and Node_ID 678 [RFC6370]. 679 ii. MPLS-TE-STD-MIB [RFC3812] does not support 680 co-routed/associated bidirectional tunnel configurations. 682 - ICC based environment 683 i. MPLS-TE-STD-MIB [RFC3812] does not support tunnel LSR 684 identifier based on ICC. 686 5.1.2 Recommendations 688 - New MIB definitions may be created for Global_Node_ID and/or 689 ICC configurations. 691 - MPLS-LSR-STD-MIB [RFC3813] MIB modules may be enhanced to identify 692 the nexthop based on MAC address for IP-less environments. 693 OutSegment may be extended to hold the MAC-address also for 694 IP-less environments. 696 - MPLS-TE-STD-MIB [RFC3812] and MPLS-LSR-STD-MIB may be 697 enhanced to provide static and signalling MIB module 698 extensions for co-routed/associated bidirectional LSPs. 700 5.2 MPLS-TP Pseudowire 702 5.2.1 Gap Analysis 704 MPLS-TP Pseudowire can be operated over IP and/or ICC environments, 705 below points capture the gaps in existing PW MIB modules 706 for managing the MPLS-TP networks. 708 [RFC6370] specifies an initial set of identifiers to be 709 used in MPLS-TP. These identifiers were chosen to be compatible with 710 existing MPLS, GMPLS, and PW definitions. 712 - IP based environment 713 i. PW-STD-MIB [RFC5601] does not support 714 PW end point identifier based on Global_ID and Node_ID. 715 ii. PW-MPLS-STD-MIB [RFC5602] does not support 716 its operation over co-routed/associated bidirectional tunnels. 718 - ICC based environment 719 i. PW-STD-MIB [RFC5601] does not support 720 PW end point identifier based on ICC. 722 5.2.2 Recommendations 724 - PW-MPLS-STD-MIB [RFC5602] can be enhanced to operate over 725 co-routed/associated bi-directional tunnel. 727 5.3 MPLS-TP Sections 729 5.3.1 Gap Analysis 731 The existing MPLS MIB modules do not support MPLS-TP sections. 733 5.3.2 Recommendations 734 Link specific and/or path/segment specific sections can be supported 735 by enhancing the IF-MIB [RFC2863], MPLS-TE-STD-MIB [RFC3812] and 736 PW-STD-MIB [RFC5601] MIB modules. 738 5.4 MPLS-TP OAM 740 5.4.1 Gap Analysis 742 MPLS manages the LSP and pseudowire faults through LSP ping 743 [RFC4379], VCCV [RFC5085], BFD for LSPs [RFC5884] and BFD for VCCV 744 [RFC5885] tools. 746 The MPLS MIB modules do not support the below MPLS-TP OAM functions: 748 o Continuity Check and Connectivity Verification 749 o Remote Defect Indication 750 o Alarm Reporting 751 o Lock Reporting 752 o Lock Instruct 753 o Client Failure Indication 754 o Packet Loss Measurement 755 o Packet Delay Measurement 757 5.4.2 Recommendations 759 New MIB module for BFD can be created to address all the gaps 760 mentioned in Section 5.4.1. (Gap Analysis). 762 5.5 MPLS-TP Protection Switching and Recovery 764 5.5.1 Gap Analysis 766 An important aspect that MPLS-TP technology provides is protection 767 switching. In general, the mechanism of protection switching 768 can be described as the substitution of a protection or standby 769 facility for a working or primary facility. 771 The MPLS MIB modules do not provide support for protection switching 772 and recovery of three different topologies (linear, ring and mesh) 773 available. 775 5.5.2 Recommendations 777 New MIB modules can be created to address all the gaps mentioned 778 in the 5.5.1 Gap Analysis section. 780 5.6 MPLS-TP Interfaces 782 5.6.1 Gap Analysis 783 As per [RFC6370], an LSR requires identification of the 784 node itself and of its interfaces. An interface is the attachment 785 point to a server layer MPLS-TP section or MPLS-TP tunnel. 787 The MPLS MIB modules do not provide support for configuring 788 the interfaces within the context of an operator. 790 5.6.2 Recommendations 792 New MIB definitions can be created to address the gaps mentioned 793 in the 5.6.1 Gap Analysis section. 795 6. An Introduction to the MPLS-TP MIB Modules 797 This section highlights new MIB modules that have been identified 798 as being required for MPLS-TP. This section also provides an overview 799 the purpose of each of the MIB modules within the MIB documents, what 800 it can be used for, and how it relates to the other MIB modules. 802 Note that each new MIB module (apart from Textual Conventions 803 modules) will contain one or more Compliance Statements to indicate 804 which objects must be supported in what manner to claim a specific 805 level of compliance. Additional text, either in the documents that 806 define the MIB modules or in separate Applicability Statements, will 807 define which Compliance Statements need to be conformed to in order 808 to provide specific MPLS-TP function. This document does not set any 809 requirements in that respect although some recommendations are 810 included in the sections that follow. 812 6.1 MPLS-TP MIB Modules 814 6.1.1 NEW MIB Modules for MPLS-TP 816 Four new MIB modules are identified as follows: 818 - Textual Conventions for MPLS-TP 820 - Identifiers for MPLS-TP 822 - LSR MIB Extensions for MPLS-TP 824 - TE MIB Extensions for MPLS-TP 826 Note that the MIB modules mentioned here are applicable for MPLS 827 operations as well. 829 6.1.2 Textual Conventions for MPLS-TP 831 A new MIB module needs to be written that will define textual 832 conventions [RFC2579] for MPLS-TP related MIB modules. These 833 conventions allow multiple MIB modules to use the same syntax and 834 format for a concept that is shared between the MIB modules. 836 For example, MEP identifier is used to identify maintenance entity 837 group end point within MPLS-TP networks. The textual convention 838 representing the MEP identifier should be defined in a new textual 839 convention MIB module. 841 All new extensions related to MPLS-TP are defined in the MIB module 842 and will be referenced by other MIB modules to support MPLS-TP. 844 6.1.3 Identifiers for MPLS-TP 846 New Identifiers describe managed objects that are used to model 847 common MPLS-TP identifiers [RFC6370]. 849 6.1.4 LSR MIB Extensions for MPLS-TP 851 MPLS-LSR-STD-MIB describes managed objects for modeling an MPLS Label 852 Switching Router (LSR). This puts it at the heart of the management 853 architecture for MPLS. 855 In the case of MPLS-TP, the MPLS-LSR-STD-MIB is extended to support 856 the MPLS-TP LSP's, which are co-routed or associated bidirectional. 857 This extended MIB is also applicable for modeling MPLS-TP tunnels. 859 6.1.5 Tunnel Extensions for MPLS-TP 861 MPLS-TE-STD-MIB describes managed objects that are used to model and 862 manage MPLS Traffic Engineered (TE) Tunnels. 864 MPLS-TP tunnels are very similar to MPLS-TE tunnels, but are 865 co-routed or associated bidirectionally. 867 The MPLS-TE-STD-MIB must be extended to support the MPLS-TP specific 868 attributes for the tunnel. 870 6.2 PWE3 MIB Modules for MPLS-TP 872 This section provides an overview of Pseudowire extension MIB 873 modules to meet the MPLS based transport network requirements. 875 6.2.1 New MIB Modules for MPLS-TP Pseudowires 877 Three new MIB modules are identified as follows: 879 - Pseudowire Extensions for MPLS-TP 881 - Pseudowire MPLS Extensions for MPLS-TP 883 - Pseudowire Textual Conventions for MPLS-TP 885 6.2.2 Pseudowire Textual Conventions for MPLS-TP 887 PW-TC-STD-MIB MIB defines textual conventions used for pseudowire 888 (PW) technology and for Pseudowire Edge-to-Edge Emulation (PWE3) MIB 889 Modules. A new textual convention MIB module is required to define 890 textual definitions for MPLS-TP specific Pseudowire attributes. 892 6.2.3 Pseudowire Extensions for MPLS-TP 894 PW-STD-MIB describes managed objects for modeling of Pseudowire 895 Edge-to-Edge services carried over a general Packet Switched Network. 896 This MIB module is extended to support MPLS-TP specific attributes 897 related to Pseudowires. 899 6.2.4 Pseudowire MPLS Extensions for MPLS-TP 901 PW-MPLS-STD-MIB defines the managed objects for Pseudowire 902 operations over MPLS LSR's. This MIB supports both, 903 manual and dynamically signaled PW's, point-to-point connections, 904 enables the use of any emulated service, MPLS-TE as outer tunnel 905 and no outer tunnel as MPLS-TE. 907 The newly extended MIB defines the managed objects, extending 908 PW-MPLS-STD-MIB, by supporting with or without MPLS-TP as outer 909 tunnel. 911 6.3 OAM MIB Modules for MPLS-TP 913 This section provides an overview of Operations, Administration, 914 and Maintenance (OAM) MIB modules for MPLS LSPs and Pseudowires. 916 6.3.1 New MIB Modules for OAM for MPLS-TP 918 Two new MIB modules are identified as follows: 920 - BFD MIB module 922 - OAM MIB module 924 6.3.2 BFD MIB module 926 BFD-STD-MIB defines managed objects for performing BFD operation in 927 IP networks. This MIB is modeled to support BFD protocol [RFC5880]. 929 A new MIB module needs to be written that will be an extension to 930 BFD-STD-MIB managed objects to support BFD operations on MPLS LSPs 931 and PWs. 933 6.3.3 Common OAM MIB modules 935 A new MIB module needs to be written that will define managed objects 936 for OAM maintenance identifiers i.e. Maintenance Entity Group 937 Identifiers (MEG), Maintenance Entity Group End-point (MEP), 938 Maintenance Entity Group Intermediate Point (MIP). Maintenance points 939 are uniquely associated with a MEG. Within the context of a MEG, MEPs 940 and MIPs must be uniquely identified. 942 6.4. Protection Switching and Recovery MIB Modules for MPLS-TP 944 This section provides an overview of protection switching and 945 recovery MIB modules for MPLS LSPs and Pseudowires. 947 6.4.1 New MIB Modules for MPLS Protection Switching and Recovery 949 Three new MIB modules are identified as follows: 951 - Linear Protection Switching MIB module 953 - Ring Protection Switching MIB module 955 - Mesh Protection Switching MIB module 957 6.4.2 Linear Protection Switching MIB module 959 A new MIB module needs to be written that will define managed objects 960 for linear protection switching of MPLS LSPs and Pseudowires. 962 6.4.3 Ring Protection Switching MIB module 964 A new MIB module will define managed objects for ring protection 965 switching of MPLS LSPs and Pseudowires. 967 6.4.4 Mesh Protection Switching MIB module 969 A new MIB module needs to be written that will define managed objects 970 for Mesh protection switching of MPLS LSPs and Pseudowires. 972 7. Management Options 974 This document applies only to scenarios where MIB modules are used to 975 manage the MPLS-TP network. It is not the intention of this document 976 to provide instructions or advice to implementers of management 977 systems, management agents, or managed entities. It is, however, 978 useful to make some observations about how the MIB modules described 979 above might be used to manage MPLS systems, if SNMP is used in the 980 management interface. 982 For MPLS specific management options, refer to [RFC4221] Section 12. 983 (Management Options). 985 8. Security Considerations 987 This document describes the interrelationships amongst the different 988 MIB modules relevant to MPLS-TP management and as such does not have 989 any security implications in and of itself. 991 Each IETF MIB document that specifies MIB objects for MPLS-TP must 992 provide a proper security considerations section that explains the 993 security aspects of those objects. 995 The attention of readers is particularly drawn to the security 996 implications of making MIB objects available for create or write 997 access through an access protocol such as SNMP. SNMPv1 by itself is 998 an insecure environment. Even if the network itself is made secure 999 (for example, by using IPSec), there is no control over who on the 1000 secure network is allowed to access the objects in this MIB. It is 1001 recommended that the implementers consider the security features as 1002 provided by the SNMPv3 framework. Specifically, the use of the 1003 User-based Security Model STD 62, RFC3414 [RFC3414], and the 1004 View-based Access Control Model STD 62, RFC 3415 [RFC3415], 1005 is recommended. 1007 It is then a customer/user responsibility to ensure that the SNMP 1008 entity giving access to an instance of each MIB module is properly 1009 configured to give access to only those objects, and to those 1010 principals (users) that have legitimate rights to access them. 1012 9. IANA Considerations 1014 This document has identified areas where additional MIB modules are 1015 neccessary for MPLS-TP. The new MIB modules recommended by this 1016 document will require OID assignments from IANA. However, this 1017 document makes no specific request for IANA action. 1019 10. Acknowledgements 1021 The authors would like to thank Eric Gray, Thomas Nadeau, Benjamin 1022 Niven-Jenkins, Saravanan Narasimhan, Joel Halpern, David Harrington, 1023 and Stephen Farrell for their valuable comments. 1025 This document also benefited from review by participants in ITU-T 1026 Study Group 15. 1028 11. References 1030 11.1 Normative References 1032 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 1033 MIB using SMIv2", RFC 2863, June 2000. 1035 [RFC3811] Nadeau, T. and J. Cucchiara, "Definition of Textual 1036 Conventions and for Multiprotocol Label Switching (MPLS) 1037 Management", RFC 3811, June 2004. 1039 [RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau, 1040 "Multiprotocol Label Switching (MPLS) Traffic 1041 Engineering (TE) Management Information Base (MIB)", 1042 RFC 3812, June 2004. 1044 [RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau, 1045 "Multiprotocol Label Switching (MPLS) Label Switching 1046 (LSR) Router Management Information Base (MIB)", RFC 3813, 1047 June 2004. 1049 [RFC3814] Nadeau, T., Srinivasan, C., and A. Viswanathan, 1050 "Multiprotocol Label Switching (MPLS) FEC-To-NHLFE 1051 (FTN) Management Information Base", RFC3814, June 1052 2004. 1054 [RFC3815] Cucchiara, J., Sjostrand, H., and Luciani, J., 1055 "Definitions of Managed Objects for the 1056 Multiprotocol Label Switching (MPLS), Label 1057 Distribution Protocol (LDP)", RFC 3815, June 2004. 1059 [RFC4220] Dubuc, M., Nadeau, T., and J. Lang, "Traffic 1060 Engineering Link Management Information Base", RFC 1061 4220, November 2005. 1063 [RFC4221] Nadeau, T., Srinivasan, C., and A. Farrel, 1064 "Multiprotocol Label Switching (MPLS) Management 1065 Overview", RFC 4221, November 2005. 1067 [RFC4801] T. Nadeau and A. Farrel, Ed., "Definitions of Textual 1068 Conventions for Generalized Multiprotocol Label Switching 1069 (GMPLS) Management", RFC4801, Feb. 2007. 1071 [RFC4802] T. D. Nadeau and A. Farrel, "Generalized Multiprotocol 1072 Label Switching (GMPLS) Traffic Engineering Management 1073 Information Base", RFC4802, Feb., 2007. 1075 [RFC4803] T. D. Nadeau and A. Farrel, "Generalized Multiprotocol 1076 Label Switching (GMPLS) Label Switching Router (LSR) 1077 Management Information Base", RFC4803, Feb., 2007. 1079 [RFC5542] Nadeau, T., Ed., Zelig, D., Ed., and O. Nicklass, Ed., 1080 "Definitions of Textual Conventions for Pseudowire (PW) 1081 Management", RFC 5542, May 2009. 1083 [RFC5601] Nadeau, T., Ed. and D. Zelig, Ed. "Pseudowire (PW) 1084 Management Information Base (MIB)", RFC 5601, July 2009. 1086 [RFC5602] Zelig, D., Ed., and T. Nadeau, Ed., "Pseudowire (PW) over 1087 MPLS PSN Management Information Base (MIB)", RFC 5602, 1088 July 2009. 1090 [RFC5603] Zelig, D., Ed., and T. Nadeau, Ed., "Ethernet Pseudowire 1091 (PW) Management Information Base (MIB)", RFC 5603, 1092 July 2009. 1094 [RFC5604] Nicklass, O., "Managed Objects for Time Division 1095 Multiplexing (TDM) over Packet Switched Networks (PSNs)", 1096 RFC5604, July 2009. 1098 11.2 Informative References 1100 [RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 1101 "Structure of Management Information Version 2 1102 (SMIv2)", STD 58, RFC 2578, April 1999. 1104 [RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 1105 "Textual Conventions for SMIv2", STD 58, RFC 2579, 1106 April 1999. 1108 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 1109 "Conformance Statements for SMIv2", STD 58, RFC 2580, 1110 April 1999. 1112 [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, 1113 "Multiprotocol Label Switching Architecture", RFC 3031, 1114 March 2001. 1116 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 1117 "Introduction and Applicability Statements for 1118 Internet-Standard Management Framework", RFC 3410, 1119 December 2002. 1121 [RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security 1122 Model (USM) for version 3 of the Simple Network 1123 Management Protocol (SNMPv3)", STD 62, RFC 3414, 1124 December 2002. 1126 [RFC3415] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 1127 Access Control Model (VACM) for the Simple Network 1128 Management Protocol (SNMP)", STD 62, RFC 3415, December 1129 2002. 1131 [RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau, 1132 "Multiprotocol Label Switching (MPLS) Traffic Engineering 1133 (TE) Management Information Base (MIB)", RFC 3812, June 1134 2004. 1136 [RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau, 1137 "Multiprotocol Label Switching (MPLS) Label Switching 1138 Router (LSR) Management Information Base (MIB)", RFC 3813, 1139 June 2004. 1141 [RFC3931] Lau, J., Townsley, M., and I. Goyret, "Layer Two Tunneling 1142 Protocol - Version 3 (L2TPv3)", RFC 3931, March 2005. 1144 [RFC3945] Mannie, E. et.al., "Generalized Multi-Protocol Label 1145 Switching (GMPLS) Architecture", IETF RFC 3945, October 1146 2004. 1148 [RFC3985] Bryant, S. and P. Pate, "Pseudo Wire Emulation Edge-to- 1149 Edge (PWE3) Architecture", RFC 3985, March 2005. 1151 [RFC4197] Riegel, M., "Requirements for Edge-to-Edge Emulation of 1152 Time Division Multiplexed (TDM) Circuits over Packet 1153 Switching Networks", RFC4197, October 2005. 1155 [RFC4377] Nadeau, T., Morrow, M., Swallow, G., Allan, D., and S. 1156 Matsushima, "Operations and Management (OAM) Requirements 1157 for Multi-Protocol Label Switched (MPLS) Networks", 1158 RFC 4377, March 2006. 1160 [RFC4378] Allan, D. and T. Nadeau, "A Framework for Multi-Protocol 1161 Label Switching (MPLS) Operations and Management (OAM)", 1162 RFC 4378, March 2006. 1164 [RFC4379] Kompella, K. and G. Swallow, "Detecting Multi-Protocol 1165 Label Switched (MPLS) Data Plane Failures", RFC 4379, 1166 March 2006. 1168 [RFC4447] Martini, L., Rosen, E., El-Aawar, N., Smith, T., and 1169 G. Heron, "Pseudowire Setup and Maintenance Using the 1170 Label Distribution Protocol (LDP)", RFC 4447, 1171 April 2006. 1173 [RFC4805] Nicklass, O., Ed., "Definitions of Managed Objects for the 1174 DS1, J1, E1, DS2, and E2 Interface Types", RFC 4805, March 1175 2007. 1177 [RFC5085] Nadeau, T. and C. Pignataro, "Pseudowire Virtual 1178 Circuit Connectivity Verification (VCCV): A Control 1179 Channel for Pseudowires", RFC 5085, December 2007. 1181 [RFC5601] Nadeau, T., Ed. and D. Zelig, Ed. "Pseudowire (PW) 1182 Management Information Base (MIB)", RFC 5601, July 2009. 1184 [RFC5602] Zelig, D., Ed., and T. Nadeau, Ed., "Pseudowire (PW) over 1185 MPLS PSN Management Information Base (MIB)", RFC 5602, 1186 July 2009. 1188 [RFC5654] Niven-Jenkins, B., et al, "MPLS-TP Requirements", 1189 RFC5654, September 2009. 1191 [RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding 1192 Detection", RFC 5880, June 2010. 1194 [RFC5884] Aggarwal, R., Kompella, K., Nadeau, T., and G. Swallow, 1195 "Bidirectional Forwarding Detection (BFD) For MPLS 1196 Label Switched Paths (LSPs)", RFC 5884, June 2010. 1198 [RFC5885] Nadeau, T. and C. Pignataro, "Bidirectional 1199 Forwarding Detection (BFD) for the Pseudowire 1200 Virtual Circuit Connectivity Verification (VCCV)", 1201 RFC5885, June 2010. 1203 [RFC5950] Gray, E., Mansfield, S., Lam, K., 1204 "MPLS-TP Network Management Framework", RFC 5950, 1205 September 2010. 1207 [RFC5951] Gray, E., Mansfield, S., Lam, K., "MPLS TP 1208 Network Management Requirements", RFC 5951, September 1209 2010. 1211 [RFC6370] Bocci, M., Swallow, G., and E. Gray, "MPLS Transport 1212 Profile (MPLS-TP) Identifiers", RFC 6370, September 2011. 1214 [MPLS-TP-OAM-FWK] Busi, I. and B. Niven-Jenkins, "MPLS-TP OAM 1215 Framework and Overview", 2009, 1216 . 1218 12. Authors' Addresses 1220 Daniel King 1221 Old Dog Consulting 1222 UK 1223 Email: daniel@olddog.co.uk 1225 Venkatesan Mahalingam 1226 Aricent 1227 India 1228 Email: venkat.mahalingams@gmail.com 1230 Adrian Farrel 1231 Old Dog Consulting 1232 UK 1233 Email: adrian@olddog.co.uk 1235 Scott Mansfield 1236 Ericsson 1237 300 Holger Way, San Jose, CA 95134, US 1238 Phone: +1 724 931 9316 1239 Email: scott.mansfield@ericsson.com 1241 Jeong-dong Ryoo 1242 ETRI 1243 161 Gajeong, Yuseong, Daejeon, 305-700, South Korea 1244 Phone: +82 42 860 5384 1245 Email: ryoo@etri.re.kr 1247 A S Kiran Koushik 1248 Cisco Systems Inc. 1249 Email: kkoushik@cisco.com 1251 A. Karmakar 1252 Cisco Systems Inc. 1253 Email: akarmaka@cisco.com 1255 Sam Aldrin 1256 Huawei Technologies, co. 1257 2330 Central Express Way, 1258 Santa Clara, CA 95051, USA 1259 Email: aldrin.ietf@gmail.com