idnits 2.17.1 draft-farrel-mpls-tp-mib-management-overview-02.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 (September 21, 2010) is 4965 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) == Outdated reference: A later version (-07) exists of draft-ietf-mpls-tp-identifiers-02 Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group A.Farrel 3 Internet-Draft D. King 4 Intended status: Informational Old Dog Consulting 5 Expires: March 21, 2011 M.Venkatesan 6 Aricent 7 J. Ryoo 8 ETRI 9 S. Mansfield 10 Ericsson 11 K. Koushik 12 Cisco Systems, Inc. 13 September 21, 2010 15 Multiprotocol Label Switching Transport Profile (MPLS-TP) 16 MIB-based Management Overview 17 draft-farrel-mpls-tp-mib-management-overview-02.txt 19 Abstract 21 A range of Management Information Base (MIB) modules has been 22 developed to help model and manage the various aspects of 23 Multiprotocol Label Switching (MPLS) networks. These MIB modules are 24 defined in separate documents that focus on the specific areas of 25 responsibility of the modules that they describe. 27 The MPLS Transport Profile (MPLS-TP) is a profile of MPLS 28 functionality specific to the construction of packet-switched 29 transport networks. 31 This document describes the MIB-based management architecture for 32 MPLS-TP and indicates the interrelationships between the different 33 MIB modules used for MPLS-TP network management. 35 This document is a product of a joint Internet Engineering Task Force 36 (IETF) / International Telecommunication Union Telecommunication 37 Standardization Sector (ITU-T) effort to include an MPLS Transport 38 Profile within the IETF MPLS and PWE3 architectures to support the 39 capabilities and functionalities of a packet transport network as 40 defined by the ITU-T. 42 This Informational Internet-Draft is aimed at achieving IETF 43 Consensus before publication as an RFC and will be subject to an IETF 44 Last Call. 46 [RFC Editor, please remove this note before publication as an RFC and 47 insert the correct Streams Boilerplate to indicate that the published 48 RFC has IETF Consensus.] 50 Status of this Memo 52 This Internet-Draft is submitted to IETF in full conformance with the 53 provisions of BCP 78 and BCP 79. 55 Internet-Drafts are working documents of the Internet Engineering 56 Task Force (IETF), its areas, and its working groups. Note that 57 other groups may also distribute working documents as Internet- 58 Drafts. 60 Internet-Drafts are draft documents valid for a maximum of six months 61 and may be updated, replaced, or obsoleted by other documents at any 62 time. It is inappropriate to use Internet-Drafts as reference 63 material or to cite them other than as "work in progress." 65 The list of current Internet-Drafts can be accessed at 66 http://www.ietf.org/ietf/1id-abstracts.txt. 68 The list of Internet-Draft Shadow Directories can be accessed at 69 http://www.ietf.org/shadow.html. 71 This Internet-Draft will expire on March 21, 2011. 73 Copyright Notice 75 Copyright (c) 2010 IETF Trust and the persons identified as the 76 document authors. All rights reserved. 78 This document is subject to BCP 78 and the IETF Trust's Legal 79 Provisions Relating to IETF Documents 80 (http://trustee.ietf.org/license-info) in effect on the date of 81 publication of this document. Please review these documents 82 carefully, as they describe your rights and restrictions with respect 83 to this document. Code Components extracted from this document must 84 include Simplified BSD License text as described in Section 4.e of 85 the Trust Legal Provisions and are provided without warranty as 86 described in the Simplified BSD License. 88 Table of Contents 90 1. Introduction.................................................3 91 2. Terminology..................................................4 92 3. The SNMP Management Framework................................4 93 4. Summary of MPLS-TP Management Function.......................4 94 5. Overview of Existing Work....................................4 95 5.1. MPLS Management Overview and Requirements...............5 96 5.2. An Introduction to the MPLS and Pseudowire MIB Modules..5 97 5.2.1. Structure of the MPLS MIB OID Tree...............5 98 5.2.2. Textual Convention Modules.......................6 99 5.2.3. Mapping Data to LSPs.............................7 100 5.2.4. Label Switching Router Modules...................8 101 5.2.5. Label Switched Path Modules......................8 102 5.2.6. Pseudowire Modules...............................8 103 5.2.7. Routing and Traffic Engineering..................10 104 5.2.8. Resiliency.......................................10 105 5.2.9. Fault Management and Performance Management......10 106 5.2.10. MIB Module Interdependencies....................11 107 5.2.11. Dependencies on External MIB Modules............12 108 6. Applicability of MPLS MIB modules to MPLS-TP.................13 109 6.1 Gap Analysis............................................13 110 6.1.1 MPLS-TP Tunnel....................................13 111 6.1.2 MPLS-TP Pseudowire................................13 112 6.1.3 MPLS-TP Sections..................................13 113 6.1.4 MPLS-TP OAM.......................................13 114 6.1.5 MPLS-TP Protection Switching......................14 115 6.1.6 MIB Module Interdependencies......................15 116 7. Interfaces...................................................17 117 7.1. MPLS Tunnels as Interfaces..............................17 118 7.2. Application of the Interfaces Group to TE Links.........17 119 7.3. References to Interface Objects from MPLS MIB Modules...17 120 8. Management Options...........................................18 121 9. Security Considerations......................................18 122 10. IANA Considerations.........................................18 123 11. Acknowledgements............................................18 124 12. Normative References........................................19 125 13. Informational References....................................19 126 14. Authors' Addresses..........................................20 128 1. Introduction 130 The MPLS Transport Profile (MPLS-TP) is a packet transport 131 technology based on a profile of the MPLS functionality specific 132 to the construction of packet-switched transport networks. 133 MPLS is described in [RFC3031] and requirements for MPLS-TP are 134 specified in [RFC5654]. 136 A range of Management Information Base (MIB) modules has been 137 developed to help model and manage the various aspects of 138 Multiprotocol Label Switching (MPLS) networks. These MIB modules 139 are defined in separate documents that focus on the specific areas of 140 responsibility of the modules that they describe. 142 An MPLS-TP network can be operated via static provisioning of 143 transport paths, or the elective use of a Generalized MPLS (GMPLS) 144 control plane to support dynamic provisioning of transport paths. 146 This document describes the MIB-based management architecture for 147 MPLS-TP and indicates the interrelationships between the existing 148 MIB modules used for MPLS-TP network management. The document also 149 indentifies areas where additional MIB modules would be required to 150 support an MPLS-TP network. 152 This document is a product of a joint Internet Engineering Task Force 153 (IETF) / International Telecommunication Union Telecommunication 154 Standardization Sector (ITU-T) effort to include an MPLS Transport 155 Profile within the IETF MPLS and PWE3 architectures to support the 156 capabilities and functionalities of a packet transport network. 158 2. Terminology 160 This document also uses terminology from the MPLS architecture 161 document [RFC3031] and the following MPLS related MIB modules: 162 MPLS TC MIB [RFC3811], MPLS LSR MIB [RFC3813], MPLS TE MIB [RFC3812], 163 MPLS LDP MIB [RFC3815], MPLS FTN MIB [RFC3814] and TE LINK MIB 164 [RFC4220]. 166 3. The SNMP Management Framework 168 Managed objects are accessed via a virtual information store, termed 169 the Management Information Base or MIB. MIB objects are generally 170 accessed through the Simple Network Management Protocol (SNMP). 171 Objects in the MIB are defined using the mechanisms defined in the 172 Structure of Management Information (SMI). 174 For a detailed overview of the documents that describe the current 175 Internet-Standard Management Framework, please refer to section 7 of 176 RFC 3410 [RFC3410]. 178 This document discusses MIB modules that are compliant to the SMIv2, 179 which is described in [RFC2578], [RFC2579] and [RFC2580]. 181 4. Summary of MPLS-TP Management Function 183 The management of the MPLS-TP networks is separable from that of its 184 client networks so that the same means of management can be used 185 regardless of the client. The management functions of MPLS-TP 186 includes fault management, configuration management, performance 187 monitoring, and security management. 189 5. Overview of Existing Work 191 This section describes the existing tools and techniques for 192 managing and modeling MPLS networks, devices, and protocols. It does 193 not focus on MPLS-TP, but is intended to provide a description of the 194 tool kit that is already available. 196 The following section (Section 6. Applicability of MPLS MIB modules 197 to MPLS-TP) of this document describes the applicability of the MPLS 198 and optional use of GMPLS MIB modules to MPLS-TP and examines the 199 additional MIB modules and objects that would be required for 200 managing an MPLS-TP network. 202 5.1. MPLS Management Overview and Requirements 204 [RFC4378] outlines how data plane protocols can assist in providing 205 the Operations and Management (OAM) requirements outlined in 206 [RFC4377] and how it is applied to the management functions of fault, 207 configuration, accounting, performance, and security (commonly known 208 as FCAPS) for MPLS networks. 210 [RFC4221] describes the management architecture for MPLS. In 211 particular, it describes how the managed objects defined in various 212 MPLS-related MIB modules model different aspects of MPLS, as well as 213 the interactions and dependencies between each of these MIB modules. 215 [RFC4377] describes the requirements for user and data plane OAM and 216 applications for MPLS. 218 [RFC5654] describes the requirements for the optional use of a 219 control plane to support dynamic provisioning of MPLS-TP transport 220 paths. The MPLS-TP LSP control plane is based on GMPLS and is 221 described in [RFC3945]. 223 5.2. An Introduction to the MPLS and Pseudowire MIB Modules 225 5.2.1. Structure of the MPLS MIB OID Tree 227 The MPLS MIB OID tree has the following structure compatible for 228 MPLS-TP. 230 mib-2 -- RFC 2578 [RFC2578] 231 | 232 +-transmission 233 | | 234 | +- mplsStdMIB 235 | | | 236 | | +- mplsTCStdMIB -- MPLS-TC-STD-MIB [RFC3811] 237 | | | 238 | | +- mplsLsrStdMIB -- MPLS-LSR-STD-MIB [RFC3813] 239 | | | 240 | | +- mplsTeStdMIB -- MPLS-TE-STD-MIB [RFC3812] 241 | | | 242 | | +- mplsLdpStdMIB -- MPLS-LDP-STD-MIB [RFC3815] 243 | | | 244 | | +- mplsLdpGenericStdMIB -- MPLS-LDP-GENERIC-STD-MIB 245 | | | 246 | | +- mplsFTNStdMIB -- MPLS-FTN-STD-MIB [RFC3814] 247 | | | 248 | | +- gmplsTCStdMIB -- GMPLS-TC-STD-MIB [RFC4801] 249 | | | 250 | | +- gmplsTeStdMIB -- GMPLS-TE-STD-MIB [RFC4802] 251 | | | 252 | | +- gmplsLsrStdMIB -- GMPLS-LSR-STD-MIB [RFC4803] 253 | | | 254 | | +- gmplsLabelStdMIB -- GMPLS-LABEL-STD-MIB [RFC4803] 255 | | 256 | +- teLinkStdMIB -- TE-LINK-STD-MIB [RFC4220] 257 | | 258 | +- pwStdMIB -- PW-STD-MIB [RFC5601] 259 | 260 +- ianaGmpls -- IANA-GMPLS-TC-MIB [RFC4802] 261 | 262 +- ianaPwe3MIB -- IANA-PWE3-MIB [RFC5601] 263 | 264 +- pwEnetStdMIB -- PW-ENET-STD-MIB [RFC5603] 265 | 266 +- pwMplsStdMIB -- PW-MPLS-STD-MIB [RFC5602] 267 | 268 +- pwTDMMIB -- PW-TDM-MIB [RFC5604] 269 | 270 +- pwTcStdMIB -- PW-TC-STD-MIB [RFC5542] 272 Note: The OIDs for MIB modules are assigned and managed by IANA. 273 They can be found in the referenced MIB documents. 275 5.2.2. Textual Convention Modules 277 MPLS-TC-STD-MIB [RFC3811] contains the Textual Conventions for 278 Multiprotocol Label Switching (MPLS) networks. These Textual 279 Conventions should be imported by MIB modules which manage MPLS 280 networks. 282 5.2.3. Mapping Data to LSPs 284 MPLS is a packet switching protocol that operates between the 285 Network layer and the data link layer in the OSI model. 287 There is a clean separation between the control and forwarding 288 planes in the MPLS protocol. This helps in easy portability and 289 extensibility to the forwarding functions. 291 A router which supports MPLS is known as a "Label Switching Router", 292 or LSR. An LSR implements the control and forwarding plane of MPLS. 294 The LSR "control plane" provides information in terms of label 295 bindings which are part of the information used to populate 296 forwarding tables in an LSR. An LSR determines which label bindings 297 to seek and retain based on configuration and other information. 299 The LSR forwarding plane then uses an index which is the incoming 300 interface and label (usually of 20-bit length) to forward the 301 packet. 303 Each entry in this forwarding table corresponds to a forwarding 304 equivalence class (FEC). This can be loosely defined as the set of 305 characteristics that are being shared by the packets which will be 306 forwarded in a similar fashion and may share the same label. 308 MPLS packets are encapsulated by one more more label entries 309 referred to as the label stack. Each label stack entry consists of a 310 label, the 3 TC-bits for classifying the Traffic Class, the bottom of 311 stack bit, and TTL. 313 The ingress and the egress devices of the MPLS network are called 314 Label Edge routers. These routers "Push" an MPLS label into an 315 incoming packet and "pop" off the MPLS label from an outgoing packet 316 respectively. 318 At the ingress when an unlabeled packet enters, one or more label 319 stack entries are (each label stack with one or more labels) is 320 prefixed to this packet based on its FEC as discussed above. In 321 addition, the "MPLS-specific" L2 encapsulation (including, for 322 instance, the MPLS PID) is also added at the ingress. Then the packet 323 is sent to the next-hop router for further processing. The next-hop 324 router examines the topmost label in the label stack and then does a 325 swap, 'push' or 'pop' operations based on the contents. 327 A label stack entry can be 'popped' or removed from the top of the 328 label stack or a label stack entry is 'pushed' or inserted into the 329 top of the stack based on the FEC information. 331 When a 'swap' operation is executed, the topmost label stack entry is 332 replaced with a different one and the depth of the label stack 333 remains the same. After the swap the packet is forwarded based on the 334 new entry. 336 5.2.4. Label Switching Router Modules 338 MPLS-LSR-STD-MIB [RFC3813] describes the managed objects for modeling 339 a Multiprotocol Label Switching (MPLS) [RFC3031] LSR. 341 MPLS-TP is specific to the use of MPLS in transport networks. 342 According to [RFC5654] multipoint-to-point LSPs do not form part of 343 MPLS-TP, so multipoint-to-point cross connects are not configured in 344 this MIB module for use in MPLS-TP. 346 5.2.5. Label Switched Path Modules 348 The path taken through the MPLS domain by a packet is referred to as 349 a label switched path (LSP). It is possible that this path may not be 350 understood or completely stored in one LSR within the MPLS domain. 352 This label switched path can be programmed using a variety of 353 mechanisms. These include manual programming and using a signalling 354 protocol. 356 RSVP-TE (Resource reservation protocol for Traffic Engineering) is 357 normally used for signalling LSPs used for Traffic Engineering. 359 5.2.6. Pseudowire Modules 361 The PW (Pseudowire) MIB modules architecture provides a layered 362 modular model into which any supported emulated service can be 363 connected to any supported packet switched network (PSN) type. This 364 specific MIB module provides the glue for mapping between the 365 emulated service onto the native PSN service. As such, the defining 366 of a PW emulated service requires the use of at least three types of 367 MIB modules. 369 Starting from the emulated service, the first type is a service- 370 specific module, which is dependent on the emulated signal type. 371 These modules are defined in other documents. 373 The second type is this module, the PW-STD-MIB module, which 374 configures general parameters of the PW that are common to all types 375 of emulated services and PSN types. 377 The third type of module is a PSN-specific module. There is a 378 different module for each type of PSN. These modules associate the 379 PW with one or more "tunnels" that carry the service over the PSN. 380 These modules are defined in other documents. 382 PW-STD-MIB [RFC5601] defines a MIB module that can be 383 used to manage pseudowire (PW) services for transmission over a 384 Packet Switched Network (PSN) [RFC3931] [RFC4447]. This MIB module 385 provides generic management of PWs that is common to all types of 386 PSN and PW services defined by the IETF PWE3 Working Group. 388 PW-MPLS-STD-MIB [RFC5602] describes a model for managing pseudowire 389 services for transmission over different flavors of MPLS tunnels. 390 The general PW MIB module [RFC5601] defines the parameters global to 391 the PW regardless of the underlying Packet Switched Network (PSN) 392 and emulated service. This document is applicable for PWs that use 393 MPLS PSN type in the PW-STD-MIB. 395 This document describes the MIB objects that define pseudowire 396 association to the MPLS PSN, in a way that is not specific to the 397 carried service. 399 Together, [RFC3811] and [RFC3812] describe the modeling of an MPLS 400 tunnel, and a tunnel's underlying cross-connects. This MIB module 401 supports MPLS-TE PSN, non-TE MPLS PSN (an outer tunnel created by the 402 Label Distribution Protocol (LDP) or manually), and MPLS PW label 403 only (no outer tunnel). 405 PW-ENET-STD-MIB [RFC5603] describes a model for managing Ethernet 406 pseudowire services for transmission over a PSN. This MIB module is 407 generic and common to all types of PSNs supported in the Pseudowire 408 Emulation Edge-to-Edge (PWE3) architecture [RFC3985], which describes 409 the transport and encapsulation of L1 and L2 services over supported 410 PSN types. 412 In particular, the MIB module associates a port or specific VLANs on 413 top of a physical Ethernet port or a virtual Ethernet interface (for 414 Virtual Private LAN Service (VPLS)) to a point-to-point PW. It is 415 complementary to the PW-STD-MIB [RFC5601], which manages the generic 416 PW parameters common to all services, including all supported PSN 417 types. 419 PW-TDM-MIB [RFC5604] describes a model for managing TDM pseudowires, 420 i.e., TDM data encapsulated for transmission over a Packet Switched 421 Network (PSN). The term TDM in this document is limited to the 422 scope of Plesiochronous Digital Hierarchy (PDH). It is currently 423 specified to carry any TDM Signals in either Structure Agnostic 424 Transport mode (E1, T1, E3, and T3) or in Structure Aware 425 Transport mode (E1, T1, and NxDS0) as defined in the Pseudowire 426 Emulation Edge-to-Edge (PWE3) TDM Requirements document [RFC4197]. 428 The PW MIB modules architecture provides a layered modular model 429 into which any supported emulated service can be connected to any 430 supported PSN type. This specific MIB module provides the glue for 431 mapping between the emulated service onto the native PSN service. As 432 such, the defining of a PW emulated service requires the use of at 433 least three types of MIB modules. 435 5.2.7. Routing and Traffic Engineering 437 In MPLS traffic engineering, its possible to specify explicit routes 438 or choose routes based on QOS metrics in setting up a path such that 439 some specific data can be routed around network hot spots. 441 MPLS-TE-STD-MIB [RFC3812] describes managed objects for modeling a 442 Multiprotocol Label Switching (MPLS) [RFC3031] based traffic 443 engineering. This MIB module should be used in conjunction with the 444 companion document [RFC3813] for MPLS based traffic engineering 445 configuration and management. 447 5.2.8. Resiliency 449 MPLS Fast Reroute is a local restoration network resiliency mechanism 450 in MPLS TE for link and node protection. Two different modes of local 451 protection are described in the [RFC4090] to protect LSP. 453 o One-to-One Backup 454 o Facility Backup 456 Facility backup uses label stacking to reroute multiple protected TE 457 LSPs using a single backup TE LSP. One-to-one backup does not use 458 label stacking, and every protected TE LSP requires a dedicated 459 backup TE LSP. 461 MPLS-FRR-GENERAL-STD-MIB [draft-ietf-mpls-fastreroute-mib-14] 462 contains objects that apply to any MPLS LSR implementing MPLS TE fast 463 reroute functionality. 465 MPLS-FRR-ONE2ONE-STD-MIB [draft-ietf-mpls-fastreroute-mib-14] 466 contains objects that apply to one-to-one backup method. 468 MPLS-FRR-FACILITY-STD-MIB [draft-ietf-mpls-fastreroute-mib-14] 469 contains objects that apply to facility backup method. 471 5.2.9. Fault Management and Performance Management 473 MPLS manages the LSP and Pseudowire faults through LSP ping 474 [RFC4379], VCCV [RFC5085], BFD for LSPs [RFC5884] and BFD for VCCV 475 [RFC5885] tools. 477 There is no MIB management model currently available for the above 478 fault management tools. 480 There is no performance management tool currently available for MPLS. 482 5.2.10. MIB Module Interdependencies 484 This section provides an overview of the relationship between the 485 MPLS MIB modules for managing MPLS networks. More details of these 486 relationships are given below. 488 The relationship "A --> B" means A depends on B and that MIB module 489 A uses an object, object identifier, or textual convention defined 490 in MIB module B, or that MIB module A contains a pointer (index or 491 RowPointer) to an object in MIB module B. 493 +-------> MPLS-TC-STD-MIB <-----------------------------------------+ 494 | ^ | 495 | | | 496 | MPLS-LSR-STD-MIB <--------------------------------+ | 497 | | | 498 +<----------------------- MPLS-LDP-STD-MIB ---------------->+ | 499 | ^ | | 500 | | | | 501 +<-- MPLS-LDP-GENERIC-STD-MIB ------>+ | | 502 | | | 503 +<------ MPLS-FTN-STD-MIB ---------+----------------------->+ | 504 | ^ | | 505 | | | | 506 +<------------- MPLS-TE-STD-MIB ->+ | 507 ^ | GMPLS-TC-STD-MIB ------------>+ 508 | | ^ | 509 | | | | 510 | +---+ +<-- GMPLS-LABEL-STD-MIB -->+ 511 | | ^ ^ ^ | 512 | | | | | | 513 +----> PW-TC-STD-MIB | | GMPLS-LSR-STD-MIB --------------->+ 514 | | | ^ ^ | 515 | | | | | | 516 | IANA-PWE3-MIB | | | | IANA-GMPLS-TC-MIB | 517 | ^ | | | | ^ | 518 | | | | | | | | 519 | | | +<--- GMPLS-TE-STD-MIB ------------->+ 520 | | | ^ | 521 +<--- PW-STD-MIB <------+ | | | 522 | | | | | 523 +<--- PW-ENET-STD-MIB ->+ | | | 524 | ^ | | | 525 | | | | | 526 +<---------------- PW-MPLS-STD-MIB -------------------------------->+ 528 Thus: 530 - All the MPLS MIB modules depend on MPLS-TC-STD-MIB. 532 - All the GMPLS MIB modules depend on GMPLS-TC-STD-MIB. 534 - All the PW MIB modules depend on PW-TC-STD-MIB. 536 - MPLS-LDP-STD-MIB, MPLS-TE-STD-MIB, MPLS-FTN-STD-MIB, 537 GMPLS-LSR-STD-MIB, and PW-MPLS-STD-MIB contain references to 538 objects in MPLS-LSR-STD-MIB. 540 - MPLS-LDP-GENERIC-STD-MIB contains references to objects in 541 MPLS-LDP-STD-MIB. 543 - MPLS-FTN-STD-MIB, PW-MPLS-STD-MIB, and GMPLS-TE-STD-MIB contain 544 references to objects in MPLS-TE-STD-MIB. 546 - PW-MPLS-STD-MIB, and PW-ENET-STD-MIB contains references to 547 objects in PW-STD-MIB. 549 - PW-STD-MIB contains references to objects in IANA-PWE3-MIB. 551 - GMPLS-TE-STD-MIB contains references to objects in 552 IANA-GMPLS-TC-MIB. 554 - GMPLS-LSR-STD-MIB contains references to objects in 555 GMPLS-LABEL-STD-MIB. 557 Note that there is a textual convention (MplsIndexType) defined in 558 MPLS-LSR-STD-MIB that is imported by MPLS-LDP-STD-MIB. 560 5.2.11. Dependencies on External MIB Modules 562 In addition to the MPLS management overview [RFC4221] 563 section 4.12 (Dependencies on External MIB Modules), some of the 564 existing MPLS MIBs, PW MIBs and GMPLS MIBs are re-used with 565 extensions for achieving the MPLS-TP functionality. 567 MPLS MIB modules have dependencies with the TE-LINK-STD-MIB 568 for maintaining the traffic engineering information. 570 MPLS MIB modules depend on the CSPF module to get the paths for MPLS 571 tunnel to traverse to reach the end point of the tunnel and BFD 572 module to verify the data-plane failures of LSPs and PWs. 574 Finally, all of the MIB modules import standard textual conventions 575 such as integers, strings, timestamps, etc., from the MIB modules in 576 which they are defined. 578 This is business as usual for a MIB module and is not discussed 579 further in this document. 581 6. Applicability of MPLS MIB modules to MPLS-TP 583 [RFC5951] specifies the requirements for the management of 584 equipment used in networks supporting an MPLS-TP. It also details the 585 essential network management capabilities for operating networks 586 consisting of MPLS-TP equipment. 588 [RFC5950] provides the network management framework for 589 MPLS-TP. The document explains how network elements and networks that 590 support MPLS-TP can be managed using solutions that satisfy the 591 requirements defined in [RFC5951]. The relationship between 592 MPLS-TP management and OAM is described in the MPLS-TP framework 593 [RFC5950] document. 595 Fault management and performance management form key parts of 596 Operations, Administration, and Maintenance (OAM) function. MPLS-TP 597 OAM is described in [MPLS-TP-OAM-FWK]. 599 This section also provides the information about the extensions of 600 existing MPLS MIB modules for MPLS-TP and the new MPLS-TP MIB 601 modules. 603 6.1 Gap Analysis 605 6.1.1 MPLS-TP Tunnel 607 MPLS-TP tunnel table MPLSTP-STD-MIB is an extension of 608 MPLS tunnel table [RFC3812] to support MPLS-TP requirements. 609 Tunnel identifiers are defined based on [MPLS-TP-IDENTIFIERS]. 611 6.1.2 MPLS-TP Pseudowire 613 MPLS-TP Pseudowire table MPLSTP-STD-MIB is an extension of 614 Pseudowire table MPLS-PW-STD-MIB to support MPLS-TP requirements. 615 Pseudowire identifiers are defined based on [MPLS-TP-IDENTIFIERS]. 617 6.1.3 MPLS-TP Sections 619 This section needs to be updated with the section layer network 620 managed objects based on the draft-ietf-mpls-tp-data-plane-04.txt 621 (Section 3.2.) draft. 623 6.1.4 MPLS-TP OAM 625 MPLS-LSP-PING-STD-MIB describes managed objects used to model and 626 manage the MPLS LSP ping [RFC4379]. LSP ping is used for 627 connectivity verification and fault isolation in an MPLS LSPs. 629 PW-VCCV-STD-MIB describes managed objects used to model and manage 630 the VCCV [RFC5085]. VCCV used for end-to-end fault detection and 631 diagnostics for a Pseudowire. 633 BFD-MPLS-STD-MIB describes the managed objects for modeling the 634 BFD for MPLS LSPs [RFC5884]. BFD for LSPs used for detecting 635 MPLS LSP data plane failures. 637 BFD-PW-VCCV-STD-MIB describes the managed objects for modeling 638 the BFD for Pseudowires [RFC5885]. BFD for Pseudowires used for 639 detecting data plane failures. 641 MPLS-LSP-PING-STD-MIB, PW-VCCV-STD-MIB, BFD-MPLS-STD-MIB and 642 BFD-PW-VCCV-STD-MIB are newly defined for MPLS. The new MPLS-TP 643 managed objects for LSP ping and BFD are based on 644 draft-ietf-mpls-tp-lsp-ping-bfd-procedures-00. 646 All MPLS-TP managed for OAM is defined in the MPLSTP-OAM-STD-MIB. 648 MPLSTP-TC-STD-MIB describes the textual conventions used for MPLS-TP. 650 MPLSTP-STD-MIB describes managed objects used to model and manage 651 the new extensions for LSPs, section and Pseudowires for IP and 652 non-IP packet based MPLS-TP transport networks. 654 The following MPLS-TP OAM functionalities can be achieved using the 655 MPLSTP-OAM-STD-MIB mib extensions: 657 o Continuity Check and Connectivity Verification, 658 o Alarm Reporting, Diagnostic, 659 o Route Tracing, 660 o Loopback tool, 661 o Lock Instruct, 662 o Lock Reporting Remote Defect Indication, 663 o Client Failure Indication, 664 o Packet Loss Measurement and 665 o Packet Delay Measurement 667 MPLS-TP OAM managed objects are defined based on the drafts: 669 o draft-ietf-mpls-tp-oam-requirements-06, 670 o draft-ietf-mpls-tp-oam-framework-06 and 671 o draft-ietf-mpls-tp-identifiers-01 673 6.1.5 MPLS-TP Protection Switching 675 An important aspect that MPLS-TP technology provides is protection 676 switching. In general, the mechanism of protection switching 677 can be described as the substitution of a protection or standby 678 facility for a working or primary facility. An MPLS-TP protection 679 switching can be managed with the following parameters: 681 o Topology (linear, ring, mesh) 682 o Protection architecture (1+1, 1:1, or others as defined in 683 different topologies) 684 o Switching type (unidirectional, bidirectional) 685 o Operation mode (revertive, non-revertive) 686 o Automatic protection channel 687 o Protection state 688 o Position of the switch 689 o Timer values (hold-off, Wait-to-Restore) 690 o Failure of protocol 692 Among those parameters for protection switching, the topology on 693 that a protection switching applies has the most significant 694 influence on the other parameters. Besides, the mechanism of a 695 particular protection switching heavily depends on its topology. 696 Therefore, three MIB modules are to be defined to model and 697 manage each of three different topologies protection switching. 699 MPLSTP-LPS-STD-MIB describes managed objects used to model and 700 manage the linear protection switching. 702 MPLSTP-RPS-STD-MIB describes managed objects used to model and 703 manage the ring protection switching. 705 MPLSTP-MPS-STD-MIB describes managed objects used to model and 706 manage the mesh protection switching. 708 6.1.6 MIB Module Interdependencies 710 This section provides an overview of the relationship between 711 the MPLS-TP MIB modules. More details of these relationships 712 are given below. 714 The arrows in the following diagram show a 'depends on' 715 relationship. A relationship "MIB module A depends on MIB module 716 B" means that MIB module A uses an object, object identifier, or 717 textual convention defined in MIB module B, or that MIB module A 718 contains a pointer (index or RowPointer) to an object in MIB 719 module B. 721 +-------------->MPLSTP-TC-STD-MIB <--------------------------+ 722 | | 723 | MPLS-TE-STD-MIB PW-STD-MIB | 724 | ^ ^ | 725 | | | | 726 +<----------- MPLSTP-STD-MIB <-------------------------------+ 727 | ^ | 728 | | +---------> MPLS-LSP-PING-STD-MIB | 729 | | ^ ^ ^ | 730 | | | | | | 731 | | | PW-VCCV-STD-MIB | | 732 | | | ^ ^ | | 733 | | | | | | | 734 | | BFD-MPLS-STD-MIB | | | 735 | | ^ +----------+ | | 736 | | | ^ | | 737 | | | | | | 738 +<----------- MPLSTP-OAM-STD-MIB ------------->+ | 739 ^ | 740 | | 741 +- MPLSTP-LPS-STD-MIB -------------------->+ 742 | | 743 +- MPLSTP-RPS-STD-MIB -------------------->+ 744 | | 745 +- MPLSTP-MPS-STD-MIB -------------------->+ 747 Thus: 749 - All the MPLS-TP MIB modules depend on MPLSTP-TC-STD-MIB. 751 - MPLSTP-OAM-STD-MIB and MPLSTP-PS-STD-MIB contain references to 752 objects in MPLSTP-STD-MIB. 754 - MPLSTP-PS-STD-MIB contains references to objects in 755 MPLSTP-OAM-STD-MIB. 757 - MPLSTP-STD-MIB contains references to objects in 758 MPLS-TE-STD-MIB and PW-STD-MIB. 760 - MPLSTP-OAM-STD-MIB contains references to objects in 761 MPLS-LSP-PING-STD-MIB, and 762 PW-VCCV-STD-MIB and BFD-MPLS-STD-MIB. 764 - BFD-MPLS-STD-MIB contains references to objects in 765 MPLS-LSP-PING-STD-MIB and PW-VCCV-STD-MIB. 767 - PW-VCCV-STD-MIB contains references to objects in 768 MPLS-LSP-PING-STD-MIB. 770 7. Interfaces 772 MPLS-TP can be carried over the existing and evolving physical 773 transport technologies such as SONET/SDH, OTN/WDM, and Ethernet. 775 The Interfaces Group of IF-MIB [RFC2863] defines generic managed 776 objects for managing interfaces. The MPLS-TP MIB modules make 777 references to interfaces so that it can be clearly determined where 778 the procedures managed by the MIB modules should be performed. 779 Additionally, the MPLS-TP MIB modules (notably MPLS-TE-STD-MIB and 780 TE-LINK-STD-MIB, PW-STD-MIB) utilize interface stacking within the 781 Interface Group. 783 Please refer to section 4. (Node and Interface Identifiers) in 784 [MPLS-TP-IDENTIFIERS] for more information on MPLS-TP specific 785 interfaces. 787 7.1. MPLS Tunnels as Interfaces 789 mplstpTunnelTable is extended from mplsTunnelTable for achieving the 790 MPLS-TP tunnel requirements. 792 MPLS Tunnel logical interfaces can be stacked over 793 PDH/SDH/OTH/Ethernet physical interfaces. For more information on 794 Tunnel interfaces, refer section 11.1 (MPLS Tunnels as Interfaces) of 795 RFC-4221. 797 7.2. Application of the Interfaces Group to TE Links 799 TE links can be formed over PDH/SDH/OTH/Ethernet physical interfaces. 800 For more information on TE links, Refer section 11.2. Application of 801 the Interfaces Group to TE Links of RFC-4221. 803 7.3. References to Interface Objects from MPLS MIB Modules 805 MPLSTP-STD-MIB includes the extensions of Tunnel table, PW table 806 for MPLS-TP. 808 More information on Tunnel interfaces can be found in the RFC-3812, 809 section 8. (Application of the Interface Group to MPLS Tunnels) 811 The PW in general is not an ifIndex on its own, for agent 812 scalability reasons. The PW is typically associated via 813 the PWE3 MIB modules to an ifIndex (physical entity) the PW is 814 emulating. Some implementations may manage the PW as an ifIndex in the 815 ifTable. A special ifType to represent a PW virtual interface (246) 816 will be used in the ifTable in this case. More information on PW 817 interfaces can be found in the RFC-5601, section 8 (PW relations to 818 the IF-MIB). 820 8. Management Options 822 It is not the intention of this document to provide instructions or 823 advice to implementers of management systems, management agents, or 824 managed entities. It is, however, useful to make some observations 825 about how the MIB modules described above might be used to manage 826 MPLS systems. 828 For MPLS specific management options, refer [RFC4221] Section 12 829 (Management Options). 831 [Editors Note: MPLS-TP specific management gaps and options will be 832 documented in this document and will be referenced here.] 834 9. Security Considerations 836 This document describes the interrelationships amongst the different 837 MIB modules relevant to MPLS-TP management and as such does not have 838 any security implications in and of itself. 840 Each IETF MIB document that specifies MIB objects for MPLS-TP must 841 provide a proper security considerations section that explains the 842 security aspects of those objects. 844 The attention of readers is particularly drawn to the security 845 implications of making MIB objects available for create or write 846 access through an access protocol such as SNMP. SNMPv1 by itself is 847 an insecure environment. Even if the network itself is made secure 848 (for example, by using IPSec), there is no control over who on the 849 secure network is allowed to access the objects in this MIB. It is 850 recommended that the implementers consider the security features as 851 provided by the SNMPv3 framework. Specifically, the use of the 852 User-based Security Model STD 62, RFC3414 [RFC3414], and the 853 View-based Access Control Model STD 62, RFC 3415 [RFC3415], 854 is recommended. 856 It is then a customer/user responsibility to ensure that the SNMP 857 entity giving access to an instance of each MIB module is properly 858 configured to give access to only those objects, and to those 859 principals (users) that have legitimate rights to access them. 861 10. IANA Considerations 863 This document makes no requests for IANA action. 865 11. Acknowledgements 867 The authors would like to thank Eric Gray, Thomas Nadeau and Benjamin 868 Niven-Jenkins for their valuable comments. 870 12. References 872 12.1 Normative References 874 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 875 MIB using SMIv2", RFC 2863, June 2000. 877 [RFC3811] Nadeau, T. and J. Cucchiara, "Definition of Textual 878 Conventions and for Multiprotocol Label Switching (MPLS) 879 Management", RFC 3811, June 2004. 881 [RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau, 882 "Multiprotocol Label Switching (MPLS) Traffic 883 Engineering (TE) Management Information Base (MIB)", 884 RFC 3812, June 2004. 886 [RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau, 887 "Multiprotocol Label Switching (MPLS) Label Switching 888 (LSR) Router Management Information Base (MIB)", RFC 3813, 889 June 2004. 891 [RFC3814] Nadeau, T., Srinivasan, C., and A. Viswanathan, 892 "Multiprotocol Label Switching (MPLS) FEC-To-NHLFE 893 (FTN) Management Information Base", RFC3814, June 894 2004. 896 [RFC3815] Cucchiara, J., Sjostrand, H., and Luciani, J., 897 "Definitions of Managed Objects for the 898 Multiprotocol Label Switching (MPLS), Label 899 Distribution Protocol (LDP)", RFC 3815, June 2004. 901 [RFC4220] Dubuc, M., Nadeau, T., and J. Lang, "Traffic 902 Engineering Link Management Information Base", RFC 903 4220, November 2005. 905 [RFC4221] Nadeau, T., Srinivasan, C., and A. Farrel, 906 "Multiprotocol Label Switching (MPLS) Management 907 Overview", RFC 4221, November 2005. 909 [RFC4801] T. Nadeau and A. Farrel, Ed., "Definitions of Textual 910 Conventions for Generalized Multiprotocol Label Switching 911 (GMPLS) Management", RFC4801, Feb. 2007. 913 [RFC4802] T. D. Nadeau and A. Farrel, "Generalized Multiprotocol 914 Label Switching (GMPLS) Traffic Engineering Management 915 Information Base", RFC4802, Feb., 2007. 917 [RFC4803] T. D. Nadeau and A. Farrel, "Generalized Multiprotocol 918 Label Switching (GMPLS) Label Switching Router (LSR) 919 Management Information Base", RFC4803, Feb., 2007. 921 [RFC5542] Nadeau, T., Ed., Zelig, D., Ed., and O. Nicklass, Ed., 922 "Definitions of Textual Conventions for Pseudowire (PW) 923 Management", RFC 5542, May 2009. 925 [RFC5601] Nadeau, T., Ed. and D. Zelig, Ed. "Pseudowire (PW) 926 Management Information Base (MIB)", RFC 5601, July 2009. 928 [RFC5602] Zelig, D., Ed., and T. Nadeau, Ed., "Pseudowire (PW) over 929 MPLS PSN Management Information Base (MIB)", RFC 5602, 930 July 2009. 932 [RFC5603] Zelig, D., Ed., and T. Nadeau, Ed., "Ethernet Pseudowire 933 (PW) Management Information Base (MIB)", RFC 5603, 934 July 2009. 936 [RFC5604] Nicklass, O., "Managed Objects for Time Division 937 Multiplexing (TDM) over Packet Switched Networks (PSNs)", 938 RFC5604, July 2009. 940 12.2 Informative References 942 [RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 943 "Structure of Management Information Version 2 944 (SMIv2)", STD 58, RFC 2578, April 1999. 946 [RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 947 "Textual Conventions for SMIv2", STD 58, RFC 2579, 948 April 1999. 950 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 951 "Conformance Statements for SMIv2", STD 58, RFC 2580, 952 April 1999. 954 [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, 955 "Multiprotocol Label Switching Architecture", RFC 3031, 956 January 2001. 958 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 959 "Introduction and Applicability Statements for 960 Internet-Standard Management Framework", RFC 3410, 961 December 2002. 963 [RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security 964 Model (USM) for version 3 of the Simple Network 965 Management Protocol (SNMPv3)", STD 62, RFC 3414, 966 December 2002. 968 [RFC3415] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 969 Access Control Model (VACM) for the Simple Network 970 Management Protocol (SNMP)", STD 62, RFC 3415, December 971 2002. 973 [RFC3931] Lau, J., Townsley, M., and I. Goyret, "Layer Two Tunneling 974 Protocol - Version 3 (L2TPv3)", RFC 3931, March 2005. 976 [RFC3945] Mannie, E. et.al., "Generalized Multi-Protocol Label 977 Switching (GMPLS) Architecture", IETF RFC 3945, October 978 2004. 980 [RFC3985] Bryant, S. and P. Pate, "Pseudo Wire Emulation Edge-to- 981 Edge (PWE3) Architecture", RFC 3985, March 2005. 983 [RFC4090] Pan, P., Ed., Swallow, G., Ed., and A. Atlas, Ed., "Fast 984 Reroute Extensions to RSVP-TE for LSP Tunnels", RFC 4090, 985 May 2005. 987 [RFC4197] Riegel, M., "Requirements for Edge-to-Edge Emulation of 988 Time Division Multiplexed (TDM) Circuits over Packet 989 Switching Networks", RFC4197, October 2005. 991 [RFC4377] Nadeau, T., Morrow, M., Swallow, G., Allan, D., and S. 992 Matsushima, "Operations and Management (OAM) Requirements 993 for Multi-Protocol Label Switched (MPLS) Networks", 994 RFC 4377, February 2006. 996 [RFC4378] Allan, D. and T. Nadeau, "A Framework for Multi-Protocol 997 Label Switching (MPLS) Operations and Management (OAM)", 998 RFC 4378, February 2006. 1000 [RFC4379] Kompella, K. and G. Swallow, "Detecting Multi-Protocol 1001 Label Switched (MPLS) Data Plane Failures", RFC 4379, 1002 February 2006. 1004 [RFC4447] Martini, L., Rosen, E., El-Aawar, N., Smith, T., and 1005 G. Heron, "Pseudowire Setup and Maintenance Using the 1006 Label Distribution Protocol (LDP)", RFC 4447, 1007 April 2006. 1009 [RFC5085] Nadeau, T. and C. Pignataro, "Pseudowire Virtual 1010 Circuit Connectivity Verification (VCCV): A Control 1011 Channel for Pseudowires", RFC 5085, December 2007. 1013 [RFC5654] Niven-Jenkins, B., et al, "MPLS-TP Requirements", 1014 RFC5654, September 2009. 1016 [RFC5884] Aggarwal, R., Kompella, K., Nadeau, T., and G. Swallow, 1017 "Bidirectional Forwarding Detection (BFD) For MPLS 1018 Label Switched Paths (LSPs)", RFC 5884, June 2010. 1020 [RFC5885] Nadeau, T. and C. Pignataro, "Bidirectional 1021 Forwarding Detection (BFD) for the Pseudowire 1022 Virtual Circuit Connectivity Verification (VCCV)", 1023 RFC5885, June 2010. 1025 [RFC5950] Gray, E., Mansfield, S., Lam, K., 1026 "MPLS-TP Network Management Framework", RFC 5950, 1027 September 2010. 1029 [RFC5951] Gray, E., Mansfield, S., Lam, K., "MPLS TP 1030 Network Management Requirements", RFC 5951, September 1031 2010. 1033 [MPLS-TP-IDENTIFIERS] Bocci, M., Swallow, G., "MPLS-TP Identifiers" 1034 draft-ietf-mpls-tp-identifiers-02, July 2010. 1036 [MPLS-TP-OAM-FWK] Busi, I. and B. Niven-Jenkins, "MPLS-TP OAM 1037 Framework and Overview", 2009, 1038 . 1040 14. Authors' Addresses 1042 Adrian Farrel 1043 Old Dog Consulting 1044 UK 1045 Email: adrian@olddog.co.uk 1047 Daniel King 1048 Old Dog Consulting 1049 UK 1050 Email: daniel@olddog.co.uk 1052 Venkatesan Mahalingam 1053 Aricent 1054 India 1055 Email: venkatesan.mahalingam@aricent.com 1057 Scott Mansfield 1058 Ericsson 1059 300 Holger Way 1060 San Jose, CA 95134 1061 US 1062 Phone: +1 724 931 9316 1063 Email: scott.mansfield@ericsson.com 1065 Jeong-dong Ryoo 1066 ETRI 1067 161 Gajeong, Yuseong, Daejeon, 305-700, South Korea 1068 Phone: +82 42 860 5384 1069 Email: ryoo@etri.re.kr 1070 A S Kiran Koushik 1071 Cisco Systems Inc. 1072 Email: kkoushik@cisco.com