idnits 2.17.00 (12 Aug 2021) /tmp/idnits49783/draft-ietf-bier-te-yang-05.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 : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 103 has weird spacing: '...main-id uin...' == Line 110 has weird spacing: '...main-id uin...' == Line 112 has weird spacing: '...fwd-bsl uin...' == Line 131 has weird spacing: '...ap-type enc...' == Line 135 has weird spacing: '...wd-intf if:...' == (1 more instance...) -- The document date (1 May 2022) is 13 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 782, but no explicit reference was found in the text == Unused Reference: 'RFC8296' is defined on line 788, but no explicit reference was found in the text == Unused Reference: 'RFC8343' is defined on line 794, but no explicit reference was found in the text == Unused Reference: 'RFC8349' is defined on line 798, but no explicit reference was found in the text == Unused Reference: 'RFC8407' is defined on line 803, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-bier-bier-yang' is defined on line 821, but no explicit reference was found in the text Summary: 0 errors (**), 0 flaws (~~), 12 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: 2 November 2022 Individual 6 R. Chen 7 ZTE Corporation 8 F. Hu 9 Individual 10 M. Sivakumar 11 Juniper networks 12 H. Chen 13 China Telecom 14 1 May 2022 16 A YANG data model for Tree Engineering for Bit Index Explicit 17 Replication (BIER-TE) 18 draft-ietf-bier-te-yang-05 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 2 November 2022. 42 Copyright Notice 44 Copyright (c) 2022 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 Revised BSD License text as 53 described in Section 4.e of the Trust Legal Provisions and are 54 provided without warranty as described in the Revised 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. Security Considerations . . . . . . . . . . . . . . . . . . . 15 66 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16 67 10. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 16 68 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 16 69 11.1. Normative References . . . . . . . . . . . . . . . . . . 16 70 11.2. Informative References . . . . . . . . . . . . . . . . . 18 71 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18 73 1. Introduction 75 [I-D.ietf-bier-te-arch] introduces an architecture for BIER-TE: Tree 76 Engineering for Bit Index Explicit Replication (BIER). This document 77 defines a YANG data model for BIER TE. The content is in keeping 78 with the TE architecture draft. In addition, this YANG data model 79 contains BIER TE frr items of [I-D.eckert-bier-te-frr]. 81 2. Conventions Used in This Document 83 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 84 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 85 "OPTIONAL" in this document are to be interpreted as described in BCP 86 14 [RFC2119] [RFC8174] when, and only when, they appear in all 87 capitals, as shown here. 89 3. Design of the Data Model 91 The BIER TE YANG model includes BIER TE adjancency configuration and 92 forwarding items configuration. Some features can also be used to 93 enhance BIER TE function, like ECMP and FRR. 95 module: ietf-bier-te 96 augment /rt:routing/rt:control-plane-protocols 97 /rt:control-plane-protocol: 98 +--rw bier-te 99 +--rw te-adj 100 | +--rw adj-if* [name] 101 | +--rw name if:interface-ref 102 | +--rw subdomain* [subdomain-id] 103 | | +--rw subdomain-id uint16 104 | | +--rw si* [si] 105 | | +--rw si uint16 106 | | +--rw adj-id* uint16 107 | +--rw adj-type? enumeration 108 +--rw te-fwd 109 +--rw subdomain* [subdomain-id] 110 +--rw subdomain-id uint16 111 +--rw bsl* [fwd-bsl] 112 | +--rw fwd-bsl uint16 113 | +--rw si* [si] 114 | +--rw si uint16 115 | +--rw te-bift-id 116 | | +--rw encap-type? encapsulation-type 117 | | +--rw value rt-types:mpls-label 118 | +--rw fwd-items* [te-bp] 119 | +--rw te-bp uint16 120 | +--rw fwd-next-hop* [next-hop] 121 | | +--rw next-hop inet:ip-address 122 | | +--rw dnr-flag? boolean 123 | | +--rw fwd-type 124 | | | +--rw (fwd-type) 125 | | | +--:(connected) 126 | | | +--:(routed) 127 | | | +--:(local-decap) 128 | | | +--:(other) 129 | | +--rw te-out-bift-id 130 | | | +--rw te-out-bift-id* [encap-type] 131 | | | +--rw encap-type encapsulation-type 132 | | | +--rw value 133 | | | rt-types:mpls-label 134 | | +--rw out-if-list* [fwd-intf] 135 | | +--rw fwd-intf if:interface-ref 136 | +--rw te-frr {bier-te-frr}? 137 | +--rw frr-index? leafref 138 | +--rw resetbitmask 139 | +--rw bit-string* [index] 140 | +--rw index uint8 141 | +--rw bitmask? uint32 142 +--rw te-frr-items {bier-te-frr}? 143 +--rw btaft* [frr-index] 144 +--rw frr-index uint16 145 +--rw frr-si uint16 146 +--rw frr-bsl uint16 147 +--rw addbitmask 148 +--rw bit-string* [index] 149 +--rw index uint8 150 +--rw bitmask? uint32 152 notifications: 153 +---n bier-te-notification 154 +--ro bp-is-zero* [if-index] 155 +--ro if-index if:interface-ref 156 +--ro adj-type? enumeration 158 4. BIER-TE configuration 160 The BIER-TE forwarding item is indexed by the combination of sub- 161 domain-id, BitStringLength and set identifier. 163 One interface can be used in different sub-domain, so the BIER TE 164 adjacency information is managed by BIER TE function other than by 165 interface itself. 167 Because the BIER-TE is controlled by controller now, the information 168 about IGP is not defined. If in the future the IGP is used to carry 169 the information about BIER-TE, the IGP extension will be added in 170 this document. 172 5. Notifications 174 If the adjacency id of one adjacency is set to zero, the value is 175 invalid. The notification should be sent to controller and network 176 manager. 178 6. RPCs 180 TBD. 182 7. BIER TE YANG model 184 file "ietf-bier-te@2021-11-08.yang" 185 module ietf-bier-te { 187 yang-version 1.1; 189 namespace "urn:ietf:params:xml:ns:yang:ietf-bier-te"; 190 prefix bier-te; 192 import ietf-inet-types { 193 prefix "inet"; 194 reference 195 "RFC 6991: Common YANG Data Types"; 196 } 198 import ietf-routing { 199 prefix "rt"; 200 reference 201 "RFC 8349: A YANG Data Model for Routing Management 202 (NMDA Version)"; 203 } 205 import ietf-interfaces { 206 prefix "if"; 207 reference 208 "RFC 8343: A YANG Data Model for Interface Management"; 209 } 211 import ietf-routing-types { 212 prefix "rt-types"; 213 reference 214 "RFC 8294: Common YANG Data Types for the Routing Area"; 215 } 217 organization " IETF BIER (Bit Indexed Explicit Replication) 218 Working Group"; 219 contact 220 "WG Web: 221 WG List: 223 Editor: Zheng Zhang 224 225 Editor: Cui Wang 226 227 Editor: Ran Chen 228 229 Editor: Fangwei Hu 230 231 Editor: Mahesh Sivakumar 232 233 Editor: Huanan Chen 234 235 "; 237 description 238 "The module defines the YANG definitions for Traffic 239 Engineering for Bit Index Explicit Replication (BIER-TE). 241 Copyright (c) 2020 IETF Trust and the persons identified as 242 authors of the code. All rights reserved. 244 Redistribution and use in source and binary forms, with or 245 without modification, is permitted pursuant to, and subject 246 to the license terms contained in, the Simplified BSD 247 License set forth in Section 4.c of the IETF Trust's Legal 248 Provisions Relating to IETF Documents 249 (https://trustee.ietf.org/license-info). 251 This version of this YANG module is part of RFC XXXX 252 (https://www.rfc-editor.org/info/rfcXXXX); see the RFC 253 itself for full legal notices. 255 The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 256 'SHALL NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 257 'NOT RECOMMENDED', 'MAY', and 'OPTIONAL' in this document 258 are to be interpreted as described in BCP 14 (RFC 2119) 259 (RFC 8174) when, and only when, they appear in all 260 capitals, as shown here."; 262 revision 2021-11-08 { 263 description 264 "Initial revision."; 265 reference 266 "I-D.ietf-bier-te-arch: Tree Engineering for Bit Index 267 Explicit Replication (BIER-TE)"; 268 } 270 /* 271 * Features 272 */ 273 feature bier-te-frr { 274 description 275 "Support Fast Re-route feature in BIER TE."; 276 reference 277 "I-D.eckert-bier-te-frr: Protection Methods for BIER-TE"; 278 } 280 /* 281 * Identities 282 */ 284 identity bier-te { 285 base rt:control-plane-protocol; 286 description 287 "Identity for the Tree Engineering for Bit Index Explicit 288 Replication (BIER-TE)."; 289 reference 290 "I-D.ietf-bier-te-arch: Tree Engineering for Bit Index 291 Explicit Replication (BIER-TE)"; 292 } 294 typedef encapsulation-type { 295 type enumeration { 296 enum MPLS { 297 description 298 "The forwarding encapsulation is MPLS 299 described in RFC8296 section 2.1."; 300 } 301 enum Ethernet { 302 description 303 "The forwarding encapsulation is Ethernet, 304 which is belonging to non-mpls part 305 described in RFC8296 section 2.2."; 306 } 307 enum IPv6 { 308 description 309 "The forwarding encapsulation is IPv6, 310 which is belonging to non-mpls part 311 described in RFC8296 section 2.2."; 312 } 313 } 314 description 315 "The encapsulation type of the BIER-TE packet. 316 If this type is not set, MPLS is the default type."; 317 } // encapsulation-type 319 grouping bit-string { 320 description 321 "The bit string which each bit represents an adjacency. 322 It is encapsulated in BIER header."; 323 reference 324 "I-D.ietf-bier-te-arch: Tree Engineering for Bit Index 325 Explicit Replication (BIER-TE), section 3.3. 326 RFC8279: Multicast Using Bit Index Explicit Replication 327 (BIER). 328 RFC8296: Encapsulation for Bit Index Explicit Replication 329 (BIER) in MPLS and Non-MPLS Networks."; 331 list bit-string { 332 key "index"; 333 description 334 "As the definition in RFC 8279, the bit-string lengths are 335 64, 128, 256, 512, 1024, 2048, 4096 bits. The according 336 encapsulation is defined in RFC8296. BIER-TE uses the 337 similar function for bit string."; 339 leaf index { 340 type uint8 { 341 range "2..128"; 342 } 343 description 344 "The index of bit-mask. The minimum index value is 64 and 345 the corresponding bit string length is 64 bits. The 346 maximum index value is 128 and the corresponding 347 bit-string length is 4096 bits."; 348 } 349 leaf bitmask { 350 type uint32; 351 description "The bit-string in 4-octet units."; 352 } 353 } 354 } // bit-string 356 grouping adj-type { 357 description "The collection of all possible adjacency type."; 359 leaf adj-type { 360 type enumeration { 361 enum p2p { 362 description "Describes p2p adjacency."; 363 } 364 enum bfer { 365 description "Describes bfer adjacency."; 366 } 367 enum leaf-bfer { 368 description 369 "Describes leaf-bfer adjacency. There is no next BFR that 370 the packet should be forwarded."; 371 } 372 enum lan { 373 description "Describes lan adjacency."; 374 } 375 enum spoke { 376 description "Describes spoke adjacency of hub-and-spoke."; 377 } 378 enum ring-clockwise { 379 description "Describes clockwise adjacency in ring."; 380 } 381 enum ring-counterclockwise { 382 description 383 "Describes counterclockwise adjacency in ring."; 384 } 385 enum ecmp { 386 description 387 "Describes ecmp adjacency. When the type is set to ecmp, 388 the corresponding ecmp entry should be used to balance 389 the load."; 390 } 391 enum virtual-link { 392 description 393 "Describes virtual adjacency between two indirect connect 394 nodes."; 395 } 396 enum other { 397 description "Describes other id type of adjacency."; 398 } 399 } 400 description "The collection of all possible adjacency type."; 401 } 402 } // adj-type 404 grouping te-items { 405 description "The BIER TE forwarding items collection."; 407 list fwd-next-hop { 408 key "next-hop"; 409 description 410 "The next hop information for forwarding. 411 If ECMP function defined in section 3.2.3 is used, 412 multiple next hops may be existed. 413 If ECMP function is not enabled, 414 the next hop may be one only."; 416 leaf next-hop { 417 type inet:ip-address; 418 mandatory true; 419 description "Next hop address."; 420 } 421 leaf dnr-flag { 422 type boolean; 423 description 424 "When the flag is set to 1, the BP of adjacency should not 425 be reset when packet copies are created. The flag makes 426 sense only when the forwarding type is 'connected'."; 427 } 428 container fwd-type { 429 description 430 "The collection of all possible forwarding types."; 431 choice fwd-type { 432 mandatory true; 433 case connected { 434 description 435 "The forwarding type is connected. Mostly connected 436 interfaces."; 437 } 438 case routed { 439 description 440 "The forwarding type is routed. Mostly not connected 441 interfaces."; 442 } 443 case local-decap { 444 description 445 "Means that the packet should be decapsulated and 446 forward out of BIER domain."; 447 } 448 case other { 449 description 450 "Means that the packet should be discarded."; 451 } 452 description 453 "The collection of all possible forwarding types."; 454 } 455 } // fwd-type 457 container te-out-bift-id { 458 description 459 "The bift-id information corresponding to a specific 460 outbound interface."; 462 list te-out-bift-id { 463 key "encap-type"; 464 leaf encap-type { 465 type encapsulation-type; 466 description 467 "The encapsulation type of BIER-TE packet."; 468 } 469 leaf value { 470 type rt-types:mpls-label; 471 mandatory true; 472 description 473 "The bift-id value of the forwarding item. 474 It can be a mpls label or an index for ethernet 475 or IPv6 encapsulation, which is used to represent 476 specific combination of [SD, BSL, SI]. 477 The ethernet or IPv6 index value is the same range 478 (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."; 575 } 576 list si { 577 key "si"; 578 description 579 "The forwarding items in one combination of SD, 580 BSL and SI."; 581 leaf si{ 582 type uint16; 583 mandatory true; 584 description 585 "The set identifier of this forwarding item."; 586 } 587 container te-bift-id { 588 description 589 "The bift-id which is used to locate the specific 590 forwarding item."; 591 leaf encap-type { 592 type encapsulation-type; 593 description 594 "The encapsulation type for BIER-TE packet."; 595 } 597 leaf value { 598 type rt-types:mpls-label; 599 mandatory true; 600 description 601 "The bift-id value of the forwarding item. 602 It can be a mpls label or an index for 603 ethernet or IPv6 encapsulation, 604 which is used to represent specific 605 combination of [SD, BSL, SI]. 606 The ethernet or IPv6 index value is the same 607 range (20bits) as mpls label."; 608 } 609 } 611 list fwd-items { 612 key "te-bp"; 613 description 614 "The forwarding information of one BIER TE 615 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; 624 container te-frr { 625 if-feature bier-te-frr; 626 leaf frr-index { 627 type leafref { 628 path "../../../../../" + 629 "te-frr-items/btaft/frr-index"; 630 } 631 description "The index of this frr path."; 632 } 633 container resetbitmask { 634 description 635 "The deleting bitmask of the forwarding 636 item."; 637 uses bit-string; 638 } 639 description 640 "If this link is protected, frr items can be 641 used to forward flows when this link is 642 down."; 643 } // te-frr 644 } // fwd-items 645 } // si 646 } // bsl 648 container te-frr-items { 649 if-feature bier-te-frr; 650 description "The TE fast re-route information."; 651 list btaft { 652 key "frr-index"; 653 description 654 "The index of the frr paths. This item can be used 655 for multiple links protection in different SI."; 656 leaf frr-index { 657 type uint16; 658 mandatory true; 659 description "The frr item index."; 660 } 661 leaf frr-si{ 662 type uint16; 663 mandatory true; 664 description 665 "The set identifier of this forwarding item."; 666 } 667 leaf frr-bsl { 668 type uint16; 669 mandatory true; 670 description "The value of bitstringlength."; 671 } 672 container addbitmask { 673 description 674 "The adding bitmask of the forwarding item. 675 This item should be merged into the packet's 676 bit-string."; 677 uses bit-string; 678 } 679 } // btaft 680 } // te-frr-items 681 } // subdomain 682 } // te-fwd 683 } // bier-te 684 } 686 /* 687 * Notifications 688 */ 689 notification bier-te-notification { 690 description 691 "The notification is sent when a condition changes."; 692 list bp-is-zero { 693 key "if-index"; 694 description "The adjacency id is zero. It is invalid."; 695 leaf if-index { 696 type if:interface-ref; 697 description "The adjacency id is zero."; 698 } 699 uses adj-type; 700 } 701 } 702 } 703 705 8. Security Considerations 707 The YANG module specified in this document defines a schema for data 708 that is designed to be accessed via network management protocols such 709 as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer 710 is the secure transport layer, and the mandatory-to-implement secure 711 transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer 712 is HTTPS, and the mandatory-to-implement secure transport is TLS 713 [RFC8446]. 715 9. IANA Considerations 717 The IANA is requested to assign two new URIs from the IETF XML 718 registry ([RFC3688]). Authors are suggesting the following URI: 720 URI: urn:ietf:params:xml:ns:yang:ietf-bier-te 722 Registrant Contact: BIER WG 724 XML: N/A, the requested URI is an XML namespace 726 This document also requests one new YANG module name in the YANG 727 Module Names registry ([RFC6020]) with the following suggestion: 729 name: ietf-bier-te 731 namespace: urn:ietf:params:xml:ns:yang:ietf-bier-te 733 prefix: bier-te 735 reference: RFC XXXX 737 10. Acknowledgement 739 The authors would like to thank Min Gu (gumin20181129@163.com) for 740 her testing, verification and valuable suggestion. And the authors 741 would like to thank Benjamin R and Benchong Xu for their valuable 742 comments. 744 11. References 746 11.1. Normative References 748 [I-D.ietf-bier-te-arch] 749 Eckert, T., Menth, M., and G. Cauchie, "Tree Engineering 750 for Bit Index Explicit Replication (BIER-TE)", Work in 751 Progress, Internet-Draft, draft-ietf-bier-te-arch-13, 25 752 April 2022, . 755 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 756 Requirement Levels", BCP 14, RFC 2119, 757 DOI 10.17487/RFC2119, March 1997, 758 . 760 [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for 761 the Network Configuration Protocol (NETCONF)", RFC 6020, 762 DOI 10.17487/RFC6020, October 2010, 763 . 765 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 766 and A. Bierman, Ed., "Network Configuration Protocol 767 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 768 . 770 [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure 771 Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, 772 . 774 [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF 775 Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, 776 . 778 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 779 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 780 May 2017, . 782 [RFC8279] Wijnands, IJ., Ed., Rosen, E., Ed., Dolganow, A., 783 Przygienda, T., and S. Aldrin, "Multicast Using Bit Index 784 Explicit Replication (BIER)", RFC 8279, 785 DOI 10.17487/RFC8279, November 2017, 786 . 788 [RFC8296] Wijnands, IJ., Ed., Rosen, E., Ed., Dolganow, A., 789 Tantsura, J., Aldrin, S., and I. Meilik, "Encapsulation 790 for Bit Index Explicit Replication (BIER) in MPLS and Non- 791 MPLS Networks", RFC 8296, DOI 10.17487/RFC8296, January 792 2018, . 794 [RFC8343] Bjorklund, M., "A YANG Data Model for Interface 795 Management", RFC 8343, DOI 10.17487/RFC8343, March 2018, 796 . 798 [RFC8349] Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for 799 Routing Management (NMDA Version)", RFC 8349, 800 DOI 10.17487/RFC8349, March 2018, 801 . 803 [RFC8407] Bierman, A., "Guidelines for Authors and Reviewers of 804 Documents Containing YANG Data Models", BCP 216, RFC 8407, 805 DOI 10.17487/RFC8407, October 2018, 806 . 808 [RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol 809 Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018, 810 . 812 11.2. Informative References 814 [I-D.eckert-bier-te-frr] 815 Eckert, T., Cauchie, G., Braun, W., and M. Menth, 816 "Protection Methods for BIER-TE", Work in Progress, 817 Internet-Draft, draft-eckert-bier-te-frr-03, 5 March 2018, 818 . 821 [I-D.ietf-bier-bier-yang] 822 Chen, R., Hu, F., Zhang, Z., Dai, X., and M. Sivakumar, 823 "YANG Data Model for BIER Protocol", Work in Progress, 824 Internet-Draft, draft-ietf-bier-bier-yang-07, 8 September 825 2020, . 828 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 829 DOI 10.17487/RFC3688, January 2004, 830 . 832 Authors' Addresses 834 Zheng(Sandy) Zhang 835 ZTE Corporation 836 Nanjing 837 China 838 Email: zhang.zheng@zte.com.cn 840 Cui(Linda) Wang 841 Individual 842 Email: lindawangjoy@gmail.com 844 Ran Chen 845 ZTE Corporation 846 Nanjing 847 China 848 Email: chen.ran@zte.com.cn 849 Fangwei Hu 850 Individual 851 Shanghai 852 China 853 Email: hufwei@gmail.com 855 Mahesh Sivakumar 856 Juniper networks 857 1133 Innovation Way 858 Sunnyvale, CALIFORNIA 94089 , 859 United States 860 Email: sivakumar.mahesh@gmail.com 862 Huanan Chen 863 China Telecom 864 China 865 Email: chenhuanan@189.cn