idnits 2.17.1 draft-zhao-pim-igmp-mld-proxy-yang-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There are 2 instances of too long lines in the document, the longest one being 3 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 156 has weird spacing: '...ce-name if:...' == Line 160 has weird spacing: '...address ine...' == Line 168 has weird spacing: '...ce-name if:...' == Line 175 has weird spacing: '...ce-name if:...' == Line 179 has weird spacing: '...address ine...' == (1 more instance...) == The document doesn't use any RFC 2119 keywords, yet has text resembling RFC 2119 boilerplate text. -- The document date (July 03, 2019) is 1731 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) == Missing Reference: 'RFC2119' is mentioned on line 95, but not defined == Missing Reference: 'RFC6241' is mentioned on line 588, but not defined == Missing Reference: 'RFC8040' is mentioned on line 588, but not defined == Missing Reference: 'RFC7950' is mentioned on line 645, but not defined == Missing Reference: 'RFC6242' is mentioned on line 590, but not defined == Missing Reference: 'RFC5246' is mentioned on line 592, but not defined ** Obsolete undefined reference: RFC 5246 (Obsoleted by RFC 8446) == Missing Reference: 'RFC6536' is mentioned on line 594, but not defined ** Obsolete undefined reference: RFC 6536 (Obsoleted by RFC 8341) == Missing Reference: 'RFC3688' is mentioned on line 632, but not defined == Unused Reference: 'RFC2236' is defined on line 661, but no explicit reference was found in the text == Unused Reference: 'RFC2710' is defined on line 664, but no explicit reference was found in the text == Unused Reference: 'RFC3376' is defined on line 667, but no explicit reference was found in the text == Unused Reference: 'RFC3810' is defined on line 671, but no explicit reference was found in the text == Unused Reference: 'RFC4604' is defined on line 674, but no explicit reference was found in the text == Unused Reference: 'RFC4607' is defined on line 684, but no explicit reference was found in the text == Unused Reference: 'RFC6991' is defined on line 691, but no explicit reference was found in the text == Unused Reference: 'RFC8343' is defined on line 697, but no explicit reference was found in the text Summary: 3 errors (**), 0 flaws (~~), 24 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 PIM Working Group H. Zhao 2 Internet Draft Ericsson 3 Intended status: Standards Track X. Liu 4 Expires: January 02, 2020 Volta 5 Y. Liu 6 Huawei 7 M. Panchanathan 8 Cisco 9 M. Sivakumar 10 Juniper 12 July 03, 2019 14 A Yang Data Model for IGMP/MLD Proxy 15 draft-zhao-pim-igmp-mld-proxy-yang-03.txt 17 Abstract 19 This document defines a YANG data model that can be used to 20 configure and manage Internet Group Management Protocol (IGMP) or 21 Multicast Listener Discovery (MLD) proxy devices. The YANG module in 22 this document conforms to Network Management Datastore Architecture 23 (NMDA). 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), its areas, and its working groups. Note that 32 other groups may also distribute working documents as Internet- 33 Drafts. 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 The list of current Internet-Drafts can be accessed at 41 http://www.ietf.org/ietf/1id-abstracts.txt 42 The list of Internet-Draft Shadow Directories can be accessed at 43 http://www.ietf.org/shadow.html 45 This Internet-Draft will expire on January 02, 2020. 47 Copyright Notice 49 Copyright (c) 2019 IETF Trust and the persons identified as the 50 document authors. All rights reserved. 52 This document is subject to BCP 78 and the IETF Trust's Legal 53 Provisions Relating to IETF Documents 54 (http://trustee.ietf.org/license-info) in effect on the date of 55 publication of this document. Please review these documents 56 carefully, as they describe your rights and restrictions with respect 57 to this document. Code Components extracted from this document must 58 include Simplified BSD License text as described in Section 4.e of 59 the Trust Legal Provisions and are provided without warranty as 60 described in the Simplified BSD License. 62 Table of Contents 64 1. Introduction...................................................3 65 1.1. Terminology...............................................3 66 1.2. Tree Diagrams.............................................3 67 2. Design of Data Model...........................................3 68 2.1. Overview..................................................4 69 2.2. Augment /rt:routing/rt:control-plane-protocols/rt:control- 70 plane-protocol.................................................4 71 3. IGMP/MLD Proxy YANG Module.....................................5 72 4. Security Considerations.......................................13 73 5. IANA Considerations...........................................14 74 6. Normative References..........................................15 75 Authors' Addresses...............................................17 77 1. Introduction 79 This document defines a YANG [RFC6020] data model for the management of 80 Internet Group Management Protocol (IGMP) or Multicast Listener 81 Discovery (MLD) proxy devices. 83 The YANG module in this document conforms to the Network Management 84 Datastore Architecture defined in [RFC8342]. The "Network Management 85 Datastore Architecture" (NMDA) adds the ability to inspect the current 86 operational values for configuration, allowing clients to use identical 87 paths for retrieving the configured values and the operational values. 89 1.1. Terminology 91 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 92 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 93 "OPTIONAL" in this document are to be interpreted as described in BCP 14 94 [RFC2119]. 96 The terminology for describing YANG data models is found in [RFC6020]. 98 1.2. Tree Diagrams 100 A simplified graphical representation of the data model is used in this 101 document. The meaning of the symbols in these diagrams is as follows: 103 o Brackets "[" and "]" enclose list keys. 105 o Abbreviations before data node names: "rw" means configuration 106 (read-write), and "ro" means state data (read-only). 108 o Symbols after data node names: "?" means an optional node, "!" 109 means a presence container, and "*" denotes a list and leaf-list. 111 o Parentheses enclose choice and case nodes, and case nodes are also 112 marked with a colon (":"). 114 o Ellipsis ("...") stands for contents of subtrees that are not 115 shown. 117 2. Design of Data Model 119 The model covers Considerations for Internet Group Management Protocol 120 (IGMP) / Multicast Listener Discovery (MLD) - Based Multicast Forwarding 121 ("IGMP/MLD Proxying") [RFC4605]. 123 The goal of this document is to define a data model that provides a 124 common user interface to IGMP/MLD proxy. This document provides freedom 125 for vendors to adapt this data model to their product implementations. 127 2.1. Overview 129 The IGMP/MLD proxy YANG module defined in this document has all the 130 common building blocks for the IGMP/MLD proxy protocol. 132 The YANG module augments /rt:routing/rt:control-plane- 133 protocols/rt:control-plane-protocol to enable IGMP/MLD proxy and 134 configure other related parameters. 136 This YANG module follows the Guidelines for YANG Module Authors (NMDA) 137 [draft-dsdt-nmda-guidelines-01]. This NMDA ("Network Management 138 Datastore Architecture") architecture provides an architectural 139 framework for datastores as they are used by network management 140 protocols such as NETCONF [RFC6241], RESTCONF [RFC8040] and the YANG 141 [RFC7950] data modeling language. 143 2.2. Augment /rt:routing/rt:control-plane-protocols/rt:control-plane- 144 protocol 146 The YANG module augments /rt:routing/rt:control-plane- 147 protocols/rt:control-plane-protocol to enable IGMP/MLD proxy under the 148 upstream interface. There is also a constraint to make sure the upstream 149 interface for IGMP/MLD proxy should not be configured PIM. 151 module: ietf-igmp-mld-proxy 152 augment /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol: 153 +--rw igmp-proxy {feature-igmp-proxy}? 154 +--rw interfaces 155 +--rw interface* [interface-name] 156 +--rw interface-name if:interface-ref 157 +--rw version? uint8 158 +--rw enable? boolean 159 +--ro group* [group-address] 160 +--ro group-address inet:ipv4-address 161 +--ro up-time? uint32 162 +--ro filter-mode? enumeration 163 +--ro source* [source-address] 164 +--ro source-address inet:ipv4-address 165 +--ro up-time? uint32 166 +--ro filter-mode? enumeration 167 +--ro downstream-interface* [interface-name] 168 +--ro interface-name if:interface-ref 169 +--ro filter-mode? enumeration 171 augment /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol: 172 +--rw mld-proxy {feature-mld-proxy}? 173 +--rw interfaces 174 +--rw interface* [interface-name] 175 +--rw interface-name if:interface-ref 176 +--rw version? uint8 177 +--rw enable? boolean 178 +--ro group* [group-address] 179 +--ro group-address inet:ipv6-address 180 +--ro up-time? uint32 181 +--ro filter-mode? enumeration 182 +--ro source* [source-address] 183 +--ro source-address inet:ipv6-address 184 +--ro up-time? uint32 185 +--ro filter-mode? enumeration 186 +--ro downstream-interface* [interface-name] 187 +--ro interface-name if:interface-ref 188 +--ro filter-mode? enumeration 190 3. IGMP/MLD Proxy YANG Module 192 file ietf-igmp-mld-proxy@2019-07-03.yang 193 module ietf-igmp-mld-proxy { 194 yang-version 1.1; 195 namespace "urn:ietf:params:xml:ns:yang:ietf-igmp-mld-proxy"; 196 // replace with IANA namespace when assigned 197 prefix imp; 199 import ietf-inet-types { 200 prefix inet; 201 } 203 import ietf-interfaces { 204 prefix if; 205 } 207 import ietf-routing { 208 prefix rt; 209 } 211 import ietf-pim-base { 212 prefix pim-base; 213 } 215 organization 216 "IETF PIM Working Group"; 218 contact 219 "WG Web: 220 WG List: 222 Editors: Hongji Zhao 223 225 Xufeng Liu 226 228 Yisong Liu 229 231 Mani Panchanathan 232 234 Mahesh Sivakumar 235 237 "; 239 description 240 "The module defines a collection of YANG definitions common for 241 all Internet Group Management Protocol (IGMP) and Multicast 242 Listener Discovery (MLD) Proxy devices. 244 Copyright (c) 2019 IETF Trust and the persons identified as 245 authors of the code. All rights reserved. 247 Redistribution and use in source and binary forms, with or 248 without modification, is permitted pursuant to, and subject to 249 the license terms contained in, the Simplified BSD License set 250 forth in Section 4.c of the IETF Trust's Legal Provisions 251 Relating to IETF Documents 252 (http://trustee.ietf.org/license-info). 254 This version of this YANG module is part of RFC XXXX; see the 255 RFC itself for full legal notices."; 257 revision 2019-07-03 { 258 description 259 "Initial revision."; 260 reference 261 "RFC XXXX: A YANG Data Model for IGMP and MLD Proxy"; 262 } 264 /* 265 * Features 266 */ 268 feature feature-igmp-proxy { 269 description 270 "Support IGMP Proxy protocol."; 271 reference 272 "RFC 4605"; 273 } 275 feature feature-mld-proxy { 276 description 277 "Support MLD Proxy protocol."; 278 reference 279 "RFC 4605"; 280 } 282 /* 283 * Identities 284 */ 286 identity igmp-proxy { 287 base rt:control-plane-protocol; 288 description 289 "IGMP Proxy protocol"; 290 } 292 identity mld-proxy { 293 base rt:control-plane-protocol; 294 description 295 "MLD Proxy protocol"; 296 } 298 /* 299 * Typedefs 300 */ 302 /* 303 * Groupings 304 */ 306 grouping per-interface-config-attributes { 308 description "Config attributes under interface view"; 310 leaf enable { 311 type boolean; 312 default false; 313 description 314 "Set the value to true to enable IGMP/MLD proxy"; 315 } 317 } // per-interface-config-attributes 319 grouping state-group-attributes { 320 description 321 "State group attributes"; 323 leaf up-time { 324 type uint32; 325 units seconds; 326 description 327 "The elapsed time for (S,G) or (*,G)."; 328 } 330 leaf filter-mode { 331 type enumeration { 332 enum "include" { 333 description 334 "In include mode, reception of packets sent 335 to the specified multicast address is requested 336 only from those IP source addresses listed in the 337 source-list parameter"; 338 } 339 enum "exclude" { 340 description 341 "In exclude mode, reception of packets sent 342 to the given multicast address is requested 343 from all IP source addresses except those 344 listed in the source-list parameter."; 345 } 346 } 347 description 348 "Filter mode for a multicast group, 349 may be either include or exclude."; 350 } 351 } // state-group-attributes 353 /* augments */ 355 augment "/rt:routing/rt:control-plane-protocols"+ 356 "/rt:control-plane-protocol" { 358 description 359 "IGMP Proxy augmentation to routing control plane protocol 360 configuration and state."; 362 container igmp-proxy { 363 when 'derived-from-or-self(../rt:type, "imp:igmp-proxy")' { 364 description 365 "This container is only valid for IGMP Proxy protocol."; 366 } 367 if-feature feature-igmp-proxy; 368 description "IGMP proxy"; 369 container interfaces { 370 description 371 "Containing a list of upstream interfaces."; 373 list interface { 374 key "interface-name"; 375 description 376 "List of upstream interfaces."; 378 leaf interface-name { 379 type if:interface-ref; 380 must "not( current() = /rt:routing"+ 381 "/rt:control-plane-protocols/pim-base:pim"+ 382 "/pim-base:interfaces/pim-base:interface"+ 383 "/pim-base:name )" { 385 description 386 "The upstream interface for IGMP proxy 387 should not be configured PIM."; 388 } 389 description "The upstream interface name."; 390 } 392 leaf version { 393 type uint8 { 394 range "1..3"; 395 } 396 default 2; 397 description "IGMP version."; 398 } 400 uses per-interface-config-attributes; 402 list group { 403 key "group-address"; 404 config false; 405 description 406 "Multicast group membership information 407 that joined on the interface."; 409 leaf group-address { 410 type inet:ipv4-address; 411 description 412 "Multicast group address."; 413 } 415 uses state-group-attributes; 416 list source { 417 key "source-address"; 418 description 419 "List of multicast source information 420 of the multicast group."; 421 leaf source-address { 422 type inet:ipv4-address; 423 description 424 "Multicast source address"; 425 } 427 uses state-group-attributes; 429 list downstream-interface { 430 key "interface-name"; 431 description "The downstream interfaces list."; 432 leaf interface-name { 433 type if:interface-ref; 434 description 435 "Downstream interfaces for each upstream-interface"; 436 } 437 leaf filter-mode { 438 type enumeration { 439 enum "include" { 440 description 441 "In include mode, reception of packets sent 442 to the specified multicast address is requested 443 only from those IP source addresses listed in 444 the 445 source-list parameter"; 446 } 447 enum "exclude" { 448 description 449 "In exclude mode, reception of packets sent 450 to the given multicast address is requested 451 from all IP source addresses except those 452 listed in the source-list parameter."; 453 } 454 } 455 description 456 "Filter mode for a multicast group, 457 may be either include or exclude."; 458 } 459 } 460 } // list source 461 } // list group 462 } // interface 463 } // interfaces 464 } 465 } 466 augment "/rt:routing/rt:control-plane-protocols"+ 467 "/rt:control-plane-protocol" { 469 description 470 "MLD Proxy augmentation to routing control plane protocol 471 configuration and state."; 473 container mld-proxy { 474 when 'derived-from-or-self(../rt:type, "imp:mld-proxy")' { 475 description 476 "This container is only valid for MLD Proxy protocol."; 477 } 478 if-feature feature-mld-proxy; 479 description "MLD proxy"; 480 container interfaces { 481 description 482 "Containing a list of upstream interfaces."; 484 list interface { 485 key "interface-name"; 486 description 487 "List of upstream interfaces."; 489 leaf interface-name { 490 type if:interface-ref; 491 must "not( current() = /rt:routing"+ 492 "/rt:control-plane-protocols/pim-base:pim"+ 493 "/pim-base:interfaces/pim-base:interface"+ 494 "/pim-base:name )" { 496 description 497 "The upstream interface for MLD proxy 498 should not be configured PIM."; 499 } 500 description "The upstream interface name."; 501 } 503 leaf version { 504 type uint8 { 505 range "1..2"; 506 } 507 default 2; 508 description "MLD version."; 509 } 511 uses per-interface-config-attributes; 513 list group { 514 key "group-address"; 515 config false; 516 description 517 "Multicast group membership information 518 that joined on the interface."; 520 leaf group-address { 521 type inet:ipv6-address; 522 description 523 "Multicast group address."; 524 } 526 uses state-group-attributes; 528 list source { 529 key "source-address"; 530 description 531 "List of multicast source information 532 of the multicast group."; 533 leaf source-address { 534 type inet:ipv6-address; 535 description 536 "Multicast source address"; 537 } 539 uses state-group-attributes; 541 list downstream-interface { 542 key "interface-name"; 543 description "The downstream interfaces list."; 544 leaf interface-name { 545 type if:interface-ref; 546 description 547 "Downstream interfaces for each upstream-interface"; 548 } 549 leaf filter-mode { 550 type enumeration { 551 enum "include" { 552 description 553 "In include mode, reception of packets sent 554 to the specified multicast address is requested 555 only from those IP source addresses listed in 556 the 557 source-list parameter"; 558 } 559 enum "exclude" { 560 description 561 "In exclude mode, reception of packets sent 562 to the given multicast address is requested 563 from all IP source addresses except those 564 listed in the source-list parameter."; 565 } 566 } 567 description 568 "Filter mode for a multicast group, 569 may be either include or exclude."; 570 } 571 } 572 } // list source 573 } // list group 574 } // interface 575 } // interfaces 576 } 577 } 579 /* RPCs */ 581 } 582 584 4. Security Considerations 586 The YANG module specified in this document defines a schema for data 587 that is designed to be accessed via network management protocols such 588 as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer 589 is the secure transport layer, and the mandatory-to-implement secure 590 transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer 591 is HTTPS, and the mandatory-to-implement secure transport is TLS 592 [RFC5246]. 594 The NETCONF access control model [RFC6536] provides the means to 595 restrict access for particular NETCONF or RESTCONF users to a 596 preconfigured subset of all available NETCONF or RESTCONF protocol 597 operations and content. 599 There are a number of data nodes defined in this YANG module that are 600 writable/creatable/deletable (i.e., config true, which is the 601 default). These data nodes may be considered sensitive or vulnerable 602 in some network environments. Write operations (e.g., edit-config) to 603 these data nodes without proper protection can have a negative effect 604 on network operations. These are the subtrees and data nodes and 605 their sensitivity/vulnerability: 607 /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol 609 Unauthorized access to any data node of these subtrees can adversely 610 affect the IGMP/MLD proxy subsystem of both the local device and the 611 network. This may lead to network malfunctions, delivery of packets 612 to inappropriate destinations, and other problems. 614 Some of the readable data nodes in this YANG module may be considered 615 sensitive or vulnerable in some network environments. It is thus 616 important to control read access (e.g., via get, get-config, or 617 notification) to these data nodes. These are the subtrees and data 618 nodes and their sensitivity/vulnerability: 620 /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol 622 Unauthorized access to any data node of these subtrees can disclose 623 the operational state information of IGMP/MLD proxy on this device. 625 5. IANA Considerations 627 RFC Ed.: In this section, replace all occurrences of 'XXXX' with the 628 actual RFC number (and remove this note). 630 This document registers the following namespace URIs in the IETF XML 632 registry [RFC3688]: 634 -------------------------------------------------------------------- 636 URI: urn:ietf:params:xml:ns:yang:ietf-igmp-mld-proxy 638 Registrant Contact: The IESG. 640 XML: N/A, the requested URI is an XML namespace. 642 -------------------------------------------------------------------- 644 This document registers the following YANG modules in the YANG 645 Module Names registry [RFC7950]: 647 -------------------------------------------------------------------- 649 name: ietf-igmp-mld-proxy 651 namespace: urn:ietf:params:xml:ns:yang:ietf-igmp-mld-proxy 653 prefix: imp 655 reference: RFC XXXX 657 -------------------------------------------------------------------- 659 6. Normative References 661 [RFC2236] Fenner, W., "Internet Group Management Protocol, Version 662 2", RFC 2236, November 1997. 664 [RFC2710] Deering, S., Fenner, W., and B. Haberman, "Multicast 665 Listener Discovery (MLD) for IPv6", RFC 2710, October 1999. 667 [RFC3376] Cain, B., Deering, S., Kouvelas, I., Fenner, B., and A. 668 Thyagarajan, "Internet Group Management Protocol, Version 669 3", RFC 3376, October 2002. 671 [RFC3810] Vida, R. and L. Costa, "Multicast Listener Discovery 672 Version 2 (MLDv2) for IPv6", RFC 3810, June 2004. 674 [RFC4604] Holbrook, H., Cain, B., and B. Haberman, "Using Internet 675 Group Management Protocol Version 3 (IGMPv3) and Multicast 676 Listener Discovery Protocol Version 2 (MLDv2) for Source- 677 Specific Multicast", RFC 4604, August 2006. 679 [RFC4605] B. Fenner, H. He, B. Haberman and H. Sandick, "Internet 680 Group Management Protocol (IGMP) / Multicast Listener 681 Discovery (MLD) - Based Multicast Forwarding ("IGMP/MLD 682 Proxying")", RFC 4605, August 2006. 684 [RFC4607] Holbrook, H. and B. Cain, "Source-Specific Multicast for 685 IP", RFC 4607, August 2006. 687 [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for 688 the Network Configuration Protocol (NETCONF)", RFC 6020, 689 October 2010. 691 [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", RFC 6991, 692 July 2013. 694 [RFC8342] M. Bjorklund and J. Schoenwaelder, "Network Management 695 Datastore Architecture (NMDA)", RFC 8342, March 2018. 697 [RFC8343] M. Bjorklund, "A YANG Data Model for Interface Management", 698 RFC 8343, March 2018. 700 [draft-ietf-pim-igmp-mld-yang-06] X. Liu, F. Guo, M. Sivakumar, P. 701 McAllister, A. Peter, "A YANG data model for Internet Group 702 Management Protocol (IGMP) and Multicast Listener Discovery 703 (MLD)", draft-ietf-pim-igmp-mld-yang-06, Oct 20, 2017. 705 [draft-dsdt-nmda-guidelines-01] M. Bjorklund, J. Schoenwaelder, P. 706 Shafer, K. Watsen, R. Wilton, "Guidelines for YANG Module 707 Authors (NMDA)", draft-dsdt-nmda-guidelines-01, May 2017 709 [draft-ietf-netmod-revised-datastores-03] M. Bjorklund, J. 710 Schoenwaelder, P. Shafer, K. Watsen, R. Wilton, "Network 711 Management Datastore Architecture", draft-ietf-netmod- 712 revised-datastores-03, July 3, 2017 714 Authors' Addresses 716 Hongji Zhao 717 Ericsson (China) Communications Company Ltd. 718 Ericsson Tower, No. 5 Lize East Street, 719 Chaoyang District Beijing 100102, P.R. China 720 Email: hongji.zhao@ericsson.com 722 Xufeng Liu 723 Volta Networks 724 USA 725 EMail: Xufeng.liu.ietf@gmail.com 727 Yisong Liu 728 Huawei Technologies 729 Huawei Bld., No.156 Beiqing Rd. 730 Beijing 100095 731 China 732 Email: liuyisong@huawei.com 734 Mani Panchanathan 735 Cisco 736 India 737 Email: mapancha@cisco.com 739 Mahesh Sivakumar 740 Juniper Networks 741 1133 Innovation Way 742 Sunnyvale, California 743 USA 744 EMail: sivakumar.mahesh@gmail.com