idnits 2.17.1 draft-ietf-bier-bier-yang-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 : ---------------------------------------------------------------------------- ** There are 24 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 105 has weird spacing: '...main-id sub...' == Line 122 has weird spacing: '...glength uin...' == Line 468 has weird spacing: '... type inet:...' -- The document date (February 6, 2018) is 2271 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 (-11) exists of draft-ietf-bier-isis-extensions-06 == Outdated reference: A later version (-18) exists of draft-ietf-bier-ospf-bier-extensions-10 == Outdated reference: A later version (-42) exists of draft-ietf-isis-yang-isis-cfg-19 == Outdated reference: A later version (-17) exists of draft-ietf-mpls-base-yang-05 == Outdated reference: A later version (-14) exists of draft-ietf-mpls-static-yang-04 == Outdated reference: A later version (-29) exists of draft-ietf-ospf-yang-09 ** Obsolete normative reference: RFC 7223 (Obsoleted by RFC 8343) Summary: 2 errors (**), 0 flaws (~~), 20 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: August 10, 2018 Xianxia. Dai 6 ZTE Corporation 7 Mahesh. Sivakumar 8 Cisco Systems, Inc. 9 February 6, 2018 11 YANG Data Model for BIER Protocol 12 draft-ietf-bier-bier-yang-03.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 https://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 August 10, 2018. 36 Copyright Notice 38 Copyright (c) 2018 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 (https://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 . . . . . . . . . . . . . . . . . . . . 17 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 rt-types:mpls-label 92 | | +--rw bier-mpls-label-range-size? bier-mpls-label-range-size 93 | +--rw ipv6* [bitstringlength bier-mpls-label-base] 94 | +--rw bitstrin+--glength uint16 95 | +--rw bier-mpls-label-base rt-types:mpls-label 96 | +--rw bier-mpls-label-range-size? bier-mpls-label-range-size 97 +--ro bier-state 98 +---bier-global-state 99 | +--ro encapsulation-type? identityref 100 | +--ro bitstringlength? bsl 101 | +--ro bfr-id? bfr-id 102 | +--ro ipv4-bfr-prefix? inet:ipv4-prefix 103 | +--ro ipv6-bfr-prefix? inet:ipv6-prefix 104 | +--ro sub-domain* [sub-domain-id] 105 | +--ro sub-domain-id sub-domain-id 106 | +--ro igp-type igp-type 107 | +--ro mt-id? mt-id 108 | +--ro bfr-id? bfr-id 109 | +--rw bitstringlength? bsl 110 | +--ro ipv4* [bitstringlength bier-mpls-label-base] 111 | | +--ro bitstringlength uint16 112 | | +--ro bier-mpls-label-base rt-types:mpls-label 113 | | +--ro bier-mpls-label-range-size? bier-mpls-label-range-size 114 | +--ro ipv6* [bitstringlength bier-mpls-label-base] 115 | +--ro bitstringlength uint16 116 | +--ro bier-mpls-label-base rt-types:mpls-label 117 | +--ro bier-mpls-label-range-size? bier-mpls-label-range-size 118 +--ro birts-state 119 +--ro birt* [sub-domain-id] 120 +--ro sub-domain-id sub-domain-id 121 +--ro birt-bitstringlength* [bitstringlength] 122 +--ro bitstringlength uint16 123 +--ro birt-si* [si] 124 +--ro si si 125 +--ro f-bm? uint16 126 +--ro bier-mpls-in-label? rt-types:mpls-label 127 +--ro bfr-nbr? inet:ip-address 128 +--ro bier-mpls-out-label? rt-types:mpls-label 130 augment /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol/ospf:ospf/ospf:instance: 131 +--rw bier-ospf-cfg 132 +--rw mt-id mt-id 133 +--rw bier-global 134 +--rw enable? boolean 135 +--rw advertise? boolean 136 +--rw receive? boolean 138 augment /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol/isis:isis: 139 +--rw bier-isis-cfg 140 +--rw mt-id mt-id 141 +--rw bier-global 142 +--rw enable? boolean 143 +--rw advertise? boolean 144 +--rw receive? boolean 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@2018-02-07.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-routing-types { 215 prefix "rt-types"; 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 2018-02-07{ 254 description 255 "latest revision"; 256 reference "RFC XXXX: YANG Data Model for BIER Protocol."; 257 } 259 revision 2017-08-10{ 260 description 261 "02 revision"; 262 reference "RFC XXXX: YANG Data Model for BIER Protocol."; 264 } 266 revision 2017-01-20{ 267 description 268 "01 revision"; 269 reference "RFC XXXX: YANG Data Model for BIER Protocol."; 270 } 272 revision 2016-07-23{ 273 description 274 "00 revision"; 275 reference "RFC XXXX: YANG Data Model for BIER Protocol."; 276 } 278 revision 2016-05-12{ 279 description 280 "04 revision"; 281 reference "RFC XXXX: YANG Data Model for BIER Protocol."; 282 } 284 revision 2016-03-16 { 285 description 286 "03 revision"; 287 reference "RFC XXXX: YANG Data Model for BIER Protocol."; 288 } 290 revision 2015-12-03 { 291 description 292 "02 revision"; 293 reference "RFC XXXX: YANG Data Model for BIER Protocol."; 294 } 296 revision 2015-10-16 { 297 description 298 "01 revision."; 299 reference "RFC XXXX: YANG Data Model for BIER Protocol."; 300 } 302 revision 2015-06-22 { 303 description 304 "Initial revision."; 305 reference "RFC XXXX: YANG Data Model for BIER Protocol."; 306 } 308 /* Identities */ 309 identity bier-encapsulation{ 310 description 311 "Base identity for BIER encapsulation."; 312 } 313 identity bier-encapsulation-mpls { 314 base bier-encapsulation; 315 description 316 "This identity represents MPLS encapsulation for bier."; 317 } 319 /*Typedefs*/ 321 typedef sub-domain-id { 322 type uint16; 323 description 324 "The type for sub-domain-id"; 325 } 327 typedef si { 328 type uint16; 329 description 330 "The type for set identifier"; 331 } 332 typedef bfr-id { 333 type uint16; 334 description 335 "The type for bfr identifier"; 336 } 338 typedef mt-id { 339 type uint16; 340 description 341 "The type for multi-topology identifier"; 342 } 344 typedef bier-mpls-label-range-size{ 345 type uint8; 346 description 347 "The type for BIER label range size."; 348 } 350 typedef bsl { 351 type enumeration{ 352 enum 64-bit{ 353 value 1; 354 description 355 "bitstringlength is 64"; 356 } 357 enum 128-bit{ 358 value 2; 359 description 360 "bitstringlength is 128"; 361 } 362 enum 256-bit{ 363 value 3; 364 description 365 "bitstringlength is 256"; 366 } 367 enum 512-bit{ 368 value 4; 369 description 370 "bitstringlength is 512"; 371 } 372 enum 1024-bit{ 373 value 5; 374 description 375 "bitstringlength is 1024"; 376 } 377 enum 2048-bit{ 378 value 6; 379 description 380 "bitstringlength is 2048"; 381 } 382 enum 4096-bit{ 383 value 7; 384 description 385 "bitstringlength is 4096"; 386 } 387 } 388 description 389 "The bitstringlength type for imposition mode"; 390 } 392 typedef igp-type { 393 type enumeration{ 394 enum ISIS{ 395 value 1; 396 description 397 "isis protocol"; 398 } 399 enum OSPF{ 400 value 2; 401 description 402 "ospf protocol"; 403 } 404 } 405 description 406 "The IGP type"; 407 } 409 /*grouping*/ 410 grouping bier-protocol-extensions{ 411 leaf mt-id{ 412 type mt-id; 413 description 414 "Multi-topology associated with bier sub-domain."; 415 } 416 container bier-global { 417 leaf enable { 418 type boolean; 419 default false; 420 description 421 "Enables bier protocol extensions."; 422 } 423 leaf advertise { 424 type boolean; 425 default true; 426 description 427 "Enable to advertise the parameters associated with bier."; 429 } 430 leaf receive { 431 type boolean; 432 default true; 433 description 434 "Enable to receive the parameters associated with bier."; 435 } 436 description 437 "BIER global config."; 438 } 439 description 440 "Defines protocol extensions."; 441 } 443 grouping bier-parameters{ 444 leaf encapsulation-type { 445 type identityref { 446 base bier-encapsulation; 447 } 448 default "bier-encapsulation-mpls"; 449 description 450 "Dataplane to be used."; 451 } 452 leaf bitstringlength{ 453 type bsl; 454 description 455 "imposition bitstringlength."; 456 } 457 leaf bfr-id { 458 type bfr-id; 459 description 460 "BIER bfr identifier."; 461 } 462 leaf ipv4-bfr-prefix { 463 type inet:ipv4-prefix; 464 description 465 "BIER IPv4 prefix."; 466 } 467 leaf ipv6-bfr-prefix { 468 type inet:ipv6-prefix; 469 description 470 "BIER IPv6 prefix."; 471 } 472 description 473 " BIER parameters."; 474 } 476 grouping bier-mpls-cfg{ 477 leaf bitstringlength { 478 type uint16; 479 description 480 "BIER bitstringlength."; 481 } 482 leaf bier-mpls-label-base{ 483 type rt-types:mpls-label; 484 description 485 "BIER label base."; 486 } 487 leaf bier-mpls-label-range-size{ 488 type bier-mpls-label-range-size; 489 description 490 "BIER label range."; 491 } 492 description 493 "Defines the necessary label ranges per bitstring length."; 494 } 496 augment "/rt:routing" { 497 description 498 "This augments routing-instance configuration with bier."; 499 container bier{ 500 container bier-global { 501 uses bier-parameters; 502 list sub-domain{ 503 key "sub-domain-id"; 504 leaf sub-domain-id{ 505 type sub-domain-id; 506 description 507 "sub-domain ID."; 508 } 509 leaf igp-type { 510 type igp-type; 511 description 512 "IGP type."; 513 } 514 leaf mt-id { 515 type mt-id; 516 description 517 "multi-topology ID."; 518 } 519 leaf bfr-id{ 520 type bfr-id; 521 description 522 "BIER bfr identifier."; 523 } 525 leaf bitstringlength{ 526 type bsl; 527 description 528 "Disposition bitstringlength."; 529 } 531 container af { 532 list ipv4 { 533 key "bitstringlength bier-mpls-label-base"; 534 uses bier-mpls-cfg; 536 description 537 "Defines the necessary label ranges per bitstring length in ipv4."; 538 } 539 list ipv6 { 540 key "bitstringlength bier-mpls-label-base"; 541 uses bier-mpls-cfg; 543 description 544 "Defines the necessary label ranges per bitstring length in ipv6."; 545 } 546 description 547 "Bier mapping entries."; 548 } 549 description 550 "Denfines subdomain configuration"; 551 } 552 description 553 "BIER global config."; 554 } 555 description "BIER config."; 556 } 557 container bier-state{ 558 config false; 559 description 560 "BIER operational state."; 561 container bier-global-state{ 562 config false; 563 uses bier-parameters; 564 list sub-domain{ 565 key "sub-domain-id"; 566 leaf sub-domain-id{ 567 type sub-domain-id; 568 description 569 "sub-domain ID."; 570 } 571 leaf igp-type { 572 type igp-type; 573 description 574 "IGP type."; 575 } 576 leaf mt-id { 577 type mt-id; 578 description 579 "multi-topology ID."; 580 } 581 leaf bfr-id{ 582 type bfr-id; 583 description 584 "BIER bfr identifier."; 585 } 587 leaf bitstringlength{ 588 type bsl; 589 description 590 "Disposition bitstringlength."; 591 } 592 list ipv4 { 593 key "bitstringlength bier-mpls-label-base"; 594 uses bier-mpls-cfg; 595 description 596 "Show the necessary label ranges per bitstring length in ipv4."; 597 } 598 list ipv6 { 599 key "bitstringlength bier-mpls-label-base"; 600 uses bier-mpls-cfg; 601 description 602 "Show the necessary label ranges per bitstring length in ipv6."; 603 } 604 description 605 "Denfines subdomain configuration"; 606 } 607 description 608 "Parameters associated with bier."; 609 } 611 container birts-state{ 612 list birt{ 613 key "sub-domain-id"; 614 leaf sub-domain-id{ 615 type sub-domain-id; 616 description 617 "BIER sub domain ID"; 618 } 619 list birt-bitstringlength { 620 key "bitstringlength"; 621 leaf bitstringlength{ 622 type uint16; 623 description 624 "BIER bitstringlength."; 625 } 626 list birt-si { 627 key "si"; 628 leaf si{ 629 type si; 630 description 631 "BIER set identifier."; 632 } 633 leaf f-bm{ 634 type uint16; 635 description 636 "BIER Forwarding Bit Mask."; 637 } 638 leaf bier-mpls-in-label{ 639 type rt-types:mpls-label; 640 description 641 "BIER in-label."; 642 } 643 leaf bfr-nbr{ 644 type inet:ip-address; 645 description 646 "BIER BFR Neighbors."; 647 } 648 leaf bier-mpls-out-label{ 649 type rt-types:mpls-label; 650 description 651 "BIER out-label."; 652 } 653 description 654 "Query the BIRT based on the key set identifier & bitstringlength & sub-domain-id."; 655 } 656 description 657 "Query the BIRT based on the key bitstringlengt & sub-domain-id."; 658 } 659 description 660 "Query the BIRT based on the key sub-domain."; 661 } 662 description 663 "Shows Bit Index Routing Table."; 664 } 665 } 666 } 668 augment "/rt:routing/rt:control-plane-protocols/" 669 + "rt:control-plane-protocol/ospf:ospf/ospf:instance" { 670 when "../../rt:type = 'ospf:ospfv2' or 671 ../../rt:type = 'ospf:ospfv3'" { 672 description 673 "This augments the ospf routing protocol when used"; 674 } 675 description 676 "This augments ospf protocol configuration with bier."; 677 container bier-ospf-cfg{ 678 uses bier-protocol-extensions; 679 description 680 "Control of bier advertisement and reception."; 681 } 682 } 684 augment "/rt:routing/rt:control-plane-protocols/" 685 +"rt:control-plane-protocol/isis:isis"{ 686 when "/rt:routing/rt:control-plane-protocols/"+ 687 "rt:control-plane-protocol/rt:type = 'isis:isis'" { 688 description 689 "This augment ISIS routing protocol when used"; 690 } 691 description 692 "This augments ISIS protocol configuration with bier."; 693 container bier-isis-cfg{ 694 uses bier-protocol-extensions; 695 description 696 "Control of bier advertisement and reception."; 698 } 699 } 701 /* Notifications */ 702 notification bfr-id-collision{ 703 leaf bfr-id{ 704 type bfr-id; 705 description 706 "BIER BFR ID."; 707 } 708 description 709 "BFR ID received in the controlplane that caused BFR ID collision."; 710 } 712 notification bfr-zero{ 713 leaf ipv4-bfr-prefix{ 714 type inet:ipv4-prefix; 715 description 716 "BIER ipv4 bfr prefix"; 717 } 718 leaf ipv6-bfr-prefix{ 719 type inet:ipv6-prefix; 720 description 721 "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-08 (work in 765 progress), September 2017. 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-06 (work in progress), October 2017. 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-12 (work in progress), 777 October 2017. 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-10 (work 783 in progress), December 2017. 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-19 (work in progress), November 2017. 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-05 (work 794 in progress), July 2017. 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-04 (work in progress), July 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-09 (work in progress), October 2017. 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 849 Zheng Zhang 850 ZTE Corporation 851 No.50 Software Avenue,Yuhuatai District 852 Nanjing, Jiangsu Province 210012 853 China 855 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