idnits 2.17.1 draft-chh-bier-bier-yang-04.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 23 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 124 has weird spacing: '...main-id sub...' == Line 141 has weird spacing: '...glength uin...' == Line 451 has weird spacing: '... type inet:...' == Line 576 has weird spacing: '...ational data ...' -- The document date (May 19, 2016) is 2900 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 759, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-isis-yang-isis-cfg' is defined on line 771, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-netmod-routing-cfg' is defined on line 776, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-ospf-yang' is defined on line 781, but no explicit reference was found in the text == Unused Reference: 'RFC6020' is defined on line 786, but no explicit reference was found in the text == Unused Reference: 'RFC6241' is defined on line 791, but no explicit reference was found in the text == Unused Reference: 'RFC6991' is defined on line 796, but no explicit reference was found in the text == Unused Reference: 'RFC7223' is defined on line 800, but no explicit reference was found in the text == Unused Reference: 'I-D.saad-mpls-static-yang' is defined on line 806, but no explicit reference was found in the text == Outdated reference: A later version (-08) exists of draft-ietf-bier-architecture-03 == 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-04 == 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 (-25) exists of draft-ietf-netmod-routing-cfg-21 == Outdated reference: A later version (-29) exists of draft-ietf-ospf-yang-04 ** Obsolete normative reference: RFC 7223 (Obsoleted by RFC 8343) Summary: 2 errors (**), 0 flaws (~~), 21 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: November 20, 2016 Xianxia. Dai 6 ZTE Corporation 7 Mahesh Sivakumar 8 Cisco Systems, Inc. 9 May 19, 2016 11 YANG Data Model for BIER Protocol 12 draft-chh-bier-bier-yang-04.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 November 20, 2016. 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 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. References . . . . . . . . . . . . . . . . . . . . . . . . . 16 64 11.1. Normative references . . . . . . . . . . . . . . . . . . 16 65 11.2. Informative references . . . . . . . . . . . . . . . . . 18 66 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18 68 1. Introduction 70 This document defines a YANG data model for BIER configuration and 71 operation. 73 2. Design of the Data Model 75 module: ietf-bier 76 augment /rt:routing: 77 +--rw bier 78 +--rw bier-global 79 +--rw encapsulation-type? identityref 80 +--rw bitstringlength? bsl 81 +--rw bfr-id? bfr-id 82 +--rw ipv4-bfr-prefix? inet:ipv4-prefix 83 +--rw ipv6-bfr-prefix? inet:ipv6-prefix 84 +--rw sub-domain* [sub-domain-id] 85 +--rw sub-domain-id sub-domain-id 86 +--rw igp-type? igp-type 87 +--rw mt-id? mt-id 88 +--rw bfr-id? bfr-id 89 +--rw bitstringlength? bsl 90 +--rw af 91 +--rw ipv4* [bitstringlength bier-mpls-label-base] 92 | +--rw bitstringlength uint16 93 | +--rw bier-mpls-label-base mpls:mpls-label 94 | +--rw bier-mpls-label-range-size? bier-mpls-label-range-size 95 +--rw ipv6* [bitstringlength bier-mpls-label-base] 96 +--rw bitstringlength uint16 97 +--rw bier-mpls-label-base mpls:mpls-label 98 +--rw bier-mpls-label-range-size? bier-mpls-label-range-size 100 augment /rt:routing/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance: 101 +--rw bier-ospf-cfg 102 +--rw mt-id mt-id 103 +--rw bier-global 104 +--rw enable? boolean 105 +--rw advertise? boolean 106 +--rw receive? boolean 108 augment /rt:routing/rt:routing-protocols/rt:routing-protocol/isis:isis: 109 +--rw bier-isis-cfg 110 +--rw mt-id mt-id 111 +--rw bier-global 112 +--rw enable? boolean 113 +--rw advertise? boolean 114 +--rw receive? boolean 116 augment /rt:routing-state: 117 +--ro bier-global 118 | +--ro encapsulation-type? identityref 119 | +--ro bitstringlength? bsl 120 | +--ro bfr-id? bfr-id 121 | +--ro ipv4-bfr-prefix? inet:ipv4-prefix 122 | +--ro ipv6-bfr-prefix? inet:ipv6-prefix 123 | +--ro sub-domain* [sub-domain-id] 124 | +--ro sub-domain-id sub-domain-id 125 | +--ro igp-type igp-type 126 | +--ro mt-id? mt-id 127 | +--ro bfr-id? bfr-id 128 | +--rw bitstringlength? bsl 129 | +--ro ipv4* [bitstringlength bier-mpls-label-base] 130 | | +--ro bitstringlength uint16 131 | | +--ro bier-mpls-label-base mpls:mpls-label 132 | | +--ro bier-mpls-label-range-size? bier-mpls-label-range-size 133 | +--ro ipv6* [bitstringlength bier-mpls-label-base] 134 | +--ro bitstringlength uint16 135 | +--ro bier-mpls-label-base mpls:mpls-label 136 | +--ro bier-mpls-label-range-size? bier-mpls-label-range-size 137 +--ro birts 138 +--ro birt* [sub-domain-id] 139 +--ro sub-domain-id sub-domain-id 140 +--ro birt-bitstringlength* [bitstringlength] 141 +--ro bitstringlength uint16 142 +--ro birt-si* [si] 143 +--ro si si 144 +--ro f-bm? uint16 145 +--ro bier-mpls-in-label? mpls:mpls-label 146 +--ro bfr-nbr? inet:ip-address 147 +--ro bier-mpls-out-label? mpls:mpls-label 148 notifications: 149 +---n bfr-id-collision 150 | +--ro bfr-id? bfr-id 151 +---n bfr-zero 152 | +--ro ipv4-bfr-prefix? inet:ipv4-prefix 153 | +--ro ipv6-bfr-prefix? inet:ipv6-prefix 154 +---n sub-domain-id-collision 155 +--ro sub-domain-id? sub-domain-id 156 +--ro mt-id? uint16 158 3. Configuration 160 This Module augments the "/rt:routing:" with a BIER container. This 161 Container defines all the configuration parameters related to BIER 162 for this particular routing. 164 The BIER configuration contains global configuration. 166 The global configuration includes BIER encapsulation type, imposition 167 BitStringLengths, BFR-id, BFR-prefixes, and parameters associated 168 with bier sub-domain. 170 In this document, we contains two types of BitStringLengths: 171 Imposition and Disposition BitStringLengths, as defined in 172 ([I-D.ietf-bier-architecture]).The imposition BitStringLengths is 173 defined under bier-global container, and the disposition 174 BitStringLengths is defined under the sub-domain. 176 4. Control plane configuration 178 This Module augments the "/rt:routing/rt:routing-instance/rt:routing- 179 protocolsbier-protocol-extensions /rt:routing-protocol/ospf:ospf/ 180 ospf:instance:" and "/rt:routing/rt:routing-instance/rt:routing- 181 protocols /rt:routing-protocol/isis:isis/isis:instance:"configuration 182 with BIER. 184 This Module supports ISIS ([I-D.ietf-bier-isis-extensions])and OSPF 185 ([I-D.ietf-bier-ospf-bier-extensions]) as control plane for BIER. 187 5. States 189 The operational states contains basic parameters associated with 190 bier, such as BIER encapsulation type, BitStringLengths, BFR-id, BFR- 191 prefixes, and parameters associated with bier sub-domain. 193 It also includes the Bit Index Routing Table(BIRT). 195 6. Notification 197 This Module includes bfr-id-collision, bfr-zero, and sub-domain-id- 198 collision. 200 7. BIER YANG Data Model 202 file "ietf-bier.yang" 203 module ietf-bier { 205 namespace "urn:ietf:params:xml:ns:yang:ietf-bier"; 207 prefix "bier"; 209 import ietf-routing { 210 prefix "rt"; 211 } 213 import ietf-inet-types { 214 prefix "inet"; 215 } 217 import ietf-mpls { 218 prefix "mpls"; 219 } 221 import ietf-isis{ 222 prefix "isis"; 223 } 225 import ietf-ospf { 226 prefix "ospf"; 227 } 229 organization 230 "IETF BIER(Bit Indexed Explicit Replication ) Working Group"; 232 contact 233 "WG List: 234 WG Chair: Tony Przygienda 235 237 WG Chair: Greg Shepherd 238 240 Editor: Ran Chen 241 242 Editor: Fangwei Hu 243 244 Editor: Zheng Zhang 245 246 Editor: Xianxian Dai 247 248 Editor: Mahesh Sivakumar 249 250 "; 251 description 252 "The YANG module defines a generic configuration 253 model for BIER."; 255 revision 2016-05-12{ 256 description 257 "04 revision"; 258 reference 259 "draft-chh-bier-bier-yang-04"; 260 } 262 revision 2016-03-16 { 263 description 264 "03 revision"; 265 reference 266 "draft-chh-bier-bier-yang-03"; 267 } 269 revision 2015-12-03 { 270 description 271 "02 revision"; 272 reference 273 "draft-chh-bier-bier-yang-02"; 274 } 276 revision 2015-10-16 { 277 description 278 "01 revision."; 279 reference 280 "draft-chh-bier-bier-yang-01"; 282 } 284 revision 2015-06-22 { 285 description 286 "Initial revision."; 287 reference 288 "draft-chh-bier-bier-yang-00"; 289 } 291 /* Identities */ 292 identity bier-encapsulation{ 293 description 294 "Base identity for BIER encapsulation."; 295 } 296 identity bier-encapsulation-mpls { 297 base bier-encapsulation; 298 description 299 "This identity represents MPLS encapsulation for bier."; 300 } 302 /*Typedefs*/ 304 typedef sub-domain-id { 305 type uint16; 306 description 307 "The type for sub-domain-id"; 308 } 310 typedef si { 311 type uint16; 312 description 313 "The type for set identifier"; 314 } 316 typedef bfr-id { 317 type uint16; 318 description 319 "The type for bfr identifier"; 320 } 322 typedef mt-id { 323 type uint16; 324 description 325 "The type for multi-topology identifier"; 326 } 328 typedef bier-mpls-label-range-size{ 329 type uint8; 330 description 331 "The type for BIER label range size."; 332 } 334 typedef bsl { 335 type enumeration{ 336 enum 64-bit{ 337 value 1; 338 description 339 "bitstringlength is 64"; 340 } 341 enum 128-bit{ 342 value 2; 343 description 344 "bitstringlength is 128"; 345 } 346 enum 256-bit{ 347 value 3; 348 description 349 "bitstringlength is 256"; 350 } 351 enum 512-bit{ 352 value 4; 353 description 354 "bitstringlength is 512"; 355 } 356 enum 1024-bit{ 357 value 5; 358 description 359 "bitstringlength is 1024"; 360 } 361 enum 2048-bit{ 362 value 6; 363 description 364 "bitstringlength is 2048"; 365 } 366 enum 4096-bit{ 367 value 7; 368 description 369 "bitstringlength is 4096"; 370 } 371 } 372 description 373 "The bitstringlength type for imposition mode"; 374 } 376 typedef igp-type { 377 type enumeration{ 378 enum ISIS{ 379 value 1; 380 description 381 "isis protocol"; 382 } 383 enum OSPF{ 384 value 2; 385 description 386 "ospf protocol"; 387 } 388 } 389 description 390 "The IGP type"; 391 } 393 /*grouping*/ 394 grouping bier-protocol-extensions{ 395 leaf mt-id{ 396 type mt-id; 397 description 398 "Multi-topology associated with bier sub-domain."; 399 } 400 container bier-global { 401 leaf enable { 402 type boolean; 403 default false; 404 description 405 "Enables bier protocol extensions."; 406 } 407 leaf advertise { 408 type boolean; 409 default true; 410 description 411 "Enable to advertise the parameters associated with bier."; 412 } 413 leaf receive { 414 type boolean; 415 default true; 416 description 417 "Enable to receive the parameters associated with bier."; 418 } 419 description 420 "BIER global config."; 421 } 422 description 423 "Defines protocol extensions."; 424 } 426 grouping bier-parameters{ 427 leaf encapsulation-type { 428 type identityref { 429 base bier-encapsulation; 430 } 431 default "bier-encapsulation-mpls"; 432 description 433 "Dataplane to be used."; 434 } 435 leaf bitstringlength{ 436 type bsl; 437 description 438 "imposition bitstringlength."; 439 } 440 leaf bfr-id { 441 type bfr-id; 442 description 443 "BIER bfr identifier."; 444 } 445 leaf ipv4-bfr-prefix { 446 type inet:ipv4-prefix; 447 description 448 "BIER IPv4 prefix."; 449 } 450 leaf ipv6-bfr-prefix { 451 type inet:ipv6-prefix; 452 description 453 "BIER IPv6 prefix."; 454 } 455 description 456 " BIER parameters."; 457 } 459 grouping bier-mpls-cfg{ 460 leaf bitstringlength { 461 type uint16; 462 description 463 "BIER bitstringlength."; 464 } 465 leaf bier-mpls-label-base{ 466 type mpls:mpls-label; 467 description 468 "BIER label base."; 469 } 470 leaf bier-mpls-label-range-size{ 471 type bier-mpls-label-range-size; 472 description 473 "BIER label range."; 475 } 476 description 477 "Defines the necessary label ranges per bitstring length."; 478 } 480 /* Configuration Data */ 481 augment "/rt:routing" { 482 description 483 "This augments routing-instance configuration with bier."; 484 container bier{ 485 container bier-global { 486 uses bier-parameters; 487 list sub-domain{ 488 key "sub-domain-id"; 489 leaf sub-domain-id{ 490 type sub-domain-id; 491 description 492 "sub-domain ID."; 493 } 494 leaf igp-type { 495 type igp-type; 496 description 497 "IGP type."; 498 } 499 leaf mt-id { 500 type mt-id; 501 description 502 "multi-topology ID."; 503 } 504 leaf bfr-id{ 505 type bfr-id; 506 description 507 "BIER bfr identifier."; 508 } 510 leaf bitstringlength{ 511 type bsl; 512 description 513 "Disposition bitstringlength."; 514 } 516 container af { 517 list ipv4 { 518 key "bitstringlength bier-mpls-label-base"; 519 uses bier-mpls-cfg; 521 description 522 "Defines the necessary label ranges per bitstring length in ipv4."; 523 } 524 list ipv6 { 525 key "bitstringlength bier-mpls-label-base"; 526 uses bier-mpls-cfg; 528 description 529 "Defines the necessary label ranges per bitstring length in ipv6."; 530 } 531 description 532 "Bier mapping entries."; 533 } 534 description 535 "Denfines subdomain configuration"; 536 } 537 description 538 "BIER global config."; 539 } 540 description "BIER config."; 541 } 542 } 544 augment "/rt:routing/rt:routing-protocols/" 545 + "rt:routing-protocol/ospf:ospf/ospf:instance" { 546 when "../../rt:type = 'ospf:ospfv2' or 547 ../../rt:type = 'ospf:ospfv3'" { 548 description 549 "This augments the ospf routing protocol when used"; 550 } 551 description 552 "This augments ospf protocol configuration with bier."; 553 container bier-ospf-cfg{ 554 uses bier-protocol-extensions; 555 description 556 "Control of bier advertisement and reception."; 557 } 558 } 560 augment "/rt:routing/rt:routing-protocols/" + 561 "rt:routing-protocol"{ 562 when "rt:type = 'isis:isis'" { 563 description 564 "This augment is only valid when routing protocol instance type is isis."; 565 } 566 description 567 "This augments ISIS protocol configuration with bier."; 568 container bier-isis-cfg{ 569 uses bier-protocol-extensions; 570 description 571 "Control of bier advertisement and reception."; 573 } 574 } 576 /* Operational data */ 577 augment "/rt:routing-state" { 578 description 579 "This augments the operational states with bier."; 580 container bier-global{ 581 uses bier-parameters; 582 list sub-domain{ 583 key "sub-domain-id"; 584 leaf sub-domain-id{ 585 type sub-domain-id; 586 description 587 "sub-domain ID."; 588 } 589 leaf igp-type { 590 type igp-type; 591 description 592 "IGP type."; 593 } 594 leaf mt-id { 595 type mt-id; 596 description 597 "multi-topology ID."; 598 } 599 leaf bfr-id{ 600 type bfr-id; 601 description 602 "BIER bfr identifier."; 603 } 605 leaf bitstringlength{ 606 type bsl; 607 description 608 "Disposition bitstringlength."; 609 } 610 list ipv4 { 611 key "bitstringlength bier-mpls-label-base"; 612 uses bier-mpls-cfg; 613 description 614 "Show the necessary label ranges per bitstring length in ipv4."; 615 } 616 list ipv6 { 617 key "bitstringlength bier-mpls-label-base"; 618 uses bier-mpls-cfg; 619 description 620 "Show the necessary label ranges per bitstring length in ipv6."; 621 } 622 description 623 "Denfines subdomain configuration"; 624 } 625 description 626 "Parameters associated with bier."; 627 } 629 container birts{ 630 list birt{ 631 key "sub-domain-id"; 632 leaf sub-domain-id{ 633 type sub-domain-id; 634 description 635 "BIER sub domain ID"; 636 } 637 list birt-bitstringlength { 638 key "bitstringlength"; 639 leaf bitstringlength{ 640 type uint16; 641 description 642 "BIER bitstringlength."; 643 } 644 list birt-si { 645 key "si"; 646 leaf si{ 647 type si; 648 description 649 "BIER set identifier."; 650 } 651 leaf f-bm{ 652 type uint16; 653 description 654 "BIER Forwarding Bit Mask."; 655 } 656 leaf bier-mpls-in-label{ 657 type mpls:mpls-label; 658 description 659 "BIER in-label."; 660 } 661 leaf bfr-nbr{ 662 type inet:ip-address; 663 description 664 "BIER BFR Neighbors."; 665 } 667 leaf bier-mpls-out-label{ 668 type mpls:mpls-label; 669 description 670 "BIER out-label."; 671 } 672 description 673 "Query the BIRT based on the key set identifier & bitstringlength & sub-domain-id."; 674 } 675 description 676 "Query the BIRT based on the key bitstringlengt & sub-domain-id."; 677 } 678 description 679 "Query the BIRT based on the key sub-domain."; 680 } 681 description 682 "Shows Bit Index Routing Table."; 683 } 684 } 686 /* Notifications */ 687 notification bfr-id-collision{ 688 leaf bfr-id{ 689 type bfr-id; 690 description 691 "BIER BFR ID."; 692 } 693 description 694 "BFR ID received in the controlplane that caused BFR ID collision."; 695 } 697 notification bfr-zero{ 698 leaf ipv4-bfr-prefix{ 699 type inet:ipv4-prefix; 700 description 701 "BIER ipv4 bfr prefix"; 702 } 703 leaf ipv6-bfr-prefix{ 704 type inet:ipv6-prefix; 705 description 706 "BIER ipv6 bfr prefix"; 707 } 708 description 709 "Invalid value associated with prefix"; 710 } 712 notification sub-domain-id-collision{ 713 leaf sub-domain-id{ 714 type sub-domain-id; 715 description 716 "BIER sub domain ID"; 717 } 718 leaf mt-id{ 719 type uint16; 720 description 721 "Multi-topology ID"; 722 } 723 description 724 "Sub domain ID received in the controlplane that caused Sub domain ID collision"; 725 } 726 } 728 730 8. Security Considerations 732 TBD. 734 9. Acknowledgements 736 We would like to thank IJsbrand Wijnands, Reshad Rahman and Giles 737 Heron for their comments and support of this work. 739 10. IANA Considerations 741 This document requires no IANA Actions. Please remove this section 742 before RFC publication. 744 11. References 746 11.1. Normative references 748 [I-D.ietf-bier-architecture] 749 Wijnands, I., Rosen, E., Dolganow, A., Przygienda, A., and 750 S. Aldrin, "Multicast using Bit Index Explicit 751 Replication", draft-ietf-bier-architecture-03 (work in 752 progress), January 2016. 754 [I-D.ietf-bier-isis-extensions] 755 Ginsberg, L., Przygienda, A., Aldrin, S., and J. Zhang, 756 "BIER support via ISIS", draft-ietf-bier-isis- 757 extensions-02 (work in progress), March 2016. 759 [I-D.ietf-bier-mpls-encapsulation] 760 Wijnands, I., Rosen, E., Dolganow, A., Tantsura, J., and 761 S. Aldrin, "Encapsulation for Bit Index Explicit 762 Replication in MPLS Networks", draft-ietf-bier-mpls- 763 encapsulation-04 (work in progress), April 2016. 765 [I-D.ietf-bier-ospf-bier-extensions] 766 Psenak, P., Kumar, N., Wijnands, I., Dolganow, A., 767 Przygienda, A., Zhang, J., and S. Aldrin, "OSPF Extensions 768 for BIER", draft-ietf-bier-ospf-bier-extensions-02 (work 769 in progress), March 2016. 771 [I-D.ietf-isis-yang-isis-cfg] 772 Litkowski, S., Yeung, D., Lindem, A., Zhang, J., and L. 773 Lhotka, "YANG Data Model for IS-IS protocol", draft-ietf- 774 isis-yang-isis-cfg-08 (work in progress), March 2016. 776 [I-D.ietf-netmod-routing-cfg] 777 Lhotka, L. and A. Lindem, "A YANG Data Model for Routing 778 Management", draft-ietf-netmod-routing-cfg-21 (work in 779 progress), March 2016. 781 [I-D.ietf-ospf-yang] 782 Yeung, D., Qu, Y., Zhang, J., Bogdanovic, D., and K. 783 Koushik, "Yang Data Model for OSPF Protocol", draft-ietf- 784 ospf-yang-04 (work in progress), March 2016. 786 [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for 787 the Network Configuration Protocol (NETCONF)", RFC 6020, 788 DOI 10.17487/RFC6020, October 2010, 789 . 791 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 792 and A. Bierman, Ed., "Network Configuration Protocol 793 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 794 . 796 [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", 797 RFC 6991, DOI 10.17487/RFC6991, July 2013, 798 . 800 [RFC7223] Bjorklund, M., "A YANG Data Model for Interface 801 Management", RFC 7223, DOI 10.17487/RFC7223, May 2014, 802 . 804 11.2. Informative references 806 [I-D.saad-mpls-static-yang] 807 Saad, T., Raza, K., Gandhi, R., Liu, X., Beeram, V., Shah, 808 H., Bryskin, I., Chen, X., Jones, R., and B. Wen, "A YANG 809 Data Model for MPLS Static LSPs", draft-saad-mpls-static- 810 yang-03 (work in progress), May 2016. 812 Authors' Addresses 814 Ran Chen 815 ZTE Corporation 816 No.50 Software Avenue,Yuhuatai District 817 Nanjing, Jiangsu Province 210012 818 China 820 Phone: +86 025 88014636 821 Email: chen.ran@zte.com.cn 823 Fangwei Hu 824 ZTE Corporation 825 No.889 Bibo Rd 826 Shanghai 201203 827 China 829 Phone: +86 21 68896273 830 Email: hu.fangwei@zte.com.cn 832 Zheng Zhang 833 ZTE Corporation 834 No.50 Software Avenue,Yuhuatai District 835 Nanjing, Jiangsu Province 210012 836 China 838 Email: zhang.zheng@zte.com.cn 840 Xianxian Dai 841 ZTE Corporation 842 No.50 Software Avenue,Yuhuatai District 843 Nanjing, Jiangsu Province 210012 844 China 846 Email: Dai.xianxian@zte.com.cn 847 Mahesh Sivakumar 848 Cisco Systems, Inc. 849 510 McCarthy Blvd 850 Milpitas,California 95035 851 United States 853 Email: masivaku@cisco.com