idnits 2.17.00 (12 Aug 2021) /tmp/idnits14452/draft-ietf-bier-te-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 : ---------------------------------------------------------------------------- ** The document seems to lack a Security Considerations section. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 469: '... This value MUST not be set to 0....' Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 92 has weird spacing: '...main-id uin...' == Line 99 has weird spacing: '...main-id uin...' == Line 101 has weird spacing: '...fwd-bsl uin...' == Line 120 has weird spacing: '...ap-type enc...' == Line 124 has weird spacing: '...wd-intf if:...' == (1 more instance...) == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: list te-out-bift-id { key "encap-type"; leaf encap-type { type encapsulation-type; description "The encapsulation type of BIER-TE packet."; } leaf value { type rt-types:mpls-label; mandatory true; description "The bift-id value of the forwarding item. It can be a mpls label or an index for ethernet or IPv6 encapsulation, which is used to represent specific combination of [SD, BSL, SI]. The ethernet or IPv6 index value is the same range (20bits) as mpls label. This value MUST not be set to 0."; } description "The bift-id value and the encapsulation type for the BIER-TE packet."; } } -- The document date (May 17, 2021) is 369 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-bier-yang' is defined on line 730, but no explicit reference was found in the text == Unused Reference: 'RFC6087' is defined on line 749, but no explicit reference was found in the text == Unused Reference: 'RFC7223' is defined on line 753, but no explicit reference was found in the text == Unused Reference: 'RFC8279' is defined on line 757, but no explicit reference was found in the text == Unused Reference: 'RFC8296' is defined on line 763, but no explicit reference was found in the text == Unused Reference: 'RFC8349' is defined on line 769, but no explicit reference was found in the text ** Downref: Normative reference to an Experimental draft: draft-eckert-bier-te-frr (ref. 'I-D.eckert-bier-te-frr') == Outdated reference: A later version (-13) exists of draft-ietf-bier-te-arch-09 ** Obsolete normative reference: RFC 6087 (Obsoleted by RFC 8407) ** Obsolete normative reference: RFC 7223 (Obsoleted by RFC 8343) Summary: 5 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: November 18, 2021 Individual 6 R. Chen 7 ZTE Corporation 8 F. Hu 9 Individual 10 M. Sivakumar 11 Juniper networks 12 H. Chen 13 Individual 14 May 17, 2021 16 A YANG data model for Traffic Engineering for Bit Index Explicit 17 Replication (BIER-TE) 18 draft-ietf-bier-te-yang-03 20 Abstract 22 This document defines a YANG data model for Traffic Engineering for 23 Bit 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 November 18, 2021. 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 49 (https://trustee.ietf.org/license-info) in effect on the date of 50 publication of this document. Please review these documents 51 carefully, as they describe your rights and restrictions with respect 52 to this document. Code Components extracted from this document must 53 include Simplified BSD License text as described in Section 4.e of 54 the Trust Legal Provisions and are provided without warranty as 55 described in the Simplified BSD License. 57 Table of Contents 59 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 60 2. Design of the Data Model . . . . . . . . . . . . . . . . . . 2 61 3. BIER-TE configuration . . . . . . . . . . . . . . . . . . . . 4 62 4. Notifications . . . . . . . . . . . . . . . . . . . . . . . . 4 63 5. RPCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 64 6. BIER TE YANG model . . . . . . . . . . . . . . . . . . . . . 4 65 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15 66 8. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 15 67 9. Normative References . . . . . . . . . . . . . . . . . . . . 16 68 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17 70 1. Introduction 72 [I-D.ietf-bier-te-arch] introduces an architecture for BIER-TE: 73 Traffic Engineering for Bit Index Explicit Replication (BIER). This 74 document defines a YANG data model for BIER TE. The content is in 75 keeping with the TE architecture draft. In addition, this YANG data 76 model contains BIER TE frr items of [I-D.eckert-bier-te-frr]. 78 2. Design of the Data Model 80 The BIER TE YANG model includes BIER TE adjancency configuration and 81 forwarding items configuration. Some features can also be used to 82 enhance BIER TE function, like ECMP and FRR. 84 module: ietf-bier-te 85 augment /rt:routing/rt:control-plane-protocols 86 /rt:control-plane-protocol: 87 +--rw bier-te 88 +--rw te-adj 89 | +--rw adj-if* [name] 90 | +--rw name if:interface-ref 91 | +--rw subdomain* [subdomain-id] 92 | | +--rw subdomain-id uint16 93 | | +--rw si* [si] 94 | | +--rw si uint16 95 | | +--rw adj-id* uint16 96 | +--rw adj-type? enumeration 97 +--rw te-fwd 98 +--rw subdomain* [subdomain-id] 99 +--rw subdomain-id uint16 100 +--rw bsl* [fwd-bsl] 101 | +--rw fwd-bsl uint16 102 | +--rw si* [si] 103 | +--rw si uint16 104 | +--rw te-bift-id 105 | | +--rw encap-type? encapsulation-type 106 | | +--rw value rt-types:mpls-label 107 | +--rw fwd-items* [te-bp] 108 | +--rw te-bp uint16 109 | +--rw fwd-next-hop* [next-hop] 110 | | +--rw next-hop inet:ip-address 111 | | +--rw dnr-flag? boolean 112 | | +--rw fwd-type 113 | | | +--rw (fwd-type) 114 | | | +--:(connected) 115 | | | +--:(routed) 116 | | | +--:(local-decap) 117 | | | +--:(other) 118 | | +--rw te-out-bift-id 119 | | | +--rw te-out-bift-id* [encap-type] 120 | | | +--rw encap-type encapsulation-type 121 | | | +--rw value 122 | | | rt-types:mpls-label 123 | | +--rw out-if-list* [fwd-intf] 124 | | +--rw fwd-intf if:interface-ref 125 | +--rw te-frr {bier-te-frr}? 126 | +--rw frr-index? leafref 127 | +--rw resetbitmask 128 | +--rw bit-string* [index] 129 | +--rw index uint8 130 | +--rw bitmask? uint32 131 +--rw te-frr-items {bier-te-frr}? 132 +--rw btaft* [frr-index] 133 +--rw frr-index uint16 134 +--rw frr-si uint16 135 +--rw frr-bsl uint16 136 +--rw addbitmask 137 +--rw bit-string* [index] 138 +--rw index uint8 139 +--rw bitmask? uint32 141 notifications: 142 +---n bier-te-notification 143 +--ro bp-is-zero* [if-index] 144 +--ro if-index if:interface-ref 145 +--ro adj-type? enumeration 147 3. BIER-TE configuration 149 The BIER-TE forwarding item is indexed by the combination of sub- 150 domain-id, BitStringLength and set identifier. 152 One interface can be used in different sub-domain, so the BIER TE 153 adjacency information is managed by BIER TE function other than by 154 interface itself. 156 Because the BIER-TE is controlled by controller now, the information 157 about IGP is not defined. If in the future the IGP is used to carry 158 the information about BIER-TE, the IGP extension will be added in 159 this document. 161 4. Notifications 163 If the adjacency id of one adjacency is set to zero, the value is 164 invalid. The notification should be sent to controller and network 165 manager. 167 5. RPCs 169 TBD. 171 6. BIER TE YANG model 173 file "ietf-bier-te@2021-05-17.yang" 174 module ietf-bier-te { 176 yang-version 1.1; 178 namespace "urn:ietf:params:xml:ns:yang:ietf-bier-te"; 180 prefix bier-te; 182 import ietf-inet-types { 183 prefix "inet"; 184 reference 185 "RFC 6991: Common YANG Data Types"; 186 } 188 import ietf-routing { 189 prefix "rt"; 190 reference 191 "RFC 8349: A YANG Data Model for Routing Management 192 (NMDA Version)"; 194 } 196 import ietf-interfaces { 197 prefix "if"; 198 reference 199 "RFC 8343: A YANG Data Model for Interface Management"; 200 } 202 import ietf-routing-types { 203 prefix "rt-types"; 204 reference 205 "RFC 8294: Common YANG Data Types for the Routing Area"; 206 } 208 organization " IETF BIER (Bit Indexed Explicit Replication) 209 Working Group"; 210 contact 211 "WG Web: 212 WG List: 214 Editor: Zheng Zhang 215 216 Editor: Cui Wang 217 218 Editor: Ran Chen 219 220 Editor: Fangwei Hu 221 222 Editor: Mahesh Sivakumar 223 224 Editor: Huanan Chen 225 226 "; 228 description 229 "The module defines the YANG definitions for Traffic 230 Engineering for Bit Index Explicit Replication (BIER-TE). 232 Copyright (c) 2020 IETF Trust and the persons identified as 233 authors of the code. All rights reserved. 235 Redistribution and use in source and binary forms, with or 236 without modification, is permitted pursuant to, and subject 237 to the license terms contained in, the Simplified BSD 238 License set forth in Section 4.c of the IETF Trust's Legal 239 Provisions Relating to IETF Documents 240 (https://trustee.ietf.org/license-info). 242 This version of this YANG module is part of RFC XXXX 243 (https://www.rfc-editor.org/info/rfcXXXX); see the RFC 244 itself for full legal notices. 246 The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 247 'SHALL NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 248 'NOT RECOMMENDED', 'MAY', and 'OPTIONAL' in this document 249 are to be interpreted as described in BCP 14 (RFC 2119) 250 (RFC 8174) when, and only when, they appear in all 251 capitals, as shown here."; 253 revision 2021-05-17 { 254 description 255 "Initial revision."; 256 reference 257 "I-D.ietf-bier-te-arch: Traffic Engineering for Bit Index 258 Explicit Replication (BIER-TE)"; 259 } 261 /* 262 * Features 263 */ 264 feature bier-te-frr { 265 description 266 "Support Fast Re-route feature in BIER TE."; 267 reference 268 "I-D.eckert-bier-te-frr: Protection Methods for BIER-TE"; 269 } 271 /* 272 * Identities 273 */ 275 identity bier-te { 276 base rt:control-plane-protocol; 277 description 278 "Identity for the Traffic Engineering for Bit Index Explicit 279 Replication (BIER-TE)."; 280 reference 281 "I-D.ietf-bier-te-arch: Traffic Engineering for Bit Index 282 Explicit Replication (BIER-TE)"; 283 } 285 typedef encapsulation-type { 286 type enumeration { 287 enum MPLS { 288 description 289 "The forwarding encapsulation is MPLS 290 described in RFC8296 section 2.1."; 291 } 292 enum Ethernet { 293 description 294 "The forwarding encapsulation is Ethernet, 295 which is belonging to non-mpls part 296 described in RFC8296 section 2.2."; 297 } 298 enum IPv6 { 299 description 300 "The forwarding encapsulation is IPv6, 301 which is belonging to non-mpls part 302 described in RFC8296 section 2.2."; 303 } 304 } 305 description 306 "The encapsulation type of the BIER-TE packet. 307 If this type is not set, MPLS is the default type."; 308 } // encapsulation-type 310 grouping bit-string { 311 description 312 "The bit string which each bit represents an adjacency. 313 It is encapsulated in BIER header."; 314 reference 315 "I-D.ietf-bier-te-arch: Traffic Engineering for Bit Index 316 Explicit Replication (BIER-TE), section 3.3. 317 RFC8279: Multicast Using Bit Index Explicit Replication 318 (BIER). 319 RFC8296: Encapsulation for Bit Index Explicit Replication 320 (BIER) in MPLS and Non-MPLS Networks."; 322 list bit-string { 323 key "index"; 324 description 325 "As the definition in RFC 8279, the bit-string lengths are 326 64, 128, 256, 512, 1024, 2048, 4096 bits. The according 327 encapsulation is defined in RFC8296. BIER-TE uses the 328 similar function for bit string."; 330 leaf index { 331 type uint8 { 332 range "2..128"; 333 } 334 description 335 "The index of bit-mask. The minimum index value is 64 and 336 the corresponding bit string length is 64 bits. The 337 maximum index value is 128 and the corresponding 338 bit-string length is 4096 bits."; 339 } 340 leaf bitmask { 341 type uint32; 342 description "The bit-string in 4-octet units."; 343 } 344 } 345 } // bit-string 347 grouping adj-type { 348 description "The collection of all possible adjacency type."; 350 leaf adj-type { 351 type enumeration { 352 enum p2p { 353 description "Describes p2p adjacency."; 354 } 355 enum bfer { 356 description "Describes bfer adjacency."; 357 } 358 enum leaf-bfer { 359 description 360 "Describes leaf-bfer adjacency. There is no next BFR that 361 the packet should be forwarded."; 362 } 363 enum lan { 364 description "Describes lan adjacency."; 365 } 366 enum spoke { 367 description "Describes spoke adjacency of hub-and-spoke."; 368 } 369 enum ring-clockwise { 370 description "Describes clockwise adjacency in ring."; 371 } 372 enum ring-counterclockwise { 373 description "Describes counterclockwise adjacency in ring."; 374 } 375 enum ecmp { 376 description 377 "Describes ecmp adjacency. When the type is set to ecmp, 378 the corresponding ecmp entry should be used to balance 379 the load."; 380 } 381 enum virtual-link { 382 description 383 "Describes virtual adjacency between two indirect connect 384 nodes."; 385 } 386 enum other { 387 description "Describes other id type of adjacency."; 388 } 389 } 390 description "The collection of all possible adjacency type."; 391 } 392 } // adj-type 394 grouping te-items { 395 description "The BIER TE forwarding items collection."; 397 list fwd-next-hop { 398 key "next-hop"; 399 description 400 "The next hop information for forwarding. 401 If ECMP function defined in section 3.2.3 is used, 402 multiple next hops may be existed. 403 If ECMP function is not enabled, 404 the next hop may be one only."; 406 leaf next-hop { 407 type inet:ip-address; 408 mandatory true; 409 description "Next hop address."; 410 } 411 leaf dnr-flag { 412 type boolean; 413 description 414 "When the flag is set to 1, the BP of adjacency should not 415 be reset when packet copies are created. The flag makes 416 sense only when the forwarding type is 'connected'."; 417 } 418 container fwd-type { 419 description 420 "The collection of all possible forwarding types."; 421 choice fwd-type { 422 mandatory true; 423 case connected { 424 description 425 "The forwarding type is connected. Mostly connected 426 interfaces."; 427 } 428 case routed { 429 description 430 "The forwarding type is routed. Mostly not connected 431 interfaces."; 432 } 433 case local-decap { 434 description 435 "Means that the packet should be decapsulated and 436 forward out of BIER domain."; 437 } 438 case other { 439 description 440 "Means that the packet should be discarded."; 441 } 442 description 443 "The collection of all possible forwarding types."; 444 } 445 } // fwd-type 447 container te-out-bift-id { 448 description 449 "The bift-id information corresponding to a specific 450 outbound interface."; 452 list te-out-bift-id { 453 key "encap-type"; 454 leaf encap-type { 455 type encapsulation-type; 456 description 457 "The encapsulation type of BIER-TE packet."; 458 } 459 leaf value { 460 type rt-types:mpls-label; 461 mandatory true; 462 description 463 "The bift-id value of the forwarding item. 464 It can be a mpls label or an index for ethernet 465 or IPv6 encapsulation, which is used to represent 466 specific combination of [SD, BSL, SI]. 467 The ethernet or IPv6 index value is the same range 468 (20bits) as mpls label. 469 This value MUST not be set to 0."; 470 } 471 description 472 "The bift-id value and the encapsulation type 473 for the BIER-TE packet."; 474 } 475 } 477 list out-if-list { 478 key "fwd-intf"; 479 description 480 "The outbound interface information for forwarding."; 482 leaf fwd-intf { 483 type if:interface-ref; 484 mandatory true; 485 description 486 "The out interface of this forwarding item."; 487 } 488 } 489 } // next-hop 490 } // te-items 492 /* 493 * data nodes 494 */ 495 augment "/rt:routing/rt:control-plane-protocols/" 496 +"rt:control-plane-protocol" { 497 description "The BIER TE information."; 498 container bier-te { 499 description "The BIER TE information container."; 501 container te-adj { 502 description "The BIER TE adjacency information."; 503 list adj-if { 504 key "name"; 505 description "List of BIER-TE interfaces."; 506 leaf name { 507 type if:interface-ref; 508 description "Interface name reference."; 509 } 510 list subdomain { 511 key "subdomain-id"; 512 description 513 "The sub-domain which the interface belongs to. 514 One interface can belong to many subdomains."; 516 leaf subdomain-id { 517 type uint16; 518 description "The sub-domain-id of this sub-domain."; 519 reference 520 "RFC 8279: Multicast Using Bit Index Explicit 521 Replication (BIER)"; 522 } 523 list si { 524 key "si"; 525 description "The set identifier value."; 527 leaf si{ 528 type uint16; 529 mandatory true; 530 description 531 "The set identifier of this forwarding item."; 532 } 533 leaf-list adj-id { 534 type uint16; 535 description "The ID of an adjacency."; 536 } 537 } 538 } 539 uses adj-type; 540 } 541 } // te-adj 543 container te-fwd { 544 description "The BIER TE forwarding information."; 546 list subdomain { 547 key "subdomain-id"; 548 description 549 "The sub-domain which the interface belongs to. 550 One interface can belong to many subdomains."; 552 leaf subdomain-id { 553 type uint16; 554 description "The sub-domain-id of this sub-domain."; 555 reference 556 "RFC 8279: Multicast Using Bit Index Explicit 557 Replication (BIER)"; 558 } 559 list bsl { 560 key "fwd-bsl"; 561 description "The forwarding items in one BSL."; 562 leaf fwd-bsl { 563 type uint16; 564 description "The value of bitstringlength."; 565 } 566 list si { 567 key "si"; 568 description 569 "The forwarding items in one combination of SD, 570 BSL and SI."; 571 leaf si{ 572 type uint16; 573 mandatory true; 574 description 575 "The set identifier of this forwarding item."; 576 } 577 container te-bift-id { 579 description 580 "The bift-id which is used to locate the specific 581 forwarding item."; 582 leaf encap-type { 583 type encapsulation-type; 584 description 585 "The encapsulation type for BIER-TE packet."; 586 } 588 leaf value { 589 type rt-types:mpls-label; 590 mandatory true; 591 description 592 "The bift-id value of the forwarding item. 593 It can be a mpls label or an index for 594 ethernet or IPv6 encapsulation, 595 which is used to represent specific combination 596 of [SD, BSL, SI]. 597 The ethernet or IPv6 index value is the same 598 range (20bits) as mpls label."; 599 } 600 } 602 list fwd-items { 603 key "te-bp"; 604 description 605 "The forwarding information of one BIER TE item."; 606 leaf te-bp { 607 type uint16; 608 mandatory true; 609 description 610 "The bit index of a BIER TE forwarding item."; 611 } 612 uses te-items; 614 container te-frr { 615 if-feature bier-te-frr; 616 leaf frr-index { 617 type leafref { 618 path "../../../../../" + 619 "te-frr-items/btaft/frr-index"; 620 } 621 description "The index of this frr path."; 622 } 623 container resetbitmask { 624 description 625 "The deleting bitmask of the forwarding item."; 626 uses bit-string; 628 } 629 description 630 "If this link is protected, frr items can be 631 used to forward flows when this link is down."; 632 } // te-frr 633 } // fwd-items 634 } // si 635 } // bsl 637 container te-frr-items { 638 if-feature bier-te-frr; 639 description "The TE fast re-route information."; 640 list btaft { 641 key "frr-index"; 642 description 643 "The index of the frr paths. This item can be used 644 for multiple links protection in different SI."; 645 leaf frr-index { 646 type uint16; 647 mandatory true; 648 description "The frr item index."; 649 } 650 leaf frr-si{ 651 type uint16; 652 mandatory true; 653 description 654 "The set identifier of this forwarding item."; 655 } 656 leaf frr-bsl { 657 type uint16; 658 mandatory true; 659 description "The value of bitstringlength."; 660 } 661 container addbitmask { 662 description 663 "The adding bitmask of the forwarding item. 664 This item should be merged into the packet's 665 bit-string."; 666 uses bit-string; 667 } 668 } // btaft 669 } // te-frr-items 670 } // subdomain 671 } // te-fwd 672 } // bier-te 673 } 675 /* 676 * Notifications 677 */ 678 notification bier-te-notification { 679 description 680 "The notification is sent when a condition changes."; 681 list bp-is-zero { 682 key "if-index"; 683 description "The adjacency id is zero. It is invalid."; 684 leaf if-index { 685 type if:interface-ref; 686 description "The adjacency id is zero."; 687 } 688 uses adj-type; 689 } 690 } 691 } 692 694 7. IANA Considerations 696 The IANA is requested to assign two new URIs from the IETF XML 697 registry ([RFC3688]). Authors are suggesting the following URI: 699 URI: urn:ietf:params:xml:ns:yang:ietf-bier-te 701 Registrant Contact: BIER WG 703 XML: N/A, the requested URI is an XML namespace 705 This document also requests one new YANG module name in the YANG 706 Module Names registry ([RFC6020]) with the following suggestion: 708 name: ietf-bier-te 710 namespace: urn:ietf:params:xml:ns:yang:ietf-bier-te 712 prefix: bier-te 714 reference: RFC XXXX 716 8. Acknowledgement 718 The authors would like to thank Min Gu (gumin20181129@163.com) for 719 her testing, verification and valuable suggestion. And the authors 720 would like to thank Benjamin R and Benchong Xu for their valuable 721 comments. 723 9. Normative References 725 [I-D.eckert-bier-te-frr] 726 Eckert, T., Cauchie, G., Braun, W., and M. Menth, 727 "Protection Methods for BIER-TE", draft-eckert-bier-te- 728 frr-03 (work in progress), March 2018. 730 [I-D.ietf-bier-bier-yang] 731 Chen, R., Hu, F., Zhang, Z., Dai, X., and M. Sivakumar, 732 "YANG Data Model for BIER Protocol", draft-ietf-bier-bier- 733 yang-07 (work in progress), September 2020. 735 [I-D.ietf-bier-te-arch] 736 Eckert, T., Cauchie, G., and M. Menth, "Tree Engineering 737 for Bit Index Explicit Replication (BIER-TE)", draft-ietf- 738 bier-te-arch-09 (work in progress), October 2020. 740 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 741 DOI 10.17487/RFC3688, January 2004, 742 . 744 [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for 745 the Network Configuration Protocol (NETCONF)", RFC 6020, 746 DOI 10.17487/RFC6020, October 2010, 747 . 749 [RFC6087] Bierman, A., "Guidelines for Authors and Reviewers of YANG 750 Data Model Documents", RFC 6087, DOI 10.17487/RFC6087, 751 January 2011, . 753 [RFC7223] Bjorklund, M., "A YANG Data Model for Interface 754 Management", RFC 7223, DOI 10.17487/RFC7223, May 2014, 755 . 757 [RFC8279] Wijnands, IJ., Ed., Rosen, E., Ed., Dolganow, A., 758 Przygienda, T., and S. Aldrin, "Multicast Using Bit Index 759 Explicit Replication (BIER)", RFC 8279, 760 DOI 10.17487/RFC8279, November 2017, 761 . 763 [RFC8296] Wijnands, IJ., Ed., Rosen, E., Ed., Dolganow, A., 764 Tantsura, J., Aldrin, S., and I. Meilik, "Encapsulation 765 for Bit Index Explicit Replication (BIER) in MPLS and Non- 766 MPLS Networks", RFC 8296, DOI 10.17487/RFC8296, January 767 2018, . 769 [RFC8349] Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for 770 Routing Management (NMDA Version)", RFC 8349, 771 DOI 10.17487/RFC8349, March 2018, 772 . 774 Authors' Addresses 776 Zheng(Sandy) Zhang 777 ZTE Corporation 778 Nanjing 779 China 781 Email: zhang.zheng@zte.com.cn 783 Cui(Linda) Wang 784 Individual 786 Email: lindawangjoy@gmail.com 788 Ran Chen 789 ZTE Corporation 790 Nanjing 791 China 793 Email: chen.ran@zte.com.cn 795 Fangwei Hu 796 Individual 797 Shanghai 798 China 800 Email: hufwei@gmail.com 802 Mahesh Sivakumar 803 Juniper networks 804 1133 Innovation Way 805 Sunnyvale, CALIFORNIA 94089 806 United States 808 Email: sivakumar.mahesh@gmail.com 809 Huanan Chen 810 Individual 811 China 813 Email: chenhuanan@189.cn