idnits 2.17.1 draft-ietf-bier-bier-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 24 instances of too long lines in the document, the longest one being 65 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 455 has weird spacing: '... type inet:...' == Line 580 has weird spacing: '...ational data ...' -- The document date (July 24, 2016) is 2832 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 760, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-isis-yang-isis-cfg' is defined on line 772, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-mpls-base-yang' is defined on line 777, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-mpls-static-yang' is defined on line 783, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-netmod-routing-cfg' is defined on line 789, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-ospf-yang' is defined on line 794, but no explicit reference was found in the text == Unused Reference: 'RFC6020' is defined on line 799, but no explicit reference was found in the text == Unused Reference: 'RFC6241' is defined on line 804, but no explicit reference was found in the text == Unused Reference: 'RFC6991' is defined on line 809, but no explicit reference was found in the text == Unused Reference: 'RFC7223' is defined on line 813, but no explicit reference was found in the text == Outdated reference: A later version (-08) exists of draft-ietf-bier-architecture-04 == Outdated reference: A later version (-11) exists of draft-ietf-bier-isis-extensions-02 == Outdated reference: A later version (-12) exists of draft-ietf-bier-mpls-encapsulation-05 == Outdated reference: A later version (-18) exists of draft-ietf-bier-ospf-bier-extensions-02 == Outdated reference: A later version (-42) exists of draft-ietf-isis-yang-isis-cfg-08 == 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-01 == Outdated reference: A later version (-25) exists of draft-ietf-netmod-routing-cfg-22 == Outdated reference: A later version (-29) exists of draft-ietf-ospf-yang-05 ** 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: January 25, 2017 Xianxia. Dai 6 ZTE Corporation 7 Mahesh Sivakumar 8 Cisco Systems, Inc. 9 July 24, 2016 11 YANG Data Model for BIER Protocol 12 draft-ietf-bier-bier-yang-00.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 January 25, 2017. 36 Copyright Notice 38 Copyright (c) 2016 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:control-plane-protocols/rt:control-plane-protocol/ospf:ospf/ospf:instance:" and "/rt:routing/ 177 rt:control-plane-protocols/rt:control-plane-protocol/isis:isis:"configuration 178 with BIER. 180 This Module supports ISIS ([I-D.ietf-bier-isis-extensions])and OSPF 181 ([I-D.ietf-bier-ospf-bier-extensions]) as control plane for BIER. 183 5. States 185 The operational states contains basic parameters associated with 186 bier, such as BIER encapsulation type, BitStringLengths, BFR-id, BFR- 187 prefixes, and parameters associated with bier sub-domain. 189 It also includes the Bit Index Routing Table(BIRT). 191 6. Notification 193 This Module includes bfr-id-collision, bfr-zero, and sub-domain-id- 194 collision. 196 7. BIER YANG Data Model 198 file "ietf-bier.yang" 199 module ietf-bier { 201 namespace "urn:ietf:params:xml:ns:yang:ietf-bier"; 203 prefix "bier"; 205 import ietf-routing { 206 prefix "rt"; 207 } 209 import ietf-inet-types { 210 prefix "inet"; 211 } 213 import ietf-mpls { 214 prefix "mpls"; 215 } 217 import ietf-isis{ 218 prefix "isis"; 219 } 221 import ietf-ospf { 222 prefix "ospf"; 223 } 225 organization 226 "IETF BIER(Bit Indexed Explicit Replication ) Working Group"; 228 contact 229 "WG List: 231 WG Chair: Tony Przygienda 232 234 WG Chair: Greg Shepherd 235 237 Editor: Ran Chen 238 239 Editor: Fangwei Hu 240 241 Editor: Zheng Zhang 242 243 Editor: Xianxian Dai 244 245 Editor: Mahesh Sivakumar 246 247 "; 248 description 249 "The YANG module defines a generic configuration 250 model for BIER."; 252 revision 2016-07-23{ 253 description 254 "00 revision"; 255 reference 256 "draft-ietf-bier-bier-yang-00"; 257 } 259 revision 2016-05-12{ 260 description 261 "04 revision"; 262 reference 263 "draft-chh-bier-bier-yang-04"; 264 } 266 revision 2016-03-16 { 267 description 268 "03 revision"; 269 reference 270 "draft-chh-bier-bier-yang-03"; 271 } 273 revision 2015-12-03 { 274 description 275 "02 revision"; 276 reference 277 "draft-chh-bier-bier-yang-02"; 278 } 280 revision 2015-10-16 { 281 description 282 "01 revision."; 283 reference 284 "draft-chh-bier-bier-yang-01"; 286 } 288 revision 2015-06-22 { 289 description 290 "Initial revision."; 291 reference 292 "draft-chh-bier-bier-yang-00"; 293 } 295 /* Identities */ 296 identity bier-encapsulation{ 297 description 298 "Base identity for BIER encapsulation."; 299 } 300 identity bier-encapsulation-mpls { 301 base bier-encapsulation; 302 description 303 "This identity represents MPLS encapsulation for bier."; 304 } 306 /*Typedefs*/ 308 typedef sub-domain-id { 309 type uint16; 310 description 311 "The type for sub-domain-id"; 312 } 314 typedef si { 315 type uint16; 316 description 317 "The type for set identifier"; 318 } 320 typedef bfr-id { 321 type uint16; 322 description 323 "The type for bfr identifier"; 324 } 326 typedef mt-id { 327 type uint16; 328 description 329 "The type for multi-topology identifier"; 330 } 332 typedef bier-mpls-label-range-size{ 333 type uint8; 334 description 335 "The type for BIER label range size."; 336 } 338 typedef bsl { 339 type enumeration{ 340 enum 64-bit{ 341 value 1; 342 description 343 "bitstringlength is 64"; 344 } 345 enum 128-bit{ 346 value 2; 347 description 348 "bitstringlength is 128"; 349 } 350 enum 256-bit{ 351 value 3; 352 description 353 "bitstringlength is 256"; 354 } 355 enum 512-bit{ 356 value 4; 357 description 358 "bitstringlength is 512"; 359 } 360 enum 1024-bit{ 361 value 5; 362 description 363 "bitstringlength is 1024"; 364 } 365 enum 2048-bit{ 366 value 6; 367 description 368 "bitstringlength is 2048"; 369 } 370 enum 4096-bit{ 371 value 7; 372 description 373 "bitstringlength is 4096"; 374 } 375 } 376 description 377 "The bitstringlength type for imposition mode"; 378 } 380 typedef igp-type { 381 type enumeration{ 382 enum ISIS{ 383 value 1; 384 description 385 "isis protocol"; 386 } 387 enum OSPF{ 388 value 2; 389 description 390 "ospf protocol"; 391 } 392 } 393 description 394 "The IGP type"; 395 } 397 /*grouping*/ 398 grouping bier-protocol-extensions{ 399 leaf mt-id{ 400 type mt-id; 401 description 402 "Multi-topology associated with bier sub-domain."; 403 } 404 container bier-global { 405 leaf enable { 406 type boolean; 407 default false; 408 description 409 "Enables bier protocol extensions."; 410 } 411 leaf advertise { 412 type boolean; 413 default true; 414 description 415 "Enable to advertise the parameters associated with bier."; 416 } 417 leaf receive { 418 type boolean; 419 default true; 420 description 421 "Enable to receive the parameters associated with bier."; 422 } 423 description 424 "BIER global config."; 425 } 426 description 427 "Defines protocol extensions."; 428 } 430 grouping bier-parameters{ 431 leaf encapsulation-type { 432 type identityref { 433 base bier-encapsulation; 434 } 435 default "bier-encapsulation-mpls"; 436 description 437 "Dataplane to be used."; 438 } 439 leaf bitstringlength{ 440 type bsl; 441 description 442 "imposition bitstringlength."; 443 } 444 leaf bfr-id { 445 type bfr-id; 446 description 447 "BIER bfr identifier."; 448 } 449 leaf ipv4-bfr-prefix { 450 type inet:ipv4-prefix; 451 description 452 "BIER IPv4 prefix."; 453 } 454 leaf ipv6-bfr-prefix { 455 type inet:ipv6-prefix; 456 description 457 "BIER IPv6 prefix."; 458 } 459 description 460 " BIER parameters."; 461 } 463 grouping bier-mpls-cfg{ 464 leaf bitstringlength { 465 type uint16; 466 description 467 "BIER bitstringlength."; 468 } 469 leaf bier-mpls-label-base{ 470 type mpls:mpls-label; 471 description 472 "BIER label base."; 473 } 474 leaf bier-mpls-label-range-size{ 475 type bier-mpls-label-range-size; 476 description 477 "BIER label range."; 479 } 480 description 481 "Defines the necessary label ranges per bitstring length."; 482 } 484 /* Configuration Data */ 485 augment "/rt:routing" { 486 description 487 "This augments routing-instance configuration with bier."; 488 container bier{ 489 container bier-global { 490 uses bier-parameters; 491 list sub-domain{ 492 key "sub-domain-id"; 493 leaf sub-domain-id{ 494 type sub-domain-id; 495 description 496 "sub-domain ID."; 497 } 498 leaf igp-type { 499 type igp-type; 500 description 501 "IGP type."; 502 } 503 leaf mt-id { 504 type mt-id; 505 description 506 "multi-topology ID."; 507 } 508 leaf bfr-id{ 509 type bfr-id; 510 description 511 "BIER bfr identifier."; 512 } 514 leaf bitstringlength{ 515 type bsl; 516 description 517 "Disposition bitstringlength."; 518 } 520 container af { 521 list ipv4 { 522 key "bitstringlength bier-mpls-label-base"; 523 uses bier-mpls-cfg; 525 description 526 "Defines the necessary label ranges per bitstring length in ipv4."; 527 } 528 list ipv6 { 529 key "bitstringlength bier-mpls-label-base"; 530 uses bier-mpls-cfg; 532 description 533 "Defines the necessary label ranges per bitstring length in ipv6."; 534 } 535 description 536 "Bier mapping entries."; 537 } 538 description 539 "Denfines subdomain configuration"; 540 } 541 description 542 "BIER global config."; 543 } 544 description "BIER config."; 545 } 546 } 548 augment "/rt:routing/rt:control-plane-protocols/" 549 + "rt:control-plane-protocol/ospf:ospf/ospf:instance" { 550 when "../../rt:type = 'ospf:ospfv2' or 551 ../../rt:type = 'ospf:ospfv3'" { 552 description 553 "This augments the ospf routing protocol when used"; 554 } 555 description 556 "This augments ospf protocol configuration with bier."; 557 container bier-ospf-cfg{ 558 uses bier-protocol-extensions; 559 description 560 "Control of bier advertisement and reception."; 561 } 562 } 564 augment "/rt:routing/rt:control-plane-protocols/" 565 +"rt:control-plane-protocol"{ 566 when "rt:type = 'isis:isis'" { 567 description 568 "This augment ISIS routing protocol when used"; 569 } 570 description 571 "This augments ISIS protocol configuration with bier."; 572 container bier-isis-cfg{ 573 uses bier-protocol-extensions; 574 description 575 "Control of bier advertisement and reception."; 577 } 578 } 580 /* Operational data */ 581 augment "/rt:routing-state" { 582 description 583 "This augments the operational states with bier."; 584 container bier-global{ 585 uses bier-parameters; 586 list sub-domain{ 587 key "sub-domain-id"; 588 leaf sub-domain-id{ 589 type sub-domain-id; 590 description 591 "sub-domain ID."; 592 } 593 leaf igp-type { 594 type igp-type; 595 description 596 "IGP type."; 597 } 598 leaf mt-id { 599 type mt-id; 600 description 601 "multi-topology ID."; 602 } 603 leaf bfr-id{ 604 type bfr-id; 605 description 606 "BIER bfr identifier."; 607 } 609 leaf bitstringlength{ 610 type bsl; 611 description 612 "Disposition bitstringlength."; 613 } 614 list ipv4 { 615 key "bitstringlength bier-mpls-label-base"; 616 uses bier-mpls-cfg; 617 description 618 "Show the necessary label ranges per bitstring length in ipv4."; 619 } 620 list ipv6 { 621 key "bitstringlength bier-mpls-label-base"; 622 uses bier-mpls-cfg; 623 description 624 "Show the necessary label ranges per bitstring length in ipv6."; 625 } 626 description 627 "Denfines subdomain configuration"; 628 } 629 description 630 "Parameters associated with bier."; 631 } 633 container birts{ 634 list birt{ 635 key "sub-domain-id"; 636 leaf sub-domain-id{ 637 type sub-domain-id; 638 description 639 "BIER sub domain ID"; 640 } 641 list birt-bitstringlength { 642 key "bitstringlength"; 643 leaf bitstringlength{ 644 type uint16; 645 description 646 "BIER bitstringlength."; 647 } 648 list birt-si { 649 key "si"; 650 leaf si{ 651 type si; 652 description 653 "BIER set identifier."; 654 } 655 leaf f-bm{ 656 type uint16; 657 description 658 "BIER Forwarding Bit Mask."; 659 } 660 leaf bier-mpls-in-label{ 661 type mpls:mpls-label; 662 description 663 "BIER in-label."; 664 } 665 leaf bfr-nbr{ 666 type inet:ip-address; 667 description 668 "BIER BFR Neighbors."; 669 } 670 leaf bier-mpls-out-label{ 671 type mpls:mpls-label; 672 description 673 "BIER out-label."; 674 } 675 description 676 "Query the BIRT based on the key set identifier & bitstringlength & sub-domain-id."; 677 } 678 description 679 "Query the BIRT based on the key bitstringlengt & sub-domain-id."; 680 } 681 description 682 "Query the BIRT based on the key sub-domain."; 683 } 684 description 685 "Shows Bit Index Routing Table."; 686 } 687 } 689 /* Notifications */ 690 notification bfr-id-collision{ 691 leaf bfr-id{ 692 type bfr-id; 693 description 694 "BIER BFR ID."; 695 } 696 description 697 "BFR ID received in the controlplane that caused BFR ID collision."; 698 } 700 notification bfr-zero{ 701 leaf ipv4-bfr-prefix{ 702 type inet:ipv4-prefix; 703 description 704 "BIER ipv4 bfr prefix"; 705 } 706 leaf ipv6-bfr-prefix{ 707 type inet:ipv6-prefix; 708 description 709 "BIER ipv6 bfr prefix"; 710 } 711 description 712 "Invalid value associated with prefix"; 713 } 715 notification sub-domain-id-collision{ 716 leaf sub-domain-id{ 717 type sub-domain-id; 718 description 719 "BIER sub domain ID"; 720 } 721 leaf mt-id{ 722 type uint16; 723 description 724 "Multi-topology ID"; 725 } 726 description 727 "Sub domain ID received in the controlplane that caused Sub domain ID collision"; 728 } 729 } 731 733 8. Security Considerations 735 TBD. 737 9. Acknowledgements 739 We would like to thank IJsbrand Wijnands, Reshad Rahman and Giles 740 Heron for their comments and support of this work. 742 10. IANA Considerations 744 This document requires no IANA Actions. Please remove this section 745 before RFC publication. 747 11. Normative references 749 [I-D.ietf-bier-architecture] 750 Wijnands, I., Rosen, E., Dolganow, A., Przygienda, T., and 751 S. Aldrin, "Multicast using Bit Index Explicit 752 Replication", draft-ietf-bier-architecture-04 (work in 753 progress), July 2016. 755 [I-D.ietf-bier-isis-extensions] 756 Ginsberg, L., Przygienda, T., Aldrin, S., and Z. Zhang, 757 "BIER support via ISIS", draft-ietf-bier-isis- 758 extensions-02 (work in progress), March 2016. 760 [I-D.ietf-bier-mpls-encapsulation] 761 Wijnands, I., Rosen, E., Dolganow, A., Tantsura, J., 762 Aldrin, S., and I. Meilik, "Encapsulation for Bit Index 763 Explicit Replication in MPLS Networks", draft-ietf-bier- 764 mpls-encapsulation-05 (work in progress), July 2016. 766 [I-D.ietf-bier-ospf-bier-extensions] 767 Psenak, P., Kumar, N., Wijnands, I., Dolganow, A., 768 Przygienda, T., Zhang, Z., and S. Aldrin, "OSPF Extensions 769 for BIER", draft-ietf-bier-ospf-bier-extensions-02 (work 770 in progress), March 2016. 772 [I-D.ietf-isis-yang-isis-cfg] 773 Litkowski, S., Yeung, D., Lindem, A., Zhang, Z., and L. 774 Lhotka, "YANG Data Model for IS-IS protocol", draft-ietf- 775 isis-yang-isis-cfg-08 (work in progress), March 2016. 777 [I-D.ietf-mpls-base-yang] 778 Raza, K., Gandhi, R., Liu, X., Beeram, V., Saad, T., 779 Bryskin, I., Chen, X., Jones, R., and B. Wen, "A YANG Data 780 Model for MPLS Base", draft-ietf-mpls-base-yang-01 (work 781 in progress), July 2016. 783 [I-D.ietf-mpls-static-yang] 784 Saad, T., Raza, K., Gandhi, R., Liu, X., Beeram, V., Shah, 785 H., Bryskin, I., Chen, X., Jones, R., and B. Wen, "A YANG 786 Data Model for MPLS Static LSPs", draft-ietf-mpls-static- 787 yang-01 (work in progress), July 2016. 789 [I-D.ietf-netmod-routing-cfg] 790 Lhotka, L. and A. Lindem, "A YANG Data Model for Routing 791 Management", draft-ietf-netmod-routing-cfg-22 (work in 792 progress), July 2016. 794 [I-D.ietf-ospf-yang] 795 Yeung, D., Qu, Y., Zhang, Z., Bogdanovic, D., and K. 796 Koushik, "Yang Data Model for OSPF Protocol", draft-ietf- 797 ospf-yang-05 (work in progress), July 2016. 799 [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for 800 the Network Configuration Protocol (NETCONF)", RFC 6020, 801 DOI 10.17487/RFC6020, October 2010, 802 . 804 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 805 and A. Bierman, Ed., "Network Configuration Protocol 806 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 807 . 809 [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", 810 RFC 6991, DOI 10.17487/RFC6991, July 2013, 811 . 813 [RFC7223] Bjorklund, M., "A YANG Data Model for Interface 814 Management", RFC 7223, DOI 10.17487/RFC7223, May 2014, 815 . 817 Authors' Addresses 819 Ran Chen 820 ZTE Corporation 821 No.50 Software Avenue,Yuhuatai District 822 Nanjing, Jiangsu Province 210012 823 China 825 Phone: +86 025 88014636 826 Email: chen.ran@zte.com.cn 828 Fangwei Hu 829 ZTE Corporation 830 No.889 Bibo Rd 831 Shanghai 201203 832 China 834 Phone: +86 21 68896273 835 Email: hu.fangwei@zte.com.cn 837 Zheng Zhang 838 ZTE Corporation 839 No.50 Software Avenue,Yuhuatai District 840 Nanjing, Jiangsu Province 210012 841 China 843 Email: zhang.zheng@zte.com.cn 845 Xianxian Dai 846 ZTE Corporation 847 No.50 Software Avenue,Yuhuatai District 848 Nanjing, Jiangsu Province 210012 849 China 851 Email: Dai.xianxian@zte.com.cn 852 Mahesh Sivakumar 853 Cisco Systems, Inc. 854 510 McCarthy Blvd 855 Milpitas,California 95035 856 United States 858 Email: masivaku@cisco.com