idnits 2.17.1 draft-zhao-pim-igmp-mld-proxy-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 : ---------------------------------------------------------------------------- ** There are 4 instances of too long lines in the document, the longest one being 66 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 (May 28, 2019) is 1793 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 582, but not defined == Missing Reference: 'RFC8040' is mentioned on line 582, but not defined == Missing Reference: 'RFC7950' is mentioned on line 638, but not defined == Missing Reference: 'RFC6242' is mentioned on line 584, but not defined == Missing Reference: 'RFC5246' is mentioned on line 586, but not defined ** Obsolete undefined reference: RFC 5246 (Obsoleted by RFC 8446) == Missing Reference: 'RFC6536' is mentioned on line 588, but not defined ** Obsolete undefined reference: RFC 6536 (Obsoleted by RFC 8341) == Missing Reference: 'RFC3688' is mentioned on line 625, but not defined == Unused Reference: 'RFC2236' is defined on line 654, but no explicit reference was found in the text == Unused Reference: 'RFC2710' is defined on line 657, but no explicit reference was found in the text == Unused Reference: 'RFC3376' is defined on line 660, but no explicit reference was found in the text == Unused Reference: 'RFC3810' is defined on line 664, but no explicit reference was found in the text == Unused Reference: 'RFC4604' is defined on line 667, but no explicit reference was found in the text == Unused Reference: 'RFC4607' is defined on line 677, but no explicit reference was found in the text == Unused Reference: 'RFC6991' is defined on line 684, but no explicit reference was found in the text == Unused Reference: 'RFC8343' is defined on line 690, 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: November 27, 2019 Volta 5 Y. Liu 6 Huawei 7 M. Panchanathan 8 Cisco 9 M. Sivakumar 10 Juniper 12 May 28, 2019 14 A Yang Data Model for IGMP/MLD Proxy 15 draft-zhao-pim-igmp-mld-proxy-yang-02.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 November 27, 2019. 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..........................................14 75 Authors' Addresses...............................................16 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-05-14.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-05-14 { 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 "current() != /rt:routing/rt:control-plane-protocols/pim-base:pim/pim-base:interfaces/pim-base:interface/pim-base:name" { 381 description 382 "The upstream interface for IGMP proxy 383 should not be configured PIM."; 384 } 385 description "The upstream interface name."; 386 } 388 leaf version { 389 type uint8 { 390 range "1..3"; 391 } 392 default 2; 393 description "IGMP version."; 394 } 396 uses per-interface-config-attributes; 398 list group { 399 key "group-address"; 400 config false; 401 description 402 "Multicast group membership information 403 that joined on the interface."; 405 leaf group-address { 406 type inet:ipv4-address; 407 description 408 "Multicast group address."; 409 } 411 uses state-group-attributes; 413 list source { 414 key "source-address"; 415 description 416 "List of multicast source information 417 of the multicast group."; 418 leaf source-address { 419 type inet:ipv4-address; 420 description 421 "Multicast source address"; 422 } 424 uses state-group-attributes; 426 list downstream-interface { 427 key "interface-name"; 428 description "The downstream interfaces list."; 429 leaf interface-name { 430 type if:interface-ref; 431 description 432 "Downstream interfaces for each upstream-interface"; 433 } 434 leaf filter-mode { 435 type enumeration { 436 enum "include" { 437 description 438 "In include mode, reception of packets sent 439 to the specified multicast address is requested 440 only from those IP source addresses listed in 441 the 442 source-list parameter"; 443 } 444 enum "exclude" { 445 description 446 "In exclude mode, reception of packets sent 447 to the given multicast address is requested 448 from all IP source addresses except those 449 listed in the source-list parameter."; 450 } 451 } 452 description 453 "Filter mode for a multicast group, 454 may be either include or exclude."; 455 } 456 } 457 } // list source 458 } // list group 459 } // interface 460 } // interfaces 461 } 462 } 464 augment "/rt:routing/rt:control-plane-protocols"+ 465 "/rt:control-plane-protocol" { 467 description 468 "MLD Proxy augmentation to routing control plane protocol 469 configuration and state."; 471 container mld-proxy { 472 when 'derived-from-or-self(../rt:type, "imp:mld-proxy")' { 473 description 474 "This container is only valid for MLD Proxy protocol."; 475 } 476 if-feature feature-mld-proxy; 477 description "MLD proxy"; 478 container interfaces { 479 description 480 "Containing a list of upstream interfaces."; 482 list interface { 483 key "interface-name"; 484 description 485 "List of upstream interfaces."; 487 leaf interface-name { 488 type if:interface-ref; 489 must "current() != /rt:routing/rt:control-plane-protocols/pim-base:pim/pim-base:interfaces/pim-base:interface/pim-base:name" { 490 description 491 "The upstream interface for MLD proxy 492 should not be configured PIM."; 493 } 494 description "The upstream interface name."; 495 } 497 leaf version { 498 type uint8 { 499 range "1..2"; 500 } 501 default 2; 502 description "MLD version."; 503 } 505 uses per-interface-config-attributes; 507 list group { 508 key "group-address"; 509 config false; 510 description 511 "Multicast group membership information 512 that joined on the interface."; 514 leaf group-address { 515 type inet:ipv6-address; 516 description 517 "Multicast group address."; 518 } 520 uses state-group-attributes; 522 list source { 523 key "source-address"; 524 description 525 "List of multicast source information 526 of the multicast group."; 527 leaf source-address { 528 type inet:ipv6-address; 529 description 530 "Multicast source address"; 531 } 533 uses state-group-attributes; 535 list downstream-interface { 536 key "interface-name"; 537 description "The downstream interfaces list."; 538 leaf interface-name { 539 type if:interface-ref; 540 description 541 "Downstream interfaces for each upstream-interface"; 542 } 543 leaf filter-mode { 544 type enumeration { 545 enum "include" { 546 description 547 "In include mode, reception of packets sent 548 to the specified multicast address is requested 549 only from those IP source addresses listed in 550 source-list parameter"; 551 } 552 enum "exclude" { 553 description 554 "In exclude mode, reception of packets sent 555 to the given multicast address is requested 556 from all IP source addresses except those 557 listed in the source-list parameter."; 558 } 559 } 560 description 561 "Filter mode for a multicast group, 562 may be either include or exclude."; 563 } 564 } 565 } // list source 567 } // list group 568 } // interface 569 } // interfaces 570 } 571 } 573 /* RPCs */ 575 } 576 578 4. Security Considerations 580 The YANG module specified in this document defines a schema for data 581 that is designed to be accessed via network management protocols such 582 as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer 583 is the secure transport layer, and the mandatory-to-implement secure 584 transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer 585 is HTTPS, and the mandatory-to-implement secure transport is TLS 586 [RFC5246]. 588 The NETCONF access control model [RFC6536] provides the means to 589 restrict access for particular NETCONF or RESTCONF users to a 590 preconfigured subset of all available NETCONF or RESTCONF protocol 591 operations and content. 593 There are a number of data nodes defined in this YANG module that are 594 writable/creatable/deletable (i.e., config true, which is the 595 default). These data nodes may be considered sensitive or vulnerable 596 in some network environments. Write operations (e.g., edit-config) to 597 these data nodes without proper protection can have a negative effect 598 on network operations. These are the subtrees and data nodes and 599 their sensitivity/vulnerability: 601 /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol 603 Unauthorized access to any data node of these subtrees can adversely 604 affect the IGMP/MLD proxy subsystem of both the local device and the 605 network. This may lead to network malfunctions, delivery of packets 606 to inappropriate destinations, and other problems. 608 Some of the readable data nodes in this YANG module may be considered 609 sensitive or vulnerable in some network environments. It is thus 610 important to control read access (e.g., via get, get-config, or 611 notification) to these data nodes. These are the subtrees and data 612 nodes and their sensitivity/vulnerability: 614 /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol 615 Unauthorized access to any data node of these subtrees can disclose 616 the operational state information of IGMP/MLD proxy on this device. 618 5. IANA Considerations 620 RFC Ed.: In this section, replace all occurrences of 'XXXX' with the 621 actual RFC number (and remove this note). 623 This document registers the following namespace URIs in the IETF XML 625 registry [RFC3688]: 627 -------------------------------------------------------------------- 629 URI: urn:ietf:params:xml:ns:yang:ietf-igmp-mld-proxy 631 Registrant Contact: The IESG. 633 XML: N/A, the requested URI is an XML namespace. 635 -------------------------------------------------------------------- 637 This document registers the following YANG modules in the YANG 638 Module Names registry [RFC7950]: 640 -------------------------------------------------------------------- 642 name: ietf-igmp-mld-proxy 644 namespace: urn:ietf:params:xml:ns:yang:ietf-igmp-mld-proxy 646 prefix: imp 648 reference: RFC XXXX 650 -------------------------------------------------------------------- 652 6. Normative References 654 [RFC2236] Fenner, W., "Internet Group Management Protocol, Version 655 2", RFC 2236, November 1997. 657 [RFC2710] Deering, S., Fenner, W., and B. Haberman, "Multicast 658 Listener Discovery (MLD) for IPv6", RFC 2710, October 1999. 660 [RFC3376] Cain, B., Deering, S., Kouvelas, I., Fenner, B., and A. 661 Thyagarajan, "Internet Group Management Protocol, Version 662 3", RFC 3376, October 2002. 664 [RFC3810] Vida, R. and L. Costa, "Multicast Listener Discovery 665 Version 2 (MLDv2) for IPv6", RFC 3810, June 2004. 667 [RFC4604] Holbrook, H., Cain, B., and B. Haberman, "Using Internet 668 Group Management Protocol Version 3 (IGMPv3) and Multicast 669 Listener Discovery Protocol Version 2 (MLDv2) for Source- 670 Specific Multicast", RFC 4604, August 2006. 672 [RFC4605] B. Fenner, H. He, B. Haberman and H. Sandick, "Internet 673 Group Management Protocol (IGMP) / Multicast Listener 674 Discovery (MLD) - Based Multicast Forwarding ("IGMP/MLD 675 Proxying")", RFC 4605, August 2006. 677 [RFC4607] Holbrook, H. and B. Cain, "Source-Specific Multicast for 678 IP", RFC 4607, August 2006. 680 [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for 681 the Network Configuration Protocol (NETCONF)", RFC 6020, 682 October 2010. 684 [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", RFC 6991, 685 July 2013. 687 [RFC8342] M. Bjorklund and J. Schoenwaelder, "Network Management 688 Datastore Architecture (NMDA)", RFC 8342, March 2018. 690 [RFC8343] M. Bjorklund, "A YANG Data Model for Interface Management", 691 RFC 8343, March 2018. 693 [draft-ietf-pim-igmp-mld-yang-06] X. Liu, F. Guo, M. Sivakumar, P. 694 McAllister, A. Peter, "A YANG data model for Internet Group 695 Management Protocol (IGMP) and Multicast Listener Discovery 696 (MLD)", draft-ietf-pim-igmp-mld-yang-06, Oct 20, 2017. 698 [draft-dsdt-nmda-guidelines-01] M. Bjorklund, J. Schoenwaelder, P. 699 Shafer, K. Watsen, R. Wilton, "Guidelines for YANG Module 700 Authors (NMDA)", draft-dsdt-nmda-guidelines-01, May 2017 702 [draft-ietf-netmod-revised-datastores-03] M. Bjorklund, J. 703 Schoenwaelder, P. Shafer, K. Watsen, R. Wilton, "Network 704 Management Datastore Architecture", draft-ietf-netmod- 705 revised-datastores-03, July 3, 2017 707 Authors' Addresses 709 Hongji Zhao 710 Ericsson (China) Communications Company Ltd. 711 Ericsson Tower, No. 5 Lize East Street, 712 Chaoyang District Beijing 100102, P.R. China 713 Email: hongji.zhao@ericsson.com 714 Xufeng Liu 715 Volta Networks 716 USA 717 EMail: Xufeng.liu.ietf@gmail.com 719 Yisong Liu 720 Huawei Technologies 721 Huawei Bld., No.156 Beiqing Rd. 722 Beijing 100095 723 China 724 Email: liuyisong@huawei.com 726 Mani Panchanathan 727 Cisco 728 India 729 Email: mapancha@cisco.com 731 Mahesh Sivakumar 732 Juniper Networks 733 1133 Innovation Way 734 Sunnyvale, California 735 USA 736 EMail: sivakumar.mahesh@gmail.com