idnits 2.17.1 draft-ietf-bier-te-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 : ---------------------------------------------------------------------------- ** The document seems to lack a Security Considerations section. ** There are 5 instances of too long lines in the document, the longest one being 2 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 102 has weird spacing: '...main-id uin...' == Line 109 has weird spacing: '...main-id uin...' == Line 111 has weird spacing: '...fwd-bsl uin...' == Line 130 has weird spacing: '...ap-type enc...' == Line 134 has weird spacing: '...wd-intf if:...' == (1 more instance...) -- The document date (7 November 2021) is 894 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: 'RFC8279' is defined on line 755, but no explicit reference was found in the text == Unused Reference: 'RFC8296' is defined on line 761, but no explicit reference was found in the text == Unused Reference: 'RFC8343' is defined on line 767, but no explicit reference was found in the text == Unused Reference: 'RFC8349' is defined on line 771, but no explicit reference was found in the text == Unused Reference: 'RFC8407' is defined on line 776, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-bier-bier-yang' is defined on line 790, but no explicit reference was found in the text == Outdated reference: A later version (-13) exists of draft-ietf-bier-te-arch-10 == Outdated reference: A later version (-08) exists of draft-ietf-bier-bier-yang-07 Summary: 2 errors (**), 0 flaws (~~), 15 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 BIER WG Z. Zhang 3 Internet-Draft ZTE Corporation 4 Intended status: Standards Track C. Wang 5 Expires: 11 May 2022 Individual 6 R. Chen 7 ZTE Corporation 8 F. Hu 9 Individual 10 M. Sivakumar 11 Juniper networks 12 H. Chen 13 Individual 14 7 November 2021 16 A YANG data model for Tree Engineering for Bit Index Explicit 17 Replication (BIER-TE) 18 draft-ietf-bier-te-yang-04 20 Abstract 22 This document defines a YANG data model for Tree Engineering for Bit 23 Index Explicit Replication (BIER-TE) configuration and operation. 25 Status of This Memo 27 This Internet-Draft is submitted in full conformance with the 28 provisions of BCP 78 and BCP 79. 30 Internet-Drafts are working documents of the Internet Engineering 31 Task Force (IETF). Note that other groups may also distribute 32 working documents as Internet-Drafts. The list of current Internet- 33 Drafts is at https://datatracker.ietf.org/drafts/current/. 35 Internet-Drafts are draft documents valid for a maximum of six months 36 and may be updated, replaced, or obsoleted by other documents at any 37 time. It is inappropriate to use Internet-Drafts as reference 38 material or to cite them other than as "work in progress." 40 This Internet-Draft will expire on 11 May 2022. 42 Copyright Notice 44 Copyright (c) 2021 IETF Trust and the persons identified as the 45 document authors. All rights reserved. 47 This document is subject to BCP 78 and the IETF Trust's Legal 48 Provisions Relating to IETF Documents (https://trustee.ietf.org/ 49 license-info) in effect on the date of publication of this document. 50 Please review these documents carefully, as they describe your rights 51 and restrictions with respect to this document. Code Components 52 extracted from this document must include Simplified BSD License text 53 as described in Section 4.e of the Trust Legal Provisions and are 54 provided without warranty as described in the Simplified BSD License. 56 Table of Contents 58 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 59 2. Conventions Used in This Document . . . . . . . . . . . . . . 2 60 3. Design of the Data Model . . . . . . . . . . . . . . . . . . 2 61 4. BIER-TE configuration . . . . . . . . . . . . . . . . . . . . 4 62 5. Notifications . . . . . . . . . . . . . . . . . . . . . . . . 4 63 6. RPCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 64 7. BIER TE YANG model . . . . . . . . . . . . . . . . . . . . . 4 65 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15 66 9. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 16 67 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 16 68 10.1. Normative References . . . . . . . . . . . . . . . . . . 16 69 10.2. Informative References . . . . . . . . . . . . . . . . . 17 70 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17 72 1. Introduction 74 [I-D.ietf-bier-te-arch] introduces an architecture for BIER-TE: Tree 75 Engineering for Bit Index Explicit Replication (BIER). This document 76 defines a YANG data model for BIER TE. The content is in keeping 77 with the TE architecture draft. In addition, this YANG data model 78 contains BIER TE frr items of [I-D.eckert-bier-te-frr]. 80 2. Conventions Used in This Document 82 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 83 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 84 "OPTIONAL" in this document are to be interpreted as described in BCP 85 14 [RFC2119] [RFC8174] when, and only when, they appear in all 86 capitals, as shown here. 88 3. Design of the Data Model 90 The BIER TE YANG model includes BIER TE adjancency configuration and 91 forwarding items configuration. Some features can also be used to 92 enhance BIER TE function, like ECMP and FRR. 94 module: ietf-bier-te 95 augment /rt:routing/rt:control-plane-protocols 96 /rt:control-plane-protocol: 97 +--rw bier-te 98 +--rw te-adj 99 | +--rw adj-if* [name] 100 | +--rw name if:interface-ref 101 | +--rw subdomain* [subdomain-id] 102 | | +--rw subdomain-id uint16 103 | | +--rw si* [si] 104 | | +--rw si uint16 105 | | +--rw adj-id* uint16 106 | +--rw adj-type? enumeration 107 +--rw te-fwd 108 +--rw subdomain* [subdomain-id] 109 +--rw subdomain-id uint16 110 +--rw bsl* [fwd-bsl] 111 | +--rw fwd-bsl uint16 112 | +--rw si* [si] 113 | +--rw si uint16 114 | +--rw te-bift-id 115 | | +--rw encap-type? encapsulation-type 116 | | +--rw value rt-types:mpls-label 117 | +--rw fwd-items* [te-bp] 118 | +--rw te-bp uint16 119 | +--rw fwd-next-hop* [next-hop] 120 | | +--rw next-hop inet:ip-address 121 | | +--rw dnr-flag? boolean 122 | | +--rw fwd-type 123 | | | +--rw (fwd-type) 124 | | | +--:(connected) 125 | | | +--:(routed) 126 | | | +--:(local-decap) 127 | | | +--:(other) 128 | | +--rw te-out-bift-id 129 | | | +--rw te-out-bift-id* [encap-type] 130 | | | +--rw encap-type encapsulation-type 131 | | | +--rw value 132 | | | rt-types:mpls-label 133 | | +--rw out-if-list* [fwd-intf] 134 | | +--rw fwd-intf if:interface-ref 135 | +--rw te-frr {bier-te-frr}? 136 | +--rw frr-index? leafref 137 | +--rw resetbitmask 138 | +--rw bit-string* [index] 139 | +--rw index uint8 140 | +--rw bitmask? uint32 141 +--rw te-frr-items {bier-te-frr}? 142 +--rw btaft* [frr-index] 143 +--rw frr-index uint16 144 +--rw frr-si uint16 145 +--rw frr-bsl uint16 146 +--rw addbitmask 147 +--rw bit-string* [index] 148 +--rw index uint8 149 +--rw bitmask? uint32 151 notifications: 152 +---n bier-te-notification 153 +--ro bp-is-zero* [if-index] 154 +--ro if-index if:interface-ref 155 +--ro adj-type? enumeration 157 4. BIER-TE configuration 159 The BIER-TE forwarding item is indexed by the combination of sub- 160 domain-id, BitStringLength and set identifier. 162 One interface can be used in different sub-domain, so the BIER TE 163 adjacency information is managed by BIER TE function other than by 164 interface itself. 166 Because the BIER-TE is controlled by controller now, the information 167 about IGP is not defined. If in the future the IGP is used to carry 168 the information about BIER-TE, the IGP extension will be added in 169 this document. 171 5. Notifications 173 If the adjacency id of one adjacency is set to zero, the value is 174 invalid. The notification should be sent to controller and network 175 manager. 177 6. RPCs 179 TBD. 181 7. BIER TE YANG model 183 file "ietf-bier-te@2021-11-08.yang" 184 module ietf-bier-te { 186 yang-version 1.1; 188 namespace "urn:ietf:params:xml:ns:yang:ietf-bier-te"; 189 prefix bier-te; 191 import ietf-inet-types { 192 prefix "inet"; 193 reference 194 "RFC 6991: Common YANG Data Types"; 195 } 197 import ietf-routing { 198 prefix "rt"; 199 reference 200 "RFC 8349: A YANG Data Model for Routing Management 201 (NMDA Version)"; 202 } 204 import ietf-interfaces { 205 prefix "if"; 206 reference 207 "RFC 8343: A YANG Data Model for Interface Management"; 208 } 210 import ietf-routing-types { 211 prefix "rt-types"; 212 reference 213 "RFC 8294: Common YANG Data Types for the Routing Area"; 214 } 216 organization " IETF BIER (Bit Indexed Explicit Replication) 217 Working Group"; 218 contact 219 "WG Web: 220 WG List: 222 Editor: Zheng Zhang 223 224 Editor: Cui Wang 225 226 Editor: Ran Chen 227 228 Editor: Fangwei Hu 229 230 Editor: Mahesh Sivakumar 231 232 Editor: Huanan Chen 233 234 "; 236 description 237 "The module defines the YANG definitions for Traffic 238 Engineering for Bit Index Explicit Replication (BIER-TE). 240 Copyright (c) 2020 IETF Trust and the persons identified as 241 authors of the code. All rights reserved. 243 Redistribution and use in source and binary forms, with or 244 without modification, is permitted pursuant to, and subject 245 to the license terms contained in, the Simplified BSD 246 License set forth in Section 4.c of the IETF Trust's Legal 247 Provisions Relating to IETF Documents 248 (https://trustee.ietf.org/license-info). 250 This version of this YANG module is part of RFC XXXX 251 (https://www.rfc-editor.org/info/rfcXXXX); see the RFC 252 itself for full legal notices. 254 The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 255 'SHALL NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 256 'NOT RECOMMENDED', 'MAY', and 'OPTIONAL' in this document 257 are to be interpreted as described in BCP 14 (RFC 2119) 258 (RFC 8174) when, and only when, they appear in all 259 capitals, as shown here."; 261 revision 2021-11-08 { 262 description 263 "Initial revision."; 264 reference 265 "I-D.ietf-bier-te-arch: Tree Engineering for Bit Index 266 Explicit Replication (BIER-TE)"; 267 } 269 /* 270 * Features 271 */ 272 feature bier-te-frr { 273 description 274 "Support Fast Re-route feature in BIER TE."; 275 reference 276 "I-D.eckert-bier-te-frr: Protection Methods for BIER-TE"; 277 } 279 /* 280 * Identities 281 */ 283 identity bier-te { 284 base rt:control-plane-protocol; 285 description 286 "Identity for the Tree Engineering for Bit Index Explicit 287 Replication (BIER-TE)."; 288 reference 289 "I-D.ietf-bier-te-arch: Tree Engineering for Bit Index 290 Explicit Replication (BIER-TE)"; 291 } 293 typedef encapsulation-type { 294 type enumeration { 295 enum MPLS { 296 description 297 "The forwarding encapsulation is MPLS 298 described in RFC8296 section 2.1."; 299 } 300 enum Ethernet { 301 description 302 "The forwarding encapsulation is Ethernet, 303 which is belonging to non-mpls part 304 described in RFC8296 section 2.2."; 305 } 306 enum IPv6 { 307 description 308 "The forwarding encapsulation is IPv6, 309 which is belonging to non-mpls part 310 described in RFC8296 section 2.2."; 311 } 312 } 313 description 314 "The encapsulation type of the BIER-TE packet. 315 If this type is not set, MPLS is the default type."; 316 } // encapsulation-type 318 grouping bit-string { 319 description 320 "The bit string which each bit represents an adjacency. 321 It is encapsulated in BIER header."; 322 reference 323 "I-D.ietf-bier-te-arch: Tree Engineering for Bit Index 324 Explicit Replication (BIER-TE), section 3.3. 325 RFC8279: Multicast Using Bit Index Explicit Replication 326 (BIER). 327 RFC8296: Encapsulation for Bit Index Explicit Replication 328 (BIER) in MPLS and Non-MPLS Networks."; 330 list bit-string { 331 key "index"; 332 description 333 "As the definition in RFC 8279, the bit-string lengths are 334 64, 128, 256, 512, 1024, 2048, 4096 bits. The according 335 encapsulation is defined in RFC8296. BIER-TE uses the 336 similar function for bit string."; 338 leaf index { 339 type uint8 { 340 range "2..128"; 341 } 342 description 343 "The index of bit-mask. The minimum index value is 64 and 344 the corresponding bit string length is 64 bits. The 345 maximum index value is 128 and the corresponding 346 bit-string length is 4096 bits."; 347 } 348 leaf bitmask { 349 type uint32; 350 description "The bit-string in 4-octet units."; 351 } 352 } 353 } // bit-string 355 grouping adj-type { 356 description "The collection of all possible adjacency type."; 358 leaf adj-type { 359 type enumeration { 360 enum p2p { 361 description "Describes p2p adjacency."; 362 } 363 enum bfer { 364 description "Describes bfer adjacency."; 365 } 366 enum leaf-bfer { 367 description 368 "Describes leaf-bfer adjacency. There is no next BFR that 369 the packet should be forwarded."; 370 } 371 enum lan { 372 description "Describes lan adjacency."; 373 } 374 enum spoke { 375 description "Describes spoke adjacency of hub-and-spoke."; 376 } 377 enum ring-clockwise { 378 description "Describes clockwise adjacency in ring."; 379 } 380 enum ring-counterclockwise { 381 description "Describes counterclockwise adjacency in ring."; 382 } 383 enum ecmp { 384 description 385 "Describes ecmp adjacency. When the type is set to ecmp, 386 the corresponding ecmp entry should be used to balance 387 the load."; 388 } 389 enum virtual-link { 390 description 391 "Describes virtual adjacency between two indirect connect 392 nodes."; 393 } 394 enum other { 395 description "Describes other id type of adjacency."; 396 } 397 } 398 description "The collection of all possible adjacency type."; 399 } 400 } // adj-type 402 grouping te-items { 403 description "The BIER TE forwarding items collection."; 405 list fwd-next-hop { 406 key "next-hop"; 407 description 408 "The next hop information for forwarding. 409 If ECMP function defined in section 3.2.3 is used, 410 multiple next hops may be existed. 411 If ECMP function is not enabled, 412 the next hop may be one only."; 414 leaf next-hop { 415 type inet:ip-address; 416 mandatory true; 417 description "Next hop address."; 418 } 419 leaf dnr-flag { 420 type boolean; 421 description 422 "When the flag is set to 1, the BP of adjacency should not 423 be reset when packet copies are created. The flag makes 424 sense only when the forwarding type is 'connected'."; 425 } 426 container fwd-type { 427 description 428 "The collection of all possible forwarding types."; 430 choice fwd-type { 431 mandatory true; 432 case connected { 433 description 434 "The forwarding type is connected. Mostly connected 435 interfaces."; 436 } 437 case routed { 438 description 439 "The forwarding type is routed. Mostly not connected 440 interfaces."; 441 } 442 case local-decap { 443 description 444 "Means that the packet should be decapsulated and 445 forward out of BIER domain."; 446 } 447 case other { 448 description 449 "Means that the packet should be discarded."; 450 } 451 description 452 "The collection of all possible forwarding types."; 453 } 454 } // fwd-type 456 container te-out-bift-id { 457 description 458 "The bift-id information corresponding to a specific 459 outbound interface."; 461 list te-out-bift-id { 462 key "encap-type"; 463 leaf encap-type { 464 type encapsulation-type; 465 description 466 "The encapsulation type of BIER-TE packet."; 467 } 468 leaf value { 469 type rt-types:mpls-label; 470 mandatory true; 471 description 472 "The bift-id value of the forwarding item. 473 It can be a mpls label or an index for ethernet 474 or IPv6 encapsulation, which is used to represent 475 specific combination of [SD, BSL, SI]. 476 The ethernet or IPv6 index value is the same range 477 (20bits) as mpls label. 479 This value MUST NOT be set to 0."; 480 } 481 description 482 "The bift-id value and the encapsulation type 483 for the BIER-TE packet."; 484 } 485 } 487 list out-if-list { 488 key "fwd-intf"; 489 description 490 "The outbound interface information for forwarding."; 492 leaf fwd-intf { 493 type if:interface-ref; 494 mandatory true; 495 description 496 "The out interface of this forwarding item."; 497 } 498 } 499 } // next-hop 500 } // te-items 502 /* 503 * data nodes 504 */ 505 augment "/rt:routing/rt:control-plane-protocols/" 506 +"rt:control-plane-protocol" { 507 description "The BIER TE information."; 508 container bier-te { 509 description "The BIER TE information container."; 511 container te-adj { 512 description "The BIER TE adjacency information."; 513 list adj-if { 514 key "name"; 515 description "List of BIER-TE interfaces."; 516 leaf name { 517 type if:interface-ref; 518 description "Interface name reference."; 519 } 520 list subdomain { 521 key "subdomain-id"; 522 description 523 "The sub-domain which the interface belongs to. 524 One interface can belong to many subdomains."; 526 leaf subdomain-id { 527 type uint16; 528 description "The sub-domain-id of this sub-domain."; 529 reference 530 "RFC 8279: Multicast Using Bit Index Explicit 531 Replication (BIER)"; 532 } 533 list si { 534 key "si"; 535 description "The set identifier value."; 537 leaf si{ 538 type uint16; 539 mandatory true; 540 description 541 "The set identifier of this forwarding item."; 542 } 543 leaf-list adj-id { 544 type uint16; 545 description "The ID of an adjacency."; 546 } 547 } 548 } 549 uses adj-type; 550 } 551 } // te-adj 553 container te-fwd { 554 description "The BIER TE forwarding information."; 556 list subdomain { 557 key "subdomain-id"; 558 description 559 "The sub-domain which the interface belongs to. 560 One interface can belong to many subdomains."; 562 leaf subdomain-id { 563 type uint16; 564 description "The sub-domain-id of this sub-domain."; 565 reference 566 "RFC 8279: Multicast Using Bit Index Explicit 567 Replication (BIER)"; 568 } 569 list bsl { 570 key "fwd-bsl"; 571 description "The forwarding items in one BSL."; 572 leaf fwd-bsl { 573 type uint16; 574 description "The value of bitstringlength."; 576 } 577 list si { 578 key "si"; 579 description 580 "The forwarding items in one combination of SD, 581 BSL and SI."; 582 leaf si{ 583 type uint16; 584 mandatory true; 585 description 586 "The set identifier of this forwarding item."; 587 } 588 container te-bift-id { 589 description 590 "The bift-id which is used to locate the specific 591 forwarding item."; 592 leaf encap-type { 593 type encapsulation-type; 594 description 595 "The encapsulation type for BIER-TE packet."; 596 } 598 leaf value { 599 type rt-types:mpls-label; 600 mandatory true; 601 description 602 "The bift-id value of the forwarding item. 603 It can be a mpls label or an index for 604 ethernet or IPv6 encapsulation, 605 which is used to represent specific combination 606 of [SD, BSL, SI]. 607 The ethernet or IPv6 index value is the same 608 range (20bits) as mpls label."; 609 } 610 } 612 list fwd-items { 613 key "te-bp"; 614 description 615 "The forwarding information of one BIER TE item."; 616 leaf te-bp { 617 type uint16; 618 mandatory true; 619 description 620 "The bit index of a BIER TE forwarding item."; 621 } 622 uses te-items; 623 container te-frr { 624 if-feature bier-te-frr; 625 leaf frr-index { 626 type leafref { 627 path "../../../../../" + 628 "te-frr-items/btaft/frr-index"; 629 } 630 description "The index of this frr path."; 631 } 632 container resetbitmask { 633 description 634 "The deleting bitmask of the forwarding item."; 635 uses bit-string; 636 } 637 description 638 "If this link is protected, frr items can be 639 used to forward flows when this link is down."; 640 } // te-frr 641 } // fwd-items 642 } // si 643 } // bsl 645 container te-frr-items { 646 if-feature bier-te-frr; 647 description "The TE fast re-route information."; 648 list btaft { 649 key "frr-index"; 650 description 651 "The index of the frr paths. This item can be used 652 for multiple links protection in different SI."; 653 leaf frr-index { 654 type uint16; 655 mandatory true; 656 description "The frr item index."; 657 } 658 leaf frr-si{ 659 type uint16; 660 mandatory true; 661 description 662 "The set identifier of this forwarding item."; 663 } 664 leaf frr-bsl { 665 type uint16; 666 mandatory true; 667 description "The value of bitstringlength."; 668 } 669 container addbitmask { 670 description 671 "The adding bitmask of the forwarding item. 672 This item should be merged into the packet's 673 bit-string."; 674 uses bit-string; 675 } 676 } // btaft 677 } // te-frr-items 678 } // subdomain 679 } // te-fwd 680 } // bier-te 681 } 683 /* 684 * Notifications 685 */ 686 notification bier-te-notification { 687 description 688 "The notification is sent when a condition changes."; 689 list bp-is-zero { 690 key "if-index"; 691 description "The adjacency id is zero. It is invalid."; 692 leaf if-index { 693 type if:interface-ref; 694 description "The adjacency id is zero."; 695 } 696 uses adj-type; 697 } 698 } 699 } 700 702 8. IANA Considerations 704 The IANA is requested to assign two new URIs from the IETF XML 705 registry ([RFC3688]). Authors are suggesting the following URI: 707 URI: urn:ietf:params:xml:ns:yang:ietf-bier-te 709 Registrant Contact: BIER WG 711 XML: N/A, the requested URI is an XML namespace 713 This document also requests one new YANG module name in the YANG 714 Module Names registry ([RFC6020]) with the following suggestion: 716 name: ietf-bier-te 717 namespace: urn:ietf:params:xml:ns:yang:ietf-bier-te 719 prefix: bier-te 721 reference: RFC XXXX 723 9. Acknowledgement 725 The authors would like to thank Min Gu (gumin20181129@163.com) for 726 her testing, verification and valuable suggestion. And the authors 727 would like to thank Benjamin R and Benchong Xu for their valuable 728 comments. 730 10. References 732 10.1. Normative References 734 [I-D.ietf-bier-te-arch] 735 Eckert, T., Cauchie, G., and M. Menth, "Tree Engineering 736 for Bit Index Explicit Replication (BIER-TE)", Work in 737 Progress, Internet-Draft, draft-ietf-bier-te-arch-10, 9 738 July 2021, . 741 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 742 Requirement Levels", BCP 14, RFC 2119, 743 DOI 10.17487/RFC2119, March 1997, 744 . 746 [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for 747 the Network Configuration Protocol (NETCONF)", RFC 6020, 748 DOI 10.17487/RFC6020, October 2010, 749 . 751 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 752 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 753 May 2017, . 755 [RFC8279] Wijnands, IJ., Ed., Rosen, E., Ed., Dolganow, A., 756 Przygienda, T., and S. Aldrin, "Multicast Using Bit Index 757 Explicit Replication (BIER)", RFC 8279, 758 DOI 10.17487/RFC8279, November 2017, 759 . 761 [RFC8296] Wijnands, IJ., Ed., Rosen, E., Ed., Dolganow, A., 762 Tantsura, J., Aldrin, S., and I. Meilik, "Encapsulation 763 for Bit Index Explicit Replication (BIER) in MPLS and Non- 764 MPLS Networks", RFC 8296, DOI 10.17487/RFC8296, January 765 2018, . 767 [RFC8343] Bjorklund, M., "A YANG Data Model for Interface 768 Management", RFC 8343, DOI 10.17487/RFC8343, March 2018, 769 . 771 [RFC8349] Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for 772 Routing Management (NMDA Version)", RFC 8349, 773 DOI 10.17487/RFC8349, March 2018, 774 . 776 [RFC8407] Bierman, A., "Guidelines for Authors and Reviewers of 777 Documents Containing YANG Data Models", BCP 216, RFC 8407, 778 DOI 10.17487/RFC8407, October 2018, 779 . 781 10.2. Informative References 783 [I-D.eckert-bier-te-frr] 784 Eckert, T., Cauchie, G., Braun, W., and M. Menth, 785 "Protection Methods for BIER-TE", Work in Progress, 786 Internet-Draft, draft-eckert-bier-te-frr-03, 5 March 2018, 787 . 790 [I-D.ietf-bier-bier-yang] 791 Chen, R., Hu, F., Zhang, Z., Dai, X., and M. Sivakumar, 792 "YANG Data Model for BIER Protocol", Work in Progress, 793 Internet-Draft, draft-ietf-bier-bier-yang-07, 8 September 794 2020, . 797 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 798 DOI 10.17487/RFC3688, January 2004, 799 . 801 Authors' Addresses 803 Zheng(Sandy) Zhang 804 ZTE Corporation 805 Nanjing 806 China 808 Email: zhang.zheng@zte.com.cn 809 Cui(Linda) Wang 810 Individual 812 Email: lindawangjoy@gmail.com 814 Ran Chen 815 ZTE Corporation 816 Nanjing 817 China 819 Email: chen.ran@zte.com.cn 821 Fangwei Hu 822 Individual 823 Shanghai 824 China 826 Email: hufwei@gmail.com 828 Mahesh Sivakumar 829 Juniper networks 830 1133 Innovation Way 831 Sunnyvale, CALIFORNIA 94089 , 832 United States 834 Email: sivakumar.mahesh@gmail.com 836 Huanan Chen 837 Individual 838 China 840 Email: chenhuanan@189.cn