idnits 2.17.1 draft-hu-bier-oam-yang-01.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 : ---------------------------------------------------------------------------- ** There are 10 instances of too long lines in the document, the longest one being 100 characters in excess of 72. ** The abstract seems to contain references ([I-D.ietf-lime-yang-connectionless-oam]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 222 has weird spacing: '...omainid bie...' == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (June 12, 2017) is 2507 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'RFC2119' is mentioned on line 98, but not defined == Outdated reference: A later version (-08) exists of draft-ietf-bier-architecture-06 == Outdated reference: A later version (-08) exists of draft-ietf-bier-bier-yang-01 == Outdated reference: A later version (-13) exists of draft-ietf-bier-ping-01 == Outdated reference: A later version (-18) exists of draft-ietf-lime-yang-connectionless-oam-06 Summary: 2 errors (**), 0 flaws (~~), 8 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 BIER WG Fangwei. Hu 3 Internet-Draft Ran. Chen 4 Intended status: Standards Track ZTE Corporation 5 Expires: December 14, 2017 R. Gu 6 China Mobile 7 June 12, 2017 9 YANG Data Model for BIER OAM 10 draft-hu-bier-oam-yang-01.txt 12 Abstract 14 This document defines YANG data model for Bit Index Explicit 15 Replication (BIER) Operations, Administration, and Maintenance (OAM). 16 It extends from the basic YANG data model for Layer independent OAM 17 Management defined in [I-D.ietf-lime-yang-connectionless-oam] with 18 BIER technology specifics. It includes BIER OAM related 19 configuration and state. 21 Status of This Memo 23 This Internet-Draft is submitted in full conformance with the 24 provisions of BCP 78 and BCP 79. 26 Internet-Drafts are working documents of the Internet Engineering 27 Task Force (IETF). Note that other groups may also distribute 28 working documents as Internet-Drafts. The list of current Internet- 29 Drafts is at http://datatracker.ietf.org/drafts/current/. 31 Internet-Drafts are draft documents valid for a maximum of six months 32 and may be updated, replaced, or obsoleted by other documents at any 33 time. It is inappropriate to use Internet-Drafts as reference 34 material or to cite them other than as "work in progress." 36 This Internet-Draft will expire on December 14, 2017. 38 Copyright Notice 40 Copyright (c) 2017 IETF Trust and the persons identified as the 41 document authors. All rights reserved. 43 This document is subject to BCP 78 and the IETF Trust's Legal 44 Provisions Relating to IETF Documents 45 (http://trustee.ietf.org/license-info) in effect on the date of 46 publication of this document. Please review these documents 47 carefully, as they describe your rights and restrictions with respect 48 to this document. Code Components extracted from this document must 49 include Simplified BSD License text as described in Section 4.e of 50 the Trust Legal Provisions and are provided without warranty as 51 described in the Simplified BSD License. 53 Table of Contents 55 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 56 2. Conventions and Terminology . . . . . . . . . . . . . . . . . 2 57 2.1. Conventions . . . . . . . . . . . . . . . . . . . . . . . 3 58 2.2. Terminologies . . . . . . . . . . . . . . . . . . . . . . 4 59 3. Architecture of OAM YANG Model and Relationship to BIER OAM . 4 60 4. BIER Extensions to LIME connectionless YANG Model . . . . . . 5 61 4.1. Test Point Locations . . . . . . . . . . . . . . . . . . 5 62 5. BIER OAM YANG Data Design . . . . . . . . . . . . . . . . . . 5 63 6. BIER OAM YANG model . . . . . . . . . . . . . . . . . . . . . 6 64 7. Security Considerations . . . . . . . . . . . . . . . . . . . 8 65 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 8 66 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 67 10. Normative References . . . . . . . . . . . . . . . . . . . . 9 68 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10 70 1. Introduction 72 YANG [RFC6020] is a data modeling language used to model 73 configuration and state data manipulated by the Network Configuration 74 Protocol (NETCONF) [RFC6241], NETCONF remote procedure calls (RPC), 75 and NETCONF notifications. This document defines the YANG data model 76 for Bit Index Explicit Replication (BIER)OAM [I-D.ietf-bier-ping]. 77 The BIER OAM YANG module involves the OAM configuration, and 78 notifications, etc. 80 Currently, [I-D.ietf-lime-yang-connectionless-oam] proposes a basic 81 YANG data model for technology-independent abstraction of key OAM 82 constructs for connectionless protocols. BIER OAM YANG data model 83 can be defined by directly extending the basic model with BIER 84 technology specifics. It can bring some obvious benefits such as 85 unified format, reusable parts, and correlation of defects, faults, 86 network failure at the specific layer. 88 In addition, various components in the BIER technology specific YANG 89 data model defined in [I-D.ietf-bier-bier-yang] can be directly 90 reused in this draft to define the BIER OAM YANG data model. 92 2. Conventions and Terminology 93 2.1. Conventions 95 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 96 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 97 document are to be interpreted as described in [RFC2119]. 99 The following terms are defined in [RFC6241] and are not redefined 100 here: 102 o client 104 o configuration data 106 o server 108 o state data 110 The following terms are defined in [RFC6020] and are not redefined 111 here: 113 o augment 115 o data model 117 o data node 119 The terminology for describing YANG data models is found in 120 [RFC6020]. 122 The following notations are used within the data tree and carry the 123 meaning as noted below. 125 Each node is printed as: 127 129 is one of: 130 + for current 131 x for deprecated 132 o for obsolete 134 is one of: 136 rw for configuration data 137 ro for non-configuration data 138 -x for rpcs 139 -n for notifications 141 is the name of the node 143 If the node is augmented into the tree from another module, its name 144 is printed as :. 146 is one of: 148 ? for an optional leaf or choice 149 ! for a presence container 150 * for a leaf-list or list 151 [] for a list's keys 153 is the name of the type for leafs and leaf-lists 155 In this document, these words will appear with that interpretation 156 only when in ALL CAPS. Lower case uses of these words are not to be 157 interpreted as carrying RFC2119 significance. 159 2.2. Terminologies 161 BFR-ID: Bit-Forwarding Router identify [I-D.ietf-bier-architecture] 163 BIER: Bit Index Explicit Replication[I-D.ietf-bier-architecture] 165 BSL: Bit String Lenght [I-D.ietf-bier-architecture] 167 LIME: Layer Independent OAM Management 168 [I-D.ietf-lime-yang-connectionless-oam] 170 OAM: Operations, Administration, and Maintenance [RFC6291] 172 3. Architecture of OAM YANG Model and Relationship to BIER OAM 174 Layer independent OAM YANG model 175 [I-D.ietf-lime-yang-connectionless-oam] is used as the basis for all 176 the other connectionless OAM YANG models. This allows users to span 177 across OAM tools of different technologies through a uniform API. 178 The following Figure depicts the relationship of BIER OAM YANG model 179 to the Layer Independent OAM YANG Model. 181 +-+-+-+-+-+-+-+-+-+ 182 | Gen OAM YANG | 183 |(connectionless) | 184 +-+-+-+-+-+-+-+-+-+ 185 | 186 O 187 | 188 +--------------+-----------------------------+ 189 | | | 190 +-+-+-+-++ +-+-++--++ +-+-++--++ 191 | BIER | | SFC | | foo | 192 |OAM YANG| |OAM YANG| |OAM YANG| 193 +-+-+-+-++ +-+-++--++ +-+-+-+-++ 194 | | | 195 | +-+-++--++ +-+-+-+-++ 196 | | SFC | . . . | foo | 197 | |sub tech| |sub tech| 198 | +-+-++--++ +-+-+-+-++ 199 | | | 200 | | | 201 +--------------------------------------------------------+ 202 | Uniform API | 203 +--------------------------------------------------------+ 204 Figure 1 Relationship of BIER OAM YANG model to Layer independent 205 OAM YANG model 207 4. BIER Extensions to LIME connectionless YANG Model 209 4.1. Test Point Locations 211 BIER protocol uses BSL ,sub-domain id and BFR-id for the forwarding 212 indicators. So we augment the definition of BSL,sub-domain id and 213 BFR-id from BIER yang data model as the test point locations for BIER 214 OAM YANG data model. 216 5. BIER OAM YANG Data Design 217 module: ietf-bier-oam 218 augment /nd:networks/nd:network/nd:node/coam:location-type/coam:ip-prefix-location-type/coam:test-point-ip-prefix-location-list/coam:test-point-locations: 219 +--rw bier-test-point-location-list 220 +--rw test-point-locations* [bier-bsl bier-subdomainid bier-bfrid] 221 +--rw bier-bsl bier-bsl 222 +--rw bier-subdomainid bier-subdomainid 223 +--rw bier-bfrid bier-bfrid 224 augment /nd:networks/nd:network/nd:node/coam:location-type/coam:ip-prefix-location-type/coam:test-point-ip-prefix-location-list/coam:test-point-locations/coam:technology: 225 +--:(bier-oam-string) 226 +--rw bier-icmp? string 228 6. BIER OAM YANG model 230 file "ietf-bier-oam@2017-06-13.yang" 231 module ietf-bier-oam { 232 namespace "urn:ietf:params:xml:ns:yang:ietf-bier-oam"; 233 prefix bieroam; 235 import ietf-bier { 236 prefix bier; 237 } 239 import ietf-connectionless-oam { 240 prefix coam; 241 } 242 import ietf-network{ 243 prefix nd; 244 } 246 organization 247 "IETF BIER(Bit Indexed Explicit Replication ) Working Group"; 249 contact 250 "WG List: 251 WG Chair: Tony Przygienda 252 253 WG Chair: Greg Shepherd 254 255 Editor: Fangwei Hu 256 257 Editor: Ran Chen 258 259 Editor: Rong Gu 260 261 "; 263 description 264 "The YANG module defines BIER OAM data model."; 266 revision 2016-12-05{ 267 description 268 "00 revision"; 269 reference 270 "draft-hu-bier-oam-yang-00"; 271 } 273 revision 2017-06-12{ 274 description 275 "01 revision,remove the OAM Layer part."; 276 reference 277 "draft-hu-bier-oam-yang-01"; 278 } 280 typedef bier-bsl { 281 type leafref { 282 path "/bier:bier/bier:bier-global/bier:sub-domain/bier:bitstringlength"; 283 } 284 description "bsl type"; 285 } 287 typedef bier-subdomainid { 288 type leafref { 289 path "/bier:bier/bier:bier-global/bier:sub-domain/bier:sub-domain-id"; 290 } 291 description "sub-domain-id type"; 292 } 294 typedef bier-bfrid { 295 type leafref { 296 path "/bier:bier/bier:bier-global/bier:sub-domain/bier:bfr-id"; 297 } 298 description "bfr-id type"; 300 } 302 identity bier-type { 303 base coam:tp-address-type; 304 description "bier type"; 305 } 307 augment "/nd:networks/nd:network/nd:node/coam:location-type/coam:ip-prefix-location-type" 308 +"/coam:test-point-ip-prefix-location-list/coam:test-point-locations" { 309 container bier-test-point-location-list { 310 list test-point-locations { 311 key "bier-bsl bier-subdomainid bier-bfrid"; 312 leaf bier-bsl { 313 type bier-bsl; 314 description "bier bsl"; 315 } 317 leaf bier-subdomainid { 318 type bier-subdomainid; 319 description "bier sub-domain id"; 320 } 322 leaf bier-bfrid { 323 type bier-bfrid; 324 description "bfr id"; 325 } 327 description "test point locations list "; 328 } 329 description "bier-test-point-location-list"; 330 } 331 description "bier-location-type"; 332 } 334 augment "/nd:networks/nd:network/nd:node/coam:location-type/coam:ip-prefix-location-type" 335 +"/coam:test-point-ip-prefix-location-list/coam:test-point-locations/coam:technology" { 336 case bier-oam-string{ 337 leaf bier-icmp{ 338 type string; 339 description 340 "bier icmp"; 341 } 342 description "bier oam icmp case."; 343 } 344 description "bier icmp technology."; 345 } 347 } 348 350 7. Security Considerations 352 TBD. 354 8. Acknowledgements 356 TBD. 358 9. IANA Considerations 360 TBD. 362 10. Normative References 364 [I-D.ietf-bier-architecture] 365 Wijnands, I., Rosen, E., Dolganow, A., Przygienda, T., and 366 S. Aldrin, "Multicast using Bit Index Explicit 367 Replication", draft-ietf-bier-architecture-06 (work in 368 progress), April 2017. 370 [I-D.ietf-bier-bier-yang] 371 Chen, R., hu, f., Zhang, Z., dai.xianxian@zte.com.cn, d., 372 and M. Sivakumar, "YANG Data Model for BIER Protocol", 373 draft-ietf-bier-bier-yang-01 (work in progress), January 374 2017. 376 [I-D.ietf-bier-ping] 377 Kumar, N., Pignataro, C., Akiya, N., Zheng, L., Chen, M., 378 and G. Mirsky, "BIER Ping and Trace", draft-ietf-bier- 379 ping-01 (work in progress), January 2017. 381 [I-D.ietf-lime-yang-connectionless-oam] 382 Kumar, D., Wang, Z., Wu, Q., Rahman, R., and S. Raghavan, 383 "Generic YANG Data Model for Connectionless Operations, 384 Administration, and Maintenance(OAM) protocols", draft- 385 ietf-lime-yang-connectionless-oam-06 (work in progress), 386 June 2017. 388 [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for 389 the Network Configuration Protocol (NETCONF)", RFC 6020, 390 DOI 10.17487/RFC6020, October 2010, 391 . 393 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 394 and A. Bierman, Ed., "Network Configuration Protocol 395 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 396 . 398 [RFC6291] Andersson, L., van Helvoort, H., Bonica, R., Romascanu, 399 D., and S. Mansfield, "Guidelines for the Use of the "OAM" 400 Acronym in the IETF", BCP 161, RFC 6291, 401 DOI 10.17487/RFC6291, June 2011, 402 . 404 Authors' Addresses 406 Fangwei Hu 407 ZTE Corporation 408 No.889 Bibo Rd 409 Shanghai 201203 410 China 412 Phone: +86 21 68896273 413 Email: hu.fangwei@zte.com.cn 415 Ran Chen 416 ZTE Corporation 417 No.50 Software Avenue,Yuhuatai District 418 Nanjing, Jiangsu Province 210012 419 China 421 Phone: +86 025 88014636 422 Email: chen.ran@zte.com.cn 424 Rong Gu 425 China Mobile 426 32 Xuanwumen West Ave, Xincheng District 427 Beijing 100053 428 China 430 Email: gurong@chinamobile.com