idnits 2.17.00 (12 Aug 2021) /tmp/idnits48498/draft-raszuk-registered-wide-bgp-community-values-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 : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). -- The document date (October 16, 2010) is 4228 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: 'RFC3765' is mentioned on line 113, but not defined == Unused Reference: 'RFC2119' is defined on line 613, but no explicit reference was found in the text == Unused Reference: 'RFC4271' is defined on line 616, but no explicit reference was found in the text == Unused Reference: 'RFC4360' is defined on line 619, but no explicit reference was found in the text == Unused Reference: 'RFC1998' is defined on line 627, but no explicit reference was found in the text == Unused Reference: 'RFC4384' is defined on line 631, but no explicit reference was found in the text == Unused Reference: 'RFC4893' is defined on line 634, but no explicit reference was found in the text == Unused Reference: 'RFC5668' is defined on line 637, but no explicit reference was found in the text -- Obsolete informational reference (is this intentional?): RFC 4893 (Obsoleted by RFC 6793) Summary: 0 errors (**), 0 flaws (~~), 10 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 IDR Working Group R. Raszuk 3 Internet-Draft Cisco Systems 4 Intended status: Standards Track J. Haas 5 Expires: April 19, 2011 Juniper Networks 6 October 16, 2010 8 Registered Wide BGP Community Values 9 draft-raszuk-registered-wide-bgp-community-values-00 11 Abstract 13 Communicating various routing policies via route tagging plays an 14 important role in external BGP peering relations. The most common 15 tool used today to attach various information about routes is 16 realized with the use of BGP communities. Such information is 17 important for the peering AS to perform some mutually agreed actions 18 without the need to maintain a separate offline database for each 19 pair of prefix and an associated with it requested set of action 20 entries. 22 This document proposes to establish a new IANA maintained registry of 23 most commonly used Wide BGP Communities by network operators. Such 24 public registry will allow for easy refernece and clear 25 interpretation of the actions associated with received community 26 values. 28 Status of this Memo 30 This Internet-Draft is submitted in full conformance with the 31 provisions of BCP 78 and BCP 79. 33 Internet-Drafts are working documents of the Internet Engineering 34 Task Force (IETF). Note that other groups may also distribute 35 working documents as Internet-Drafts. The list of current Internet- 36 Drafts is at http://datatracker.ietf.org/drafts/current/. 38 Internet-Drafts are draft documents valid for a maximum of six months 39 and may be updated, replaced, or obsoleted by other documents at any 40 time. It is inappropriate to use Internet-Drafts as reference 41 material or to cite them other than as "work in progress." 43 This Internet-Draft will expire on April 19, 2011. 45 Copyright Notice 47 Copyright (c) 2010 IETF Trust and the persons identified as the 48 document authors. All rights reserved. 50 This document is subject to BCP 78 and the IETF Trust's Legal 51 Provisions Relating to IETF Documents 52 (http://trustee.ietf.org/license-info) in effect on the date of 53 publication of this document. Please review these documents 54 carefully, as they describe your rights and restrictions with respect 55 to this document. Code Components extracted from this document must 56 include Simplified BSD License text as described in Section 4.e of 57 the Trust Legal Provisions and are provided without warranty as 58 described in the Simplified BSD License. 60 Table of Contents 62 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 63 2. Globally significant pre-defined values . . . . . . . . . . . 3 64 2.1. Well Known Standard BGP Communities . . . . . . . . . . . 3 65 2.2. Registered pre-defined Wide BGP Communities . . . . . . . 3 66 2.2.1. General Registered Wide BGP Community Values . . . . . 4 67 2.2.2. Advertisement control Registered Wide BGP 68 Communities . . . . . . . . . . . . . . . . . . . . . 7 69 2.2.3. AS source marking Registered Wide BGP Communities . . 8 70 2.2.4. Return path influencing Registered Wide BGP 71 Communities . . . . . . . . . . . . . . . . . . . . . 10 72 2.2.5. AS_PATH modifying Registered Wide BGP Communities . . 10 73 2.2.6. Local Preference Registered Community . . . . . . . . 11 74 2.2.7. AS_PATH TTL Registered Community . . . . . . . . . . . 12 75 3. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 76 4. Security considerations . . . . . . . . . . . . . . . . . . . 13 77 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 78 6. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 14 79 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 15 80 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 16 81 8.1. Normative References . . . . . . . . . . . . . . . . . . . 16 82 8.2. Informative References . . . . . . . . . . . . . . . . . . 16 83 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 16 85 1. Introduction 87 RFC 1997 [RFC1997] defines a BGP Community Attribute to be used as a 88 tool to contain in BGP update message various additional information 89 about routes which may help to automate peering administration. As 90 defined in RFC 1997 [RFC1997] BGP Communities attribute consists of 91 one or more sets of four octet values, where each one of them 92 specifies a different community. Except two reserved ranges the 93 encoding of community values mandates that first two octets are to 94 contain the Autonomous System number followed by next two octets 95 containing locally defined value. 97 This document lists the most commonly used today BGP communities as 98 well as provides a new registry for future definitions. 100 2. Globally significant pre-defined values 102 2.1. Well Known Standard BGP Communities 104 According to RFC 1997 as well as to IANA's Well-Known BGP Communities 105 registry today the following BGP communities are defined to have 106 global significance: 108 +------------+---------------------+----------------------------+ 109 | 0xFFFF0000 | planned-shut | [draft-francois-bgp-gshut] | 110 | 0xFFFFFF01 | NO_EXPORT | [RFC1997] | 111 | 0xFFFFFF02 | NO_ADVERTISE | [RFC1997] | 112 | 0xFFFFFF03 | NO_EXPORT_SUBCONFED | [RFC1997] | 113 | 0xFFFFFF04 | NOPEER | [RFC3765] | 114 +------------+---------------------+----------------------------+ 116 This document recommends for simplicity as well as for avoidance of 117 backward compatibility issues the continued use of BGP Standard 118 Community Attribute type 8 as defined in RFC 1997 to distribute non 119 Autonomous System specific Well-Known BGP Communities. 121 For the same reason the described registry does not intend to 122 obsolete BGP Extended Community Attribute and any already defined and 123 deployed extended communities. The new registry is to be used 124 primarly for new community definitions in particular those which 125 require to carry various new parameters or which should be propagated 126 with a controled scope and radius. 128 2.2. Registered pre-defined Wide BGP Communities 130 It has been requested numerous times to have a globally unified way 131 to express some particular Autonomous System based routing policies. 133 When defining a new way to encode bgp communities we have an 134 opportunity to define set of new registered routing policies and 135 route markings which could be passed within and between Autonomous 136 Systems resulting in their common interpretation. 138 This document will request IANA to define and maintain a new registry 139 for pre-defined Wide BGP Community values. The allocation policy is 140 on a first come first served basis. 142 It is recommended that an implementation supports by an explicit 143 enabling defined below Registered Wide BGP Communities. Depending on 144 the BGP implementation support it is recommended that an 145 implementation would support Registered Wide BGP Communities without 146 breaking static or dynamic peer/update groups. However it needs to 147 be pointed out that support of all Registered Wide BGP Communities is 148 not mandatory. It will be perfectly valid for any BGP implementation 149 to support only subset of Wide BGP Communities. 151 It is strongly advised that each Autonomous System does an inbound 152 verification of received Wide BGP Communities from all of its EBGP 153 peers before accepting them and propagating within their own domain. 155 The document does not mandate nor enforces that given registered type 156 value of Wide BGP Community would be of transitive or non-transitive 157 type. It is for the operator to determine the propagation AS radius 158 required for such community when appending it to routing information. 159 However the document will provide a transitivity radius 160 recommendation to defined communities. 162 The following Wide BGP Communities have global significance and their 163 execution should be uniformly implemented by any BGP speaker 164 supporting given set of Wide BGP Communities. 166 The defined below value of the community should be interpreted as 167 registered value only if "R" - registered bit is set in the community 168 Type 1 container as described in [draft-raszuk-wide-bgp-communities] 169 Otherwise the value is local and it's actions is locally defined by 170 the operator. 172 2.2.1. General Registered Wide BGP Community Values 174 The below set of communities will be defined to be carried in Wide 175 BGP Community Type 1, with the container type values as per 176 Section 5. 178 0 1 2 3 179 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 180 +-+-+-+-+-+-+-+-+ 181 | 0x01 | 182 +-+-+-+-+-+-+-+-+ 183 |R C 0 0 0 0 0 0| 184 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 185 | Length | 186 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 187 | TTL | 188 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 189 | Source AS number | 190 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 191 | Registered/Local value | 192 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 193 | Parameter/s (optional, variable)... | 194 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 196 Figure 1: Wide BGP Community Type 1 198 Description format: 200 NAME 202 TTL - defines domain or sub-domain propagation radius 203 LENGTH - Length of the TLV in octets 204 PARAMETERS - optional parameters for execution 205 DESCRIPTION - defines the use and post execution action 207 BLACKHOLE 209 TTL - Operator's defined 210 LENGTH - 13 octets 211 PARAMETERS - none 213 DESCRIPTION - All transit traffic to destinations for which 214 advertised routes carry such community value should be dropped. It 215 is recommended that specified Autonomous System number should be 216 eligible and verified by BGP Origin Validation functionality to 217 advertise given BGP destinations. 219 SOURCE BLACKHOLE 221 TTL - Operator's defined 222 LENGTH - 13 octets 223 PARAMETERS - none 225 DESCRIPTION - All transit traffic which source addresses have been 226 tagged by such Wide BGP Community should be dropped. 228 SOURCE DO RPF 230 TTL - Operator's defined 231 LENGTH - 13 octets 232 PARAMETERS - none 234 DESCRIPTION - All transit traffic which source addresses have been 235 tagged by such Wide BGP Community should be subject to Reverse Path 236 Forwarding check when crossing Autonomous System boundaries. Source 237 Autonomous System number specified in the body of this community 238 should directly indicate the peering interfaces on which such RPF 239 check should be performed. 241 HIGH PRIORITY PREFIX 243 TTL - 0x00 (local to domain) 244 LENGTH - 13 octets 245 PARAMETERS - none 247 DESCRIPTION - BGP prefixes carrying such Wide BGP Community should be 248 advertised to restarting peers before other prefixes received by 249 given BGP speaker. 251 ATTACK TARGET 253 TTL - Operator's defined 254 LENGTH - 13 octets 255 PARAMETERS - none 257 DESCRIPTION - The ATTACK_TARGET Registered Wide BGP Community 258 indicates that BGP prefixes carrying such community are receiving 259 unusual amount of unwanted traffic most likely due to some form of 260 network attack. Network devices capable of analyzing and mitigating 261 such attacks can use such community as a hint on what destinations to 262 focus the most. 264 2.2.2. Advertisement control Registered Wide BGP Communities 266 NO ADVERTISE TO AS 268 TTL - Operator's defined 269 LENGTH - 17 octets 270 PARAMETERS - Target AS number - 4 octets 272 DESCRIPTION - All routes received which carry such Wide BGP Community 273 containing this value MUST NOT be advertised to BGP peer which 274 Autonomous System number has been listed in the body of this 275 community. 277 Semantically specifying the reserved Autonomous System value of 278 0xFFFFFFFF (ANY AS) would be an equivalent of using NO_ADVERTISE 279 Well-Known Standard BGP Community Attribute. 281 ADVERTISE TO AS 283 TTL - Operator's defined 284 LENGTH - 17 octets 285 PARAMETERS - Target AS number - 4 octets 287 DESCRIPTION - All routes received carrying such Wide BGP Community 288 containing this value MUST ONLY be advertised to BGP peers which 289 Autonomous System number is specified in the PARAMETER field of this 290 community. 292 Semantically specifying the reserved Autonomous System value of 293 0xFFFFFFFF (ANY AS) would be an equivalent of advertisement to all 294 neighbors. Post execution this community MUST be removed. 296 ADVERTISE AND SET NO EXPORT 298 TTL - Operator's defined 299 LENGTH - 17 octets 300 PARAMETERS - Target AS number - 4 octets 302 DESCRIPTION - All routes received carrying such Wide BGP Community 303 containing this value MUST be advertised to BGP peer which Autonomous 304 System number is specified in the PARAMETER section of this community 305 with NO_EXPORT Standard BGP Community attached. 307 Semantically specifying the reserved Autonomous System value of 308 0xFFFFFFFF (ANY AS) would be an equivalent of advertisement to all 309 neighbors with NO_EXPORT community being set. Post execution this 310 community MUST be removed. 312 2.2.3. AS source marking Registered Wide BGP Communities 314 FROM PEER 316 TTL - 0x00 - Local AS tagging only 317 LENGTH - 13 octets 318 PARAMETERS - none 320 DESCRIPTION - Autonomous System may attach this community to routes 321 received from their EBGP peers to later, when advertising them 322 outside the domain, apply or relax local policies only on such group 323 of destinations. 325 FROM CUSTOMER 327 TTL - 0x00 - Local AS tagging only 328 LENGTH - 13 octets 329 PARAMETERS - none 331 DESCRIPTION - Autonomous System may attach this community to routes 332 received from their customers to later, when advertising them outside 333 the domain, apply or relax local policies only on such group of 334 destinations. 336 INTERNAL 338 TTL - 0x00 - Local AS tagging only 339 LENGTH - 13 octets 340 PARAMETERS - none 342 DESCRIPTION - Autonomous System may attach this community to routes 343 originated in their own domain to later, when advertising them 344 outside the domain, apply or relax local policies only on such group 345 of destinations. 347 FROM UPSTREAM 349 TTL - 0x00 - Local AS tagging only 350 LENGTH - 13 octets 351 PARAMETERS - none 353 DESCRIPTION - Autonomous System may attach this community to routes 354 received from their EBGP upstream peers to later, when advertising 355 them outside the domain, apply or relax local policies only on such 356 group of destinations. 358 FROM IX 360 TTL - 0x00 Local AS tagging only 361 LENGTH - 13 octets 362 PARAMETERS - none 364 DESCRIPTION - Autonomous System may attach this community to routes 365 received from their EBGP peering sessions with the Internet Exchange 366 peers or with Route Server to later, when advertising them outside 367 the domain, apply or relax local policies only on such group of 368 destinations. 370 LEARNED FROM AS 372 TTL - 0x00 Local AS tagging only 373 LENGTH - 17 octets 374 PARAMETERS - 4 octets - Peer's AS number 376 DESCRIPTION - Autonomous System may attach this community to routes 377 received from their EBGP peer by explicitly tagging them with their 378 peer's Autonomous System number as a value of the PARAMETER field. 379 If the AS number is a two octet number first two octest will be 380 filled with zero. It is possible to use this to also carry private 381 AS number of customers. 383 2.2.4. Return path influencing Registered Wide BGP Communities 385 PATH HINT 387 TTL - Operator's defined 388 LENGTH - 17 octets 389 PARAMETERS - 4 octets AS number 391 DESCRIPTION - Autonomous System receiving such Wide BGP Community 392 value should prefer for BGP prefixes received with such community 393 (for example by increasing value of local preference on ingress), a 394 BGP path which traverses Autonomous System number which has been 395 specified in the PARAMETER field of this community. Post execution 396 this community SHOULD be kept. 398 NEGATIVE PATH HINT 400 TTL - Operator's defined 401 LENGTH - 17 octets 402 PARAMETERS - 4 octets AS number 404 DESCRIPTION - Autonomous System receiving such Wide BGP Community 405 value should prefer for BGP prefixes received with such community 406 (for example by increasing value of local preference on ingress), a 407 BGP path which DOES NOT traverses Autonomous System number which has 408 been specified in the PARAMETERS field of this community. Post 409 execution this community SHOULD be kept. 411 2.2.5. AS_PATH modifying Registered Wide BGP Communities 413 PREPEND N TIMES BY AS 415 TTL - Operator's defined 416 LENGTH - 18 octets 417 PARAMETERS - 4 octets AS number + 1 octet prepend's number 419 DESCRIPTION - The Autonomous System specified in the PARAMETERS field 420 of such community should prepend N times its own Autonomous System 421 number when advertising routes tagged with this community to peers. 422 Number of requested AS prepends is provided in the last octet of 423 PARAMETERS field value. Post execution this community MUST be 424 removed. 426 PREPEND N TIMES TO AS 428 TTL - Operator's defined 429 LENGTH - 18 octets 430 PARAMETERS - 4 octets AS number + 1 octet prepend's number 432 DESCRIPTION - The Autonomous System advertising routes externally 433 should prepend N times its own Autonomous System number when 434 advertising routes tagged with this community to peer which AS number 435 is defined by the first 4 octets of PARAMETERS field. Number of 436 requested AS prepends is provided in the last octet of PARAMETERS 437 field value. Post execution this community MUST be removed. 439 REPLACE BY 441 TTL - Operator's defined 442 LENGTH - 17 octets 443 PARAMETERS - 4 octets AS number 445 DESCRIPTION - All routes marked with such community advertised by an 446 Autonomous System to all of its external peers should have any 447 occurrence of an Autonomous System number specified in the PARAMETERS 448 field replaced with advertising domain's local Autonomous System 449 number. Post execution this community MUST be removed. 451 2.2.6. Local Preference Registered Community 453 LOCAL PREFERENCE 455 TTL - Operator's defined 456 LENGTH - 14 octets 457 PARAMETERS - 1 octet 1st bit indicates: 458 0-increment, 1-decrement; 459 7 bits - value of local preference value 1..127 461 DESCRIPTION - Autonomous System may suggest to its EBGP neighbor the 462 following adjustments to the value of local preference as specified 463 by given domain's local policy. The values of requested increment or 464 decrement local preference value is carried in the PARAMETERS field. 465 Post execution this community MUST be removed. 467 2.2.7. AS_PATH TTL Registered Community 469 AS_PATH TTL MAX RADIUS 471 TTL - Operator's defined 472 LENGTH - 14 octets 473 PARAMETERS - 1 octet - max AS_PATH radius 475 DESCRIPTION - Autonomous System may suggest to drop advertised prefix 476 by any transit network if its AS_PATH attribute length would be equal 477 or greater to encoded value both inbound or outbound of EBGP session. 478 The value of max AS_PATH length allowed is specified in the 479 PARAMETERS field of the community. Post comparison this community 480 MUST be kept. 482 3. Example 484 Customer of the source AS number XYZ requests to execute AS_PATH 485 prepend 4 times when advertising the prefixes to AS number 2424. We 486 will use the following community assigned on ingress or at the prefix 487 origination. 489 PREPEND N TIMES TO AS 491 TTL - 0x00 492 LENGTH - 18 octets 493 VALUE - 17 / 0x12 494 PARAMETERS - 4 octets AS number + 1 octet prepend's number 496 0 1 2 3 497 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 498 +-+-+-+-+-+-+-+-+ 499 | 0x1 | 500 +-+-+-+-+-+-+-+-+ 501 |1 0 0 0 0 0 0 0| 502 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 503 | Length: 18 | 504 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 505 | TTL: 0 | 506 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 507 | Own ASN | 508 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 509 | Community: PREPEND N TIMES TO AS / 0x12 | 510 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 511 | Target ASN / 0x0978 | 512 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 513 | Prepend #: 4 | 514 +-+-+-+-+-+-+-+-+ 516 4. Security considerations 518 All the security considerations for BGP Communities as well as for 519 BGP Extended Communities RFCs apply here. 521 5. IANA Considerations 523 This document requests IANA to define and maintain a new registry 524 named: "Registered Wide BGP Communities Values". The reserved pool 525 of 0x00000000-0xFFFFFFFF has been defined for its allocations. The 526 allocation policy is on a first come first served basis. 528 This document makes the following assignments for the Registered Wide 529 BGP Community values: 531 +-----------------------------+------------+ 532 | Name | Type Value | 533 +-----------------------------+------------+ 534 | BLACKHOLE | 1 | 535 | SOURCE BLACKHOLE | 2 | 536 | SOURCE DO RPF | 3 | 537 | HIGH PRIORITY PREFIX | 4 | 538 | ATTACK TARGET | 5 | 539 | NO ADVERTISE TO AS | 6 | 540 | ADVERTISE TO AS | 7 | 541 | ADVERTISE AND SET NO EXPORT | 8 | 542 | FROM PEER | 9 | 543 | FROM CUSTOMER | 10 | 544 | INTERNAL | 11 | 545 | FROM UPSTREAM | 12 | 546 | FROM IX | 13 | 547 | LEARNED FROM AS | 14 | 548 | PATH HINT | 15 | 549 | PATH NEGATIVE HINT | 16 | 550 | PREPEND N TIMES BY AS | 17 | 551 | PREPEND N TIMES TO AS | 18 | 552 | REPLACE BY | 19 | 553 | LOCAL PREFERENCE | 20 | 554 | AS_PATH TTL MAX RADIUS | 21 | 555 | FREE POOL | 22.. | 556 +-----------------------------+------------+ 558 6. Contributors 560 The following people contributed significantly to the content of the 561 document: 563 Bruno Decraene 564 France Telecom 565 38-40 rue du General Leclerc 566 92794 Issi Moulineaux cedex 9 567 France 568 Email: bruno.decraene@orange-ftgroup.com 569 Shintaro Kojima 570 OTEMACHI 1st. SQUARE EAST TOWER, 3F 571 1-5-1, Otemachi, 572 Chiyoda-ku, Tokyo 100-0004 573 Japan 574 Email: koji@mfeed.ad.jp 576 Juan Alcaide 577 Cisco Systems 578 Research Triangle Park, NC 579 United States 580 Email: jalcaide@cisco.com 582 Burjiz Pithawala 583 Cisco Systems 584 170 West Tasman Dr 585 San Jose, CA 586 United States 587 Email: bpithaw@cisco.com 589 Saku Ytti 590 TDC Oy 591 Mechelininkatu 1a 592 00094 TDC 593 Finland 594 Email: ytti@tdc.net 596 Paul Jakma 597 School of Computing Science, Uni. of Glasgow 598 Sir Alwyn Williams Building 599 University of Glasgow 600 Glasgow 601 G1 5AE 602 UK 603 Email: paulj@dcs.gla.ac.uk 605 7. Acknowledgments 607 Authors would like to thank Enke Chen, Pedro Marques and Alton Lo for 608 their valuable input. 610 8. References 611 8.1. Normative References 613 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 614 Requirement Levels", BCP 14, RFC 2119, March 1997. 616 [RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway 617 Protocol 4 (BGP-4)", RFC 4271, January 2006. 619 [RFC4360] Sangli, S., Tappan, D., and Y. Rekhter, "BGP Extended 620 Communities Attribute", RFC 4360, February 2006. 622 8.2. Informative References 624 [RFC1997] Chandrasekeran, R., Traina, P., and T. Li, "BGP 625 Communities Attribute", RFC 1997, August 1996. 627 [RFC1998] Chen, E. and T. Bates, "An Application of the BGP 628 Community Attribute in Multi-home Routing", RFC 1998, 629 August 1996. 631 [RFC4384] Meyer, D., "BGP Communities for Data Collection", BCP 114, 632 RFC 4384, February 2006. 634 [RFC4893] Vohra, Q. and E. Chen, "BGP Support for Four-octet AS 635 Number Space", RFC 4893, May 2007. 637 [RFC5668] Rekhter, Y., Sangli, S., and D. Tappan, "4-Octet AS 638 Specific BGP Extended Community", RFC 5668, October 2009. 640 Authors' Addresses 642 Robert Raszuk 643 Cisco Systems 644 170 West Tasman Drive 645 San Jose, CA 95134 646 US 648 Email: raszuk@cisco.com 649 Jeffrey Haas 650 Juniper Networks 651 1194 N.Mathilda Ave 652 Sunnyvale, CA 94089 653 US 655 Email: jhaas@pfrc.org