idnits 2.17.1 draft-hu-bier-oam-yang-00.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 15 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 (December 4, 2016) is 2699 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-05 == Outdated reference: A later version (-08) exists of draft-ietf-bier-bier-yang-00 == Outdated reference: A later version (-13) exists of draft-ietf-bier-ping-00 == Outdated reference: A later version (-18) exists of draft-ietf-lime-yang-connectionless-oam-02 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: June 7, 2017 R. Gu 6 China Mobile 7 December 4, 2016 9 YANG Data Model for BIER OAM 10 draft-hu-bier-oam-yang-00.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 June 7, 2017. 38 Copyright Notice 40 Copyright (c) 2016 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 . . . . . . . . . . . . . . . . . . . 9 65 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 9 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 | | NVO3 | | MPLS | | IP | . . .| foo | 192 |OAM YANG| |OAM YANG| |OAM YANG| |OAM YANG| |OAM YANG| 193 +-+-+-+-++ +-+-++--++ +-+-++--++ +-+-++--++ +-+-+-+-++ 194 | | | | | 195 | +-+-++--++ +-+-++--++ | +-+-+-+-++ 196 | | NVO3 | | MPLS | | . . .| foo | 197 | |sub tech| |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 227 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:oam-layers: 228 +--rw af 229 +--rw ipv4* [bitstringlength bier-mpls-label-base] 230 | +--rw bitstringlength uint16 231 | +--rw bier-mpls-label-base mpls:mpls-label 232 | +--rw bier-mpls-label-range-size? bier-mpls-label-range-size 233 +--rw ipv6* [bitstringlength bier-mpls-label-base] 234 +--rw bitstringlength uint16 235 +--rw bier-mpls-label-base mpls:mpls-label 236 +--rw bier-mpls-label-range-size? bier-mpls-label-range-size 238 6. BIER OAM YANG model 240 file "ietf-bier-oam@2016-12-05.yang" 241 module ietf-bier-oam { 242 namespace "urn:ietf:params:xml:ns:yang:ietf-bier-oam"; 243 prefix bieroam; 245 import ietf-bier { 246 prefix bier; 247 } 249 import ietf-connectionless-oam { 250 prefix coam; 251 } 252 import ietf-network{ 253 prefix nd; 254 } 256 organization 257 "IETF BIER(Bit Indexed Explicit Replication ) Working Group"; 259 contact 260 "WG List: 261 WG Chair: Tony Przygienda 262 264 WG Chair: Greg Shepherd 265 266 Editor: Fangwei Hu 267 268 Editor: Ran Chen 269 270 Editor: Rong Gu 271 272 "; 274 description 275 "The YANG module defines BIER OAM data model."; 277 revision 2016-12-05{ 278 description 279 "00 revision"; 280 reference 281 "draft-hu-bier-oam-yang-00"; 282 } 284 typedef bier-bsl { 285 type leafref { 286 path "/bier:bier/bier:bier-global/bier:sub-domain/bier:bitstringlength"; 287 } 288 description "bsl type"; 289 } 291 typedef bier-subdomainid { 292 type leafref { 293 path "/bier:bier/bier:bier-global/bier:sub-domain/bier:sub-domain-id"; 294 } 295 description "sub-domain-id type"; 296 } 298 typedef bier-bfrid { 299 type leafref { 300 path "/bier:bier/bier:bier-global/bier:sub-domain/bier:bfr-id"; 301 } 302 description "bfr-id type"; 304 } 306 identity bier-type { 307 base coam:tp-address-type; 308 description "bier type"; 309 } 311 augment "/nd:networks/nd:network/nd:node/coam:location-type/coam:ip-prefix-location-type" 312 +"/coam:test-point-ip-prefix-location-list/coam:test-point-locations" { 313 container bier-test-point-location-list { 314 list test-point-locations { 315 key "bier-bsl bier-subdomainid bier-bfrid"; 317 leaf bier-bsl { 318 type bier-bsl; 319 description "bier bsl"; 320 } 322 leaf bier-subdomainid { 323 type bier-subdomainid; 324 description "bier sub-domain id"; 325 } 327 leaf bier-bfrid { 328 type bier-bfrid; 329 description "bfr id"; 330 } 332 description "test point locations list "; 333 } 334 description "bier-test-point-location-list"; 335 } 336 description "bier-location-type"; 337 } 339 augment "/nd:networks/nd:network/nd:node/coam:location-type/coam:ip-prefix-location-type" 340 +"/coam:test-point-ip-prefix-location-list/coam:test-point-locations/coam:technology" { 341 case bier-oam-string{ 342 leaf bier-icmp{ 343 type string; 344 description 345 "bier icmp"; 346 } 347 description "bier oam icmp case."; 348 } 349 description "bier icmp technology."; 350 } 352 augment "/nd:networks/nd:network/nd:node/coam:location-type/coam:ip-prefix-location-type" 353 +"/coam:test-point-ip-prefix-location-list/coam:test-point-locations/coam:oam-layers" { 354 container af { 355 list ipv4 { 356 key "bitstringlength bier-mpls-label-base"; 357 uses bier:bier-mpls-cfg; 358 description 359 "Defines the necessary label ranges per bitstring length in ipv4."; 361 } 362 list ipv6 { 363 key "bitstringlength bier-mpls-label-base"; 364 uses bier:bier-mpls-cfg; 365 description 366 "Defines the necessary label ranges per bitstring length in ipv6."; 367 } 368 description "Bier mapping entries."; 369 } 370 description "bier af."; 371 } 372 } 373 375 7. Security Considerations 377 TBD. 379 8. Acknowledgements 381 TBD. 383 9. IANA Considerations 385 TBD. 387 10. Normative References 389 [I-D.ietf-bier-architecture] 390 Wijnands, I., Rosen, E., Dolganow, A., Przygienda, T., and 391 S. Aldrin, "Multicast using Bit Index Explicit 392 Replication", draft-ietf-bier-architecture-05 (work in 393 progress), October 2016. 395 [I-D.ietf-bier-bier-yang] 396 Chen, R., hu, f., Zhang, Z., dai.xianxian@zte.com.cn, d., 397 and M. Sivakumar, "YANG Data Model for BIER Protocol", 398 draft-ietf-bier-bier-yang-00 (work in progress), July 399 2016. 401 [I-D.ietf-bier-ping] 402 Kumar, N., Pignataro, C., Akiya, N., Zheng, L., Chen, M., 403 and G. Mirsky, "BIER Ping and Trace", draft-ietf-bier- 404 ping-00 (work in progress), July 2016. 406 [I-D.ietf-lime-yang-connectionless-oam] 407 Kumar, D., Wang, Z., Wu, Q., Rahman, R., and S. Raghavan, 408 "Generic YANG Data Model for Connectionless Operations, 409 Administration, and Maintenance(OAM) protocols", draft- 410 ietf-lime-yang-connectionless-oam-02 (work in progress), 411 October 2016. 413 [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for 414 the Network Configuration Protocol (NETCONF)", RFC 6020, 415 DOI 10.17487/RFC6020, October 2010, 416 . 418 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 419 and A. Bierman, Ed., "Network Configuration Protocol 420 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 421 . 423 [RFC6291] Andersson, L., van Helvoort, H., Bonica, R., Romascanu, 424 D., and S. Mansfield, "Guidelines for the Use of the "OAM" 425 Acronym in the IETF", BCP 161, RFC 6291, 426 DOI 10.17487/RFC6291, June 2011, 427 . 429 Authors' Addresses 431 Fangwei Hu 432 ZTE Corporation 433 No.889 Bibo Rd 434 Shanghai 201203 435 China 437 Phone: +86 21 68896273 438 Email: hu.fangwei@zte.com.cn 440 Ran Chen 441 ZTE Corporation 442 No.50 Software Avenue,Yuhuatai District 443 Nanjing, Jiangsu Province 210012 444 China 446 Phone: +86 025 88014636 447 Email: chen.ran@zte.com.cn 448 Rong Gu 449 China Mobile 450 32 Xuanwumen West Ave, Xincheng District 451 Beijing 100053 452 China 454 Email: gurong@chinamobile.com