idnits 2.17.1 draft-ietf-idr-large-community-12.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 use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- The document date (January 5, 2017) is 2666 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) -- Looks like a reference, but probably isn't: '1' on line 346 Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 IDR J. Heitz, Ed. 3 Internet-Draft Cisco 4 Intended status: Standards Track J. Snijders, Ed. 5 Expires: July 9, 2017 NTT 6 K. Patel 7 Arrcus 8 I. Bagdonas 9 Equinix 10 N. Hilliard 11 INEX 12 January 5, 2017 14 BGP Large Communities 15 draft-ietf-idr-large-community-12 17 Abstract 19 This document describes the BGP Large Communities attribute, an 20 extension to BGP-4. This attribute provides a mechanism to signal 21 opaque information within separate namespaces to aid in routing 22 management. The attribute is suitable for use with all Autonomous 23 System Numbers including four-octet Autonomous System Numbers. 25 Requirements Language 27 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 28 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 29 document are to be interpreted as described in [RFC2119]. 31 Status of This Memo 33 This Internet-Draft is submitted in full conformance with the 34 provisions of BCP 78 and BCP 79. 36 Internet-Drafts are working documents of the Internet Engineering 37 Task Force (IETF). Note that other groups may also distribute 38 working documents as Internet-Drafts. The list of current Internet- 39 Drafts is at http://datatracker.ietf.org/drafts/current/. 41 Internet-Drafts are draft documents valid for a maximum of six months 42 and may be updated, replaced, or obsoleted by other documents at any 43 time. It is inappropriate to use Internet-Drafts as reference 44 material or to cite them other than as "work in progress." 46 This Internet-Draft will expire on July 9, 2017. 48 Copyright Notice 50 Copyright (c) 2017 IETF Trust and the persons identified as the 51 document authors. All rights reserved. 53 This document is subject to BCP 78 and the IETF Trust's Legal 54 Provisions Relating to IETF Documents 55 (http://trustee.ietf.org/license-info) in effect on the date of 56 publication of this document. Please review these documents 57 carefully, as they describe your rights and restrictions with respect 58 to this document. Code Components extracted from this document must 59 include Simplified BSD License text as described in Section 4.e of 60 the Trust Legal Provisions and are provided without warranty as 61 described in the Simplified BSD License. 63 Table of Contents 65 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 66 2. BGP Large Communities Attribute . . . . . . . . . . . . . . . 3 67 3. Aggregation . . . . . . . . . . . . . . . . . . . . . . . . . 4 68 4. Canonical Representation . . . . . . . . . . . . . . . . . . 4 69 5. Error Handling . . . . . . . . . . . . . . . . . . . . . . . 4 70 6. Security Considerations . . . . . . . . . . . . . . . . . . . 5 71 7. Implementation status - RFC EDITOR: REMOVE BEFORE PUBLICATION 5 72 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 73 9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 6 74 10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 6 75 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 76 11.1. Normative References . . . . . . . . . . . . . . . . . . 7 77 11.2. Informative References . . . . . . . . . . . . . . . . . 7 78 11.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 8 79 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8 81 1. Introduction 83 BGP [RFC4271] implementations typically support a routing policy 84 language to control the distribution of routing information. Network 85 operators attach BGP communities to routes to associate particular 86 properties with these routes. These properties may include 87 information such as the route origin location, or specification of a 88 routing policy action to be taken, or one that has been taken, and is 89 applied to all routes contained in a BGP Update Message where the 90 Communities Attribute is included. Because BGP communities are 91 optional transitive BGP attributes, BGP communities may be acted upon 92 or otherwise used by routing policies in other Autonomous Systems 93 (ASes) on the Internet. 95 BGP Communities attributes are a variable length attribute consisting 96 of a set of one or more four-octet values, each of which specify a 97 community [RFC1997]. Common use of the individual values of this 98 attribute type split this single 32-bit value into two 16-bit values. 99 The most significant word is interpreted as an Autonomous System 100 Number (ASN) and the least significant word is a locally defined 101 value whose meaning is assigned by the operator of the Autonomous 102 System in the most significant word. 104 Since the adoption of four-octet ASNs [RFC6793], the BGP Communities 105 attribute can no longer accommodate the above encoding, as a two- 106 octet word cannot fit a four-octet ASN. The BGP Extended Communities 107 attribute [RFC4360] is also unsuitable. The six-octet length of the 108 Extended Community value precludes the common operational practise of 109 encoding four-octet ASNs in both the Global Administrator and the 110 Local Administrator sub-fields. 112 To address these shortcomings, this document defines a BGP Large 113 Communities attribute encoded as an unordered set of one or more 114 twelve-octet values, each consisting of a four-octet Global 115 Administrator field and two four-octet operator-defined fields, each 116 of which can be used to denote properties or actions significant to 117 the operator of the Autonomous System assigning the values. 119 2. BGP Large Communities Attribute 121 This document defines the BGP Large Communities attribute as an 122 optional transitive path attribute of variable length. All routes 123 with the BGP Large Communities attribute belong to the communities 124 specified in the attribute. 126 Each BGP Large Community value is encoded as a 12-octet quantity, as 127 follows: 129 0 1 2 3 130 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 131 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 132 | Global Administrator | 133 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 134 | Local Data Part 1 | 135 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 136 | Local Data Part 2 | 137 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 139 Global Administrator: A four-octet namespace identifier. 141 Local Data Part 1: A four-octet operator-defined value. 143 Local Data Part 2: A four-octet operator-defined value. 145 The Global Administrator field is intended to allow different 146 Autonomous Systems to define BGP Large Communities without collision. 147 This field SHOULD be an Autonomous System Number (ASN), in which case 148 the Local Data Parts are to be interpreted as defined by the owner of 149 the ASN. The use of Reserved ASNs (0 [RFC7607], 65535 and 4294967295 150 [RFC7300]) is NOT RECOMMENDED. 152 There is no significance to the order in which twelve-octet Large 153 Community Attribute values are encoded in a Large Communities 154 attribute, A BGP speaker can transmit them in any order. 156 Duplicate BGP Large Community values MUST NOT be transmitted. A 157 receiving speaker MUST silently remove redundant BGP Large Community 158 values from a BGP Large Community attribute. 160 3. Aggregation 162 If a range of routes is aggregated, then the resulting aggregate 163 should have a BGP Large Communities attribute which contains all of 164 the BGP Large Communities attributes from all of the aggregated 165 routes. 167 4. Canonical Representation 169 The canonical representation of BGP Large Communities is three 170 separate unsigned integers in decimal notation in the following 171 order: Global Administrator, Local Data 1, Local Data 2. Numbers 172 MUST NOT contain leading zeros; a zero value MUST be represented with 173 a single zero. Each number is separated from the next by a single 174 colon. For example: 64496:4294967295:2, 64496:0:0. 176 BGP Large Communities SHOULD be represented in the canonical 177 representation. 179 5. Error Handling 181 The error handling of BGP Large Communities is as follows: 183 o A BGP Large Communities attribute SHALL be considered malformed if 184 the length of the BGP Large Communities Attribute value, expressed 185 in octets, is not a non-zero multiple of 12. 187 o A BGP Large Communities attribute SHALL NOT be considered 188 malformed due solely to presence of duplicate community values. 190 o A BGP UPDATE message with a malformed BGP Large Communities 191 attribute SHALL be handled using the approach of "treat-as- 192 withdraw" as described in section 2 [RFC7606]. 194 The BGP Large Communities Global Administrator field may contain any 195 value, and a BGP Large Communities attribute MUST NOT be considered 196 malformed if the Global Administrator field contains an unallocated, 197 unassigned or reserved ASN. 199 6. Security Considerations 201 This document does not change any underlying security issues 202 associated with any other BGP Communities mechanism. Specifically, 203 an AS relying on the BGP Large Communities attribute carried in BGP 204 must have trust in every other AS in the path, as any intermediate 205 Autonomous System in the path may have added, deleted, or altered the 206 BGP Large Communities attribute. Specifying the mechanism to provide 207 such trust is beyond the scope of this document. 209 BGP Large Communities do not protect the integrity of each community 210 value. Operators should be aware that it is possible for a BGP 211 speaker to alter BGP Large Community Attribute values in a BGP Update 212 Message. Protecting the integrity of the transitive handling of BGP 213 Large Community attributes in a manner consistent with the intent of 214 expressed BGP routing policies falls within the broader scope of 215 securing BGP, and is not specifically addressed here. 217 Network administrators should note the recommendations in Section 11 218 of BGP Operations and Security [RFC7454]. 220 7. Implementation status - RFC EDITOR: REMOVE BEFORE PUBLICATION 222 This section records the status of known implementations of the 223 protocol defined by this specification at the time of posting of this 224 Internet-Draft, and is based on a proposal described in RFC7942. The 225 description of implementations in this section is intended to assist 226 the IETF in its decision processes in progressing drafts to RFCs. 227 Please note that the listing of any individual implementation here 228 does not imply endorsement by the IETF. Furthermore, no effort has 229 been spent to verify the information presented here that was supplied 230 by IETF contributors. This is not intended as, and must not be 231 construed to be, a catalog of available implementations or their 232 features. Readers are advised to note that other implementations may 233 exist. 235 As of today these vendors have produced an implementation of BGP 236 Large Communities: 238 o Cisco IOS XR 240 o ExaBGP 242 o GoBGP 244 o BIRD 246 o OpenBGPD 248 o pmacct 250 o Quagga 252 The latest implementation news is tracked at 253 http://largebgpcommunities.net/ [1]. 255 8. IANA Considerations 257 IANA has made an Early Allocation of the value 32 (LARGE_COMMUNITY) 258 in the "BGP Path Attributes" registry under the "Border Gateway 259 Protocol (BGP) Parameters" group and is now asked to make that 260 Permanent. 262 9. Contributors 264 The following people contributed significantly to the content of the 265 document: 267 John Heasley 268 NTT Communications 269 Email: heas@shrubbery.net 271 Adam Simpson 272 Nokia 273 Email: adam.1.simpson@nokia.com 275 10. Acknowledgments 277 The authors would like to thank Ruediger Volk, Russ White, Acee 278 Lindem, Shyam Sethuram, Jared Mauch, Joel M. Halpern, Jeffrey Haas, 279 Gunter van de Velde, Marco Marzetti, Eduardo Ascenco Reis, Mark 280 Schouten, Paul Hoogsteder, Martijn Schmidt, Greg Hankins, Bertrand 281 Duvivier, Barry O'Donovan, Grzegorz Janoszka, Linda Dunbar, Marco 282 Davids, Gaurab Raj Upadhaya, Jeff Tantsura, Teun Vink, Adam 283 Davenport, Theodore Baschak, Pier Carlo Chiodi, Nabeel Cocker, Ian 284 Dickinson, Jan Baggen, Duncan Lockwood, David Farmer, Randy Bush, Wim 285 Henderickx, Stefan Plug, Kay Rechthien, Rob Shakir, Warren Kumari, 286 Gert Doering, Thomas King, Mikael Abrahamsson, Wesley Steehouwer, 287 Sander Steffann, Brad Dreisbach, Martin Millnert, Christopher Morrow, 288 Jay Borkenhagen, Arnold Nipper, Joe Provo, Niels Bakker, Bill Fenner, 289 Tom Daly, Ben Maddison, Alexander Azimov, Brian Dickson, Peter van 290 Dijk, Julian Seifert, Tom Petch, Tom Scholl, Arjen Zonneveld, Remco 291 van Mook, Adam Chappell, Jussi Peltola, Kristian Larsson, Markus 292 Hauschild, Richard Steenbergen, David Freedman, Richard Hartmann, 293 Geoff Huston, Mach Chen, and Alvaro Retana for their support, 294 insightful review and comments. 296 11. References 298 11.1. Normative References 300 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 301 Requirement Levels", BCP 14, RFC 2119, 302 DOI 10.17487/RFC2119, March 1997, 303 . 305 [RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A 306 Border Gateway Protocol 4 (BGP-4)", RFC 4271, 307 DOI 10.17487/RFC4271, January 2006, 308 . 310 [RFC7606] Chen, E., Ed., Scudder, J., Ed., Mohapatra, P., and K. 311 Patel, "Revised Error Handling for BGP UPDATE Messages", 312 RFC 7606, DOI 10.17487/RFC7606, August 2015, 313 . 315 11.2. Informative References 317 [RFC1997] Chandra, R., Traina, P., and T. Li, "BGP Communities 318 Attribute", RFC 1997, DOI 10.17487/RFC1997, August 1996, 319 . 321 [RFC4360] Sangli, S., Tappan, D., and Y. Rekhter, "BGP Extended 322 Communities Attribute", RFC 4360, DOI 10.17487/RFC4360, 323 February 2006, . 325 [RFC6793] Vohra, Q. and E. Chen, "BGP Support for Four-Octet 326 Autonomous System (AS) Number Space", RFC 6793, 327 DOI 10.17487/RFC6793, December 2012, 328 . 330 [RFC7300] Haas, J. and J. Mitchell, "Reservation of Last Autonomous 331 System (AS) Numbers", BCP 6, RFC 7300, 332 DOI 10.17487/RFC7300, July 2014, 333 . 335 [RFC7454] Durand, J., Pepelnjak, I., and G. Doering, "BGP Operations 336 and Security", BCP 194, RFC 7454, DOI 10.17487/RFC7454, 337 February 2015, . 339 [RFC7607] Kumari, W., Bush, R., Schiller, H., and K. Patel, 340 "Codification of AS 0 Processing", RFC 7607, 341 DOI 10.17487/RFC7607, August 2015, 342 . 344 11.3. URIs 346 [1] http://largebgpcommunities.net 348 Authors' Addresses 350 Jakob Heitz (editor) 351 Cisco 352 170 West Tasman Drive 353 San Jose, CA 95054 354 USA 356 Email: jheitz@cisco.com 358 Job Snijders (editor) 359 NTT Communications 360 Theodorus Majofskistraat 100 361 Amsterdam 1065 SZ 362 The Netherlands 364 Email: job@ntt.net 366 Keyur Patel 367 Arrcus, Inc 369 Email: keyur@arrcus.com 371 Ignas Bagdonas 372 Equinix 373 80 Cheapside 374 London EC2V 6EE 375 United Kingdom 377 Email: ibagdona.ietf@gmail.com 378 Nick Hilliard 379 INEX 380 4027 Kingswood Road 381 Dublin 24 382 IE 384 Email: nick@inex.ie