| 1 |
<pre>Internet Engineering Task Force (IETF) J. Mitchell |
| 2 |
Request for Comments: 6996 Microsoft Corporation |
| 3 |
BCP: 6 July 2013 |
| 4 |
Updates: <a href="./rfc1930">1930</a> |
| 5 |
Category: Best Current Practice |
| 6 |
ISSN: 2070-1721 |
| 7 |
|
| 8 |
|
| 9 |
<span class="h1">Autonomous System (AS) Reservation for Private Use</span> |
| 10 |
|
| 11 |
Abstract |
| 12 |
|
| 13 |
This document describes the reservation of Autonomous System Numbers |
| 14 |
(ASNs) that are for Private Use only, known as Private Use ASNs, and |
| 15 |
provides operational guidance on their use. This document enlarges |
| 16 |
the total space available for Private Use ASNs by documenting the |
| 17 |
reservation of a second, larger range and updates <a href="./rfc1930">RFC 1930</a> by |
| 18 |
replacing <a href="#section-10">Section 10</a> of that document. |
| 19 |
|
| 20 |
Status of This Memo |
| 21 |
|
| 22 |
This memo documents an Internet Best Current Practice. |
| 23 |
|
| 24 |
This document is a product of the Internet Engineering Task Force |
| 25 |
(IETF). It represents the consensus of the IETF community. It has |
| 26 |
received public review and has been approved for publication by the |
| 27 |
Internet Engineering Steering Group (IESG). Further information on |
| 28 |
BCPs is available in <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>. |
| 29 |
|
| 30 |
Information about the current status of this document, any errata, |
| 31 |
and how to provide feedback on it may be obtained at |
| 32 |
<a href="http://www.rfc-editor.org/info/rfc6996">http://www.rfc-editor.org/info/rfc6996</a>. |
| 33 |
|
| 34 |
Copyright Notice |
| 35 |
|
| 36 |
Copyright (c) 2013 IETF Trust and the persons identified as the |
| 37 |
document authors. All rights reserved. |
| 38 |
|
| 39 |
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal |
| 40 |
Provisions Relating to IETF Documents |
| 41 |
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of |
| 42 |
publication of this document. Please review these documents |
| 43 |
carefully, as they describe your rights and restrictions with respect |
| 44 |
to this document. Code Components extracted from this document must |
| 45 |
include Simplified BSD License text as described in Section 4.e of |
| 46 |
the Trust Legal Provisions and are provided without warranty as |
| 47 |
described in the Simplified BSD License. |
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Mitchell Best Current Practice [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc6996">RFC 6996</a> Private Use AS Reservation July 2013</span> |
| 55 |
|
| 56 |
|
| 57 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span> |
| 58 |
|
| 59 |
The original IANA reservation of Autonomous System Numbers (ASNs) for |
| 60 |
Private Use was a block of 1023 ASNs. This was also documented by |
| 61 |
the IETF in <a href="./rfc1930#section-10">Section 10 of [RFC1930]</a>. Since the time that the range |
| 62 |
was reserved, the Border Gateway Protocol (BGP) [<a href="./rfc4271" title=""A Border Gateway Protocol 4 (BGP-4)"">RFC4271</a>] has seen |
| 63 |
deployment in new application domains, such as data center networks, |
| 64 |
which require a larger Private Use AS space. |
| 65 |
|
| 66 |
Since the introduction of "BGP Support for Four-Octet Autonomous |
| 67 |
System (AS) Number Space" [<a href="./rfc6793" title=""BGP Support for Four-Octet Autonomous System (AS) Number Space"">RFC6793</a>], the total size of ASN space has |
| 68 |
increased dramatically. A larger subset of the space is available to |
| 69 |
network operators to deploy in these Private Use cases. The existing |
| 70 |
range of Private Use ASNs is widely deployed, and the ability to |
| 71 |
renumber this resource in existing networks cannot be coordinated |
| 72 |
given that these ASNs, by definition, are not registered. Therefore, |
| 73 |
this RFC documents the existing Private Use ASN reservation while |
| 74 |
also introducing a second, larger range that can also be utilized. |
| 75 |
|
| 76 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Requirements Language</span> |
| 77 |
|
| 78 |
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", |
| 79 |
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this |
| 80 |
document are to be interpreted as described in <a href="./rfc2119">RFC 2119</a> [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>]. |
| 81 |
|
| 82 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Private Use ASNs</span> |
| 83 |
|
| 84 |
To allow the continued growth of BGP protocol usage in new network |
| 85 |
applications that utilize Private Use ASNs, two ranges of ASNs are |
| 86 |
reserved by <a href="#section-5">Section 5</a> of this document. The first is part of the |
| 87 |
original 16-bit Autonomous System range previously defined in |
| 88 |
[<a href="./rfc1930" title=""Guidelines for creation, selection, and registration of an Autonomous System (AS)"">RFC1930</a>], and the second is a larger range out of the Four-Octet AS |
| 89 |
Number Space [<a href="./rfc6793" title=""BGP Support for Four-Octet Autonomous System (AS) Number Space"">RFC6793</a>]. |
| 90 |
|
| 91 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Operational Considerations</span> |
| 92 |
|
| 93 |
If Private Use ASNs are used and prefixes originate from these ASNs, |
| 94 |
Private Use ASNs MUST be removed from AS path attributes (including |
| 95 |
AS4_PATH if utilizing a four-octet AS number space) before being |
| 96 |
advertised to the global Internet. Operators SHOULD ensure that all |
| 97 |
External Border Gateway Protocol (EBGP) speakers support the |
| 98 |
extensions described in [<a href="./rfc6793" title=""BGP Support for Four-Octet Autonomous System (AS) Number Space"">RFC6793</a>] and that implementation-specific |
| 99 |
features that recognize Private Use ASNs have been updated to |
| 100 |
recognize both ranges prior to making use of the newer, numerically |
| 101 |
higher range of Private Use ASNs in the four-octet AS number space. |
| 102 |
Some existing implementations that remove Private Use ASNs from the |
| 103 |
AS_PATH are known to not remove Private Use ASNs if the AS_PATH |
| 104 |
contains a mixture of Private Use and Non-Private Use ASNs. If such |
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Mitchell Best Current Practice [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc6996">RFC 6996</a> Private Use AS Reservation July 2013</span> |
| 111 |
|
| 112 |
|
| 113 |
implementations have not been updated to recognize the new range of |
| 114 |
ASNs in this document and a mix of old and new range Private Use ASNs |
| 115 |
exist in the AS4_PATH, these implementations will likely cease to |
| 116 |
remove any Private Use ASNs from either of the AS path attributes. |
| 117 |
Normal AS path filtering MAY also be used to prevent prefixes |
| 118 |
originating from Private Use ASNs from being advertised to the global |
| 119 |
Internet. |
| 120 |
|
| 121 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. IANA Considerations</span> |
| 122 |
|
| 123 |
IANA has reserved, for Private Use, a contiguous block of 1023 |
| 124 |
Autonomous System numbers from the "16-bit Autonomous System Numbers" |
| 125 |
registry, namely 64512 - 65534 inclusive. |
| 126 |
|
| 127 |
IANA has also reserved, for Private Use, a contiguous block of |
| 128 |
94,967,295 Autonomous System numbers from the "32-bit Autonomous |
| 129 |
System Numbers" registry, namely 4200000000 - 4294967294 inclusive. |
| 130 |
|
| 131 |
These reservations have been documented in the IANA "Autonomous |
| 132 |
System (AS) Numbers" registry [<a href="#ref-IANA.AS" title=""Autonomous System (AS) Numbers"">IANA.AS</a>]. |
| 133 |
|
| 134 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Security Considerations</span> |
| 135 |
|
| 136 |
Private Use ASNs do not raise any unique security concerns. Loss of |
| 137 |
connectivity might result from their inappropriate use, specifically |
| 138 |
outside of a single organization, since they are not globally unique. |
| 139 |
This loss of connectivity is limited to the organization using |
| 140 |
Private Use ASNs inappropriately or without reference to <a href="#section-4">Section 4</a>. |
| 141 |
General BGP security considerations are discussed in [<a href="./rfc4271" title=""A Border Gateway Protocol 4 (BGP-4)"">RFC4271</a>] and |
| 142 |
[<a href="./rfc4272" title=""BGP Security Vulnerabilities Analysis"">RFC4272</a>]. Identification of the originator of a route with a |
| 143 |
Private Use ASN in the AS path would have to be done by tracking the |
| 144 |
route back to the neighboring globally unique AS in the path or by |
| 145 |
inspecting other attributes. |
| 146 |
|
| 147 |
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. References</span> |
| 148 |
|
| 149 |
<span class="h3"><a class="selflink" id="section-7.1" href="#section-7.1">7.1</a>. Normative References</span> |
| 150 |
|
| 151 |
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate |
| 152 |
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997. |
| 153 |
|
| 154 |
[<a id="ref-RFC4271">RFC4271</a>] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway |
| 155 |
Protocol 4 (BGP-4)", <a href="./rfc4271">RFC 4271</a>, January 2006. |
| 156 |
|
| 157 |
[<a id="ref-RFC6793">RFC6793</a>] Vohra, Q. and E. Chen, "BGP Support for Four-Octet |
| 158 |
Autonomous System (AS) Number Space", <a href="./rfc6793">RFC 6793</a>, |
| 159 |
December 2012. |
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Mitchell Best Current Practice [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc6996">RFC 6996</a> Private Use AS Reservation July 2013</span> |
| 167 |
|
| 168 |
|
| 169 |
<span class="h3"><a class="selflink" id="section-7.2" href="#section-7.2">7.2</a>. Informative References</span> |
| 170 |
|
| 171 |
[<a id="ref-IANA.AS">IANA.AS</a>] IANA, "Autonomous System (AS) Numbers", |
| 172 |
<<a href="http://www.iana.org/assignments/as-numbers/">http://www.iana.org/assignments/as-numbers/</a>>. |
| 173 |
|
| 174 |
[<a id="ref-RFC1930">RFC1930</a>] Hawkinson, J. and T. Bates, "Guidelines for creation, |
| 175 |
selection, and registration of an Autonomous System (AS)", |
| 176 |
<a href="https://www.rfc-editor.org/bcp/bcp6">BCP 6</a>, <a href="./rfc1930">RFC 1930</a>, March 1996. |
| 177 |
|
| 178 |
[<a id="ref-RFC4272">RFC4272</a>] Murphy, S., "BGP Security Vulnerabilities Analysis", |
| 179 |
<a href="./rfc4272">RFC 4272</a>, January 2006. |
| 180 |
|
| 181 |
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Acknowledgements</span> |
| 182 |
|
| 183 |
The author would like to acknowledge Christopher Morrow, Jason |
| 184 |
Schiller, and John Scudder for their advice on how to pursue this |
| 185 |
change. The author would also like to thank Brian Dickson, David |
| 186 |
Farmer, Jeffrey Haas, Nick Hilliard, Joel Jaeggli, Warren Kumari, and |
| 187 |
Jeff Wheeler for their comments and suggestions. |
| 188 |
|
| 189 |
Author's Address |
| 190 |
|
| 191 |
Jon Mitchell |
| 192 |
Microsoft Corporation |
| 193 |
One Microsoft Way |
| 194 |
Redmond, WA 98052 |
| 195 |
USA |
| 196 |
|
| 197 |
EMail: [email protected] |
| 198 |
|
| 199 |
|
| 200 |
|
| 201 |
|
| 202 |
|
| 203 |
|
| 204 |
|
| 205 |
|
| 206 |
|
| 207 |
|
| 208 |
|
| 209 |
|
| 210 |
|
| 211 |
|
| 212 |
|
| 213 |
|
| 214 |
|
| 215 |
|
| 216 |
|
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
Mitchell Best Current Practice [Page 4] |
| 221 |
</pre> |