idnits 2.17.1 draft-ietf-idr-as-private-reservation-01.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 (Using the creation date from RFC1930, updated by this document, for RFC5378 checks: 1996-03-01) -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (December 20, 2012) is 4116 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- No issues found here. Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group J. Mitchell 3 Internet-Draft Microsoft Corporation 4 Updates: 1930 (if approved) December 20, 2012 5 Intended status: Informational 6 Expires: June 23, 2013 8 Autonomous System (AS) Reservation for Private Use 9 draft-ietf-idr-as-private-reservation-01 11 Abstract 13 This document describes the reservation of Autonomous System numbers 14 (ASNs) that are for Private Use only and should not be advertised to 15 the Internet, known as Private Use ASNs. This document enlarges the 16 total space available for Private Use ASNs by documenting the 17 reservation of a second, larger range and updates RFC 1930 by 18 replacing Section 10. 20 Status of this Memo 22 This Internet-Draft is submitted in full conformance with the 23 provisions of BCP 78 and BCP 79. 25 Internet-Drafts are working documents of the Internet Engineering 26 Task Force (IETF). Note that other groups may also distribute 27 working documents as Internet-Drafts. The list of current Internet- 28 Drafts is at http://datatracker.ietf.org/drafts/current/. 30 Internet-Drafts are draft documents valid for a maximum of six months 31 and may be updated, replaced, or obsoleted by other documents at any 32 time. It is inappropriate to use Internet-Drafts as reference 33 material or to cite them other than as "work in progress." 35 This Internet-Draft will expire on June 23, 2013. 37 Copyright Notice 39 Copyright (c) 2012 IETF Trust and the persons identified as the 40 document authors. All rights reserved. 42 This document is subject to BCP 78 and the IETF Trust's Legal 43 Provisions Relating to IETF Documents 44 (http://trustee.ietf.org/license-info) in effect on the date of 45 publication of this document. Please review these documents 46 carefully, as they describe your rights and restrictions with respect 47 to this document. Code Components extracted from this document must 48 include Simplified BSD License text as described in Section 4.e of 49 the Trust Legal Provisions and are provided without warranty as 50 described in the Simplified BSD License. 52 1. Introduction 54 The original IANA reservation of Autonomous System Numbers (ASNs) for 55 Private Use was a block of 1023 ASNs. This was also documented by 56 IETF in Section 10 of [RFC1930]. Since the time when that range was 57 reserved, BGP has seen much wider deployment in service provider, 58 enterprise, and datacenter networks. The places in these networks 59 where Private Use ASNs are in use include networks that are attached 60 to the Internet, utilizing implementation specific features to remove 61 them upon advertisement to Internet peers, and networks that are not 62 attached to the Internet. 64 The limited size of the current range of Private Use ASNs has led to 65 the re-use of the same ASN within a single organization, requiring 66 the use of a number of implementation specific features that 67 manipulate the AS_PATH or remove AS_PATH based loop prevention 68 described in Section 9 of [RFC4271]. These workarounds have 69 increased the operational complexity of the networks since the 70 implementations of these functions vary and are not defined in 71 existing BGP standards. 73 Since the introduction of BGP Support for Four-octet AS Number Space 74 [RFC6793], the total size of the ASN space has increased 75 dramatically, and a larger subset of the space should be available to 76 network operators to deploy in Private Use cases. The existing range 77 of Private Use ASNs is widely deployed and the ability to renumber 78 this resource in existing networks cannot be coordinated given these 79 ASNs by definition are not registered. Therefore this documents the 80 existing Private Use ASN reservation, while also introducing a 81 second, larger range that can also be utilized. 83 2. Private Use ASNs 85 To allow the continued growth of usage of the BGP protocol in 86 networks that utilize Private Use ASNs, two ranges of ASNs are 87 reserved by this document in Section 5. The first which was 88 previously defined in [RFC1930] out of the original 16-bit Autonomous 89 System range and a second, larger range out of the higher part of the 90 Four-Octet AS Number Space [RFC6793]. 92 3. Operational Considerations 94 If Private Use ASNs are used and prefixes are originated from these 95 ASNs which are destined to the Internet, Private Use ASNs must be 96 removed from the AS_PATH before being advertised to the global 97 Internet. Operators are cautioned to ensure any implementation 98 specific features that recognize Private Use ASNs have been updated 99 to recognize both ranges prior to making use of the newer, 100 numerically higher range of Private Use ASNs. Some implementations 101 of such features will fail to remove any Private Use ASNs from the 102 AS_PATH if the AS_PATH contains a mix of Private Use and non-Private 103 Use ASNs and if these implementations are not updated, the newer 104 range may be classified as the later. Normal AS_PATH filtering may 105 also be used to limit prefixes originating from Private Use ASNs from 106 being advertised to the global Internet and can help in transition 107 scenarios until the implementation specific features that manipulate 108 AS_PATH are updated. 110 4. Acknowledgements 112 The author would like to acknowledge Christopher Morrow, Jason 113 Schiller, and John Scudder for their advice on how to pursue this 114 change. The author would also like to thank Brian Dickson, David 115 Farmer, Jeffrey Haas, Nick Hilliard, Warren Kumari, and Jeff Wheeler 116 for their comments and suggestions. 118 5. IANA Considerations 120 [Note to IANA, NOT for publication: The IANA should update the "16- 121 bit Autonomous System Numbers" registry to reference this RFC (when 122 published) for the existing Private Use reservation. Further, to 123 maintain consistency from an operator standpoint, it is suggested 124 that the end of the "32-bit Autonomous System Numbers" range be 125 reserved for Private Use, and a size of 94,967,295 (value to replace 126 TBD1 below) is suggested corresponding to the range of 4200000000 127 (value to replace TBD2 below) to 4294967294 (value to replace TBD3 128 below).] 130 IANA has reserved, for Private Use, a contiguous block of 1023 131 Autonomous System numbers from the "16-bit Autonomous System Numbers" 132 registry, namely 64512 - 65534 inclusive. 134 IANA has also reserved, for Private Use, a contiguous block of TBD1 135 Autonomous System numbers from the "32-bit Autonomous System Numbers" 136 registry, namely TBD2 - TBD3 inclusive. 138 These reservations have been documented in the IANA Autonomous System 139 Numbers Registry [IANA.AS]. 141 6. Security Considerations 143 This document does not introduce any additional security concerns in 144 regards to Private Use ASNs. 146 7. References 148 7.1. Normative References 150 [RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway 151 Protocol 4 (BGP-4)", RFC 4271, January 2006. 153 [RFC6793] Vohra, Q. and E. Chen, "BGP Support for Four-Octet 154 Autonomous System (AS) Number Space", RFC 6793, 155 December 2012. 157 7.2. Informative References 159 [IANA.AS] IANA, "Autonomous System (AS) Numbers", December 2012, 160 . 162 [RFC1930] Hawkinson, J. and T. Bates, "Guidelines for creation, 163 selection, and registration of an Autonomous System (AS)", 164 BCP 6, RFC 1930, March 1996. 166 Author's Address 168 Jon Mitchell 169 Microsoft Corporation 170 12012 Sunset Hills Road 171 Reston, VA 20190 172 USA 174 Email: Jon.Mitchell@microsoft.com