idnits 2.17.1 draft-ietf-bier-te-yang-02.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 92 has weird spacing: '...main-id uin...' == Line 99 has weird spacing: '...main-id uin...' == Line 101 has weird spacing: '...fwd-bsl uin...' == Line 106 has weird spacing: '...w value rt-...' == Line 122 has weird spacing: '...w value rt-...' == (1 more instance...) -- The document date (August 12, 2020) is 1352 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 696, but no explicit reference was found in the text == Unused Reference: 'RFC6087' is defined on line 716, but no explicit reference was found in the text == Unused Reference: 'RFC7223' is defined on line 720, but no explicit reference was found in the text == Unused Reference: 'RFC8279' is defined on line 724, but no explicit reference was found in the text == Unused Reference: 'RFC8296' is defined on line 730, but no explicit reference was found in the text == Unused Reference: 'RFC8349' is defined on line 736, 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-08 ** 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: February 13, 2021 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 August 12, 2020 16 A YANG data model for Traffic Engineering for Bit Index Explicit 17 Replication (BIER-TE) 18 draft-ietf-bier-te-yang-02 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 February 13, 2021. 42 Copyright Notice 44 Copyright (c) 2020 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 . . . . . . . . . . . . . . . . . . . . . 14 66 8. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 15 67 9. Normative References . . . . . . . . . . . . . . . . . . . . 15 68 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16 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 type? enumeration 106 | | +--rw value rt-types:mpls-label 107 | +--rw fwd-items* [te-bp] 108 | +--rw te-bp uint16 109 | +--rw te-ecmp? boolean {bier-te-ecmp}? 110 | +--rw out-info 111 | | +--rw out-if-list* [fwd-intf] 112 | | +--rw fwd-intf if:interface-ref 113 | | +--rw dnr-flag? boolean 114 | | +--rw fwd-type 115 | | | +--rw (fwd-type) 116 | | | +--:(connected) 117 | | | +--:(routed) 118 | | | +--:(local-decap) 119 | | | +--:(other) 120 | | +--rw te-out-bift-id 121 | | +--rw type? enumeration 122 | | +--rw value rt-types:mpls-label 123 | +--rw te-frr {bier-te-frr}? 124 | +--rw frr-index? 125 -> ../../../../../te-frr-items/btaft/frr-index 126 | +--rw resetbitmask 127 | +--rw bit-string* [index] 128 | +--rw index uint8 129 | +--rw bitmask? uint32 130 +--rw te-frr-items {bier-te-frr}? 131 +--rw btaft* [frr-index] 132 +--rw frr-index uint16 133 +--rw frr-si uint16 134 +--rw frr-bsl uint16 135 +--rw addbitmask 136 +--rw bit-string* [index] 137 +--rw index uint8 138 +--rw bitmask? uint32 140 notifications: 141 +---n bier-te-notification 142 +--ro bp-is-zero* [if-index] 143 +--ro if-index if:interface-ref 144 +--ro adj-type? enumeration 146 3. BIER-TE configuration 148 The BIER-TE forwarding item is indexed by the combination of sub- 149 domain-id, BitStringLength and set identifier. 151 One interface can be used in different sub-domain, so the BIER TE 152 adjacency information is managed by BIER TE function other than by 153 interface itself. 155 Because the BIER-TE is controlled by controller now, the information 156 about IGP is not defined. If in the future the IGP is used to carry 157 the information about BIER-TE, the IGP extension will be added in 158 this document. 160 4. Notifications 162 If the adjacency id of one adjacency is set to zero, the value is 163 invalid. The notification should be sent to controller and network 164 manager. 166 5. RPCs 168 TBD. 170 6. BIER TE YANG model 172 file "ietf-bier-te@2020-02-05.yang" 173 module ietf-bier-te { 175 yang-version 1.1; 177 namespace "urn:ietf:params:xml:ns:yang:ietf-bier-te"; 179 prefix bier-te; 181 import ietf-routing { 182 prefix "rt"; 183 reference 184 "RFC 8349: A YANG Data Model for Routing Management 185 (NMDA Version)"; 186 } 188 import ietf-interfaces { 189 prefix "if"; 190 reference 191 "RFC 8343: A YANG Data Model for Interface Management"; 192 } 193 import ietf-routing-types { 194 prefix "rt-types"; 195 reference 196 "RFC 8294: Common YANG Data Types for the Routing Area"; 197 } 199 organization " IETF BIER (Bit Indexed Explicit Replication) 200 Working Group"; 201 contact 202 "WG Web: 203 WG List: 205 Editor: Zheng Zhang 206 207 Editor: Cui Wang 208 209 Editor: Ran Chen 210 211 Editor: Fangwei Hu 212 213 Editor: Mahesh Sivakumar 214 215 Editor: Huanan Chen 216 217 "; 219 description 220 "The module defines the YANG definitions for Traffic 221 Engineering for Bit Index Explicit Replication (BIER-TE). 223 Copyright (c) 2020 IETF Trust and the persons identified as 224 authors of the code. All rights reserved. 226 Redistribution and use in source and binary forms, with or 227 without modification, is permitted pursuant to, and subject 228 to the license terms contained in, the Simplified BSD 229 License set forth in Section 4.c of the IETF Trust's Legal 230 Provisions Relating to IETF Documents 231 (https://trustee.ietf.org/license-info). 233 This version of this YANG module is part of RFC XXXX 234 (https://www.rfc-editor.org/info/rfcXXXX); see the RFC 235 itself for full legal notices. 237 The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 238 'SHALL NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 239 'NOT RECOMMENDED', 'MAY', and 'OPTIONAL' in this document 240 are to be interpreted as described in BCP 14 (RFC 2119) 241 (RFC 8174) when, and only when, they appear in all 242 capitals, as shown here."; 244 revision 2020-02-05 { 245 description 246 "Initial revision."; 247 reference 248 "I-D.ietf-bier-te-arch: Traffic Engineering for Bit Index 249 Explicit Replication (BIER-TE)"; 250 } 252 /* 253 * Features 254 */ 255 feature bier-te-frr { 256 description 257 "Support Fast Re-route feature in BIER TE."; 258 reference 259 "I-D.eckert-bier-te-frr: Protection Methods for BIER-TE"; 260 } 261 feature bier-te-ecmp { 262 description 263 "Support ECMP feature in BIER TE."; 264 reference 265 "I-D.ietf-bier-te-arch: Traffic Engineering for Bit Index 266 Explicit Replication (BIER-TE), section 3.2.3"; 267 } 269 /* 270 * Identities 271 */ 273 identity bier-te { 274 base rt:control-plane-protocol; 275 description 276 "Identity for the Traffic Engineering for Bit Index Explicit 277 Replication (BIER-TE)."; 278 reference 279 "I-D.ietf-bier-te-arch: Traffic Engineering for Bit Index 280 Explicit Replication (BIER-TE)"; 281 } 283 grouping bit-string { 284 description 285 "The bit string which each bit represents an adjacency. 286 It is encapsulated in BIER header."; 287 reference 288 "I-D.ietf-bier-te-arch: Traffic Engineering for Bit Index 289 Explicit Replication (BIER-TE), section 3.3. 290 RFC8279: Multicast Using Bit Index Explicit Replication 291 (BIER). 292 RFC8296: Encapsulation for Bit Index Explicit Replication 293 (BIER) in MPLS and Non-MPLS Networks."; 295 list bit-string { 296 key "index"; 297 description 298 "As the definition in RFC 8279, the bit-string lengths are 299 64, 128, 256, 512, 1024, 2048, 4096 bits. The according 300 encapsulation is defined in RFC8296. BIER-TE uses the 301 similar function for bit string."; 303 leaf index { 304 type uint8 { 305 range "2..128"; 306 } 307 description 308 "The index of bit-mask. The minimum index value is 64 and 309 the corresponding bit string length is 64 bits. The 310 maximum index value is 128 and the corresponding 311 bit-string length is 4096 bits."; 312 } 313 leaf bitmask { 314 type uint32; 315 description "The bit-string in 4-octet units."; 316 } 317 } 318 } // bit-string 320 grouping adj-type { 321 description "The collection of all possible adjacency type."; 323 leaf adj-type { 324 type enumeration { 325 enum p2p { 326 description "Describes p2p adjacency."; 327 } 328 enum bfer { 329 description "Describes bfer adjacency."; 330 } 331 enum leaf-bfer { 332 description 333 "Describes leaf-bfer adjacency. There is no next BFR that 334 the packet should be forwarded."; 335 } 336 enum lan { 337 description "Describes lan adjacency."; 338 } 339 enum spoke { 340 description "Describes spoke adjacency of hub-and-spoke."; 341 } 342 enum ring-clockwise { 343 description "Describes clockwise adjacency in ring."; 344 } 345 enum ring-counterclockwise { 346 description "Describes counterclockwise adjacency in ring."; 347 } 348 enum ecmp { 349 description 350 "Describes ecmp adjacency. When the type is set to ecmp, 351 the corresponding ecmp entry should be used to balance 352 the load."; 353 } 354 enum virtual-link { 355 description 356 "Describes virtual adjacency between two indirect connect 357 nodes."; 358 } 359 enum other { 360 description "Describes other id type of adjacency."; 361 } 362 } 363 description "The collection of all possible adjacency type."; 364 } 365 } // adj-type 367 grouping te-bift-id { 368 description "The index of BIER forwarding items. It usually 369 represents the combination of [SD, BSL, SI]."; 370 leaf type { 371 type enumeration { 372 enum mpls { 373 description 374 "The bift-id value is represent the BIER TE mpls 375 forwarding plane. It is a mpls label."; 376 } 377 enum eth { 378 description 379 "The bift-id value is represent the BIER TE ethernet 380 forwarding plane. It is an index of ethernet 381 encapsulation."; 382 } 383 enum other { 384 description "Describes other type of te-bift-id."; 386 } 387 } 388 description "The types of BIER TE bift-id. If this type 389 is not set, mpls is default type."; 390 } 391 leaf value { 392 type rt-types:mpls-label; 393 mandatory true; 394 description 395 "The bift-id value of the forwarding item. It can be a mpls 396 label or an index of ethernet encapsulation which is used 397 to represent specific combination of [SD, BSL, SI]. The 398 ethernet index value is the same range (20bits) as mpls 399 label."; 400 } 401 } // te-bift-id 403 grouping te-items { 404 description "The BIER TE forwarding items collection."; 406 container out-info { 407 description 408 "The information of out forwarding packets. Includes the 409 outbound interface and the bift-id of next hop."; 411 list out-if-list { 412 key "fwd-intf"; 413 description 414 "The outbound interface information for forwarding."; 416 leaf fwd-intf { 417 type if:interface-ref; 418 mandatory true; 419 description 420 "The out interface of this forwarding item."; 421 } 422 leaf dnr-flag { 423 type boolean; 424 description 425 "When the flag is set to 1, the BP of adjacency should not 426 be reset when packet copies are created. The flag makes 427 sense only when the forwarding type is 'connected'."; 428 } 429 container fwd-type { 430 description 431 "The collection of all possible forwarding types."; 432 choice fwd-type { 433 mandatory true; 434 case connected { 435 description 436 "The forwarding type is connected. Mostly connected 437 interfaces."; 438 } 439 case routed { 440 description 441 "The forwarding type is routed. Mostly not connected 442 interfaces."; 443 } 444 case local-decap { 445 description 446 "Means that the packet should be decapsulated and 447 forward out of BIER domain."; 448 } 449 case other { 450 description 451 "Means that the packet should be discarded."; 452 } 453 description 454 "The collection of all possible forwarding types."; 455 } 456 } // fwd-type 458 container te-out-bift-id { 459 description 460 "The bift-id information corresponding to a specific 461 outbound interface."; 462 uses te-bift-id; 463 } 464 } 465 } 466 } // te-items 468 /* 469 * data nodes 470 */ 471 augment "/rt:routing/rt:control-plane-protocols/" 472 +"rt:control-plane-protocol" { 473 description "The BIER TE information."; 474 container bier-te { 475 description "The BIER TE information container."; 477 container te-adj { 478 description "The BIER TE adjacency information."; 479 list adj-if { 480 key "name"; 481 description "List of BIER-TE interfaces."; 482 leaf name { 483 type if:interface-ref; 484 description "Interface name reference."; 485 } 486 list subdomain { 487 key "subdomain-id"; 488 description 489 "The sub-domain which the interface belongs to. 490 One interface can belong to many subdomains."; 492 leaf subdomain-id { 493 type uint16; 494 description "The sub-domain-id of this sub-domain."; 495 reference 496 "RFC 8279: Multicast Using Bit Index Explicit 497 Replication (BIER)"; 498 } 499 list si { 500 key "si"; 501 description "The set identifier value."; 503 leaf si{ 504 type uint16; 505 mandatory true; 506 description 507 "The set identifier of this forwarding item."; 508 } 509 leaf-list adj-id { 510 type uint16; 511 description "The ID of an adjacency."; 512 } 513 } 514 } 515 uses adj-type; 516 } 517 } // te-adj 519 container te-fwd { 520 description "The BIER TE forwarding information."; 522 list subdomain { 523 key "subdomain-id"; 524 description 525 "The sub-domain which the interface belongs to. 526 One interface can belong to many subdomains."; 528 leaf subdomain-id { 529 type uint16; 530 description "The sub-domain-id of this sub-domain."; 531 reference 532 "RFC 8279: Multicast Using Bit Index Explicit 533 Replication (BIER)"; 534 } 535 list bsl { 536 key "fwd-bsl"; 537 description "The forwarding items in one BSL."; 538 leaf fwd-bsl { 539 type uint16; 540 description "The value of bitstringlength."; 541 } 542 list si { 543 key "si"; 544 description 545 "The forwarding items in one combination of SD, 546 BSL and SI."; 547 leaf si{ 548 type uint16; 549 mandatory true; 550 description 551 "The set identifier of this forwarding item."; 552 } 553 container te-bift-id { 554 description 555 "The bift-id which is used to locate the specific 556 forwarding item."; 557 uses te-bift-id; 558 } 560 list fwd-items { 561 key "te-bp"; 562 description 563 "The forwarding information of one BIER TE item."; 564 leaf te-bp { 565 type uint16; 566 mandatory true; 567 description 568 "The bit index of a BIER TE forwarding item."; 569 } 571 leaf te-ecmp { 572 if-feature bier-te-ecmp; 573 type boolean; 574 description 575 "The list of the ecmp paths. When the type of 576 BP is set to ecmp, this interface ecmp list 577 should be used to balance the load on each 578 interface."; 579 } 580 uses te-items; 582 container te-frr { 583 if-feature bier-te-frr; 584 leaf frr-index { 585 type leafref { 586 path "../../../../../" + 587 "te-frr-items/btaft/frr-index"; 588 } 589 description "The index of this frr path."; 590 } 591 container resetbitmask { 592 description 593 "The deleting bitmask of the forwarding item."; 594 uses bit-string; 595 } 596 description 597 "If this link is protected, frr items can be used to 598 forward flows when this link is down."; 599 } // te-frr 600 } // fwd-items 601 } // si 602 } // bsl 604 container te-frr-items { 605 if-feature bier-te-frr; 606 description "The TE fast re-route information."; 607 list btaft { 608 key "frr-index"; 609 description 610 "The index of the frr paths. This item can be used 611 for multiple links protection in different SI."; 612 leaf frr-index { 613 type uint16; 614 mandatory true; 615 description "The frr item index."; 616 } 617 leaf frr-si{ 618 type uint16; 619 mandatory true; 620 description 621 "The set identifier of this forwarding item."; 622 } 623 leaf frr-bsl { 624 type uint16; 625 mandatory true; 626 description "The value of bitstringlength."; 627 } 628 container addbitmask { 629 description 630 "The adding bitmask of the forwarding item. 631 This item should be merged into the packet's 632 bit-string."; 633 uses bit-string; 634 } 635 } // btaft 636 } // te-frr-items 637 } // subdomain 638 } // te-fwd 639 } // bier-te 640 } 642 /* 643 * Notifications 644 */ 645 notification bier-te-notification { 646 description 647 "The notification is sent when a condition changes."; 648 list bp-is-zero { 649 key "if-index"; 650 description "The adjacency id is zero. It is invalid."; 651 leaf if-index { 652 type if:interface-ref; 653 description "The adjacency id is zero."; 654 } 655 uses adj-type; 656 } 657 } 658 } 659 661 7. IANA Considerations 663 The IANA is requested to assign two new URIs from the IETF XML 664 registry ([RFC3688]). Authors are suggesting the following URI: 666 URI: urn:ietf:params:xml:ns:yang:ietf-bier-te 668 Registrant Contact: BIER WG 670 XML: N/A, the requested URI is an XML namespace 672 This document also requests one new YANG module name in the YANG 673 Module Names registry ([RFC6020]) with the following suggestion: 675 name: ietf-bier-te 677 namespace: urn:ietf:params:xml:ns:yang:ietf-bier-te 679 prefix: bier-te 681 reference: RFC XXXX 683 8. Acknowledgement 685 The authors would like to thank Min Gu (gumin20181129@163.com) for 686 her testing, verification and valuable suggestion. And the authors 687 would like to thank Benjamin R for his valuable comments. 689 9. Normative References 691 [I-D.eckert-bier-te-frr] 692 Eckert, T., Cauchie, G., Braun, W., and M. Menth, 693 "Protection Methods for BIER-TE", draft-eckert-bier-te- 694 frr-03 (work in progress), March 2018. 696 [I-D.ietf-bier-bier-yang] 697 Chen, R., hu, f., Zhang, Z., dai.xianxian@zte.com.cn, d., 698 and M. Sivakumar, "YANG Data Model for BIER Protocol", 699 draft-ietf-bier-bier-yang-06 (work in progress), February 700 2020. 702 [I-D.ietf-bier-te-arch] 703 Eckert, T., Cauchie, G., and M. Menth, "Tree Engineering 704 for Bit Index Explicit Replication (BIER-TE)", draft-ietf- 705 bier-te-arch-08 (work in progress), July 2020. 707 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 708 DOI 10.17487/RFC3688, January 2004, 709 . 711 [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for 712 the Network Configuration Protocol (NETCONF)", RFC 6020, 713 DOI 10.17487/RFC6020, October 2010, 714 . 716 [RFC6087] Bierman, A., "Guidelines for Authors and Reviewers of YANG 717 Data Model Documents", RFC 6087, DOI 10.17487/RFC6087, 718 January 2011, . 720 [RFC7223] Bjorklund, M., "A YANG Data Model for Interface 721 Management", RFC 7223, DOI 10.17487/RFC7223, May 2014, 722 . 724 [RFC8279] Wijnands, IJ., Ed., Rosen, E., Ed., Dolganow, A., 725 Przygienda, T., and S. Aldrin, "Multicast Using Bit Index 726 Explicit Replication (BIER)", RFC 8279, 727 DOI 10.17487/RFC8279, November 2017, 728 . 730 [RFC8296] Wijnands, IJ., Ed., Rosen, E., Ed., Dolganow, A., 731 Tantsura, J., Aldrin, S., and I. Meilik, "Encapsulation 732 for Bit Index Explicit Replication (BIER) in MPLS and Non- 733 MPLS Networks", RFC 8296, DOI 10.17487/RFC8296, January 734 2018, . 736 [RFC8349] Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for 737 Routing Management (NMDA Version)", RFC 8349, 738 DOI 10.17487/RFC8349, March 2018, 739 . 741 Authors' Addresses 743 Zheng(Sandy) Zhang 744 ZTE Corporation 745 Nanjing 746 China 748 Email: zhang.zheng@zte.com.cn 750 Cui(Linda) Wang 751 Individual 753 Email: lindawangjoy@gmail.com 755 Ran Chen 756 ZTE Corporation 757 Nanjing 758 China 760 Email: chen.ran@zte.com.cn 762 Fangwei Hu 763 Individual 764 Shanghai 765 China 767 Email: hufwei@gmail.com 768 Mahesh Sivakumar 769 Juniper networks 770 1133 Innovation Way 771 Sunnyvale, CALIFORNIA 94089 772 United States 774 Email: sivakumar.mahesh@gmail.com 776 Huanan Chen 777 China Telecom 778 109 West Zhongshan Ave 779 Guangzhou, Guangdong 510630 780 China 782 Phone: +86 20 38639346 783 Email: chenhuanan@gsta.com