idnits 2.17.1 draft-heitz-idr-large-community-03.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 doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (September 2, 2016) is 2792 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) No issues found here. Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 IDR J. Heitz 3 Internet-Draft Cisco 4 Intended status: Standards Track K. Patel 5 Expires: March 6, 2017 Arrcus 6 J. Snijders 7 NTT 8 I. Bagdonas 9 Equinix 10 A. Simpson 11 Nokia 12 September 2, 2016 14 Large BGP Community 15 draft-heitz-idr-large-community-03 17 Abstract 19 A new type of BGP community attribute that contains communities that 20 each hold a 4-octet AS number and a 8-octet opaque field is defined. 22 Requirements Language 24 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 25 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 26 document are to be interpreted as described in [RFC2119]. 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 March 6, 2017. 45 Copyright Notice 47 Copyright (c) 2016 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. Large BGP Community Attribute . . . . . . . . . . . . . . . . 2 64 3. Textual Representation . . . . . . . . . . . . . . . . . . . 3 65 4. Security Considerations . . . . . . . . . . . . . . . . . . . 3 66 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 67 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 3 68 7. Normative References . . . . . . . . . . . . . . . . . . . . 3 69 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 4 71 1. Introduction 73 A BGP Community attribute is defined that encodes 12 byte 74 communities, suitable for 4-Octet Autonomous System Numbers that 75 require 8 octets of locally significant opaque data. 77 To ensure rapid and smooth adoption of the new community attribute, 78 it must be as similar to the [RFC1997] community as possible, only 79 bigger. 81 2. Large BGP Community Attribute 83 The Large Community Attribute is a transitive optional BGP attribute, 84 with the Type Code (suggested 41) to be assigned by IANA. The 85 attribute consists of a set of "Large Communities". All routes with 86 the Large Community attribute belong to the communities listed in the 87 attribute. 89 Each Large Community is encoded as a 12-octet quantity, as follows: 91 0 1 2 3 92 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 93 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 94 | Autonomous System number | 95 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 96 | Local Data Part 1 | 97 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 98 | Local Data Part 2 | 99 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 101 3. Textual Representation 103 The textual representation of the Large BGP Community is A:B:C, where 104 A is the Autonomous System number, B is the Local Data part 1 and C 105 is the Local Data part 2. A ranges from 0 to 4294967295. B ranges 106 from 0 to 4294967295. C ranges from 0 to 4294967295. A, B and C are 107 plain decimal non-negative integers without leading zeroes. Each 108 number must appear, even if it is 0. For example, "0:1:2" cannot be 109 written as ":1:2". The string is expected to match the following 110 regular expression: ^[0-9]+:[0-9]+:[0-9]+$ 112 4. Security Considerations 114 TBD 116 5. IANA Considerations 118 IANA is requested to assign a BGP path attribute value for the Large 119 community attribute. 121 6. Acknowledgements 123 Thanks to Russ White, Acee Lindem, Shyam Sethuram and Jared Mauch for 124 insightful review and comments. 126 7. Normative References 128 [RFC1997] Chandra, R., Traina, P., and T. Li, "BGP Communities 129 Attribute", RFC 1997, DOI 10.17487/RFC1997, August 1996, 130 . 132 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 133 Requirement Levels", BCP 14, RFC 2119, 134 DOI 10.17487/RFC2119, March 1997, 135 . 137 Authors' Addresses 139 Jakob Heitz 140 Cisco 141 170 West Tasman Drive 142 San Jose, CA 95054 143 USA 145 Email: jheitz@cisco.com 147 Keyur Patel 148 Arrcus, Inc 150 Email: keyur@arrcus.com 152 Job Snijders 153 NTT Communications, Inc. 154 Theodorus Majofskistraat 100 155 Amsterdam 1065 SZ 156 NL 158 Email: job@ntt.net 160 Ignas Bagdonas 161 Equinix 162 London 163 UK 165 Email: ibagdona.ietf@gmail.com 167 Adam Simpson 168 Nokia 169 600 March Road 170 Ottawa Ontario K2K 2E6 171 Canada 173 Email: adam.1.simpson@nokia.com