idnits 2.17.1 draft-heitz-idr-large-community-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 : ---------------------------------------------------------------------------- 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 (July 18, 2016) is 2839 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 K. Patel 4 Intended status: Standards Track Cisco 5 Expires: January 19, 2017 J. Snijders 6 NTT 7 I. Bagdonas 8 Equinix 9 July 18, 2016 11 Large BGP Community 12 draft-heitz-idr-large-community-02 14 Abstract 16 A new type of BGP community attribute that contains communities that 17 each hold a 4-octet AS number and a 8-octet opaque field is defined. 19 Requirements Language 21 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 22 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 23 document are to be interpreted as described in [RFC2119]. 25 Status of This Memo 27 This Internet-Draft is submitted in full conformance with the 28 provisions of BCP 78 and BCP 79. 30 Internet-Drafts are working documents of the Internet Engineering 31 Task Force (IETF). Note that other groups may also distribute 32 working documents as Internet-Drafts. The list of current Internet- 33 Drafts is at http://datatracker.ietf.org/drafts/current/. 35 Internet-Drafts are draft documents valid for a maximum of six months 36 and may be updated, replaced, or obsoleted by other documents at any 37 time. It is inappropriate to use Internet-Drafts as reference 38 material or to cite them other than as "work in progress." 40 This Internet-Draft will expire on January 19, 2017. 42 Copyright Notice 44 Copyright (c) 2016 IETF Trust and the persons identified as the 45 document authors. All rights reserved. 47 This document is subject to BCP 78 and the IETF Trust's Legal 48 Provisions Relating to IETF Documents 49 (http://trustee.ietf.org/license-info) in effect on the date of 50 publication of this document. Please review these documents 51 carefully, as they describe your rights and restrictions with respect 52 to this document. Code Components extracted from this document must 53 include Simplified BSD License text as described in Section 4.e of 54 the Trust Legal Provisions and are provided without warranty as 55 described in the Simplified BSD License. 57 Table of Contents 59 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 60 2. Large BGP Community Attribute . . . . . . . . . . . . . . . . 2 61 3. Textual Representation . . . . . . . . . . . . . . . . . . . 3 62 4. Security Considerations . . . . . . . . . . . . . . . . . . . 3 63 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 64 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 3 65 7. Normative References . . . . . . . . . . . . . . . . . . . . 3 66 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 3 68 1. Introduction 70 A BGP Community attribute is defined that encodes 12 byte 71 communities, suitable for 4-Octet Autonomous System Numbers that 72 require 8 octets of locally significant opaque data. 74 To ensure rapid and smooth adoption of the new community attribute, 75 it must be as similar to the [RFC1997] community as possible, only 76 bigger. 78 2. Large BGP Community Attribute 80 The Large Community Attribute is a transitive optional BGP attribute, 81 with the Type Code (suggested 41) to be assigned by IANA. The 82 attribute consists of a set of "Large Communities". All routes with 83 the Large Community attribute belong to the communities listed in the 84 attribute. 86 Each Large Community is encoded as a 12-octet quantity, as follows: 88 0 1 2 3 89 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 90 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 91 | Autonomous System number | 92 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 93 | Local Data Part 1 | 94 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 95 | Local Data Part 2 | 96 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 98 3. Textual Representation 100 The textual representation of the Large BGP Community is A:B:C, where 101 A is the Autonomous System number, B is the Local Data part 1 and C 102 is the Local Data part 2. A ranges from 0 to 4294967295. B ranges 103 from 0 to 4294967295. C ranges from 0 to 4294967295. A, B and C are 104 plain decimal non-negative integers without leading zeroes. Each 105 number must appear, even if it is 0. For example, "0:1:2" cannot be 106 written as ":1:2". The string is expected to match the following 107 regular expression: ^[0-9]+:[0-9]+:[0-9]+$ 109 4. Security Considerations 111 TBD 113 5. IANA Considerations 115 IANA is requested to assign a BGP path attribute value for the Large 116 community attribute. 118 6. Acknowledgements 120 Thanks to Russ White, Acee Lindem, Shyam Sethuram and Jared Mauch for 121 insightful review and comments. 123 7. Normative References 125 [RFC1997] Chandra, R., Traina, P., and T. Li, "BGP Communities 126 Attribute", RFC 1997, DOI 10.17487/RFC1997, August 1996, 127 . 129 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 130 Requirement Levels", BCP 14, RFC 2119, 131 DOI 10.17487/RFC2119, March 1997, 132 . 134 Authors' Addresses 136 Jakob Heitz 137 Cisco 138 170 West Tasman Drive 139 San Jose, CA 95054 140 USA 142 Email: jheitz@cisco.com 143 Keyur Patel 144 Cisco 145 170 West Tasman Drive 146 San Jose, CA 95054 147 USA 149 Email: keyupate@cisco.com 151 Job Snijders 152 NTT Communications, Inc. 153 Theodorus Majofskistraat 100 154 Amsterdam 1065 SZ 155 NL 157 Email: job@ntt.net 159 Ignas Bagdonas 160 Equinix 161 London 162 UK 164 Email: ibagdona.ietf@gmail.com