idnits 2.17.1 draft-ietf-bier-bier-yang-07.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 : ---------------------------------------------------------------------------- ** There are 13 instances of too long lines in the document, the longest one being 157 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 94 has weird spacing: '...on-type ide...' == Line 101 has weird spacing: '...glength uin...' -- The document date (September 8, 2020) is 1297 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-isis-yang-isis-cfg' is defined on line 692, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-mpls-base-yang' is defined on line 697, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-mpls-static-yang' is defined on line 702, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-ospf-yang' is defined on line 707, but no explicit reference was found in the text == Unused Reference: 'RFC6020' is defined on line 712, but no explicit reference was found in the text == Unused Reference: 'RFC6241' is defined on line 717, but no explicit reference was found in the text == Unused Reference: 'RFC6991' is defined on line 722, but no explicit reference was found in the text == Unused Reference: 'RFC7223' is defined on line 726, but no explicit reference was found in the text == Unused Reference: 'RFC8022' is defined on line 730, but no explicit reference was found in the text == Unused Reference: 'RFC8279' is defined on line 734, but no explicit reference was found in the text == Unused Reference: 'RFC8296' is defined on line 740, but no explicit reference was found in the text == Outdated reference: A later version (-17) exists of draft-ietf-mpls-base-yang-15 == Outdated reference: A later version (-14) exists of draft-ietf-mpls-static-yang-11 ** Obsolete normative reference: RFC 7223 (Obsoleted by RFC 8343) ** Obsolete normative reference: RFC 8022 (Obsoleted by RFC 8349) Summary: 3 errors (**), 0 flaws (~~), 16 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 BIER WG Ran. Chen 3 Internet-Draft ZTE Corporation 4 Intended status: Standards Track Fangwei. Hu 5 Expires: March 12, 2021 Individual 6 Zheng. Zhang 7 Xianxia. Dai 8 ZTE Corporation 9 Mahesh. Sivakumar 10 Juniper networks 11 September 8, 2020 13 YANG Data Model for BIER Protocol 14 draft-ietf-bier-bier-yang-07 16 Abstract 18 This document defines a YANG data model for BIER configuration and 19 operation. 21 Status of This Memo 23 This Internet-Draft is submitted in full conformance with the 24 provisions of BCP 78 and BCP 79. 26 Internet-Drafts are working documents of the Internet Engineering 27 Task Force (IETF). Note that other groups may also distribute 28 working documents as Internet-Drafts. The list of current Internet- 29 Drafts is at https://datatracker.ietf.org/drafts/current/. 31 Internet-Drafts are draft documents valid for a maximum of six months 32 and may be updated, replaced, or obsoleted by other documents at any 33 time. It is inappropriate to use Internet-Drafts as reference 34 material or to cite them other than as "work in progress." 36 This Internet-Draft will expire on March 12, 2021. 38 Copyright Notice 40 Copyright (c) 2020 IETF Trust and the persons identified as the 41 document authors. All rights reserved. 43 This document is subject to BCP 78 and the IETF Trust's Legal 44 Provisions Relating to IETF Documents 45 (https://trustee.ietf.org/license-info) in effect on the date of 46 publication of this document. Please review these documents 47 carefully, as they describe your rights and restrictions with respect 48 to this document. Code Components extracted from this document must 49 include Simplified BSD License text as described in Section 4.e of 50 the Trust Legal Provisions and are provided without warranty as 51 described in the Simplified BSD License. 53 Table of Contents 55 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 56 2. Design of the Data Model . . . . . . . . . . . . . . . . . . 2 57 3. Configuration . . . . . . . . . . . . . . . . . . . . . . . . 3 58 4. Control plane configuration . . . . . . . . . . . . . . . . . 4 59 5. Notification . . . . . . . . . . . . . . . . . . . . . . . . 4 60 6. BIER YANG Data Model . . . . . . . . . . . . . . . . . . . . 4 61 7. Security Considerations . . . . . . . . . . . . . . . . . . . 15 62 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 15 63 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15 64 10. Normative References . . . . . . . . . . . . . . . . . . . . 15 65 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17 67 1. Introduction 69 This document defines a YANG data model for BIER configuration and 70 operation. 72 2. Design of the Data Model 74 module: ietf-bier 75 augment /rt:routing: 76 +--rw bier 77 +--rw encapsulation-type? identityref 78 +--rw bsl? enumeration 79 +--rw bfr-id? uint16 80 +--rw bfr-prefix? inet:ip-prefix 81 +--rw sub-domain* [sub-domain-id address-family] 82 | +--rw sub-domain-id uint16 83 | +--rw address-family identityref 84 | +--rw bfr-prefix? inet:ip-prefix 85 | +--rw underlay-protocol-type? enumeration 86 | +--rw mt-id? uint16 87 | +--rw bfr-id? uint16 88 | +--rw bsl? enumeration 89 | +--rw igp-algorithm? uint8 90 | +--rw bier-algorithm? uint8 91 | +--rw load-balance-num? uint8 92 | +--rw encapsulation* [bsl encapsulation-type] 93 | +--rw bsl uint16 94 | +--rw encapsulation-type identityref 95 | +--rw max-si? uint16 96 | +--rw bift-id-base? uint32 97 +--rw birt* [sub-domain-id] 98 +--rw sub-domain-id uint16 99 +--rw bfr-id? uint16 100 +--rw birt-bitstringlength* [bitstringlength] 101 +--rw bitstringlength uint16 102 +--rw birt-si* [si] 103 +--rw si uint16 104 +--rw in-bift-id? uint32 105 +--rw bfr-nbr 106 +--rw bfr-nbr inet:ip-prefix 107 +--rw encapsulation-type? enumeration 108 +--rw out-bift-id uint32 110 augment /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol/ospf:ospf: 111 +--rw bier-ospf-cfg 112 +--rw mt-id? uint16 113 +--rw bier 114 +--rw enable? boolean 115 +--rw advertise? boolean 116 +--rw receive? boolean 117 augment /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol/isis:isis: 118 +--rw bier-isis-cfg 119 +--rw mt-id? uint16 120 +--rw bier 121 +--rw enable? boolean 122 +--rw advertise? boolean 123 +--rw receive? boolean 125 notifications: 126 +---n bfr-id-collision 127 | +--ro bfr-id? uint16 128 +---n bfr-zero 129 | +--ro ipv4-bfr-prefix? inet:ipv4-prefix 130 | +--ro ipv6-bfr-prefix? inet:ipv6-prefix 131 +---n sub-domain-id-collision 132 +--ro sub-domain-id? uint16 133 +--ro mt-id? uint16 135 3. Configuration 137 This Module augments the "/rt:routing:" with a BIER container. This 138 Container defines all the configuration parameters related to BIER 139 for this particular routing. 141 The BIER configuration contains global configuration. 143 The global configuration includes BIER encapsulation type, 144 BitStringLengths, BFR-id, BFR-prefixes, and parameters associated 145 with bier sub-domain. 147 4. Control plane configuration 149 This Module augments the "/rt:routing/rt:routing-protocols/ 150 rt:routing-protocol/ospf:ospf:" and "/rt:routing/rt:routing- 151 protocols/rt:routing-protocol/isis:isis:"configuration with BIER. 153 This Module supports ISIS ([RFC8401])and OSPF ([RFC8444]) as control 154 plane for BIER. 156 5. Notification 158 This Module includes bfr-id-collision, bfr-zero, and sub-domain-id- 159 collision. 161 6. BIER YANG Data Model 163 file "ietf-bier@2019-05-14.yang" 164 module ietf-bier { 165 yang-version 1.1; 166 namespace "urn:ietf:params:xml:ns:yang:ietf-bier"; 167 prefix "bier"; 169 import ietf-routing { 170 prefix "rt"; 171 } 172 import ietf-interfaces { 173 prefix "if"; 174 reference "RFC7223"; 175 } 176 import ietf-inet-types { 177 prefix "inet"; 178 } 180 import ietf-isis{ 181 prefix "isis"; 182 } 184 import ietf-ospf { 185 prefix "ospf"; 186 } 188 organization 189 "IETF BIER(Bit Indexed Explicit Replication ) Working Group"; 191 contact 192 "WG List: 194 WG Chair: Tony Przygienda 195 197 WG Chair: Greg Shepherd 198 200 Editor: Ran Chen 201 202 Editor: Fangwei Hu 203 204 Editor: Zheng Zhang 205 206 Editor: Xianxian Dai 207 208 Editor: Mahesh Sivakumar 209 210 "; 211 description 212 "The YANG module defines a generic configuration 213 model for BIER."; 215 revision 2020-09-08{ 216 description 217 "latest revision"; 218 reference "RFC XXXX: YANG Data Model for BIER Protocol."; 219 } 221 revision 2019-05-14{ 222 description 223 "latest revision"; 224 reference "RFC XXXX: YANG Data Model for BIER Protocol."; 225 } 227 revision 2018-09-29{ 228 description 229 "04 revision"; 230 reference "RFC XXXX: YANG Data Model for BIER Protocol."; 231 } 233 revision 2018-02-07{ 234 description 235 "03 revision"; 236 reference "RFC XXXX: YANG Data Model for BIER Protocol."; 238 } 240 revision 2017-08-10{ 241 description 242 "02 revision"; 243 reference "RFC XXXX: YANG Data Model for BIER Protocol."; 245 } 247 revision 2017-01-20{ 248 description 249 "01 revision"; 250 reference "RFC XXXX: YANG Data Model for BIER Protocol."; 251 } 253 revision 2016-07-23{ 254 description 255 "00 revision"; 256 reference "RFC XXXX: YANG Data Model for BIER Protocol."; 257 } 259 revision 2016-05-12{ 260 description 261 "04 revision"; 262 reference "RFC XXXX: YANG Data Model for BIER Protocol."; 263 } 265 revision 2016-03-16 { 266 description 267 "03 revision"; 268 reference "RFC XXXX: YANG Data Model for BIER Protocol."; 269 } 271 revision 2015-12-03 { 272 description 273 "02 revision"; 274 reference "RFC XXXX: YANG Data Model for BIER Protocol."; 275 } 277 revision 2015-10-16 { 278 description 279 "01 revision."; 280 reference "RFC XXXX: YANG Data Model for BIER Protocol."; 281 } 283 revision 2015-06-22 { 284 description 285 "Initial revision."; 286 reference "RFC XXXX: YANG Data Model for BIER Protocol."; 287 } 289 /* Identities */ 290 identity bier-encapsulation{ 291 description 292 "Base identity for BIER encapsulation."; 293 } 294 identity bier-encapsulation-mpls { 295 base bier-encapsulation; 296 description 297 "This identity represents MPLS encapsulation for bier."; 298 } 299 identity bier-encapsulation-ipv6 { 300 base bier-encapsulation; 301 description 302 "This identity represents ipv6 encapsulation for bier."; 303 } 304 identity bier-encapsulation-ethernet { 305 base bier-encapsulation; 306 description 307 "This identity represents ethernet encapsulation for bier."; 308 } 309 identity address-family { 310 description 311 "Base identity from which identities describing address 312 families are derived."; 313 } 314 identity ipv4 { 315 base address-family; 316 description 317 "This identity represents an IPv4 address family."; 318 } 320 identity ipv6 { 321 base address-family; 322 description 323 "This identity represents an IPv6 address family."; 324 } 326 /*grouping*/ 327 grouping bier-protocol-extensions{ 328 description 329 "Defines protocol extensions."; 330 leaf mt-id{ 331 type uint16 ; 332 description 333 "Multi-topology associated with bier sub-domain."; 334 } 335 container bier { 336 leaf enable { 337 type boolean; 338 default false; 339 description 340 "Enables bier protocol extensions."; 341 } 342 leaf advertise { 343 type boolean; 344 default true; 345 description 346 "Enable to advertise the parameters associated with bier."; 347 } 348 leaf receive { 349 type boolean; 350 default true; 351 description 352 "Enable to receive the parameters associated with bier."; 353 } 354 description 355 "BIER global config."; 356 } 357 } 359 grouping bsl { 360 description 361 "The bitstringlength type."; 362 leaf bsl { 363 type enumeration{ 364 enum "64-bit"{ 365 description 366 "bitstringlength is 64"; 367 } 368 enum "128-bit"{ 369 description 370 "bitstringlength is 128"; 371 } 372 enum "256-bit"{ 373 description 374 "bitstringlength is 256"; 375 } 376 enum "512-bit"{ 377 description 378 "bitstringlength is 512"; 379 } 380 enum "1024-bit"{ 381 description 382 "bitstringlength is 1024"; 383 } 384 enum "2048-bit"{ 385 description 386 "bitstringlength is 2048"; 387 } 388 enum "4096-bit"{ 389 description 390 "bitstringlength is 4096"; 391 } 392 } 393 default "256-bit"; 394 description 395 "list of the bitstringlength type to be supported."; 396 } 397 } 398 grouping underlay-protocol-type { 399 description 400 "The underlay protocol type."; 401 leaf underlay-protocol-type { 402 type enumeration{ 403 enum "isis" { 404 description 405 "isis protocol"; 406 } 407 enum "ospf" { 408 description 409 "ospf protocol"; 410 } 411 enum "bgp" { 412 description 413 "bgp protocol"; 414 } 415 } 416 description 417 "list of the underlay protocol to be supported."; 418 } 419 } 421 grouping encapsulation { 422 description 423 "The Bit Index Forwarding T6able.When MPLS is used as the transport, the Bit Indexed Forwarding Table (BIFT) is identified by a MPLS Label. When non-MPLS transport is used, the BIFT is identified by a 20bit value."; 424 list encapsulation { 425 key "bsl encapsulation-type"; 426 leaf bsl{ 427 type uint16; 428 description 429 "The value of the bitstringlength."; 430 } 432 leaf encapsulation-type { 433 type identityref { 434 base bier-encapsulation; 435 } 436 description 437 "Dataplane to be used."; 438 } 439 leaf max-si { 440 type uint16; 441 description 442 "Maximum Set Identifier ."; 443 } 444 leaf bift-id-base { 445 type uint32; 446 description 447 "The value of the bift id."; 448 } 449 description 450 "Different dataplane, different value of the bift-id."; 451 } 452 } 453 grouping sub-domain { 454 description 455 "The parameters of the sub domain."; 456 list sub-domain { 457 key "sub-domain-id address-family"; 458 leaf sub-domain-id { 459 type uint16; 460 description 461 "The type for sub-domain-id"; 462 } 463 leaf address-family { 464 type identityref { 465 base address-family; 466 } 467 mandatory true; 468 description 469 "Address family."; 470 } 472 leaf bfr-prefix { 473 type inet:ip-prefix; 474 description 475 "the bfr prefix."; 476 } 477 uses underlay-protocol-type; 478 leaf mt-id { 479 type uint16; 480 description 481 "The type for multi-topology identifier"; 482 } 483 leaf bfr-id { 484 type uint16; 485 description 486 "The type for bfr identifier"; 487 } 488 uses bsl; 489 leaf igp-algorithm { 490 type uint8; 491 description 492 "The type for igp algorithm"; 493 } 494 leaf bier-algorithm { 495 type uint8; 496 description 497 "The type for bier algorithm"; 498 } 499 leaf load-balance-num { 500 type uint8; 501 description 502 "The multicast load balance num."; 503 } 504 uses encapsulation; 505 description 506 "list the parameters of the sub domain."; 507 } 508 } 510 grouping bfr-nbr{ 511 description "The bfr nbr information, including bfr-nbr, encapsulation type and out-bift-id."; 512 leaf bfr-nbr { 513 type inet:ip-prefix; 514 description 515 "the bfr nbr."; 516 } 517 leaf encapsulation-type { 518 type identityref { 519 base bier-encapsulation; 520 } 521 description 522 "Dataplane to be used."; 523 } 525 leaf out-bift-id{ 526 type uint32; 527 description 528 "BIER out-bift-id."; 529 } 530 } 532 augment "/rt:routing" { 533 description 534 "This augments routing-instance configuration with bier."; 535 container bier{ 536 description 537 "bier global configuration."; 538 leaf encapsulation-type { 539 type identityref { 540 base bier-encapsulation; 541 } 542 description 543 "Dataplane to be used."; 544 } 545 uses bsl; 546 leaf bfr-id { 547 type uint16; 548 description 549 "The type for bfr identifier"; 550 } 551 leaf bfr-prefix { 552 type inet:ip-prefix; 553 description 554 "the bfr prefix."; 555 } 556 uses sub-domain; 557 list birt{ 558 key "sub-domain-id"; 559 leaf sub-domain-id{ 560 type uint16; 561 description 562 "BIER sub domain ID"; 563 } 564 list birt-bitstringlength { 565 key "bitstringlength"; 566 leaf bitstringlength{ 567 type uint16; 568 description 569 "BIER bitstringlength."; 570 } 571 list birt-si { 572 key "si"; 573 leaf si{ 574 type uint16; 575 description 576 "BIER set identifier."; 577 } 578 leaf in-bift-id{ 579 type uint32; 580 description 581 "BIER in-bift-id."; 582 } 583 uses bfr-nbr; 584 description 585 "The BIRT based on the key set identifier"; 586 } 587 description 588 "The BIRT based on the key set identifier & bitstringlength"; 589 } 590 description 591 "The information of the BIRT."; 592 } 594 } 595 } 597 augment "/rt:routing/rt:control-plane-protocols/" 598 + "rt:control-plane-protocol/ospf:ospf" { 599 when "../rt:type = 'ospf:ospfv2' or 600 ../rt:type = 'ospf:ospfv3'" { 601 description 602 "This augments the ospf routing protocol when used"; 603 } 604 description 605 "This augments ospf protocol configuration with bier."; 606 container bier-ospf-cfg{ 607 uses bier-protocol-extensions; 608 description 609 "Control of bier advertisement and reception."; 610 } 611 } 613 augment "/rt:routing/rt:control-plane-protocols/" 614 +"rt:control-plane-protocol/isis:isis"{ 615 when "/rt:routing/rt:control-plane-protocols/"+ 616 "rt:control-plane-protocol/rt:type = 'isis:isis'" { 617 description 618 "This augment ISIS routing protocol when used"; 619 } 620 description 621 "This augments ISIS protocol configuration with bier."; 622 container bier-isis-cfg{ 623 uses bier-protocol-extensions; 624 description 625 "Control of bier advertisement and reception."; 627 } 628 } 630 /* Notifications */ 631 notification bfr-id-collision{ 632 leaf bfr-id{ 633 type uint16; 634 description 635 "The type for bfr identifier"; 636 } 638 description 639 "BFR ID received in the controlplane that caused BFR ID collision."; 640 } 642 notification bfr-zero{ 643 leaf ipv4-bfr-prefix{ 644 type inet:ipv4-prefix; 645 description 646 "BIER ipv4 bfr prefix"; 647 } 648 leaf ipv6-bfr-prefix{ 649 type inet:ipv6-prefix; 650 description 651 "BIER ipv6 bfr prefix"; 652 } 653 description 654 "Invalid value associated with prefix"; 655 } 657 notification sub-domain-id-collision{ 658 leaf sub-domain-id { 659 type uint16; 660 description 661 "The type for sub-domain-id"; 662 } 663 leaf mt-id{ 664 type uint16; 665 description 666 "Multi-topology ID"; 667 } 668 description 669 "Sub domain ID received in the controlplane that caused Sub domain ID collision"; 670 } 671 } 673 675 7. Security Considerations 677 TBD. 679 8. Acknowledgements 681 We would like to thank IJsbrand Wijnands, Reshad Rahman ,Giles Heron, 682 Senthil Dhanaraj ,Benchong xu and jingrong Xie for their comments and 683 support of this work. 685 9. IANA Considerations 687 This document requires no IANA Actions. Please remove this section 688 before RFC publication. 690 10. Normative References 692 [I-D.ietf-isis-yang-isis-cfg] 693 Litkowski, S., Yeung, D., Lindem, A., Zhang, Z., and L. 694 Lhotka, "YANG Data Model for IS-IS Protocol", draft-ietf- 695 isis-yang-isis-cfg-42 (work in progress), October 2019. 697 [I-D.ietf-mpls-base-yang] 698 Saad, T., Raza, K., Gandhi, R., Liu, X., and V. Beeram, "A 699 YANG Data Model for MPLS Base", draft-ietf-mpls-base- 700 yang-15 (work in progress), August 2020. 702 [I-D.ietf-mpls-static-yang] 703 Saad, T., Gandhi, R., Liu, X., Beeram, V., and I. Bryskin, 704 "A YANG Data Model for MPLS Static LSPs", draft-ietf-mpls- 705 static-yang-11 (work in progress), April 2020. 707 [I-D.ietf-ospf-yang] 708 Yeung, D., Qu, Y., Zhang, Z., Chen, I., and A. Lindem, 709 "YANG Data Model for OSPF Protocol", draft-ietf-ospf- 710 yang-29 (work in progress), October 2019. 712 [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for 713 the Network Configuration Protocol (NETCONF)", RFC 6020, 714 DOI 10.17487/RFC6020, October 2010, 715 . 717 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 718 and A. Bierman, Ed., "Network Configuration Protocol 719 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 720 . 722 [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", 723 RFC 6991, DOI 10.17487/RFC6991, July 2013, 724 . 726 [RFC7223] Bjorklund, M., "A YANG Data Model for Interface 727 Management", RFC 7223, DOI 10.17487/RFC7223, May 2014, 728 . 730 [RFC8022] Lhotka, L. and A. Lindem, "A YANG Data Model for Routing 731 Management", RFC 8022, DOI 10.17487/RFC8022, November 732 2016, . 734 [RFC8279] Wijnands, IJ., Ed., Rosen, E., Ed., Dolganow, A., 735 Przygienda, T., and S. Aldrin, "Multicast Using Bit Index 736 Explicit Replication (BIER)", RFC 8279, 737 DOI 10.17487/RFC8279, November 2017, 738 . 740 [RFC8296] Wijnands, IJ., Ed., Rosen, E., Ed., Dolganow, A., 741 Tantsura, J., Aldrin, S., and I. Meilik, "Encapsulation 742 for Bit Index Explicit Replication (BIER) in MPLS and Non- 743 MPLS Networks", RFC 8296, DOI 10.17487/RFC8296, January 744 2018, . 746 [RFC8401] Ginsberg, L., Ed., Przygienda, T., Aldrin, S., and Z. 747 Zhang, "Bit Index Explicit Replication (BIER) Support via 748 IS-IS", RFC 8401, DOI 10.17487/RFC8401, June 2018, 749 . 751 [RFC8444] Psenak, P., Ed., Kumar, N., Wijnands, IJ., Dolganow, A., 752 Przygienda, T., Zhang, J., and S. Aldrin, "OSPFv2 753 Extensions for Bit Index Explicit Replication (BIER)", 754 RFC 8444, DOI 10.17487/RFC8444, November 2018, 755 . 757 Authors' Addresses 759 Ran Chen 760 ZTE Corporation 761 No.50 Software Avenue,Yuhuatai District 762 Nanjing, Jiangsu Province 210012 763 China 765 Phone: +86 025 88014636 766 Email: chen.ran@zte.com.cn 768 Fangwei Hu 769 Individual 770 No.889 Bibo Rd 771 Shanghai 201203 772 China 774 Email: hufwei@gmail.com 776 Zheng Zhang 777 ZTE Corporation 778 No.50 Software Avenue,Yuhuatai District 779 Nanjing, Jiangsu Province 210012 780 China 782 Email: zhang.zheng@zte.com.cn 784 Xianxian Dai 785 ZTE Corporation 786 No.50 Software Avenue,Yuhuatai District 787 Nanjing, Jiangsu Province 210012 788 China 790 Email: Dai.xianxian@zte.com.cn 792 Mahesh Sivakumar 793 Juniper networks 794 1133 Innovation Way 795 Sunnyvale, CALIFORNIA 94089 796 United States 798 Email: sivakumar.mahesh@gmail.com