idnits 2.17.1 draft-ietf-bier-te-yang-01.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 is 1 instance 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 90 has weird spacing: '...main-id uin...' == Line 97 has weird spacing: '...main-id uin...' == Line 99 has weird spacing: '...fwd-bsl uin...' == Line 104 has weird spacing: '...w value rt-...' == Line 120 has weird spacing: '...w value rt-...' == (1 more instance...) -- The document date (February 6, 2020) is 1540 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 694, but no explicit reference was found in the text == Unused Reference: 'RFC6087' is defined on line 715, but no explicit reference was found in the text == Unused Reference: 'RFC7223' is defined on line 719, but no explicit reference was found in the text == Unused Reference: 'RFC8279' is defined on line 723, but no explicit reference was found in the text == Unused Reference: 'RFC8296' is defined on line 729, but no explicit reference was found in the text == Unused Reference: 'RFC8349' is defined on line 735, 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 (-08) exists of draft-ietf-bier-bier-yang-06 == Outdated reference: A later version (-13) exists of draft-ietf-bier-te-arch-05 ** 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 C. Wang 4 Intended status: Standards Track R. Chen 5 Expires: August 9, 2020 ZTE Corporation 6 F. Hu 7 Individual 8 M. Sivakumar 9 Juniper networks 10 H. Chen 11 China Telecom 12 February 6, 2020 14 A YANG data model for Traffic Engineering for Bit Index Explicit 15 Replication (BIER-TE) 16 draft-ietf-bier-te-yang-01 18 Abstract 20 This document defines a YANG data model for Traffic Engineering for 21 Bit Index Explicit Replication (BIER-TE) configuration and operation. 23 Status of This Memo 25 This Internet-Draft is submitted in full conformance with the 26 provisions of BCP 78 and BCP 79. 28 Internet-Drafts are working documents of the Internet Engineering 29 Task Force (IETF). Note that other groups may also distribute 30 working documents as Internet-Drafts. The list of current Internet- 31 Drafts is at https://datatracker.ietf.org/drafts/current/. 33 Internet-Drafts are draft documents valid for a maximum of six months 34 and may be updated, replaced, or obsoleted by other documents at any 35 time. It is inappropriate to use Internet-Drafts as reference 36 material or to cite them other than as "work in progress." 38 This Internet-Draft will expire on August 9, 2020. 40 Copyright Notice 42 Copyright (c) 2020 IETF Trust and the persons identified as the 43 document authors. All rights reserved. 45 This document is subject to BCP 78 and the IETF Trust's Legal 46 Provisions Relating to IETF Documents 47 (https://trustee.ietf.org/license-info) in effect on the date of 48 publication of this document. Please review these documents 49 carefully, as they describe your rights and restrictions with respect 50 to this document. Code Components extracted from this document must 51 include Simplified BSD License text as described in Section 4.e of 52 the Trust Legal Provisions and are provided without warranty as 53 described in the Simplified BSD License. 55 Table of Contents 57 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 58 2. Design of the Data Model . . . . . . . . . . . . . . . . . . 2 59 3. BIER-TE configuration . . . . . . . . . . . . . . . . . . . . 4 60 4. Notifications . . . . . . . . . . . . . . . . . . . . . . . . 4 61 5. RPCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 62 6. BIER TE YANG model . . . . . . . . . . . . . . . . . . . . . 4 63 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 64 8. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 15 65 9. Normative References . . . . . . . . . . . . . . . . . . . . 15 66 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16 68 1. Introduction 70 [I-D.ietf-bier-te-arch] introduces an architecture for BIER-TE: 71 Traffic Engineering for Bit Index Explicit Replication (BIER). This 72 document defines a YANG data model for BIER TE. The content is in 73 keeping with the TE architecture draft. In addition, this YANG data 74 model contains BIER TE frr items of [I-D.eckert-bier-te-frr]. 76 2. Design of the Data Model 78 The BIER TE YANG model includes BIER TE adjancency configuration and 79 forwarding items configuration. Some features can also be used to 80 enhance BIER TE function, like ECMP and FRR. 82 module: ietf-bier-te 83 augment /rt:routing/rt:control-plane-protocols 84 /rt:control-plane-protocol: 85 +--rw bier-te 86 +--rw te-adj 87 | +--rw adj-if* [name] 88 | +--rw name if:interface-ref 89 | +--rw subdomain* [subdomain-id] 90 | | +--rw subdomain-id uint16 91 | | +--rw si* [si] 92 | | +--rw si uint16 93 | | +--rw adj-id* uint16 94 | +--rw adj-type? enumeration 95 +--rw te-fwd 96 +--rw subdomain* [subdomain-id] 97 +--rw subdomain-id uint16 98 +--rw bsl* [fwd-bsl] 99 | +--rw fwd-bsl uint16 100 | +--rw si* [si] 101 | +--rw si uint16 102 | +--rw te-bift-id 103 | | +--rw type? enumeration 104 | | +--rw value rt-types:mpls-label 105 | +--rw fwd-items* [te-bp] 106 | +--rw te-bp uint16 107 | +--rw te-ecmp? boolean {bier-te-ecmp}? 108 | +--rw out-info 109 | | +--rw out-if-list* [fwd-intf] 110 | | +--rw fwd-intf if:interface-ref 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 type? enumeration 120 | | +--rw value rt-types:mpls-label 121 | +--rw te-frr {bier-te-frr}? 122 | +--rw frr-index? 123 -> ../../../../../te-frr-items/btaft/frr-index 124 | +--rw resetbitmask 125 | +--rw bit-string* [index] 126 | +--rw index uint8 127 | +--rw bitmask? uint32 128 +--rw te-frr-items {bier-te-frr}? 129 +--rw btaft* [frr-index] 130 +--rw frr-index uint16 131 +--rw frr-si uint16 132 +--rw frr-bsl uint16 133 +--rw addbitmask 134 +--rw bit-string* [index] 135 +--rw index uint8 136 +--rw bitmask? uint32 138 notifications: 139 +---n bier-te-notification 140 +--ro bp-is-zero* [if-index] 141 +--ro if-index if:interface-ref 142 +--ro adj-type? enumeration 144 3. BIER-TE configuration 146 The BIER-TE forwarding item is indexed by the combination of sub- 147 domain-id, BitStringLength and set identifier. 149 One interface can be used in different sub-domain, so the BIER TE 150 adjacency information is managed by BIER TE function other than by 151 interface itself. 153 Because the BIER-TE is controlled by controller now, the information 154 about IGP is not defined. If in the future the IGP is used to carry 155 the information about BIER-TE, the IGP extension will be added in 156 this document. 158 4. Notifications 160 If the adjacency id of one adjacency is set to zero, the value is 161 invalid. The notification should be sent to controller and network 162 manager. 164 5. RPCs 166 TBD. 168 6. BIER TE YANG model 170 file "ietf-bier-te@2020-02-05.yang" 171 module ietf-bier-te { 173 yang-version 1.1; 175 namespace "urn:ietf:params:xml:ns:yang:ietf-bier-te"; 177 prefix bier-te; 179 import ietf-routing { 180 prefix "rt"; 181 reference 182 "RFC 8349: A YANG Data Model for Routing Management 183 (NMDA Version)"; 184 } 186 import ietf-interfaces { 187 prefix "if"; 188 reference 189 "RFC 8343: A YANG Data Model for Interface Management"; 190 } 191 import ietf-routing-types { 192 prefix "rt-types"; 193 reference 194 "RFC 8294: Common YANG Data Types for the Routing Area"; 195 } 197 organization " IETF BIER (Bit Indexed Explicit Replication) 198 Working Group"; 199 contact 200 "WG Web: 201 WG List: 203 Editor: Zheng Zhang 204 205 Editor: Cui Wang 206 207 Editor: Ran Chen 208 209 Editor: Fangwei Hu 210 211 Editor: Mahesh Sivakumar 212 213 Editor: Huanan Chen 214 215 "; 217 description 218 "The module defines the YANG definitions for Traffic 219 Engineering for Bit Index Explicit Replication (BIER-TE). 221 Copyright (c) 2020 IETF Trust and the persons identified as 222 authors of the code. All rights reserved. 224 Redistribution and use in source and binary forms, with or 225 without modification, is permitted pursuant to, and subject 226 to the license terms contained in, the Simplified BSD 227 License set forth in Section 4.c of the IETF Trust's Legal 228 Provisions Relating to IETF Documents 229 (https://trustee.ietf.org/license-info). 231 This version of this YANG module is part of RFC XXXX 232 (https://www.rfc-editor.org/info/rfcXXXX); see the RFC 233 itself for full legal notices. 235 The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 236 'SHALL NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 237 'NOT RECOMMENDED', 'MAY', and 'OPTIONAL' in this document 238 are to be interpreted as described in BCP 14 (RFC 2119) 239 (RFC 8174) when, and only when, they appear in all 240 capitals, as shown here."; 242 revision 2020-02-05 { 243 description 244 "Initial revision."; 245 reference 246 "I-D.ietf-bier-te-arch: Traffic Engineering for Bit Index 247 Explicit Replication (BIER-TE)"; 248 } 250 /* 251 * Features 252 */ 253 feature bier-te-frr { 254 description 255 "Support Fast Re-route feature in BIER TE."; 256 reference 257 "I-D.eckert-bier-te-frr: Protection Methods for BIER-TE"; 258 } 259 feature bier-te-ecmp { 260 description 261 "Support ECMP feature in BIER TE."; 262 reference 263 "I-D.ietf-bier-te-arch: Traffic Engineering for Bit Index 264 Explicit Replication (BIER-TE), section 3.2.3"; 265 } 267 /* 268 * Identities 269 */ 271 identity bier-te { 272 base rt:control-plane-protocol; 273 description 274 "Identity for the Traffic Engineering for Bit Index Explicit 275 Replication (BIER-TE)."; 276 reference 277 "I-D.ietf-bier-te-arch: Traffic Engineering for Bit Index 278 Explicit Replication (BIER-TE)"; 279 } 281 grouping bit-string { 282 description 283 "The bit string which each bit represents an adjacency. 284 It is encapsulated in BIER header."; 285 reference 286 "I-D.ietf-bier-te-arch: Traffic Engineering for Bit Index 287 Explicit Replication (BIER-TE), section 3.3. 288 RFC8279: Multicast Using Bit Index Explicit Replication 289 (BIER). 290 RFC8296: Encapsulation for Bit Index Explicit Replication 291 (BIER) in MPLS and Non-MPLS Networks."; 293 list bit-string { 294 key "index"; 295 description 296 "As the definition in RFC 8279, the bit-string lengths are 297 64, 128, 256, 512, 1024, 2048, 4096 bits. The according 298 encapsulation is defined in RFC8296. BIER-TE uses the 299 similar function for bit string."; 301 leaf index { 302 type uint8 { 303 range "2..128"; 304 } 305 description 306 "The index of bit-mask. The minimum index value is 64 and 307 the corresponding bit string length is 64 bits. The 308 maximum index value is 128 and the corresponding 309 bit-string length is 4096 bits."; 310 } 311 leaf bitmask { 312 type uint32; 313 description "The bit-string in 4-octet units."; 314 } 315 } 316 } // bit-string 318 grouping adj-type { 319 description "The collection of all possible adjacency type."; 321 leaf adj-type { 322 type enumeration { 323 enum p2p { 324 description "Describes p2p adjacency."; 325 } 326 enum bfer { 327 description "Describes bfer adjacency."; 328 } 329 enum leaf-bfer { 330 description 331 "Describes leaf-bfer adjacency. There is no next BFR that 332 the packet should be forwarded."; 333 } 334 enum lan { 335 description "Describes lan adjacency."; 336 } 337 enum spoke { 338 description "Describes spoke adjacency of hub-and-spoke."; 339 } 340 enum ring-clockwise { 341 description "Describes clockwise adjacency in ring."; 342 } 343 enum ring-counterclockwise { 344 description "Describes counterclockwise adjacency in ring."; 345 } 346 enum ecmp { 347 description 348 "Describes ecmp adjacency. When the type is set to ecmp, 349 the corresponding ecmp entry should be used to balance 350 the load."; 351 } 352 enum virtual-link { 353 description 354 "Describes virtual adjacency between two indirect connect 355 nodes."; 356 } 357 enum other { 358 description "Describes other id type of adjacency."; 359 } 360 } 361 description "The collection of all possible adjacency type."; 362 } 363 } // adj-type 365 grouping te-bift-id { 366 description "The index of BIER forwarding items. It usually 367 represents the combination of [SD, BSL, SI]."; 368 leaf type { 369 type enumeration { 370 enum mpls { 371 description 372 "The bift-id value is represent the BIER TE mpls 373 forwarding plane. It is a mpls label."; 374 } 375 enum eth { 376 description 377 "The bift-id value is represent the BIER TE ethernet 378 forwarding plane. It is an index of ethernet 379 encapsulation."; 380 } 381 enum other { 382 description "Describes other type of te-bift-id."; 384 } 385 } 386 description "The types of BIER TE bift-id. If this type 387 is not set, mpls is default type."; 388 } 389 leaf value { 390 type rt-types:mpls-label; 391 mandatory true; 392 description 393 "The bift-id value of the forwarding item. It can be a mpls 394 label or an index of ethernet encapsulation which is used 395 to represent specific combination of [SD, BSL, SI]. The 396 ethernet index value is the same range (20bits) as mpls 397 label."; 398 } 399 } // te-bift-id 401 grouping te-items { 402 description "The BIER TE forwarding items collection."; 404 container out-info { 405 description 406 "The information of out forwarding packets. Includes the 407 outbound interface and the bift-id of next hop."; 409 list out-if-list { 410 key "fwd-intf"; 411 description 412 "The outbound interface information for forwarding."; 414 leaf fwd-intf { 415 type if:interface-ref; 416 mandatory true; 417 description 418 "The out interface of this forwarding item."; 419 } 420 leaf dnr-flag { 421 type boolean; 422 description 423 "When the flag is set to 1, the BP of adjacency should not 424 be reset when packet copies are created. The flag makes 425 sense only when the forwarding type is 'connected'."; 426 } 427 container fwd-type { 428 description 429 "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."; 460 uses te-bift-id; 461 } 462 } 463 } 464 } // te-items 466 /* 467 * data nodes 468 */ 469 augment "/rt:routing/rt:control-plane-protocols/" 470 +"rt:control-plane-protocol" { 471 description "The BIER TE information."; 472 container bier-te { 473 description "The BIER TE information container."; 475 container te-adj { 476 description "The BIER TE adjacency information."; 477 list adj-if { 478 key "name"; 479 description "List of BIER-TE interfaces."; 480 leaf name { 481 type if:interface-ref; 482 description "Interface name reference."; 483 } 484 list subdomain { 485 key "subdomain-id"; 486 description 487 "The sub-domain which the interface belongs to. 488 One interface can belong to many subdomains."; 490 leaf subdomain-id { 491 type uint16; 492 description "The sub-domain-id of this sub-domain."; 493 reference 494 "RFC 8279: Multicast Using Bit Index Explicit 495 Replication (BIER)"; 496 } 497 list si { 498 key "si"; 499 description "The set identifier value."; 501 leaf si{ 502 type uint16; 503 mandatory true; 504 description 505 "The set identifier of this forwarding item."; 506 } 507 leaf-list adj-id { 508 type uint16; 509 description "The ID of an adjacency."; 510 } 511 } 512 } 513 uses adj-type; 514 } 515 } // te-adj 517 container te-fwd { 518 description "The BIER TE forwarding information."; 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 bsl { 534 key "fwd-bsl"; 535 description "The forwarding items in one BSL."; 536 leaf fwd-bsl { 537 type uint16; 538 description "The value of bitstringlength."; 539 } 540 list si { 541 key "si"; 542 description 543 "The forwarding items in one combination of SD, 544 BSL and SI."; 545 leaf si{ 546 type uint16; 547 mandatory true; 548 description 549 "The set identifier of this forwarding item."; 550 } 551 container te-bift-id { 552 description 553 "The bift-id which is used to locate the specific 554 forwarding item."; 555 uses te-bift-id; 556 } 558 list fwd-items { 559 key "te-bp"; 560 description 561 "The forwarding information of one BIER TE item."; 562 leaf te-bp { 563 type uint16; 564 mandatory true; 565 description 566 "The bit index of a BIER TE forwarding item."; 567 } 569 leaf te-ecmp { 570 if-feature bier-te-ecmp; 571 type boolean; 572 description 573 "The list of the ecmp paths. When the type of 574 BP is set to ecmp, this interface ecmp list 575 should be used to balance the load on each 576 interface."; 577 } 578 uses te-items; 580 container te-frr { 581 if-feature bier-te-frr; 582 leaf frr-index { 583 type leafref { 584 path "../../../../../" + 585 "te-frr-items/btaft/frr-index"; 586 } 587 description "The index of this frr path."; 588 } 589 container resetbitmask { 590 description 591 "The deleting bitmask of the forwarding item."; 592 uses bit-string; 593 } 594 description 595 "If this link is protected, frr items can be used to 596 forward flows when this link is down."; 597 } // te-frr 598 } // fwd-items 599 } // si 600 } // bsl 602 container te-frr-items { 603 if-feature bier-te-frr; 604 description "The TE fast re-route information."; 605 list btaft { 606 key "frr-index"; 607 description 608 "The index of the frr paths. This item can be used 609 for multiple links protection in different SI."; 610 leaf frr-index { 611 type uint16; 612 mandatory true; 613 description "The frr item index."; 614 } 615 leaf frr-si{ 616 type uint16; 617 mandatory true; 618 description 619 "The set identifier of this forwarding item."; 620 } 621 leaf frr-bsl { 622 type uint16; 623 mandatory true; 624 description "The value of bitstringlength."; 625 } 626 container addbitmask { 627 description 628 "The adding bitmask of the forwarding item. 629 This item should be merged into the packet's 630 bit-string."; 631 uses bit-string; 632 } 633 } // btaft 634 } // te-frr-items 635 } // subdomain 636 } // te-fwd 637 } // bier-te 638 } 640 /* 641 * Notifications 642 */ 643 notification bier-te-notification { 644 description 645 "The notification is sent when a condition changes."; 646 list bp-is-zero { 647 key "if-index"; 648 description "The adjacency id is zero. It is invalid."; 649 leaf if-index { 650 type if:interface-ref; 651 description "The adjacency id is zero."; 652 } 653 uses adj-type; 654 } 655 } 656 } 657 659 7. IANA Considerations 661 The IANA is requested to assign two new URIs from the IETF XML 662 registry ([RFC3688]). Authors are suggesting the following URI: 664 URI: urn:ietf:params:xml:ns:yang:ietf-bier-te 666 Registrant Contact: BIER WG 668 XML: N/A, the requested URI is an XML namespace 670 This document also requests one new YANG module name in the YANG 671 Module Names registry ([RFC6020]) with the following suggestion: 673 name: ietf-bier-te 675 namespace: urn:ietf:params:xml:ns:yang:ietf-bier-te 677 prefix: bier-te 679 reference: RFC XXXX 681 8. Acknowledgement 683 The authors would like to thank Min Gu (gumin20181129@163.com) for 684 her testing, verification and valuable suggestion. And the authors 685 would like to thank Benjamin R for his valuable comments. 687 9. Normative References 689 [I-D.eckert-bier-te-frr] 690 Eckert, T., Cauchie, G., Braun, W., and M. Menth, 691 "Protection Methods for BIER-TE", draft-eckert-bier-te- 692 frr-03 (work in progress), March 2018. 694 [I-D.ietf-bier-bier-yang] 695 Chen, R., hu, f., Zhang, Z., dai.xianxian@zte.com.cn, d., 696 and M. Sivakumar, "YANG Data Model for BIER Protocol", 697 draft-ietf-bier-bier-yang-06 (work in progress), February 698 2020. 700 [I-D.ietf-bier-te-arch] 701 Eckert, T., Cauchie, G., and M. Menth, "Traffic 702 Engineering for Bit Index Explicit Replication (BIER-TE)", 703 draft-ietf-bier-te-arch-05 (work in progress), November 704 2019. 706 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 707 DOI 10.17487/RFC3688, January 2004, 708 . 710 [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for 711 the Network Configuration Protocol (NETCONF)", RFC 6020, 712 DOI 10.17487/RFC6020, October 2010, 713 . 715 [RFC6087] Bierman, A., "Guidelines for Authors and Reviewers of YANG 716 Data Model Documents", RFC 6087, DOI 10.17487/RFC6087, 717 January 2011, . 719 [RFC7223] Bjorklund, M., "A YANG Data Model for Interface 720 Management", RFC 7223, DOI 10.17487/RFC7223, May 2014, 721 . 723 [RFC8279] Wijnands, IJ., Ed., Rosen, E., Ed., Dolganow, A., 724 Przygienda, T., and S. Aldrin, "Multicast Using Bit Index 725 Explicit Replication (BIER)", RFC 8279, 726 DOI 10.17487/RFC8279, November 2017, 727 . 729 [RFC8296] Wijnands, IJ., Ed., Rosen, E., Ed., Dolganow, A., 730 Tantsura, J., Aldrin, S., and I. Meilik, "Encapsulation 731 for Bit Index Explicit Replication (BIER) in MPLS and Non- 732 MPLS Networks", RFC 8296, DOI 10.17487/RFC8296, January 733 2018, . 735 [RFC8349] Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for 736 Routing Management (NMDA Version)", RFC 8349, 737 DOI 10.17487/RFC8349, March 2018, 738 . 740 Authors' Addresses 742 Zheng(Sandy) Zhang 743 ZTE Corporation 744 No. 50 Software Ave, Yuhuatai Distinct 745 Nanjing 746 China 748 Email: zzhang_ietf@hotmail.com 750 Cui(Linda) Wang 751 ZTE Corporation 753 Email: lindawangjoy@gmail.com 755 Ran Chen 756 ZTE Corporation 757 No. 50 Software Ave, Yuhuatai Distinct 758 Nanjing 759 China 761 Email: chen.ran@zte.com.cn 762 Fangwei Hu 763 Individual 764 Shanghai 765 China 767 Email: hufwei@gmail.com 769 Mahesh Sivakumar 770 Juniper networks 771 1133 Innovation Way 772 Sunnyvale, CALIFORNIA 94089 773 United States 775 Email: sivakumar.mahesh@gmail.com 777 Huanan Chen 778 China Telecom 779 109 West Zhongshan Ave 780 Guangzhou, Guangdong 510630 781 China 783 Phone: +86 20 38639346 784 Email: chenhuanan@gsta.com