idnits 2.17.1 draft-raszuk-registered-wide-bgp-communities-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 (March 7, 2015) is 3338 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 708, but no explicit reference was found in the text == Unused Reference: 'RFC4271' is defined on line 711, but no explicit reference was found in the text == Unused Reference: 'RFC4360' is defined on line 714, but no explicit reference was found in the text == Unused Reference: 'RFC1998' is defined on line 722, but no explicit reference was found in the text == Unused Reference: 'RFC4384' is defined on line 726, but no explicit reference was found in the text == Unused Reference: 'RFC4893' is defined on line 729, but no explicit reference was found in the text == Unused Reference: 'RFC5668' is defined on line 732, 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, Ed. 3 Internet-Draft Mirantis Inc. 4 Intended status: Standards Track J. Haas 5 Expires: September 8, 2015 Juniper Networks 6 March 7, 2015 8 Registered Wide BGP Community Values 9 draft-raszuk-registered-wide-bgp-communities-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 September 8, 2015. 45 Copyright Notice 47 Copyright (c) 2015 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 . . . . . . . . . . . . . . . . . . . . . . . . 2 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 Communities 7 68 2.2.3. AS source marking Registered Wide BGP Communities . . 8 69 2.2.4. Return path influencing Registered Wide BGP 70 Communities . . . . . . . . . . . . . . . . . . . . . 10 71 2.2.5. AS_PATH modifying Registered Wide BGP Communities . . 10 72 2.2.6. Local Preference Registered Community . . . . . . . . 11 73 2.2.7. AS_PATH TTL Registered Community . . . . . . . . . . 12 74 2.2.8. GEO-LOCATION Registered Community . . . . . . . . . . 12 75 3. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 76 4. Security considerations . . . . . . . . . . . . . . . . . . . 14 77 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 78 6. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 15 79 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 16 80 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 16 81 8.1. Normative References . . . . . . . . . . . . . . . . . . 16 82 8.2. Informative References . . . . . . . . . . . . . . . . . 17 83 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17 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. 132 When defining a new way to encode bgp communities we have an 133 opportunity to define set of new registered routing policies and 134 route markings which could be passed within and between Autonomous 135 Systems resulting in their common interpretation. 137 This document will request IANA to define and maintain a new registry 138 for pre-defined Wide BGP Community values. The allocation policy is 139 on a first come first served basis. 141 It is recommended that an implementation supports by an explicit 142 enabling defined below Registered Wide BGP Communities. Depending on 143 the BGP implementation support it is recommended that an 144 implementation would support Registered Wide BGP Communities without 145 breaking static or dynamic peer/update groups. However it needs to 146 be pointed out that support of all Registered Wide BGP Communities is 147 not mandatory. It will be perfectly valid for any BGP implementation 148 to support only subset of Wide BGP Communities. 150 It is strongly advised that each Autonomous System does an inbound 151 verification of received Wide BGP Communities from all of its EBGP 152 peers before accepting them and propagating within their own domain. 154 The document does not mandate nor enforces that given registered type 155 value of Wide BGP Community would be of transitive or non-transitive 156 type. It is for the operator to determine the propagation AS radius 157 required for such community when appending it to routing information. 158 However the document will provide a transitivity radius 159 recommendation to defined communities. 161 The following Wide BGP Communities have global significance and their 162 execution should be uniformly implemented by any BGP speaker 163 supporting given set of Wide BGP Communities. 165 The defined below value of the community should be interpreted as 166 registered value only if "R" - registered bit is set in the community 167 Type 1 container as described in [draft-raszuk-wide-bgp-communities] 168 Otherwise the value is local and it's actions is locally defined by 169 the operator. 171 2.2.1. General Registered Wide BGP Community Values 173 The below set of communities will be defined to be carried in Wide 174 BGP Community Type 1, with the container type values (Community 175 Registered Value) as per Section 5. 177 0 1 2 3 178 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 179 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 180 | 0x0001 |R C 0 0 0 0 0 0| Hop Count | 181 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 182 | Length | 183 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 184 | Registered Community Value | 185 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 186 | Source AS Number | 187 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 188 | Context AS Number | 189 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 190 | Wide Community Target(s) TLV (optional) | 191 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 192 | Wide Community Exclude Target(s) TLV (optional) | 193 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 194 | Wide Community Parameter(s) TLV (optional) | 195 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 197 Figure 1: Wide BGP Community Type 1 199 Description format: 201 TYPE: 202 0x0001 (constant for this registry) 203 FLAGS "F": 204 R - Registered bit (Set to 1 for registered values) 205 C - Confederation bit (Set when applicable) 206 HOP COUNT "H": 207 Defines domain or sub-domain propagation radius 208 LENGTH "L": 209 Length of the Container Type 1 in octets 210 REGISTERED COMMUNITY VALUE "R": 211 Value of the community in registry 212 SOURCE AS "S": 213 Originator AS of Wide BGP Community 214 CONTEXT AS "C": 215 For registered communities carries predefined meaning 216 or otherwise should be set to 0x00000000 217 TARGET TLV "T": 218 Set of atoms containing targets for execution 219 EXCLUDE TARGET TLV "E": 220 Set of atoms containing excluded targets for execution 221 PARAMETER TLV "P": 222 Set of atoms containing optional parameters for execution 224 BLACKHOLE 225 Type: 0x0001 S = src AS # 226 F = 0x80 C = 0x00000000 227 H = Operator's defined T = none 228 L = 18 octets E = none 229 R = IANA assigned P = none 231 DESCRIPTION - All transit traffic to destinations for which 232 advertised routes carry such community value should be dropped. It 233 is recommended that specified Autonomous System number should be 234 eligible and verified by BGP Origin Validation functionality to 235 advertise given BGP destinations. 237 SOURCE FILTER 238 Type: 0x0001 S = src AS # 239 F = 0x80 C = 0x00000000 240 H = Operator's defined T = none 241 L = 18 octets E = none 242 R = IANA assigned P = none 244 DESCRIPTION - All transit traffic which source addresses have been 245 tagged by such Wide BGP Community should be dropped. 247 SOURCE DO RPF 248 Type: 0x0001 S = src AS # 249 F = 0x80 C = 0x00000000 250 H = Operator's defined T = none 251 L = 18 octets E = none 252 R = IANA assigned P = none 254 DESCRIPTION - All transit traffic which source addresses have been 255 tagged by such Wide BGP Community should be subject to Reverse Path 256 Forwarding check when crossing Autonomous System boundaries. Source 257 Autonomous System number specified in the body of this community 258 should directly indicate the peering interfaces on which such RPF 259 check should be performed. 261 HIGH PRIORITY PREFIX 262 Type: 0x0001 S = src AS # 263 F = 0x80 C = 0x00000000 264 H = 0x00 T = none 265 L = 18 octets E = none 266 R = IANA assigned P = none 268 DESCRIPTION - BGP prefixes carrying such Wide BGP Community should be 269 advertised to restarting peers before other prefixes received by 270 given BGP speaker. 272 ATTACK TARGET 273 Type: 0x0001 S = src AS # 274 F = 0x80 C = 0x00000000 275 H = Operator's defined T = none 276 L = 18 octets E = none 277 R = IANA assigned P = none 279 DESCRIPTION - The ATTACK_TARGET Registered Wide BGP Community 280 indicates that BGP prefixes carrying such community are receiving 281 unusual amount of unwanted traffic most likely due to some form of 282 network attack. Network devices capable of analyzing and mitigating 283 such attacks can use such community as a hint on what destinations to 284 focus the most. 286 2.2.2. Advertisement control Registered Wide BGP Communities 288 NO ADVERTISE TO AS 289 Type: 0x0001 S = src AS # 290 F = 0x80 C = 0x00000000 291 H = Operator's defined T = Type_1 (Peer_AS) 292 L = 25 octets E = none 293 R = IANA assigned P = none 295 DESCRIPTION - All routes received which carry such Wide BGP Community 296 containing this value MUST NOT be advertised to BGP peer which 297 Autonomous System number has been listed in the TARGET TLV field of 298 this community. 300 Semantically specifying the reserved Autonomous System value of 301 0xFFFFFFFF (ANY AS) would be an equivalent of using NO_ADVERTISE 302 Well-Known Standard BGP Community Attribute. 304 ADVERTISE TO AS 305 Type: 0x0001 S = src AS # 306 F = 0x80 C = 0x00000000 307 H = Operator's defined T = Type_1 (Peer_AS) 308 L = 25 octets E = none 309 R = IANA assigned P = none 311 DESCRIPTION - All routes received carrying such Wide BGP Community 312 containing this value MUST ONLY be advertised to BGP peers which 313 Autonomous System number is specified in the TARGET TLV field of this 314 community. 316 Semantically specifying the reserved Autonomous System value of 317 0xFFFFFFFF (ANY AS) would be an equivalent of advertisement to all 318 neighbors. Post execution this community MUST be removed. 320 ADVERTISE AND SET NO EXPORT 321 Type: 0x0001 S = src AS # 322 F = 0x80 C = 0x00000000 323 H = Operator's defined T = Type_1 (Peer_AS) 324 L = 25 octets E = none 325 R = IANA assigned P = none 327 DESCRIPTION - All routes received carrying such Wide BGP Community 328 containing this value MUST be advertised to BGP peer which Autonomous 329 System number is specified in the TARGET TLV field of this community 330 with NO_EXPORT Standard BGP Community attached. 332 Semantically specifying in TARGET TLV the reserved Autonomous System 333 value of 0xFFFFFFFF (ANY AS) would be an equivalent of advertisement 334 to all neighbors with NO_EXPORT community being set. Post execution 335 this community MUST be removed. 337 2.2.3. AS source marking Registered Wide BGP Communities 339 FROM PEER 340 Type: 0x0001 S = src AS # 341 F = 0x80 C = 0x00000000 342 H = 0x00 T = none 343 L = 18 octets E = none 344 R = IANA assigned P = none 346 DESCRIPTION - Autonomous System may attach this community to routes 347 received from their EBGP peers to later, when advertising them 348 outside the domain, apply or relax local policies only on such group 349 of destinations. 351 FROM CUSTOMER 352 Type: 0x0001 S = src AS # 353 F = 0x80 C = 0x00000000 354 H = 0x00 T = none 355 L = 18 octets E = none 356 R = IANA assigned P = none 358 DESCRIPTION - Autonomous System may attach this community to routes 359 received from their customers to later, when advertising them outside 360 the domain, apply or relax local policies only on such group of 361 destinations. 363 INTERNAL 364 Type: 0x0001 S = src AS # 365 F = 0x80 C = 0x00000000 366 H = 0x00 T = none 367 L = 18 octets E = none 368 R = IANA assigned P = none 370 DESCRIPTION - Autonomous System may attach this community to routes 371 originated in their own domain to later, when advertising them 372 outside the domain, apply or relax local policies only on such group 373 of destinations. 375 FROM UPSTREAM 376 Type: 0x0001 S = src AS # 377 F = 0x80 C = 0x00000000 378 H = 0x00 T = none 379 L = 18 octets E = none 380 R = IANA assigned P = none 382 DESCRIPTION - Autonomous System may attach this community to routes 383 received from their EBGP upstream peers to later, when advertising 384 them outside the domain, apply or relax local policies only on such 385 group of destinations. 387 FROM IX 388 Type: 0x0001 S = src AS # 389 F = 0x80 C = 0x00000000 390 H = 0x00 T = none 391 L = 18 octets E = none 392 R = IANA assigned P = none 394 DESCRIPTION - Autonomous System may attach this community to routes 395 received from their EBGP peering sessions with the Internet Exchange 396 peers or with Route Server to later, when advertising them outside 397 the domain, apply or relax local policies only on such group of 398 destinations. 400 LEARNED FROM AS 401 Type: 0x0001 S = src AS # 402 F = 0x80 C = 0x00000000 403 H = 0x00 T = Type_1 (Peer_AS) 404 L = 25 octets E = none 405 R = IANA assigned P = none 407 DESCRIPTION - Autonomous System may attach this community to routes 408 received from their EBGP peer by explicitly tagging them with their 409 peer's Autonomous System number as a value of the TARGET TLV field. 410 If the AS number is a two octet number first two octest will be 411 filled with zero. It is possible to use this to also carry private 412 AS number of customers. 414 2.2.4. Return path influencing Registered Wide BGP Communities 416 PATH HINT 417 Type: 0x0001 S = src AS # 418 F = 0x80 C = 0x00000000 419 H = Operator's defined T = Type_1 (AS#) 420 L = 25 octets E = none 421 R = IANA assigned P = none 423 DESCRIPTION - Autonomous System receiving such Wide BGP Community 424 value should prefer for BGP prefixes received with such community 425 (for example by increasing value of local preference on ingress), a 426 BGP path which traverses Autonomous System number which has been 427 specified in the TARGET TLV field of this community. Post execution 428 this community SHOULD be kept. 430 NEGATIVE PATH HINT 431 Type: 0x0001 S = src AS # 432 F = 0x80 C = 0x00000000 433 H = Operator's defined T = Type_1 (AS#) 434 L = 25 octets E = none 435 R = IANA assigned P = none 437 DESCRIPTION - Autonomous System receiving such Wide BGP Community 438 value should prefer for BGP prefixes received with such community 439 (for example by increasing value of local preference on ingress), a 440 BGP path which DOES NOT traverses Autonomous System number which has 441 been specified in the TARGET TLV field of this community. Post 442 execution this community SHOULD be kept. 444 2.2.5. AS_PATH modifying Registered Wide BGP Communities 446 PREPEND N TIMES BY AS 447 Type: 0x0001 S = src AS # 448 F = 0x80 C = 0x00000000 449 H = Operator's defined T = Type_1 (AS#) 450 L = 29 octets E = none 451 R = IANA assigned P = Type_4 (0xAA) 453 DESCRIPTION - The Autonomous System specified in the TARGET TLV field 454 of such community should prepend N times (encoded as 0xAA) its own 455 Autonomous System number when advertising routes tagged with this 456 community to peers. Number of requested AS prepends is provided in 457 the PARAMETERS TLV field value. Post execution this community MUST 458 be removed. 460 PREPEND N TIMES TO AS 461 Type: 0x0001 S = src AS # 462 F = 0x80 C = 0x00000000 463 H = Operator's defined T = Type_1 (AS#) 464 L = 29 octets E = none 465 R = IANA assigned P = Type_4 (0xAA) 467 DESCRIPTION - The Autonomous System advertising routes externally 468 should prepend N times (encoded as 0xAA) its own Autonomous System 469 number when advertising routes tagged with this community to peer 470 which AS number is defined by TARGET TLV field. Number of requested 471 AS prepends is provided in the PARAMETERS TLV field. Post execution 472 this community MUST be removed. 474 REPLACE BY 475 Type: 0x0001 S = src AS # 476 F = 0x80 C = 0x00000000 477 H = Operator's defined T = Type_1 (AS#) 478 L = 25 octets E = none 479 R = IANA assigned P = none 481 DESCRIPTION - All routes marked with such community advertised by an 482 Autonomous System to all of its external peers should have any 483 occurrence of an Autonomous System number specified in the TARGET TLV 484 field replaced with advertising domain's local Autonomous System 485 number. Post execution this community MUST be removed. 487 2.2.6. Local Preference Registered Community 489 LOCAL PREFERENCE 490 Type: 0x0001 S = src AS # 491 F = 0x80 C = 0x00000000 492 H = Operator's defined T = none 493 L = 22 octets E = none 494 R = IANA assigned P = Type_4 (ABBBBBBB) 496 SEMANTICS of PARAMETERS TLV 497 1 octet 1st bit indicates: 498 0-increment, 1-decrement 499 7 bits - value of local preference value 1..127 501 DESCRIPTION - Autonomous System may suggest to its EBGP neighbor the 502 following adjustments to the value of local preference as specified 503 by given domain's local policy. The values of requested increment or 504 decrement of local preference value is carried in the PARAMETERS TLV 505 field. Post execution this community MUST be removed. 507 2.2.7. AS_PATH TTL Registered Community 509 AS_PATH TTL MAX RADIUS 510 Type: 0x0001 S = src AS # 511 F = 0x80 C = 0x00000000 512 H = Operator's defined T = none 513 L = 22 octets E = none 514 R = IANA assigned P = Type_4 (0xAA) max AS_PATH radius 516 DESCRIPTION - Autonomous System may suggest to drop advertised prefix 517 by any transit network if its AS_PATH attribute length would be equal 518 or greater to encoded value both inbound or outbound of EBGP session. 519 The value of max AS_PATH length allowed is specified in the 520 PARAMETERS TLV field of the community. Post comparison this 521 community MUST be kept. 523 2.2.8. GEO-LOCATION Registered Community 525 GEOGRAPHIC LOCATION WHERE BGP ROUTE IS INTRODUCED TO AS 526 Type: 0x0001 S = src AS # 527 F = 0x80 C = 0x00000000 528 H = Operator's defined T = none 529 L = 26 octets E = none 530 R = IANA assigned P = Type_8 (5 UTF-8 characters) 532 DESCRIPTION - Autonomous Systems may attach this community to routes 533 received from EBGP neighbors or introduced to BGP by other routing 534 protocols to identify the geographic location where the route was 535 introduced to the AS. The "right-most" two octets of PARAMETERS TLV 536 correspond to an ISO3166-1 alpha-2 country identifier, while the 537 "left-most" three octets may express a more specific geographic 538 location, such as a city or IXP encoded in 3 octets. 540 Example: 542 Wide BGP Community describing route learnt by the AS at London, GB 543 HOP COUNT - operator defined 544 LENGTH - 26 545 PARAMETERS - 3 octets locality string + 2 octets country id. 547 0 1 2 3 548 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 549 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 550 | 0x0001 | 0x80 | 0xFF | 551 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 552 | 0x001A | 553 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 554 | IANA assigned | 555 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 556 | 0x000000AS | 557 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 558 | 0x00000000 | 559 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 560 | 0x08 | 0x0008 | 561 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 562 | "L" | "O" | "N" | "G" | 563 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 564 | "B" | 565 +-+-+-+-+-+-+-+-+ 567 3. Example 569 Customer of the source AS number 100 requests to execute AS_PATH 570 prepend 4 times when advertising the prefixes to AS number 2424. We 571 will use the following community assigned on ingress or at the prefix 572 origination. 574 PREPEND N TIMES TO AS 575 Type: 0x0001 S = 0x00000064 (dec 100) 576 F = 0x80 C = 0x00000000 577 H = 0x00 T = 0x00000978 (dec 2424) 578 L = 0x001D (dec 29 octets) E = none 579 R = IANA assigned P = 0x04 (dec 4) 581 0 1 2 3 582 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 583 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 584 | 0x0001 | 0x80 | 0x00 | 585 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 586 | 0x001D | 587 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 588 | IANA assigned | 589 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 590 | 0x00000064 | 591 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 592 | 0x00000000 | 593 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 594 | 0x01 | 0x0007 | 595 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 596 | 0x00000978 | 597 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 598 | 0x04 | 0x0004 | 599 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 600 | 0x04 | 601 +-+-+-+-+-+-+-+-+ 603 4. Security considerations 605 All the security considerations for BGP Communities as well as for 606 BGP Extended Communities RFCs apply here. 608 5. IANA Considerations 610 This document requests IANA to define and maintain a new registry 611 named: "Registered Wide BGP Communities Values". The reserved pool 612 of 0x00000000-0xFFFFFFFF has been defined for its allocations. The 613 allocation policy is on a first come first served basis. 615 This document makes the following assignments for the Registered Wide 616 BGP Community values: 618 +---------------------------------+------------+ 619 | Name | Type Value | 620 +---------------------------------+------------+ 621 | BLACKHOLE | 1 | 622 | SOURCE FILTER | 2 | 623 | SOURCE DO RPF | 3 | 624 | HIGH PRIORITY PREFIX | 4 | 625 | ATTACK TARGET | 5 | 626 | | | 627 | NO ADVERTISE TO AS | 6 | 628 | ADVERTISE TO AS | 7 | 629 | ADVERTISE AND SET NO EXPORT | 8 | 630 | | | 631 | FROM PEER | 9 | 632 | FROM CUSTOMER | 10 | 633 | INTERNAL | 11 | 634 | FROM UPSTREAM | 12 | 635 | FROM IX | 13 | 636 | LEARNED FROM AS | 14 | 637 | | | 638 | PATH HINT | 15 | 639 | PATH NEGATIVE HINT | 16 | 640 | | | 641 | PREPEND N TIMES BY AS | 17 | 642 | PREPEND N TIMES TO AS | 18 | 643 | REPLACE BY | 19 | 644 | | | 645 | LOCAL PREFERENCE | 20 | 646 | AS_PATH TTL MAX RADIUS | 21 | 647 | GEO-LOCATION | 22 | 648 | | | 649 | FREE POOL | 23.. | 650 +---------------------------------+------------+ 652 6. Contributors 654 The following people contributed significantly to the content of the 655 document: 657 Bruno Decraene 658 France Telecom 659 38-40 rue du General Leclerc 660 92794 Issi Moulineaux cedex 9 661 France 662 Email: bruno.decraene@orange-ftgroup.com 663 Shintaro Kojima 664 OTEMACHI 1st. SQUARE EAST TOWER, 3F 665 1-5-1, Otemachi, 666 Chiyoda-ku, Tokyo 100-0004 667 Japan 668 Email: koji@mfeed.ad.jp 670 Juan Alcaide 671 Cisco Systems 672 Research Triangle Park, NC 673 United States 674 Email: jalcaide@cisco.com 676 Burjiz Pithawala 677 Cisco Systems 678 170 West Tasman Dr 679 San Jose, CA 680 United States 681 Email: bpithaw@cisco.com 683 Saku Ytti 684 TDC Oy 685 Mechelininkatu 1a 686 00094 TDC 687 Finland 688 Email: ytti@tdc.net 690 Paul Jakma 691 School of Computing Science, Uni. of Glasgow 692 Sir Alwyn Williams Building 693 University of Glasgow 694 Glasgow 695 G1 5AE 696 UK 697 Email: paulj@dcs.gla.ac.uk 699 7. Acknowledgments 701 Authors would like to thank Enke Chen, Pedro Marques, Alton Lo and 702 Jeff Wheeler for their valuable input. 704 8. References 706 8.1. Normative References 708 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 709 Requirement Levels", BCP 14, RFC 2119, March 1997. 711 [RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway 712 Protocol 4 (BGP-4)", RFC 4271, January 2006. 714 [RFC4360] Sangli, S., Tappan, D., and Y. Rekhter, "BGP Extended 715 Communities Attribute", RFC 4360, February 2006. 717 8.2. Informative References 719 [RFC1997] Chandrasekeran, R., Traina, P., and T. Li, "BGP 720 Communities Attribute", RFC 1997, August 1996. 722 [RFC1998] Chen, E. and T. Bates, "An Application of the BGP 723 Community Attribute in Multi-home Routing", RFC 1998, 724 August 1996. 726 [RFC4384] Meyer, D., "BGP Communities for Data Collection", BCP 114, 727 RFC 4384, February 2006. 729 [RFC4893] Vohra, Q. and E. Chen, "BGP Support for Four-octet AS 730 Number Space", RFC 4893, May 2007. 732 [RFC5668] Rekhter, Y., Sangli, S., and D. Tappan, "4-Octet AS 733 Specific BGP Extended Community", RFC 5668, October 2009. 735 Authors' Addresses 737 Robert Raszuk (editor) 738 Mirantis Inc. 739 615 National Ave. #100 740 Mt View, CA 94043 741 USA 743 Email: robert@raszuk.net 745 Jeffrey Haas 746 Juniper Networks 747 1194 N.Mathilda Ave 748 Sunnyvale, CA 94089 749 US 751 Email: jhaas@pfrc.org