idnits 2.17.1 draft-ietf-bier-bier-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 22 instances of too long lines in the document, the longest one being 45 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 122 has weird spacing: '...main-id sub...' == Line 139 has weird spacing: '...glength uin...' == Line 465 has weird spacing: '... type inet:...' == Line 591 has weird spacing: '...ational data ...' -- The document date (January 21, 2017) is 2652 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) == Unused Reference: 'I-D.ietf-bier-mpls-encapsulation' is defined on line 772, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-isis-yang-isis-cfg' is defined on line 785, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-mpls-base-yang' is defined on line 790, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-mpls-static-yang' is defined on line 796, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-netmod-routing-cfg' is defined on line 802, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-ospf-yang' is defined on line 807, but no explicit reference was found in the text == Unused Reference: 'RFC6020' is defined on line 812, but no explicit reference was found in the text == Unused Reference: 'RFC6241' is defined on line 817, but no explicit reference was found in the text == Unused Reference: 'RFC6991' is defined on line 822, but no explicit reference was found in the text == Unused Reference: 'RFC7223' is defined on line 826, but no explicit reference was found in the text == Outdated reference: A later version (-08) exists of draft-ietf-bier-architecture-05 == Outdated reference: A later version (-11) exists of draft-ietf-bier-isis-extensions-03 == Outdated reference: A later version (-12) exists of draft-ietf-bier-mpls-encapsulation-06 == Outdated reference: A later version (-18) exists of draft-ietf-bier-ospf-bier-extensions-04 == Outdated reference: A later version (-42) exists of draft-ietf-isis-yang-isis-cfg-14 == Outdated reference: A later version (-17) exists of draft-ietf-mpls-base-yang-01 == Outdated reference: A later version (-14) exists of draft-ietf-mpls-static-yang-02 == Outdated reference: A later version (-29) exists of draft-ietf-ospf-yang-06 ** Obsolete normative reference: RFC 7223 (Obsoleted by RFC 8343) Summary: 2 errors (**), 0 flaws (~~), 23 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 BIER WG Ran. Chen 3 Internet-Draft Fangwei. Hu 4 Intended status: Standards Track Zheng. Zhang 5 Expires: July 25, 2017 Xianxia. Dai 6 ZTE Corporation 7 Mahesh Sivakumar 8 Cisco Systems, Inc. 9 January 21, 2017 11 YANG Data Model for BIER Protocol 12 draft-ietf-bier-bier-yang-01.txt 14 Abstract 16 This document defines a YANG data model for BIER configuration and 17 operation. 19 Status of This Memo 21 This Internet-Draft is submitted in full conformance with the 22 provisions of BCP 78 and BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF). Note that other groups may also distribute 26 working documents as Internet-Drafts. The list of current Internet- 27 Drafts is at http://datatracker.ietf.org/drafts/current/. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 This Internet-Draft will expire on July 25, 2017. 36 Copyright Notice 38 Copyright (c) 2017 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents 43 (http://trustee.ietf.org/license-info) in effect on the date of 44 publication of this document. Please review these documents 45 carefully, as they describe your rights and restrictions with respect 46 to this document. Code Components extracted from this document must 47 include Simplified BSD License text as described in Section 4.e of 48 the Trust Legal Provisions and are provided without warranty as 49 described in the Simplified BSD License. 51 Table of Contents 53 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 54 2. Design of the Data Model . . . . . . . . . . . . . . . . . . 2 55 3. Configuration . . . . . . . . . . . . . . . . . . . . . . . . 4 56 4. Control plane configuration . . . . . . . . . . . . . . . . . 4 57 5. States . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 58 6. Notification . . . . . . . . . . . . . . . . . . . . . . . . 5 59 7. BIER YANG Data Model . . . . . . . . . . . . . . . . . . . . 5 60 8. Security Considerations . . . . . . . . . . . . . . . . . . . 16 61 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 16 62 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16 63 11. Normative references . . . . . . . . . . . . . . . . . . . . 16 64 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18 66 1. Introduction 68 This document defines a YANG data model for BIER configuration and 69 operation. 71 2. Design of the Data Model 73 module: ietf-bier 74 augment /rt:routing: 75 +--rw bier 76 +--rw bier-global 77 +--rw encapsulation-type? identityref 78 +--rw bitstringlength? bsl 79 +--rw bfr-id? bfr-id 80 +--rw ipv4-bfr-prefix? inet:ipv4-prefix 81 +--rw ipv6-bfr-prefix? inet:ipv6-prefix 82 +--rw sub-domain* [sub-domain-id] 83 +--rw sub-domain-id sub-domain-id 84 +--rw igp-type? igp-type 85 +--rw mt-id? mt-id 86 +--rw bfr-id? bfr-id 87 +--rw bitstringlength? bsl 88 +--rw af 89 +--rw ipv4* [bitstringlength bier-mpls-label-base] 90 | +--rw bitstringlength uint16 91 | +--rw bier-mpls-label-base mpls:mpls-label 92 | +--rw bier-mpls-label-range-size? bier-mpls-label-range-size 93 +--rw ipv6* [bitstringlength bier-mpls-label-base] 94 +--rw bitstringlength uint16 95 +--rw bier-mpls-label-base mpls:mpls-label 96 +--rw bier-mpls-label-range-size? bier-mpls-label-range-size 98 augment /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol/ospf:ospf/ospf:instance: 99 +--rw bier-ospf-cfg 100 +--rw mt-id mt-id 101 +--rw bier-global 102 +--rw enable? boolean 103 +--rw advertise? boolean 104 +--rw receive? boolean 106 augment /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol/isis:isis: 107 +--rw bier-isis-cfg 108 +--rw mt-id mt-id 109 +--rw bier-global 110 +--rw enable? boolean 111 +--rw advertise? boolean 112 +--rw receive? boolean 114 augment /rt:routing-state: 115 +--ro bier-global 116 | +--ro encapsulation-type? identityref 117 | +--ro bitstringlength? bsl 118 | +--ro bfr-id? bfr-id 119 | +--ro ipv4-bfr-prefix? inet:ipv4-prefix 120 | +--ro ipv6-bfr-prefix? inet:ipv6-prefix 121 | +--ro sub-domain* [sub-domain-id] 122 | +--ro sub-domain-id sub-domain-id 123 | +--ro igp-type igp-type 124 | +--ro mt-id? mt-id 125 | +--ro bfr-id? bfr-id 126 | +--rw bitstringlength? bsl 127 | +--ro ipv4* [bitstringlength bier-mpls-label-base] 128 | | +--ro bitstringlength uint16 129 | | +--ro bier-mpls-label-base mpls:mpls-label 130 | | +--ro bier-mpls-label-range-size? bier-mpls-label-range-size 131 | +--ro ipv6* [bitstringlength bier-mpls-label-base] 132 | +--ro bitstringlength uint16 133 | +--ro bier-mpls-label-base mpls:mpls-label 134 | +--ro bier-mpls-label-range-size? bier-mpls-label-range-size 135 +--ro birts 136 +--ro birt* [sub-domain-id] 137 +--ro sub-domain-id sub-domain-id 138 +--ro birt-bitstringlength* [bitstringlength] 139 +--ro bitstringlength uint16 140 +--ro birt-si* [si] 141 +--ro si si 142 +--ro f-bm? uint16 143 +--ro bier-mpls-in-label? mpls:mpls-label 144 +--ro bfr-nbr? inet:ip-address 145 +--ro bier-mpls-out-label? mpls:mpls-label 146 notifications: 147 +---n bfr-id-collision 148 | +--ro bfr-id? bfr-id 149 +---n bfr-zero 150 | +--ro ipv4-bfr-prefix? inet:ipv4-prefix 151 | +--ro ipv6-bfr-prefix? inet:ipv6-prefix 152 +---n sub-domain-id-collision 153 +--ro sub-domain-id? sub-domain-id 154 +--ro mt-id? uint16 156 3. Configuration 158 This Module augments the "/rt:routing:" with a BIER container. This 159 Container defines all the configuration parameters related to BIER 160 for this particular routing. 162 The BIER configuration contains global configuration. 164 The global configuration includes BIER encapsulation type, imposition 165 BitStringLengths, BFR-id, BFR-prefixes, and parameters associated 166 with bier sub-domain. 168 In this document, we contains two types of BitStringLengths: 169 Imposition and Disposition BitStringLengths, as defined in 170 ([I-D.ietf-bier-architecture]).The imposition BitStringLengths is 171 defined under bier-global container, and the disposition 172 BitStringLengths is defined under the sub-domain. 174 4. Control plane configuration 176 This Module augments the "/rt:routing/rt:routing-protocols/ 177 rt:routing-protocol/ospf:ospf/ospf:instance:" and "/rt:routing/ 178 rt:routing-protocols/rt:routing-protocol/isis:isis:"configuration 179 with BIER. 181 This Module supports ISIS ([I-D.ietf-bier-isis-extensions])and OSPF 182 ([I-D.ietf-bier-ospf-bier-extensions]) as control plane for BIER. 184 5. States 186 The operational states contains basic parameters associated with 187 bier, such as BIER encapsulation type, BitStringLengths, BFR-id, BFR- 188 prefixes, and parameters associated with bier sub-domain. 190 It also includes the Bit Index Routing Table(BIRT). 192 6. Notification 194 This Module includes bfr-id-collision, bfr-zero, and sub-domain-id- 195 collision. 197 7. BIER YANG Data Model 199 file "ietf-bier.yang" 200 module ietf-bier { 202 namespace "urn:ietf:params:xml:ns:yang:ietf-bier"; 204 prefix "bier"; 206 import ietf-routing { 207 prefix "rt"; 208 } 210 import ietf-inet-types { 211 prefix "inet"; 212 } 214 import ietf-mpls { 215 prefix "mpls"; 216 } 218 import ietf-isis{ 219 prefix "isis"; 220 } 222 import ietf-ospf { 223 prefix "ospf"; 224 } 226 organization 227 "IETF BIER(Bit Indexed Explicit Replication ) Working Group"; 229 contact 230 "WG List: 232 WG Chair: Tony Przygienda 233 235 WG Chair: Greg Shepherd 236 238 Editor: Ran Chen 239 240 Editor: Fangwei Hu 241 242 Editor: Zheng Zhang 243 244 Editor: Xianxian Dai 245 246 Editor: Mahesh Sivakumar 247 248 "; 249 description 250 "The YANG module defines a generic configuration 251 model for BIER."; 253 revision 2017-01-20{ 254 description 255 "01 revision"; 256 reference 257 "draft-ietf-bier-bier-yang-01"; 258 } 260 revision 2016-07-23{ 261 description 262 "00 revision"; 263 reference 264 "draft-ietf-bier-bier-yang-00"; 265 } 267 revision 2016-05-12{ 268 description 269 "04 revision"; 270 reference 271 "draft-chh-bier-bier-yang-04"; 272 } 274 revision 2016-03-16 { 275 description 276 "03 revision"; 277 reference 278 "draft-chh-bier-bier-yang-03"; 279 } 281 revision 2015-12-03 { 282 description 283 "02 revision"; 284 reference 285 "draft-chh-bier-bier-yang-02"; 287 } 289 revision 2015-10-16 { 290 description 291 "01 revision."; 292 reference 293 "draft-chh-bier-bier-yang-01"; 294 } 296 revision 2015-06-22 { 297 description 298 "Initial revision."; 299 reference 300 "draft-chh-bier-bier-yang-00"; 301 } 303 /* Identities */ 304 identity bier-encapsulation{ 305 description 306 "Base identity for BIER encapsulation."; 307 } 308 identity bier-encapsulation-mpls { 309 base bier-encapsulation; 310 description 311 "This identity represents MPLS encapsulation for bier."; 312 } 314 /*Typedefs*/ 316 typedef sub-domain-id { 317 type uint16; 318 description 319 "The type for sub-domain-id"; 320 } 322 typedef si { 323 type uint16; 324 description 325 "The type for set identifier"; 326 } 328 typedef bfr-id { 329 type uint16; 330 description 331 "The type for bfr identifier"; 332 } 334 typedef mt-id { 335 type uint16; 336 description 337 "The type for multi-topology identifier"; 338 } 340 typedef bier-mpls-label-range-size{ 341 type uint8; 342 description 343 "The type for BIER label range size."; 344 } 346 typedef bsl { 347 type enumeration{ 348 enum 64-bit{ 349 value 1; 350 description 351 "bitstringlength is 64"; 352 } 353 enum 128-bit{ 354 value 2; 355 description 356 "bitstringlength is 128"; 357 } 358 enum 256-bit{ 359 value 3; 360 description 361 "bitstringlength is 256"; 362 } 363 enum 512-bit{ 364 value 4; 365 description 366 "bitstringlength is 512"; 367 } 368 enum 1024-bit{ 369 value 5; 370 description 371 "bitstringlength is 1024"; 372 } 373 enum 2048-bit{ 374 value 6; 375 description 376 "bitstringlength is 2048"; 377 } 378 enum 4096-bit{ 379 value 7; 380 description 381 "bitstringlength is 4096"; 382 } 384 } 385 description 386 "The bitstringlength type for imposition mode"; 387 } 389 typedef igp-type { 390 type enumeration{ 391 enum ISIS{ 392 value 1; 393 description 394 "isis protocol"; 395 } 396 enum OSPF{ 397 value 2; 398 description 399 "ospf protocol"; 400 } 401 } 402 description 403 "The IGP type"; 404 } 406 /*grouping*/ 407 grouping bier-protocol-extensions{ 408 leaf mt-id{ 409 type mt-id; 410 description 411 "Multi-topology associated with bier sub-domain."; 412 } 413 container bier-global { 414 leaf enable { 415 type boolean; 416 default false; 417 description 418 "Enables bier protocol extensions."; 419 } 420 leaf advertise { 421 type boolean; 422 default true; 423 description 424 "Enable to advertise the parameters associated with bier."; 425 } 426 leaf receive { 427 type boolean; 428 default true; 429 description 430 "Enable to receive the parameters associated with bier."; 431 } 433 description 434 "BIER global config."; 435 } 436 description 437 "Defines protocol extensions."; 438 } 440 grouping bier-parameters{ 441 leaf encapsulation-type { 442 type identityref { 443 base bier-encapsulation; 444 } 445 default "bier-encapsulation-mpls"; 446 description 447 "Dataplane to be used."; 448 } 449 leaf bitstringlength{ 450 type bsl; 451 description 452 "imposition bitstringlength."; 453 } 454 leaf bfr-id { 455 type bfr-id; 456 description 457 "BIER bfr identifier."; 458 } 459 leaf ipv4-bfr-prefix { 460 type inet:ipv4-prefix; 461 description 462 "BIER IPv4 prefix."; 463 } 464 leaf ipv6-bfr-prefix { 465 type inet:ipv6-prefix; 466 description 467 "BIER IPv6 prefix."; 468 } 469 description 470 " BIER parameters."; 471 } 473 grouping bier-mpls-cfg{ 474 leaf bitstringlength { 475 type uint16; 476 description 477 "BIER bitstringlength."; 478 } 479 leaf bier-mpls-label-base{ 480 type mpls:mpls-label; 481 description 482 "BIER label base."; 483 } 484 leaf bier-mpls-label-range-size{ 485 type bier-mpls-label-range-size; 486 description 487 "BIER label range."; 488 } 489 description 490 "Defines the necessary label ranges per bitstring length."; 491 } 493 /* Configuration Data */ 494 augment "/rt:routing" { 495 description 496 "This augments routing-instance configuration with bier."; 497 container bier{ 498 container bier-global { 499 uses bier-parameters; 500 list sub-domain{ 501 key "sub-domain-id"; 502 leaf sub-domain-id{ 503 type sub-domain-id; 504 description 505 "sub-domain ID."; 506 } 507 leaf igp-type { 508 type igp-type; 509 description 510 "IGP type."; 511 } 512 leaf mt-id { 513 type mt-id; 514 description 515 "multi-topology ID."; 516 } 517 leaf bfr-id{ 518 type bfr-id; 519 description 520 "BIER bfr identifier."; 521 } 523 leaf bitstringlength{ 524 type bsl; 525 description 526 "Disposition bitstringlength."; 527 } 529 container af { 530 list ipv4 { 531 key "bitstringlength bier-mpls-label-base"; 532 uses bier-mpls-cfg; 534 description 535 "Defines the necessary label ranges per bitstring length in ipv4."; 536 } 537 list ipv6 { 538 key "bitstringlength bier-mpls-label-base"; 539 uses bier-mpls-cfg; 541 description 542 "Defines the necessary label ranges per bitstring length in ipv6."; 543 } 544 description 545 "Bier mapping entries."; 546 } 547 description 548 "Denfines subdomain configuration"; 549 } 550 description 551 "BIER global config."; 552 } 553 description "BIER config."; 554 } 555 } 557 augment "/rt:routing/rt:control-plane-protocols/" 558 + "rt:control-plane-protocol/ospf:ospf/ospf:instance" { 559 when "../../rt:type = 'ospf:ospfv2' or 560 ../../rt:type = 'ospf:ospfv3'" { 561 description 562 "This augments the ospf routing protocol when used"; 563 } 564 description 565 "This augments ospf protocol configuration with bier."; 566 container bier-ospf-cfg{ 567 uses bier-protocol-extensions; 568 description 569 "Control of bier advertisement and reception."; 570 } 571 } 573 augment "/rt:routing/rt:control-plane-protocols/" 574 +"rt:control-plane-protocol/isis:isis"{ 575 when "/rt:routing/rt:control-plane-protocols/"+ 576 "rt:control-plane-protocol/rt:type = 'isis:isis'" { 578 description 579 "This augment ISIS routing protocol when used"; 580 } 581 description 582 "This augments ISIS protocol configuration with bier."; 583 container bier-isis-cfg{ 584 uses bier-protocol-extensions; 585 description 586 "Control of bier advertisement and reception."; 588 } 589 } 591 /* Operational data */ 592 augment "/rt:routing-state" { 593 description 594 "This augments the operational states with bier."; 595 container bier-global{ 596 uses bier-parameters; 597 list sub-domain{ 598 key "sub-domain-id"; 599 leaf sub-domain-id{ 600 type sub-domain-id; 601 description 602 "sub-domain ID."; 603 } 604 leaf igp-type { 605 type igp-type; 606 description 607 "IGP type."; 608 } 609 leaf mt-id { 610 type mt-id; 611 description 612 "multi-topology ID."; 613 } 614 leaf bfr-id{ 615 type bfr-id; 616 description 617 "BIER bfr identifier."; 618 } 620 leaf bitstringlength{ 621 type bsl; 622 description 623 "Disposition bitstringlength."; 624 } 625 list ipv4 { 626 key "bitstringlength bier-mpls-label-base"; 627 uses bier-mpls-cfg; 628 description 629 "Show the necessary label ranges per bitstring length in ipv4."; 630 } 631 list ipv6 { 632 key "bitstringlength bier-mpls-label-base"; 633 uses bier-mpls-cfg; 634 description 635 "Show the necessary label ranges per bitstring length in ipv6."; 636 } 637 description 638 "Denfines subdomain configuration"; 639 } 640 description 641 "Parameters associated with bier."; 642 } 644 container birts{ 645 list birt{ 646 key "sub-domain-id"; 647 leaf sub-domain-id{ 648 type sub-domain-id; 649 description 650 "BIER sub domain ID"; 651 } 652 list birt-bitstringlength { 653 key "bitstringlength"; 654 leaf bitstringlength{ 655 type uint16; 656 description 657 "BIER bitstringlength."; 658 } 659 list birt-si { 660 key "si"; 661 leaf si{ 662 type si; 663 description 664 "BIER set identifier."; 665 } 666 leaf f-bm{ 667 type uint16; 668 description 669 "BIER Forwarding Bit Mask."; 670 } 671 leaf bier-mpls-in-label{ 672 type mpls:mpls-label; 673 description 674 "BIER in-label."; 675 } 676 leaf bfr-nbr{ 677 type inet:ip-address; 678 description 679 "BIER BFR Neighbors."; 680 } 681 leaf bier-mpls-out-label{ 682 type mpls:mpls-label; 683 description 684 "BIER out-label."; 685 } 686 description 687 "Query the BIRT based on the key set identifier & bitstringlength & sub-domain-id."; 688 } 689 description 690 "Query the BIRT based on the key bitstringlengt & sub-domain-id."; 691 } 692 description 693 "Query the BIRT based on the key sub-domain."; 694 } 695 description 696 "Shows Bit Index Routing Table."; 697 } 698 } 700 /* Notifications */ 701 notification bfr-id-collision{ 702 leaf bfr-id{ 703 type bfr-id; 704 description 705 "BIER BFR ID."; 706 } 707 description 708 "BFR ID received in the controlplane that caused BFR ID collision."; 709 } 711 notification bfr-zero{ 712 leaf ipv4-bfr-prefix{ 713 type inet:ipv4-prefix; 714 description 715 "BIER ipv4 bfr prefix"; 716 } 717 leaf ipv6-bfr-prefix{ 718 type inet:ipv6-prefix; 719 description 720 "BIER ipv6 bfr prefix"; 722 } 723 description 724 "Invalid value associated with prefix"; 725 } 727 notification sub-domain-id-collision{ 728 leaf sub-domain-id{ 729 type sub-domain-id; 730 description 731 "BIER sub domain ID"; 732 } 733 leaf mt-id{ 734 type uint16; 735 description 736 "Multi-topology ID"; 737 } 738 description 739 "Sub domain ID received in the controlplane that caused Sub domain ID collision"; 740 } 741 } 743 745 8. Security Considerations 747 TBD. 749 9. Acknowledgements 751 We would like to thank IJsbrand Wijnands, Reshad Rahman and Giles 752 Heron for their comments and support of this work. 754 10. IANA Considerations 756 This document requires no IANA Actions. Please remove this section 757 before RFC publication. 759 11. Normative references 761 [I-D.ietf-bier-architecture] 762 Wijnands, I., Rosen, E., Dolganow, A., Przygienda, T., and 763 S. Aldrin, "Multicast using Bit Index Explicit 764 Replication", draft-ietf-bier-architecture-05 (work in 765 progress), October 2016. 767 [I-D.ietf-bier-isis-extensions] 768 Ginsberg, L., Przygienda, T., Aldrin, S., and Z. Zhang, 769 "BIER support via ISIS", draft-ietf-bier-isis- 770 extensions-03 (work in progress), September 2016. 772 [I-D.ietf-bier-mpls-encapsulation] 773 Wijnands, I., Rosen, E., Dolganow, A., Tantsura, J., 774 Aldrin, S., and I. Meilik, "Encapsulation for Bit Index 775 Explicit Replication in MPLS and non-MPLS Networks", 776 draft-ietf-bier-mpls-encapsulation-06 (work in progress), 777 December 2016. 779 [I-D.ietf-bier-ospf-bier-extensions] 780 Psenak, P., Kumar, N., Wijnands, I., Dolganow, A., 781 Przygienda, T., Zhang, Z., and S. Aldrin, "OSPF Extensions 782 for BIER", draft-ietf-bier-ospf-bier-extensions-04 (work 783 in progress), September 2016. 785 [I-D.ietf-isis-yang-isis-cfg] 786 Litkowski, S., Yeung, D., Lindem, A., Zhang, Z., and L. 787 Lhotka, "YANG Data Model for IS-IS protocol", draft-ietf- 788 isis-yang-isis-cfg-14 (work in progress), November 2016. 790 [I-D.ietf-mpls-base-yang] 791 Raza, K., Gandhi, R., Liu, X., Beeram, V., Saad, T., 792 Bryskin, I., Chen, X., Jones, R., and B. Wen, "A YANG Data 793 Model for MPLS Base", draft-ietf-mpls-base-yang-01 (work 794 in progress), July 2016. 796 [I-D.ietf-mpls-static-yang] 797 Saad, T., Raza, K., Gandhi, R., Liu, X., Beeram, V., Shah, 798 H., Bryskin, I., Chen, X., Jones, R., and B. Wen, "A YANG 799 Data Model for MPLS Static LSPs", draft-ietf-mpls-static- 800 yang-02 (work in progress), January 2017. 802 [I-D.ietf-netmod-routing-cfg] 803 Lhotka, L. and A. Lindem, "A YANG Data Model for Routing 804 Management", draft-ietf-netmod-routing-cfg-25 (work in 805 progress), November 2016. 807 [I-D.ietf-ospf-yang] 808 Yeung, D., Qu, Y., Zhang, Z., Chen, I., and A. Lindem, 809 "Yang Data Model for OSPF Protocol", draft-ietf-ospf- 810 yang-06 (work in progress), October 2016. 812 [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for 813 the Network Configuration Protocol (NETCONF)", RFC 6020, 814 DOI 10.17487/RFC6020, October 2010, 815 . 817 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 818 and A. Bierman, Ed., "Network Configuration Protocol 819 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 820 . 822 [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", 823 RFC 6991, DOI 10.17487/RFC6991, July 2013, 824 . 826 [RFC7223] Bjorklund, M., "A YANG Data Model for Interface 827 Management", RFC 7223, DOI 10.17487/RFC7223, May 2014, 828 . 830 Authors' Addresses 832 Ran Chen 833 ZTE Corporation 834 No.50 Software Avenue,Yuhuatai District 835 Nanjing, Jiangsu Province 210012 836 China 838 Phone: +86 025 88014636 839 Email: chen.ran@zte.com.cn 841 Fangwei Hu 842 ZTE Corporation 843 No.889 Bibo Rd 844 Shanghai 201203 845 China 847 Phone: +86 21 68896273 848 Email: hu.fangwei@zte.com.cn 850 Zheng Zhang 851 ZTE Corporation 852 No.50 Software Avenue,Yuhuatai District 853 Nanjing, Jiangsu Province 210012 854 China 856 Email: zhang.zheng@zte.com.cn 857 Xianxian Dai 858 ZTE Corporation 859 No.50 Software Avenue,Yuhuatai District 860 Nanjing, Jiangsu Province 210012 861 China 863 Email: Dai.xianxian@zte.com.cn 865 Mahesh Sivakumar 866 Cisco Systems, Inc. 867 510 McCarthy Blvd 868 Milpitas,California 95035 869 United States 871 Email: masivaku@cisco.com