idnits 2.17.00 (12 Aug 2021) /tmp/idnits10947/draft-keyupate-idr-bgp-ext-yang-00.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 16 instances of too long lines in the document, the longest one being 11 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 250 has weird spacing: '...ra Jain dhja...' == The document seems to contain a disclaimer for pre-RFC5378 work, but was first submitted on or after 10 November 2008. The disclaimer is usually necessary only for documents that revise or obsolete older RFCs, and that take significant amounts of text from those RFCs. If you can contact all authors of the source material and they are willing to grant the BCP78 rights to the IETF Trust, you can and should remove the disclaimer. Otherwise, the disclaimer is needed and you can ignore this comment. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (July 8, 2016) is 2136 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-netmod-routing-cfg' is defined on line 609, but no explicit reference was found in the text == Unused Reference: 'RFC2547' is defined on line 627, but no explicit reference was found in the text == Unused Reference: 'RFC4364' is defined on line 636, but no explicit reference was found in the text == Unused Reference: 'RFC4760' is defined on line 640, but no explicit reference was found in the text == Unused Reference: 'RFC7224' is defined on line 655, but no explicit reference was found in the text == Unused Reference: 'RFC5492' is defined on line 666, but no explicit reference was found in the text == Outdated reference: A later version (-13) exists of draft-ietf-idr-bgp-model-01 == Outdated reference: draft-ietf-netmod-routing-cfg has been published as RFC 8022 ** Downref: Normative reference to an Informational RFC: RFC 2519 ** Obsolete normative reference: RFC 2547 (Obsoleted by RFC 4364) Summary: 3 errors (**), 0 flaws (~~), 11 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 IDR Working Group K. Patel 3 Internet-Draft D. Jain 4 Intended status: Standards Track Cisco 5 Expires: January 9, 2017 S. Hares 6 Huawei 7 July 8, 2016 9 Yang Data Model for BGP extended features 10 draft-keyupate-idr-bgp-ext-yang-00.txt 12 Abstract 14 This document defines a YANG data model that can be used to configure 15 and manage BGP features which are not covered in the base BGP YANG 16 data model. 18 Status of This Memo 20 This Internet-Draft is submitted in full conformance with the 21 provisions of BCP 78 and BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF). Note that other groups may also distribute 25 working documents as Internet-Drafts. The list of current Internet- 26 Drafts is at http://datatracker.ietf.org/drafts/current/. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 This Internet-Draft will expire on January 9, 2017. 35 Copyright Notice 37 Copyright (c) 2016 IETF Trust and the persons identified as the 38 document authors. All rights reserved. 40 This document is subject to BCP 78 and the IETF Trust's Legal 41 Provisions Relating to IETF Documents 42 (http://trustee.ietf.org/license-info) in effect on the date of 43 publication of this document. Please review these documents 44 carefully, as they describe your rights and restrictions with respect 45 to this document. Code Components extracted from this document must 46 include Simplified BSD License text as described in Section 4.e of 47 the Trust Legal Provisions and are provided without warranty as 48 described in the Simplified BSD License. 50 This document may contain material from IETF Documents or IETF 51 Contributions published or made publicly available before November 52 10, 2008. The person(s) controlling the copyright in some of this 53 material may not have granted the IETF Trust the right to allow 54 modifications of such material outside the IETF Standards Process. 55 Without obtaining an adequate license from the person(s) controlling 56 the copyright in such materials, this document may not be modified 57 outside the IETF Standards Process, and derivative works of it may 58 not be created outside the IETF Standards Process, except to format 59 it for publication as an RFC or to translate it into languages other 60 than English. 62 Table of Contents 64 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 65 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 66 2. Definitions and Acronyms . . . . . . . . . . . . . . . . . . 3 67 3. BGP extended features . . . . . . . . . . . . . . . . . . . . 3 68 3.1. AIGP . . . . . . . . . . . . . . . . . . . . . . . . . . 3 69 3.2. Aggregate routes . . . . . . . . . . . . . . . . . . . . 4 70 3.3. DMZ link bandwidth . . . . . . . . . . . . . . . . . . . 4 71 3.4. Network . . . . . . . . . . . . . . . . . . . . . . . . . 4 72 3.5. Dampening . . . . . . . . . . . . . . . . . . . . . . . . 4 73 4. Yang model . . . . . . . . . . . . . . . . . . . . . . . . . 4 74 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 75 6. Security Considerations . . . . . . . . . . . . . . . . . . . 13 76 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 13 77 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 13 78 8.1. Normative References . . . . . . . . . . . . . . . . . . 13 79 8.2. Informative References . . . . . . . . . . . . . . . . . 15 80 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 15 82 1. Introduction 84 YANG [RFC6020] is a data definition language that was introduced to 85 define the contents of a conceptual data store that allows networked 86 devices to be managed using NETCONF [RFC6241]. YANG is proving 87 relevant beyond its initial confines, as bindings to other interfaces 88 (e.g. ReST) and encodings other than XML (e.g. JSON) are being 89 defined. Furthermore, YANG data models can be used as the basis of 90 implementation for other interfaces, such as CLI and programmatic 91 APIs. 93 This document defines a YANG data model that can be used to configure 94 and manage BGP features which are not covered in the base model 95 [I-D.ietf-idr-bgp-model]. This model is defined by augmenting the 96 applicable containers from the base BGP model. 98 1.1. Requirements Language 100 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 101 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 102 document are to be interpreted as described in RFC 2119 [RFC2119]. 104 2. Definitions and Acronyms 106 AF: Address Family 108 AIGP: Accumulated IGP 110 AS: Autonomous System 112 BGP: Border Gateway Protocol 114 DMZ: Demilitarized zone. Used in context of DMZ link bandwidth for a 115 link that connects two single hop eBGP peers. 117 IGP: Interior Gatewate Protocol 119 MED(med): Multi Exit Discriminator 121 NETCONF: Network Configuration Protocol 123 ReST: Representational State Transfer, a style of stateless interface 124 and protocol that is generally carried over HTTP 126 YANG: Data definition language for NETCONF 128 3. BGP extended features 130 This yang model covers a number of BGP extended features by 131 augmenting BGP base model defiend in [I-D.ietf-idr-bgp-model]. These 132 features are described below. This model is expected to grow with 133 more such features in future. 135 3.1. AIGP 137 The Accumulated IGP Metric Attribute for BGP is an optional non- 138 transitive BGP path attribute and is specified in [RFC7311]. 139 Configuration to enable and set the parameters for AIGP are 140 applicable per address family per neighbor granularity. These are 141 defined by agumenting AF containers under neighbor and peer-group 142 from base BGP model [I-D.ietf-idr-bgp-model]. 144 3.2. Aggregate routes 146 This refers to the BGP specific configuration for enabling mechanisms 147 for route aggregation as per [RFC4271] [RFC2519] . These parameters 148 are modeled as new leafs augmenting global address family containers 149 from the BGP base yang model [I-D.ietf-idr-bgp-model]. 151 3.3. DMZ link bandwidth 153 The BGP link bandwidth feature is used to advertise the bandwidth of 154 an autonomous system exit link as an extended community [TODO: 155 reference]. Configuration to enable DMZ link bandwidth extended 156 community is modeled by augmenting BGP neighbor and peer-group 157 containers defined in [I-D.ietf-idr-bgp-model]. 159 3.4. Network 161 Leafs to add network in BGP routing table. BGP global address family 162 container from the base BGP model [I-D.ietf-idr-bgp-model] is 163 agumented for this purpose. 165 3.5. Dampening 167 Configration parameters for BGP dampening behavior as defined in 168 [RFC2439]. These parameters are defined under BGP global address 169 family mode. 171 4. Yang model 173 module: ietf-bgp-extensions 174 augment /bgp:bgp/bgp:global: 175 augment /bgp:bgp/bgp:global/bgp:afi-safis/bgp:afi-safi: 176 +--rw aggregate-addr 177 | +--rw aggregate-address? inet:ip-address 178 | +--rw summary-only? boolean 179 | +--rw as-set? boolean 180 | +--rw as-confed-set? boolean 181 | +--rw route-policy? string 182 +--rw aggregate-timer 183 | +--rw enable? boolean 184 | +--rw threshold? uint16 185 +--rw network 186 | +--rw network? inet:ip-address 187 | +--rw policy? string 188 +--rw bgp-dampening 189 | +--rw half-time? uint8 190 | +--rw reuse-limit? uint16 191 | +--rw supresss-limit? uint16 192 | +--rw max-supress-time? uint8 193 | +--rw policy? string 194 | ... 196 +--rw auto-summary? boolean 197 +--rw advertise-best-external? boolean 199 augment /bgp:bgp/bgp:neighbors/bgp:neighbor: 200 +--rw propagate-dmzlink-bw? boolean 202 augment /bgp:bgp/bgp:neighbors/bgp:neighbor/bgp:afi-safis/bgp:afi-safi: 203 +--rw aigp 204 | +--rw enable? boolean 205 | +--rw send-med? boolean 206 | +--rw send-cost-community 207 | +--rw id? uint32 208 | +--rw igp-cost-transitive? boolean 209 | +--rw point-of-insertion? enumeration 210 +--rw soft-reconfig? enumeration 212 augment /bgp:bgp/bgp:peer-groups/bgp:peer-group: 213 +--rw propagate-dmzlink-bw? boolean 215 augment /bgp:bgp/bgp:peer-groups/bgp:peer-group/bgp:afi-safis/bgp:afi-safi: 216 +--rw aigp 217 | +--rw enable? boolean 218 | +--rw send-med? boolean 219 | +--rw send-cost-community 220 | +--rw id? uint32 221 | +--rw igp-cost-transitive? boolean 222 | +--rw point-of-insertion? enumeration 223 +--rw soft-reconfig? enumeration 225 file "ietf-bgp-extensions@2016-07-08.yang" 227 module ietf-bgp-extensions { 228 namespace "urn:ietf:params:xml:ns:yang:ietf-bgp-extensions"; 229 // replace with IANA namespace when assigned 231 prefix bgp-ext; 233 import ietf-inet-types { 234 prefix inet; 236 } 238 import ietf-bgp { 239 prefix bgp; 240 revision-date 2016-01-06; 241 } 243 organization 244 "Cisco Systems 245 170 West Tasman Drive 246 San Jose, CA 95134-1706 247 USA"; 248 contact 249 "Keyur Patel keyupate@cisco.com 250 Dhanendra Jain dhjain@cisco.com 251 Susan Hares shares@ndzh.com"; 253 description 254 "This YANG module defines the extensions to the base BGP yang 255 model common across all of the vendor implementations of the 256 protocol. It is intended that the model will be extended by 257 vendors to define vendor-specific models. 259 Terms and Acronyms 261 AIGP (aigp): Accumulated IGP 263 BGP (bgp): Border Gateway Protocol 265 IGP (igp): Interior Gateway Protocol 267 IP (ip): Internet Protocol 269 IPv4 (ipv4):Internet Protocol Version 4 271 IPv6 (ipv6): Internet Protocol Version 6 273 MED(med): Multi Exit Discriminator 275 MTU (mtu) Maximum Transmission Unit 277 "; 279 revision 2016-07-08 { 280 description 281 "Initial revision."; 283 reference 284 "RFC XXXX: A YANG Data Model for BGP extended features"; 285 } 287 // 288 // AIGP parameters used in global mode and neighbor AF mode. 289 // 290 grouping bgp-aigp { 291 description 292 "A set of configuration parameters applicable for AIGP configuration"; 293 container aigp { 294 description "AIGP configuration parameters"; 295 leaf enable { 296 type boolean; 297 description "Enable AIGP"; 298 } 299 leaf send-med { 300 type boolean; 301 description "Send AIGP value in MED"; 302 } 303 container send-cost-community { 304 description "Send AIGP value in Cost Community"; 305 leaf id { 306 type uint32; 307 description "Cost Community ID"; 308 } 309 leaf igp-cost-transitive { 310 type boolean; 311 description "Enable transitive cost community"; 312 } 313 leaf point-of-insertion { 314 type enumeration { 315 enum igp-cost { 316 description "Cost community is used after IGP distance to next-hop"; 317 } 318 enum pre-bestpath { 319 description "Cost community is first step in best-path calculation"; 320 } 321 } 322 description "Point of insertion for best-path calculation"; 323 } 324 } 325 } 326 } 328 // 329 // DMZ link bandwidth params 330 // 331 grouping bgp-dmz-link-bw { 332 description 333 "A set of configuration parameters for DMZ link bandwidth"; 334 leaf propagate-dmzlink-bw { 335 type boolean; 336 description 337 "Propagate the DMZ link bandwidth."; 338 } 339 } 341 // 342 // BGP dampening params 343 // 344 grouping bgp-dampening-params { 345 description "BGP dampening parameters"; 346 container bgp-dampening { 347 description 348 "BGP Route Flap Dampening."; 350 leaf half-time { 351 type uint8 { 352 range "1..45"; 353 } 354 description 355 "Half Time (in minutes) to reduce the penalty 356 assigned to a route by half."; 357 } 359 leaf reuse-limit { 360 type uint16 { 361 range "1..20000"; 362 } 363 description 364 "A configurable numeric value that is compared with the penalty. 365 If the penalty is less than the reuse limit, a suppressed route 366 that is up will no longer be suppressed. "; 367 } 369 leaf supresss-limit { 370 type uint16 { 371 range "1..20000"; 372 } 373 description 374 "A configurable numeric value that is compared with the penalty. 375 If the penalty is greater than the suppress limit, 376 the route is suppressed"; 377 } 378 leaf max-supress-time { 379 type uint8 { 380 range "1..255"; 381 } 382 description 383 "The longest amount of time, in minutes, that a route can be suppressed."; 384 } 385 leaf policy { 386 type string ; //TBD leafref to policy model 387 description 388 "Policy to specify criteria for dampening"; 389 } 390 } 391 } 393 // 394 // Grouping for Aggregate address 395 // 396 grouping bgp-aggregate-addr { 397 description "BGP aggregate address parameters grouping"; 398 container aggregate-addr { 399 description "Aggregate address configuration"; 400 leaf aggregate-address { 401 type inet:ip-address; 402 description 403 "Configure BGP aggregate address."; 404 } 405 leaf summary-only { 406 type boolean; 407 description "Filter more specific routes from updates"; 408 } 409 leaf as-set { 410 type boolean; 411 description "Generate AS set path information"; 412 } 413 leaf as-confed-set { 414 type boolean; 415 description "Generate AS confed set path information"; 416 } 417 leaf route-policy { 418 type string; 419 description "Policy to filter routes and specify conditions"; 420 } 421 } 422 } 424 // 425 // Grouping for soft reconfig 426 // 427 grouping soft-reconfig { 428 description "Soft reconfig parameters. Configuring this enables storing 429 of routes as received by this node, prior to applying 430 inbound route-policy"; 431 leaf soft-reconfig { 432 type enumeration { 433 enum "always" { 434 description "Use soft reconfig database upon neighbor reset even 435 if route refresh is configured"; 436 } 437 enum "backup" { 438 description "Use soft reconfig database as backup to route refresh"; 439 } 440 } 441 description "Enable storing of unprocessed routes as received by this node"; 442 } 443 } 445 // 446 // Grouping for all AF extensions. 447 // 448 grouping bgp-af-extension-cfg { 449 description 450 "Grouping for configuration parameters which are applicable 451 to all address families of the BGP router."; 453 // Aggregate related 454 uses bgp-aggregate-addr; 456 // Aggregate Timer 457 container aggregate-timer { 458 description 459 "Configure aggregation timer to specify time interval at which BGP routes 460 will be aggregated for route aggregation."; 461 leaf enable { 462 type boolean; 463 default "true"; 464 description "Enable aggregate timer"; 465 } 466 leaf threshold { 467 type uint16 { 468 range "6..60"; 469 } 470 description "Threshold value in seconds"; 471 } 472 } 473 //Network 474 container network { 475 description "Add networks to BGP table"; 476 leaf network { 477 type inet:ip-address; 478 description 479 "Specify a network to announce via BGP."; 480 } 481 leaf policy { 482 type string; //TBD leaf to policy model. 483 description "Modify route attribute as per policy"; 484 } 485 } 487 // Dampening 488 uses bgp-dampening-params; 490 //Other leafs 491 leaf auto-summary { 492 type boolean; 493 description 494 "Enable automatic network number summarization"; 495 } 496 // Best external 497 leaf advertise-best-external { 498 type boolean; 499 description 500 "Advertise best external path to the internal peers."; 501 } 502 } 504 // Global mode extensions can go here. 505 grouping bgp-gbl-extension-cfg { 506 description "BGP process global extensions grouping"; 507 // BGP process global extensions here. 508 } 510 // Global address family specific extensions. 511 grouping bgp-gbl-af-extension-cfg { 512 description "BGP global address family specific extensions"; 514 //AF extensions common to all AFs 515 uses bgp-af-extension-cfg; 516 } 518 // Neighbor mode extensions. 519 grouping bgp-nbr-extension-cfg { 520 description "BGP neighbor specific extensions"; 521 //NBR extensions go here 522 uses bgp-dmz-link-bw; 523 } 525 // Neighbor address family specific extensions. 526 grouping bgp-nbr-af-extension-cfg { 527 description "BGP neighbor address-family specific extensions"; 528 // NBR-AF extensions go here 529 uses bgp-aigp ; 530 uses soft-reconfig; 531 } 533 //----------------------------------- 534 // Augment BGP model in various places. 535 //------------------------------------ 537 // BGP Global parameters 538 augment "/bgp:bgp/bgp:global" { 539 description "BGP global mode specific extensions"; 540 //add BGP global extensions here 541 uses bgp-gbl-extension-cfg; 542 } 544 // BGP Global Address Family Specific 545 augment "/bgp:bgp/bgp:global/bgp:afi-safis/bgp:afi-safi" { 546 description "BGP global address family mode specific extensions"; 547 //add BGP global AF extensions here 548 uses bgp-gbl-af-extension-cfg; 549 } 551 //BGP Neighbor Specific 552 augment "/bgp:bgp/bgp:neighbors/bgp:neighbor" { 553 description "BGP neighbor mode specific extensions"; 554 // add nbr specific extensions here 555 uses bgp-nbr-extension-cfg; 556 } 558 //BGP Neighbor address-family Specific 559 augment "/bgp:bgp/bgp:neighbors/bgp:neighbor/bgp:afi-safis/bgp:afi-safi" { 560 description "BGP neighbor address family mode specific extensions"; 561 // add nbr AFI-SAFI specific extensions here. 562 uses bgp-nbr-af-extension-cfg; 563 } 565 // BGP Neighbor Groups specific 566 augment "/bgp:bgp/bgp:peer-groups/bgp:peer-group" { 567 description "BGP peer-group mode specific extensions"; 568 // add nbr specific extensions here 569 uses bgp-nbr-extension-cfg; 570 } 572 // BGP Neighbor Group address-family Specific. 573 augment "/bgp:bgp/bgp:peer-groups/bgp:peer-group/bgp:afi-safis/bgp:afi-safi" { 574 description "BGP peer-group address family mode specific extensions"; 575 // add nbr AFI-SAFI specific extensions here. 576 uses bgp-nbr-af-extension-cfg; 577 } 578 } 580 582 5. IANA Considerations 584 6. Security Considerations 586 The transport protocol used for sending the BGP configuration data 587 MUST support authentication and SHOULD support encryption. The data- 588 model by itself does not create any security implications. 590 This draft does not change any underlying security issues inherent in 591 the base BGP model [I-D.ietf-idr-bgp-model], that it augments to 592 define yang model for extented features. 594 7. Acknowledgements 596 The authors would like to thank TBD for their detail reviews and 597 comments. 599 8. References 601 8.1. Normative References 603 [I-D.ietf-idr-bgp-model] 604 Shaikh, A., Shakir, R., Patel, K., Hares, S., D'Souza, K., 605 Bansal, D., Clemm, A., Zhdankin, A., Jethanandani, M., and 606 X. Liu, "BGP Model for Service Provider Networks", draft- 607 ietf-idr-bgp-model-01 (work in progress), January 2016. 609 [I-D.ietf-netmod-routing-cfg] 610 Lhotka, L., "A YANG Data Model for Routing Management", 611 draft-ietf-netmod-routing-cfg-15 (work in progress), May 612 2014. 614 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 615 Requirement Levels", BCP 14, RFC 2119, 616 DOI 10.17487/RFC2119, March 1997, 617 . 619 [RFC2439] Villamizar, C., Chandra, R., and R. Govindan, "BGP Route 620 Flap Damping", RFC 2439, DOI 10.17487/RFC2439, November 621 1998, . 623 [RFC2519] Chen, E. and J. Stewart, "A Framework for Inter-Domain 624 Route Aggregation", RFC 2519, DOI 10.17487/RFC2519, 625 February 1999, . 627 [RFC2547] Rosen, E. and Y. Rekhter, "BGP/MPLS VPNs", RFC 2547, 628 DOI 10.17487/RFC2547, March 1999, 629 . 631 [RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A 632 Border Gateway Protocol 4 (BGP-4)", RFC 4271, 633 DOI 10.17487/RFC4271, January 2006, 634 . 636 [RFC4364] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private 637 Networks (VPNs)", RFC 4364, DOI 10.17487/RFC4364, February 638 2006, . 640 [RFC4760] Bates, T., Chandra, R., Katz, D., and Y. Rekhter, 641 "Multiprotocol Extensions for BGP-4", RFC 4760, 642 DOI 10.17487/RFC4760, January 2007, 643 . 645 [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for 646 the Network Configuration Protocol (NETCONF)", RFC 6020, 647 DOI 10.17487/RFC6020, October 2010, 648 . 650 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 651 and A. Bierman, Ed., "Network Configuration Protocol 652 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 653 . 655 [RFC7224] Bjorklund, M., "IANA Interface Type YANG Module", 656 RFC 7224, DOI 10.17487/RFC7224, May 2014, 657 . 659 [RFC7311] Mohapatra, P., Fernando, R., Rosen, E., and J. Uttaro, 660 "The Accumulated IGP Metric Attribute for BGP", RFC 7311, 661 DOI 10.17487/RFC7311, August 2014, 662 . 664 8.2. Informative References 666 [RFC5492] Scudder, J. and R. Chandra, "Capabilities Advertisement 667 with BGP-4", RFC 5492, DOI 10.17487/RFC5492, February 668 2009, . 670 Authors' Addresses 672 Keyur Patel 673 Cisco 674 170 W. Tasman Drive 675 San Jose, CA 95134 676 USA 678 Email: keyupate@cisco.com 680 Dhanendra Jain 681 Cisco 682 170 W. Tasman Drive 683 San Jose, CA 95134 684 USA 686 Email: dhjain@cisco.com 688 Susan Hares 689 Huawei 690 7453 Hickory Hill 691 Saline, MI 48176 692 USA 694 Email: shares@ndzh.com