idnits 2.17.1 draft-txh-lime-gap-analysis-03.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 doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (December 7, 2016) is 2696 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Outdated reference: A later version (-10) exists of draft-ietf-lime-yang-oam-model-07 == Outdated reference: A later version (-17) exists of draft-ietf-bfd-yang-03 == Outdated reference: A later version (-05) exists of draft-ietf-trill-yang-oam-04 Summary: 0 errors (**), 0 flaws (~~), 5 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 LIME Working Group Y. Tochio 3 Internet-Draft Fujitsu 4 Intended status: Informational H. van Helvoort 5 Expires: June 10, 2017 Hai Gaoming BV 6 L. Xia 7 Huawei 8 December 7, 2016 10 Gap Analysis for Layer and Technology Independent OAM Management in the 11 Multi-Layer Environment 12 draft-txh-lime-gap-analysis-03 14 Abstract 16 This draft analyses the existing management plane OAM related works 17 in different SDOs, against the key objectives of Layer Independent 18 OAM Management (LIME), to find the gap between them. The results can 19 be used as the guidance for further work. This gap analysis is not 20 targeted at L0-L2 transport OAM in ITU-T, either technology specific 21 or generic across those technologies. Rather, it is intended to 22 leverage knowledge from that domain for the benefit of developing 23 generic layer independent OAM management for L3-L7 (and L2.5 MPLS 24 OAM). 26 Status of This Memo 28 This Internet-Draft is submitted in full conformance with the 29 provisions of BCP 78 and BCP 79. 31 Internet-Drafts are working documents of the Internet Engineering 32 Task Force (IETF). Note that other groups may also distribute 33 working documents as Internet-Drafts. The list of current Internet- 34 Drafts is at http://datatracker.ietf.org/drafts/current/. 36 Internet-Drafts are draft documents valid for a maximum of six months 37 and may be updated, replaced, or obsoleted by other documents at any 38 time. It is inappropriate to use Internet-Drafts as reference 39 material or to cite them other than as "work in progress." 41 This Internet-Draft will expire on December 7, 2016. 43 Copyright Notice 45 Copyright (c) 2016 IETF Trust and the persons identified as the 46 document authors. All rights reserved. 48 This document is subject to BCP 78 and the IETF Trust's Legal 49 Provisions Relating to IETF Documents 50 (http://trustee.ietf.org/license-info) in effect on the date of 51 publication of this document. Please review these documents 52 carefully, as they describe your rights and restrictions with respect 53 to this document. Code Components extracted from this document must 54 include Simplified BSD License text as described in Section 4.e of 55 the Trust Legal Provisions and are provided without warranty as 56 described in the Simplified BSD License. 58 Table of Contents 60 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 61 2. Conventions used in this document . . . . . . . . . . . . . . 3 62 2.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 63 3. Existing OAM Related Works . . . . . . . . . . . . . . . . . 4 64 3.1. Survey of ITU-T Work from L0-L2 . . . . . . . . . . . . . 5 65 3.1.1. Generic L0-L2 . . . . . . . . . . . . . . . . . . . . 5 66 3.1.2. Technology Specific L0-L2 . . . . . . . . . . . . . . 5 67 3.2. Management Information Models . . . . . . . . . . . . . . 5 68 3.3. IEEE CFM MIB . . . . . . . . . . . . . . . . . . . . . . 6 69 3.4. MEF SOAM FM and PM MIB . . . . . . . . . . . . . . . . . 6 70 3.5. IETF Technology-specific MIB Series . . . . . . . . . . . 7 71 3.6. MEF CFM and SOAM YANG Data Model . . . . . . . . . . . . 7 72 3.7. YANG Model for OAM Management and Technology-specific 73 extensions . . . . . . . . . . . . . . . . . . . . . . . 7 74 3.8. Discussion . . . . . . . . . . . . . . . . . . . . . . . 8 75 4. Security Considerations . . . . . . . . . . . . . . . . . . . 8 76 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 77 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 8 78 7. Normative References . . . . . . . . . . . . . . . . . . . . 8 79 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12 81 1. Introduction 83 Operations, Administration, and Maintenance (OAM) mechanisms are 84 critical building blocks in network operations that are used for 85 service assurance, fulfillment, or service diagnosis, 86 troubleshooting, and repair. The current practice is maintenance and 87 troubleshooting are achieved per technology and per layer. The 88 operation process can be very cumbersome. At present, within the 89 L0-L2 technology domains, considerable effort has been expended in 90 ITU-T to establish a coherent approach to OAM, including generic 91 layer independent principles. 93 Due to this fact, [I-D.edprop-opsawg-multi-layer-oam-ps] discusses a 94 valuable direction in management plane by establishing a coherent 95 approach to OAM information from L2.5-L7 using a centralized 96 management entity and have a unified and consistent OAM view of 97 multi-layer networks. Operators can rely on consolidated OAM 98 management to correlate different layer OAM information (e.g., fault, 99 defects and network failure), and quickly identify the faulty element 100 with its layer information in the network path. Note that current 101 LIME work focuses on layer-independent and technology-independent 102 configuration, reporting and presentation for OAM mechanisms in the 103 context of IP, MPLS, BFD, pseudowires, and Transparent 104 Interconnection of Lots of Links (TRILL) technology developed by 105 IETF. The second important objective of LIME is to achieve a layer 106 and technology independent OAM view of a network and allow management 107 applications present to the user an abstract view of this network and 108 its supporting layers that is strictly topological, free of any 109 technology specific information. This means an abstract and generic 110 OAM management model in the management plane should be utilized (with 111 extensions as appropriate to L2.5-L7), from which OAM specific views 112 can be established, and technology-specific OAM data models can be 113 developed by mapping from the information model view. A generic OAM 114 management model can provide a consistent configuration, reporting, 115 and presentation for the OAM mechanisms. It also can mitigate the 116 problem related to specific OAM technology dependency. 118 This draft analyses the existing management plane OAM related work in 119 several SDOs, against the key objectives of LIME, to find the gap 120 between them. The results can be used as the guidance for further 121 work. 123 2. Conventions used in this document 125 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 126 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 127 document are to be interpreted as described in RFC2119 [RFC2119]. 129 2.1. Terminology 131 DM Data Model 133 EMS Element Management System 134 IM Information Model 136 NMS Network Management System 138 MP Maintenance Point [802.1Q] 140 MEG Maintenance Entity Group [G.8013] [RFC6371] 142 MEP MEG End Point [G.8013] [RFC6371] 144 MIP MEG Intermediate Point [G.8013] [RFC6371] 146 ME Maintenance Entity [G.8013] [RFC6371] 148 MD Maintenance Domain [802.1Q] 150 MPLS Multiprotocol Label Switching 152 NE Network Element 154 OAM Operations, Administration, and Maintenance [RFC6291] 156 LIME Layer Independent OAM Management 158 SFC Service Function Chaining 160 SFF Service Function Forwarder 162 SDO Standard Developing Organization 164 3. Existing OAM Related Works 166 3.1. Survey of ITU-T Work from L0-L2 168 3.1.1. Generic L0-L2 170 [G.800] and [G.805] specify the unified and generic functional 171 architecture of transport networks. [G.806] specifies the generic 172 processing of transport equipment functions, including handling of 173 OAM, defect correlation, and alarm suppression, etc. [G.7710] 174 specifies the generic management requirements for configuration, 175 fault, and performance (i.e. the C, F, P of FCAPS). [G.7711] is on- 176 going work in ITU-T to specify the generic management information 177 model for L0-L2 transport networks. 179 3.1.2. Technology Specific L0-L2 181 [G.803], [G.872], [G.8010] and [G.8110.1] specify the functional 182 architecture respectively for SDH, OTN, Ethernet, MPLS-TP transport 183 networks. [G.783], [G.798], [G.8021] and [G.8121] specify 184 respectively the processing of transport equipment functions for 185 SDH, OTN, Ethernet, MPLS-TP, including handling of OAM, and defect 186 correlation, and alarm suppression, etc. 187 [G.784], [G.874], [G.8051] and [G.8151] specify respectively the 188 management requirements for configuration, fault, and performance 189 (i.e. the C, F, P of FCAPS). [G.774], [G.874.1], [G.8052] and 190 [G.8152] specify respectively the management information model for 191 SDH, OTN, Ethernet, MPLS-TP transport networks. 193 3.2. Management Information Models 195 ITU-T's Recommendation [G.8052] and [G.8152] provide the management 196 protocol-neutral information models for managing network elements in 197 the Ethernet transport network and MPLS-TP transport network as 198 defined in Recommendations [G.8010] and [G.8110.1] respectively. The 199 management information models are derived from the "functional 200 models", which describe the data plane behavior and processing. 201 Management information models manage the "atomic functions" defined 202 in the data plane in transport networks. They contain the object 203 classes for the Ethernet and MPLS-TP NE management. This includes 204 the Termination Point (TP), Maintenance Entity Group (MEG) End Point 205 (MEP), MEG Intermediate Point (MIP), Traffic Conditioning & Shaping 206 (TCS), Loss Measurement (LM), Delay Measurement (DM), and the general 207 Performance Monitoring (PM), Current Data (CD) and History Data (HD). 208 [G.8052] has been published. [G.8152] is still in progress. There 209 is already some degree of consolidation among the /L0 (OTN) 210 [G.874.1], (SDH) [G.774]/, /L1 (OTN) [G.874.1], (SDH) [G.774]/ and 211 /L2 (Ethernet) [G.8052], (MPLS-TP) [G.8152]/ information models 212 specified by these ITU-T recommendations. In fact, they have a 213 common basis for information model and are not technology-specific 214 models any more. 216 [MEF-7.1] specifies the EMS-NMS interface profile identifying the 217 managed objects (i.e. logical UML objects) needed to support Metro 218 Ethernet services. This specification provides the profile of 219 management entities based on ITU-T [Q.840.1], and also provides a 220 mapping to the TMF's MTNM 3.5 Ethernet model. Specifically this 221 document adds management support for Service OAM. The Ethernet 222 Service OAM object definitions include common OAM objects (e.g., 223 EthMe, EthMeg, EthMep, etc.), Fault Management Objects (e.g., 224 Continuity Check, Loopback, etc.), Performance Monitoring Objects 225 (e.g., Loss Measurement, Delay Measurement, etc.). 227 3.3. IEEE CFM MIB 229 The IEEE8021-CFM-MIB MIB Module and IEEE8021-CFM-V2-MIB MIB module 230 are CFM MIB modules for managing IEEE CFM in [802.1Q]. The former 231 document defines all the MIB objects that used to read, create, 232 modify, and delete OAM related information (i.e., CFM Stack Table, MD 233 Table, MA Table, MEP Table, LinkTrace Reply Table, MEP DB Table, 234 Notifications Table, etc). The latter document defines CFM V2 module 235 for managing IEEE CFM. It contains objects that replace those 236 deprecated in the IEEE8021-CFM-MIB module (i.e., CFM Stack Table, CFM 237 Vlan Table, CFM Default MD Level Table, etc). 239 3.4. MEF SOAM FM and PM MIB 241 [MEF-31] defines the MIB modules for MEF Service OAM Fault Management 242 (FM). This document includes two MIBs necessary to support the MEF 243 SOAM FM functionality: the MEF-SOAM-TC-MIB that includes the Textual 244 Conventions (TC) for the SOAM MIB family and the MEF-SOAM-FM-MIB that 245 includes extensions to Connectivity Fault Management (CFM) as 246 developed in [IEEE 802.1Q], including MIBs found in [IEEE 802.1Q] and 247 [IEEE 802.1ap], and enhanced by ITU-T [Y.1731] to support the SOAM FM 248 functions as presented in the [MEF-30] specification. It includes 249 the SOAM FM MIB objects such as mefSoamNet, mefSoamMeg, mefSoamMep, 250 mefSoamCc, mefSoamAis, mefSoamLb, etc. 252 [MEF-36] specifies the Performance Monitoring (PM) MIB necessary to 253 manage SOAM implementations that satisfy the Service OAM requirements 254 and framework specified by [MEF-17], the Service OAM Performance 255 Monitoring requirements as specified by [MEF-35], and the Service OAM 256 management objects as specified by [MEF-7.1] which are applicable to 257 Performance Monitoring functions. Two non-MEF documents serve as the 258 baseline documents for this work: ITU-T [G.8013] and IEEE [802.1Q]. 259 The SOAM PM MIB is divided into a number of different object 260 groupings: the PM MIB MEP Objects, PM MIB Loss Measurement Objects, 261 PM MIB Delay Measurement Objects, and SOAM PM Notifications. 263 3.5. IETF Technology-specific MIB Series 265 IETF specifies a series MIB module for various technologies, which 266 includes: [RFC7331] for BFD MIB, [RFC4560] for PING MIB, [MPLS-TP OAM 267 ID MIB] for MPLS-TP MIB, etc. 269 All these documents are technology-specific and limited to L1, L2, 270 L3. The OAM MIB definition above L3 (i.e., SFC service layer) is 271 still missing in IETF. 273 3.6. MEF CFM and SOAM YANG Data Model 275 SOAM CFM YANG module [MEF-38] is an important work that defines the 276 managed objects necessary to support SOAM CFM functionality by using 277 the IETF YANG Module Language [RFC6020]. This YANG module contains 278 the management data definitions for the management of Ethernet 279 Services OAM for Connectivity Fault Management. 281 [MEF-39] provides the YANG module that supports the Ethernet Service 282 OAM (SOAM) Performance Monitoring functions. This YANG module 283 contains the management data definitions for the management of 284 Ethernet Services OAM for Performance Monitoring and extends the 285 Connectivity Fault Management (CFM) YANG modules. 287 3.7. YANG Model for OAM Management and Technology-specific extensions 289 [I-D.ietf-lime-yang-oam-model] is an IETF work that creates a YANG 290 unified data models for OAM that is based on IEEE CFM model. [I-D. 291 ietf-lime-yang-oam-model] defines a YANG [RFC6020] data model for 292 Layer independent OAM Management implementations that can be applied 293 to various network technologies. 295 [I-D.ietf-trill-yang-oam] extends the Generic YANG model defined in 296 [I-D.ietf-lime-yang-oam-model] for OAM with TRILL technology 297 specifies Yang Module for TRILL OAM. 299 [I-D.ietf-bfd-yang] defines YANG data model for BFD without 300 augmenting the Generic YANG model for connection-less OAM defined in 301 []I-D. ietf-lime-yang-connectionless]. 303 3.8. Discussion 305 Until now, all the OAM models and operations in the management plane 306 for L3-L7 are technology dependent and limited to one specific layer. 307 One point which should be noticed is that the information models 308 specified for transport networks (L0/L1/L2, [G.874.1], [G.8052], 309 [G.8152] ) by the ITU-T have received some degree of consolidation, 310 and are not technology dependent. [I-D. lam-lime-summary-l0-l2- 311 layer-independent] provides the summary on this point. 313 Also, [I-D.ietf-bfd-yang] indicates the concern how it can augment to 314 the Generic YANG model defined [I-D. ietf-lime-yang-connectionless]. 316 It is noted that the YANG Data model for OAM Performance Management 317 has not been developed and and some drafts for them are expired. 319 4. Security Considerations 321 TBD. 323 5. IANA Considerations 325 This drafts includes no request to IANA. 327 6. Acknowledgements 329 The authors would like to thank for Eve Varma, Maarten Vissers for 330 their valuable comments and thoughtful inputs to this draft regarding 331 ITU-T OAM works in L0-L2. 333 7. Normative References 335 [G.774] "Synchronous digital hierarchy (SDH) - Management 336 information model for the network element view", ITU-T 337 G.774, February 2001. 339 [G.783] "Characteristics of synchronous digital hierarchy (SDH) 340 equipment functional blocks", ITU-T G.783, March 2006. 342 [G.784] "Management aspects of synchronous digital hierarchy (SDH) 343 transport network elements", ITU-T G.784, March 2008. 345 [G.798] "Characteristics of optical transport network hierarchy 346 equipment functional blocks", ITU-T G.798, December 2012. 348 [G.800] "Unified functional architecture of transport networks", 349 ITU-T G.800, February 2012. 351 [G.8010] "Architecture of Ethernet layer networks", ITU-T G.8010, 352 February 2004. 354 [G.8013] "OAM functions and mechanisms for Ethernet based 355 networks", ITU-T G.8013/Y.1731, August 2015. 357 [G.8021] "Characteristics of Ethernet transport network equipment 358 functional blocks", ITU-T G.8021, January 2015. 360 [G.803] "Architecture of transport networks based on the 361 synchronous digital hierarchy (SDH)", ITU-T G.803, March 362 2000. 364 [G.805] "Generic functional architecture of transport networks", 365 ITU-T G.805, March 2000. 367 [G.8051] "Management aspects of the Ethernet Transport (ET) capable 368 network element", ITU-T G.8051, August 2015. 370 [G.8052] "Protocol-neutral management information model for the 371 Ethernet transport capable network element", ITU-T 372 G.8052/Y.1346, November 2015. 374 [G.806] "Characteristics of transport equipment - Description 375 methodology and generic functionality", ITU-T G.806, 376 February 2012. 378 [G.8110.1] 379 "Architecture of MPLS Transport Profile (MPLS-TP) layer 380 network", ITU-T G.8110.1/Y.1370.1, December 2011. 382 [G.8121] "Characteristics of MPLS-TP equipment functional blocks", 383 ITU-T G.8121, April 2016. 385 [G.8151] "Management aspects of the MPLS-TP network element", ITU-T 386 G.8151, January 2015. 388 [G.8152] "Protocol-neutral management information model for the 389 MPLS-TP network element", ITU-T G.8152/Y.1375, 390 December 2016. 392 [G.7710] "Common equipment management function requirements", 393 ITU-T G.7710, February 2012. 395 [G.7711] "Generic protocol-neutral information model for transport 396 resources", ITU-T G.7711, August 2015. 398 [G.872] "Architecture of optical transport networks", ITU-T G.872, 399 October 2012. 401 [G.874] "Management aspects of optical transport network 402 elements", ITU-T G.874, August 2013. 404 [G.874.1] "Optical transport network: Protocol-neutral management 405 information model for the network element view", ITU-T 406 G.874.1, October 2012. 408 [I-D.edprop-opsawg-multi-layer-oam-ps] 409 Taylor, T., "Problem Statement for Layer and Technology 410 Independent OAM in a Multi-Layer Environment", ID draft- 411 edprop-opsawg-multi-layer-oam-ps(Expired), September 2014. 413 [I-D.ietf-lime-yang-oam-model] 414 Senevirathne, T., Finn, N., Kumar, D., Salam, S., and Q. 415 Wu, "Generic YANG Data Model for Operations, 416 Administration, and Maintenance (OAM)", draft-ietf-lime- 417 yang-oam-model-07, July 2016. 419 [I-D.ietf-bfd-yang] 420 Zheng, L., " Yang Data Model for Bidirectional Forwarding 421 Detection(BFD) ", ID draft-ietf-bfd-yang-03, August 2015. 423 [I-D.ietf-trill-yang-oam] 424 Kumar, D., "YANG Data Model for TRILL Operations, 425 Administration, and Maintenance (OAM)", draft-ietf-trill- 426 yang-oam-04, July 2016. 428 [I-D. lam-lime-summary-l0-l2-layer-independent] 429 K. Lam., "Existing Support for Network Operations in 430 Multilayer Transport Network based upon unified approach 431 to OAM (Layer 0 - Layer 2)", ID draft-lam-lime-summary- 432 l0-l2-layer-independent-05, October 2016. 434 [I-D. ietf-lime-yang-connectionless] 435 Kumar, D., "Generic YANG Data Model for Connection Less, 436 Operations, Administration, and Maintenance (OAM) 437 protocols", draft-ietf-lime-yang-connectionless-oam-02, 438 Oct 2016 440 [802.1Q] "Media Access Control (MAC) Bridges and Virtual Bridged 441 Local Area Networks", IEEE Std 802.1Q-2014, November 2014. 443 [MEF-17] "Service OAM Requirements & Framework - Phase 1", MEF 17, 444 April 2007. 446 [MEF-30] "Service OAM Fault Management Implementation Agreement", 447 MEF 30, January 2011. 449 [MEF-31] "Service OAM Fault Management Definition of Managed 450 Objects", MEF 31, January 2011. 452 [MEF-35] "Service OAM Performance Monitoring Implementation 453 Agreement", MEF 35, January 2012. 455 [MEF-36] "Service OAM SNMP MIB for Performance Monitoring", MEF 36, 456 January 2012. 458 [MEF-38] "Service OAM Fault Management YANG Modules", MEF 38, April 459 2012. 461 [MEF-39] "Service OAM Performance Monitoring YANG Module", MEF 39, 462 April 2012. 464 [MEF-7.1] "EMS-NMS Information Model - Phase 2", MEF Fourm 465 MEF 7.1, 2009. 467 [Q.840.1] "Requirements and Analysis for NMS-EMS Management 468 Interface of Ethernet over Transport and Metro Ethernet 469 Network", Draft Recommendation ITU-T Q.840.1, 2007. 471 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 472 Requirement Levels", March 1997. 474 [RFC4560] Quittek, J., "Definitions of Managed Objects for Remote 475 Ping, Traceroute, and Lookup Operations", June 2006. 477 [RFC6020] Bjorklund, M., "YANG - A Data Modeling Language for the 478 Network Configuration Protocol (NETCONF)", RFC 6020, 479 October 2010. 481 [RFC6291] Andersson, L., van Helvoort, H., Bonica, R., Romascanu, 482 D., and S. Mansfield, "Guidelines for the use of the "OAM" 483 Acronym in the IETF", RFC 6291, June 2011. 485 [RFC6371] Busi, I. and D. Allan, "Operations, Administration, and 486 Maintenance Framework for MPLS-Based Transport Networks", 487 RFC 6371, September 2011. 489 [RFC7331] Nadeau, T., Ali, Z., and N. Akiya, "Bidirectional 490 Forwarding Detection (BFD) Management Information Base", 491 RFC 7331, August 2014. 493 Authors' Addresses 495 Yuji Tochio 496 Fujitsu 498 Email: tochio@jp.fujitsu.com 500 Huub van Helvoort 501 Hai Gaoming BV 502 The Netherlands 504 Email: huubatwork@gmail.com 506 Liang (Frank) Xia 507 Huawei 508 101 Software Avenue, Yuhua District 509 Nanjing, Jiangsu 210012 510 China 512 Email: Frank.xialiang@huawei.com