idnits 2.17.1 draft-vandevelde-idr-ipv6-flowspec-imp-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 40 instances of too long lines in the document, the longest one being 20 characters in excess of 72. ** The abstract seems to contain references ([I-D.ietf-idr-flow-spec-v6]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. == There are 2 instances of lines with private range IPv4 addresses in the document. If these are generic example addresses, they should be changed to use any of the ranges defined in RFC 6890 (or successor): 192.0.2.x, 198.51.100.x or 203.0.113.x. == There are 4 instances of lines with non-RFC3849-compliant IPv6 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 240 has weird spacing: '...nt-type first...' == Line 333 has weird spacing: '...nt-type first...' == The document doesn't use any RFC 2119 keywords, yet has text resembling RFC 2119 boilerplate text. -- The document date (July 2, 2015) is 3214 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Unused Reference: 'RFC4271' is defined on line 518, but no explicit reference was found in the text == Outdated reference: A later version (-22) exists of draft-ietf-idr-flow-spec-v6-06 Summary: 2 errors (**), 0 flaws (~~), 8 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 IDR G. Van de Velde 3 Internet-Draft W. Henderickx 4 Intended status: Informational Alcatel-Lucent 5 Expires: January 3, 2016 N. Fevrier 6 A. Karch 7 Cisco Systems 8 A. Grewal 9 Juniper Networks 10 July 2, 2015 12 Dissemination of Flow Specification Rules for IPv6 Implementation Report 13 draft-vandevelde-idr-ipv6-flowspec-imp-02 15 Abstract 17 This document is an implementation report for the BGP Flow 18 Specification Rules for IPv6 as defined in 19 [I-D.ietf-idr-flow-spec-v6]. The respondents are experts with the 20 implementations they reported on, and their responses are considered 21 authoritative for the implementations for which their responses 22 represent. 24 Status of This Memo 26 This Internet-Draft is submitted in full conformance with the 27 provisions of BCP 78 and BCP 79. 29 Internet-Drafts are working documents of the Internet Engineering 30 Task Force (IETF). Note that other groups may also distribute 31 working documents as Internet-Drafts. The list of current Internet- 32 Drafts is at http://datatracker.ietf.org/drafts/current/. 34 Internet-Drafts are draft documents valid for a maximum of six months 35 and may be updated, replaced, or obsoleted by other documents at any 36 time. It is inappropriate to use Internet-Drafts as reference 37 material or to cite them other than as "work in progress." 39 This Internet-Draft will expire on January 3, 2016. 41 Copyright Notice 43 Copyright (c) 2015 IETF Trust and the persons identified as the 44 document authors. All rights reserved. 46 This document is subject to BCP 78 and the IETF Trust's Legal 47 Provisions Relating to IETF Documents 48 (http://trustee.ietf.org/license-info) in effect on the date of 49 publication of this document. Please review these documents 50 carefully, as they describe your rights and restrictions with respect 51 to this document. Code Components extracted from this document must 52 include Simplified BSD License text as described in Section 4.e of 53 the Trust Legal Provisions and are provided without warranty as 54 described in the Simplified BSD License. 56 Table of Contents 58 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 59 2. Requirements Language . . . . . . . . . . . . . . . . . . . . 2 60 3. Implementation Forms . . . . . . . . . . . . . . . . . . . . 3 61 4. NLRI and Extended Community subtypes . . . . . . . . . . . . 3 62 5. Interoperable Implementations . . . . . . . . . . . . . . . . 6 63 5.1. Cisco Systems - Alcatel-Lucent . . . . . . . . . . . . . 6 64 5.2. Cisco Systems - Juniper Networks . . . . . . . . . . . . 8 65 5.3. Juniper Networks - Cisco Systems . . . . . . . . . . . . 10 66 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 67 7. Security Considerations . . . . . . . . . . . . . . . . . . . 12 68 8. Privacy Considerations . . . . . . . . . . . . . . . . . . . 12 69 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 13 70 10. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . 13 71 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 13 72 11.1. Normative References . . . . . . . . . . . . . . . . . . 13 73 11.2. Informative References . . . . . . . . . . . . . . . . . 13 74 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13 76 1. Introduction 78 In order to share Flow Specification Rules for IPv6 using the BGP 79 routing protocol a new BGP Network Layer Reachability Information 80 (NLRI) encoding format is required. 82 This document provides an implementation report for the BGP 83 Dissemination of Flow Specification Rules for IPv6 NLRI Format as 84 defined in [I-D.ietf-idr-flow-spec-v6]. 86 The editors did not verify the accuracy of the information provided 87 by respondents or by any alternative means. The respondents are 88 experts with the implementations they reported on, and their 89 responses are considered authoritative for the implementations for 90 which their responses represent. 92 2. Requirements Language 94 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 95 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" are to 96 be interpreted as described in [RFC2119] only when they appear in all 97 upper case. They may also appear in lower or mixed case as English 98 words, without any normative meaning. 100 3. Implementation Forms 102 Contact and implementation information for person filling out this 103 form: 105 Cisco 106 Name: Nicolas Fevrier 107 Email: nifevrie@cisco.com 108 Vendor: Cisco Systems, Inc. 109 Release: IOS-XR 5.3.1 110 Protocol Role: Sender, Receiver 112 Alcatel-Lucent 113 Name: Wim Henderickx 114 Email: wim.henderickx@alcatel-lucent.com 115 Vendor: Alcatel-Lucent, Inc. 116 Release: R12R4 117 Protocol Role: Sender, Receiver 119 Juniper 120 Name: Ashutosh Grewal 121 Email: agrewal@juniper.net 122 Vendor: Juniper Networks, Inc. 123 Release: JunOS 15.2 124 Protocol Role: Sender, Receiver 126 4. NLRI and Extended Community subtypes 128 Does the implementation support the Network Layer Reachability (NLRI) 129 subtypes as described in Section 3 and 4 of 130 [I-D.ietf-idr-flow-spec-v6]. 132 o N1: Type 1 - Destination IPv6 Prefix 134 o N2: Type 2 - Source IPv6 Prefix 136 o N3: Type 3 - Next Header 138 o N4: Type 4 - Port 140 o N5: Type 5 - Destination port 142 o N6: Type 6 - Source port 144 o N7: Type 7 - ICMP type 145 o N8: Type 8 - ICMP code 147 o N9: Type 9 - TCP flags 149 o N10: Type 10 - Packet length 151 o N11: Type 11 - DSCP (Diffserv Code Point) 153 o N12: Type 12 - Fragment 155 o N13: Type 13 - Flow Label 157 o E1: Extended Community - traffic-rate 159 o E2: Extended Community - traffic-action 161 o E3: Extended Community - redirect 163 o E4: Extended Community - traffic-marking 164 +--------+--------+-------+---------+ 165 | | Cisco | ALU | Juniper | 166 +--------+--------+-------+---------+ 167 | Rcv.N1 | YES | YES | YES | 168 | Snd.N1 | YES | YES | YES | 169 | Rcv.N2 | YES | YES | YES | 170 | Snd.N2 | YES | YES | YES | 171 | Rcv.N3 | YES | YES | YES | 172 | Snd.N3 | YES | YES | YES | 173 | Rcv.N4 | YES | YES | YES | 174 | Snd.N4 | YES | YES | YES | 175 | Rcv.N5 | YES | YES | YES | 176 | Snd.N5 | YES | YES | YES | 177 | Rcv.N6 | YES | YES | YES | 178 | Snd.N6 | YES | YES | YES | 179 | Rcv.N7 | YES | YES | YES | 180 | Snd.N7 | YES | YES | YES | 181 | Rcv.N8 | YES | YES | YES | 182 | Snd.N8 | YES | YES | YES | 183 | Rcv.N9 | YES | YES | YES | 184 | Snd.N9 | YES | YES | YES | 185 | Rcv.N10| YES | YES | YES | 186 | Snd.N10| YES | YES | YES | 187 | Rcv.N11| YES | YES | YES | 188 | Snd.N11| YES | YES | YES | 189 | Rcv.N12| YES | YES | YES | 190 | Snd.N12| YES | YES | YES | 191 | Rcv.N13| YES | YES | YES | 192 | Snd.N13| YES | YES | YES | 193 | Rcv.E1 | YES | YES | YES | 194 | Snd.E1 | YES | YES | YES | 195 | Rcv.E2 | YES | YES | YES | 196 | Snd.E2 | YES | YES | YES | 197 | Rcv.E3 | YES | YES | YES | 198 | Snd.E3 | YES | YES | YES | 199 | Rcv.E4 | YES | YES | YES | 200 | Snd.E4 | YES | YES | YES | 201 +--------+--------+-------+---------+ 203 Yes 205 o Rcv: BGP speaker can receive the information into the BGP process 207 o Snd: BGP speaker can relay the information from the BGP process 209 No 210 o Rcv: BGP speaker can not receive the information into the BGP 211 process 213 o Snd: BGP speaker can not relay the information from the BGP 214 process 216 5. Interoperable Implementations 218 Summary of executed Interop tests between different implementations 220 5.1. Cisco Systems - Alcatel-Lucent 222 This Interop test was between a Cisco router and a Alcatel-Lucent 223 router. Between the two BGP devices an iBGP session is established. 225 The following IPv6 Flow Specification NLRI is constructed using the 226 Cisco router as IPv6 Flow Specification controller: 228 ! 229 class-map type traffic match-all InteropMatchList 230 match destination-address ipv6 2001:2::3/128 231 match source-address ipv6 2002:2::3/128 232 match destination-port 1-5 7-11 13-18 20-25 27-31 233 match source-port 33-37 39-43 45-50 53-58 60-65 234 match ipv6 icmp-type 35 235 match ipv6 icmp-code 55 236 match packet length 120-130 135-140 145-160 165-200 205-225 237 match dscp 1-10 11-20 22-30 32-40 52-60 238 match tcp-flag 240 any 239 match protocol 6-71 73-80 85-90 95-105 110-115 240 match fragment-type first-fragment 241 end-class-map 242 ! 243 ! 244 policy-map type pbr InteropPolicy 245 class type traffic InteropMatchList 246 police rate 200 bps 247 ! 248 redirect nexthop 2001::1 249 set dscp 45 250 ! 251 class type traffic class-default 252 ! 253 end-policy-map 254 ! 255 flowspec 256 address-family ipv6 257 service-policy type pbr InteropPolicy 258 ! 259 ! 261 This results with the following Flow Specification Extended 262 communities and IPv6 Flow Specification NLRI: 264 AFI: IPv6 265 NLRI (Hex dump) : 266 0x0180002001000200000000000000000000000302800020020002000000000000 267 0000000000030303064547034945500355455a035f4569036ec573050301450503 268 07450b030d451203144519031bc51f06032145250327452b032d45320335453a03 269 3cc5410781230881370980f00a037845820387458c039145a003a545c803cdc5e1 270 0b0301450a030b45140316451e032045280334c53c0c8104 271 Actions :Traffic-rate: 200 bps DSCP: 45 272 Nexthop: 2001::1 (policy.1.InteropPolicy.InteropMatchList) 274 The above IPv6 Flow Specification rule is correctly received by the 275 Alcatel-Lucent BGP speaker and is reflected as follows on the device: 277 *A:PE26>show>router>bgp# routes flow-ipv6 278 =============================================================================== 279 BGP Router ID:195.207.5.200 AS:65117 Local AS:65117 280 =============================================================================== 281 Legend - 282 Status codes : u - used, s - suppressed, h - history, d - decayed, * - valid 283 l - leaked, x - stale, > - best, b - backup 284 Origin codes : i - IGP, e - EGP, ? - incomplete 285 =============================================================================== 286 BGP FLOW IPV6 Routes 287 =============================================================================== 288 Flag Network Nexthop LocalPref MED 289 As-Path 290 ------------------------------------------------------------------------------- 291 u*>i -- 2001::1 100 None 292 No As-Path 294 Community Action: ext:800:0 295 Community Action: rate-limit: 65117:1103626240 296 Community Action: mark-dscp: 45 297 NLRI Subcomponents: 298 Dest Pref : 2001:2::3/128 offset 0 299 Src Pref : 2002:2::3/128 offset 0 300 Ip Proto : [ >= 6 ] and [ <= 71 ] or [ >= 73 ] and [ <= 80 ] or [ >= 301 Dest Port : [ >= 1 ] and [ <= 5 ] or [ >= 7 ] and [ <= 11 ] or [ >= 13 302 Src Port : [ >= 33 ] and [ <= 37 ] or [ >= 39 ] and [ <= 43 ] or [ >= 303 ICMP Type : [ == 35 ] 304 ICMP Code : [ == 55 ] 305 TCP Flags : [ 240 ] 306 TCP Flags : [ 240 ] 307 DSCP : [ >= 1 ] and [ <= 10 ] or [ >= 11 ] and [ <= 20 ] or [ >= 308 Frag : [ == 4 ] 309 ------------------------------------------------------------------------------- 310 Routes : 1 311 =============================================================================== 313 5.2. Cisco Systems - Juniper Networks 315 This Interop test was between a Cisco router and a Juniper router. 316 Between the two BGP devices an iBGP session is established. 318 The following IPv6 Flow Specification NLRI is constructed using the 319 Cisco router as IPv6 Flow Specification controller: 321 ! 322 class-map type traffic match-all InteropMatchList 323 match destination-address ipv6 2001:2::3/128 324 match source-address ipv6 2002:2::3/128 325 match destination-port 1-5 7-11 13-18 20-25 27-31 326 match source-port 33-37 39-43 45-50 53-58 60-65 327 match ipv6 icmp-type 35 328 match ipv6 icmp-code 55 329 match packet length 120-130 135-140 145-160 165-200 205-225 330 match dscp 1-10 11-20 22-30 32-40 52-60 331 match tcp-flag 240 any 332 match protocol 6-71 73-80 85-90 95-105 110-115 333 match fragment-type first-fragment 334 end-class-map 335 ! 336 ! 337 policy-map type pbr InteropPolicy 338 class type traffic InteropMatchList 339 police rate 200 bps 340 ! 341 redirect nexthop 2001::1 342 set dscp 45 343 ! 344 class type traffic class-default 345 ! 346 end-policy-map 347 ! 348 flowspec 349 address-family ipv6 350 service-policy type pbr InteropPolicy 351 ! 352 ! 354 This results with the following Flow Specification Extended 355 communities and IPv6 Flow Specification NLRI: 357 AFI: IPv6 358 NLRI (Hex dump) : 359 0x0180002001000200000000000000000000000302800020020002000000000000 360 0000000000030303064547034945500355455a035f4569036ec573050301450503 361 07450b030d451203144519031bc51f06032145250327452b032d45320335453a03 362 3cc5410781230881370980f00a037845820387458c039145a003a545c803cdc5e1 363 0b0301450a030b45140316451e032045280334c53c0c8104 364 Actions :Traffic-rate: 200 bps DSCP: 45 365 Nexthop: 2001::1 (policy.1.InteropPolicy.InteropMatchList) 367 The above IPv6 Flow Specification rule is correctly received by the 368 Juniper BGP speaker and is reflected as follows on the device: 370 root@sdn-st-mx480-b> show route table inet6flow.0 extensive 371 inet6flow.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden) 372 2001:2::3/128,2002:2::3/128,proto>=6&<=71,>=73&<=80,>=85&<=90,>=95&<=105,>=110&<=115, 373 dstport>=1&<=5,>=7&<=11,>=13&<=18,>=20&<=25,>=27&<=31, 374 srcport>=33&<=37,>=39&<=43,>=45&<=50,>=53&<=58,>=60&<=65,icmp6-type=35,icmp6-code=55, 375 tcp-flag:f0,len>=120&<=130,>=135&<=140,>=145&<=160,>=165&<=200,>=205&<=225, 376 dscp>=1&<=10,>=11&<=20,>=22&<=30,>=32&<=40,>=52&<=60,frag=04/term:N/A 377 (1 entry, 0 announced) 378 *BGP Preference: 170/-101 379 Next hop type: Fictitious, Next hop index: 0 380 Address: 0x95542a4 381 Next-hop reference count: 2 382 State: 383 Local AS: 65117 Peer AS: 65117 384 Age: 1:58 385 Validation State: unverified 386 Task: BGP_65117.10.0.0.2 387 AS path: I 388 Communities: unknown iana 800 traffic-rate:65117:25 traffic-marking:45 389 Accepted 390 Localpref: 100 391 Router ID: 10.0.0.2 392 Jun 12 15:37:57.990156 BGP RECV 10.0.0.2+179 -> 10.0.0.1+58360 393 Jun 12 15:37:57.990202 BGP RECV message type 2 (Update) length 245 394 Jun 12 15:37:57.990228 BGP RECV Update PDU length 245 395 Jun 12 15:37:57.990260 BGP RECV flags 0x90 code MP_reach(14): AFI/SAFI 2/133 396 Jun 12 15:37:57.990287 -akg- nhlen from packet : 16 397 Jun 12 15:37:57.990316 BGP RECV nhop zero-len len 16 398 Jun 12 15:37:57.990388 BGP RECV 2001:2::3/128,2002:2::3/128,proto>=6&<=71,>=73&<=80, 399 >=85&<=90,>=95&<=105,>=110&<=115,dstport>=1&<=5,>=7&<=11,>=13&<=18,>=20&<=25,>=27&<=31, 400 srcport>=33&<=37,>=39&<=43,>=45&<=50,>=53&<=58,>=60&<=65,icmp6-type=35,icmp6-code=55, 401 tcp-flag:f0,len>=120&<=130,>=135&<=140,>=145&<=160,>=165&<=200,>=205&<=225, 402 dscp>=1&<=10,>=11&<=20,>=22&<=30,>=32&<=40,>=52&<=60,frag=04/1240 403 Jun 12 15:37:57.990418 BGP RECV flags 0x40 code Origin(1): IGP 404 Jun 12 15:37:57.990446 BGP RECV flags 0x40 code ASPath(2) length 0: 405 Jun 12 15:37:57.990471 BGP RECV flags 0x40 code LocalPref(5): 100 406 Jun 12 15:37:57.990517 BGP RECV flags 0xc0 code Extended Communities(16): 408 5.3. Juniper Networks - Cisco Systems 410 This Interop test was between a Juniper router and a Cisco router. 411 Between the two BGP devices an iBGP session is established. 413 The following IPv6 Flow Specification NLRI is constructed using the 414 Juniper router as IPv6 Flow Specification controller: 416 ! 417 root@sdn-st-mx480-b# show routing-options 418 rib inet6.0 { 419 flow { 420 route flowroute { 421 match { 422 destination abcd::1/128; 423 source abcd::2/128; 424 protocol [ 6-71 73-80 85-90 95-105 110-115 ]; 425 destination-port [ 1-5 7-11 13-18 20-25 27-31 ]; 426 source-port [ 33-37 39-43 45-50 53-58 60-65 ]; 427 icmp6-type 35; 428 icmp6-code 55; 429 tcp-flags 240; 430 packet-length [ 120-130 135-140 145-160 165-200 205-225 ]; 431 dscp [ 1-10 11-20 22-30 32-40 52-60 ]; 432 fragment first-fragment; 433 flow-label [ ( 22 || 77 ) 11 33 89 ]; 434 } 435 then { 436 rate-limit 9600; 437 mark 45; 438 } 439 } 440 } 441 } 443 The above IPv6 Flow Specification rule is correctly received by the 444 Cisco BGP speaker and is reflected as follows on the device: 446 RP/0/RSP0/CPU0:ASR9k-FlowSpec-Interop#sh flowspec ipv6 detail 447 AFI: IPv6 448 Flow :Dest:abcd::1/0-128,Source:abcd::2/0-128, 449 NH:>=6&<=71|>=73&<=80|>=85&<=90|>=95&<=105|>=110&<=115, 450 DPort:>=1&<=5|>=7&<=11|>=13&<=18|>=20&<=25|>=27&<=31, 451 SPort:>=33&<=37|>=39&<=43|>=45&<=50|>=53&<=58|>=60&<=65,ICMPType:=35,ICMPCode:=55, 452 TCPFlags:~0xf0,Length:>=120&<=130|>=135&<=140|>=145&<=160|>=165&<=200|>=205&<=225, 453 DSCP:>=1&<=10|>=11&<=20|>=22&<=30|>=32&<=40|>=52&<=60,Frag:~FF, 454 FlowLabel:=22|=77|=11|=33|=89 455 Actions :Traffic-rate: 9600 bps DSCP: 45 (bgp.1) 456 Statistics (packets/bytes) 457 Matched : 0/0 458 Dropped : 0/0 459 RP/0/RSP0/CPU0:ASR9k-FlowSpec-Interop#sh flowspec ipv6 nlri 460 AFI: IPv6 461 NLRI (Hex dump) : 0x018000abcd0000000000000000000000000001028000abcd0000000000 462 0000000000000000020303064547034945500355455a035f4569036ec57305030145050307450b030d45 463 1203144519031bc51f06032145250327452b032d45320335453a033cc5410781230881370980f00a0378 464 45820387458c039145a003a545c803cdc5e10b0301450a030b45140316451e032045280334c53c0c8004 465 0d0116014d010b01218159 466 Actions :Traffic-rate: 9600 bps DSCP: 45 (bgp.1) 468 RP/0/RSP0/CPU0:ASR9k-FlowSpec-Interop# 470 6. IANA Considerations 472 This document makes no request of IANA. 474 Note to RFC Editor: The IANA has requested that this section remain 475 in the document upon publication as an RFC. This note to the RFC 476 Editor, however, may be removed. 478 7. Security Considerations 480 No new security issues are introduced to the BGP defined in 481 Dissemination of Flow Specification Rules for IPv6 482 [I-D.ietf-idr-flow-spec-v6]. 484 8. Privacy Considerations 486 No new privacy issues are introduced to the BGP defined in 487 Dissemination of Flow Specification Rules for IPv6 488 [I-D.ietf-idr-flow-spec-v6]. 490 9. Acknowledgements 492 The authors would like to thank Hyojeong Kim, Bertrand Duvivier, R. 493 Divya, and Adam Simpson. 495 10. Change Log 497 Initial Version: 8 October 2014 499 -01 Version: 20 May 2015 501 -02 Version: 2 July 2015 503 11. References 505 11.1. Normative References 507 [I-D.ietf-idr-flow-spec-v6] 508 Raszuk, R., Pithawala, B., McPherson, D., and A. Andy, 509 "Dissemination of Flow Specification Rules for IPv6", 510 draft-ietf-idr-flow-spec-v6-06 (work in progress), 511 November 2014. 513 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 514 Requirement Levels", BCP 14, RFC 2119, March 1997. 516 11.2. Informative References 518 [RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway 519 Protocol 4 (BGP-4)", RFC 4271, January 2006. 521 Authors' Addresses 523 Gunter Van de Velde 524 Alcatel-Lucent 525 Copernicuslaan 50 526 Antwerpen 2018 527 Belgium 529 Email: gunter.van_de_velde@alcatel-lucent.com 531 Wim Henderickx 532 Alcatel-Lucent 534 Email: wim.henderickx@alcatel-lucent.be 535 Nicolas Fevrier 536 Cisco Systems 537 11 Rue Camille Desmoulins 538 Issy-les-Koulineaux 92130 539 France 541 Email: nifevrie@cisco.com 543 Andy Karch 544 Cisco Systems 545 170 W. Tasman Drive 546 San Jose, CA 95124 95134 547 USA 549 Email: akarch@cisco.com 551 Ashutosh Grewal 552 Juniper Networks 553 1133 Innovation Way 554 Sunnyvale, CA 94089 94089 555 USA 557 Email: agrewal@juniper.net