1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
|
<pre>Internet Engineering Task Force (IETF) J. Haas
Request for Comments: 7300 Juniper Networks
BCP: 6 J. Mitchell
Updates: <a href="./rfc1930">1930</a> Microsoft Corporation
Category: Best Current Practice July 2014
ISSN: 2070-1721
<span class="h1">Reservation of Last Autonomous System (AS) Numbers</span>
Abstract
This document reserves two Autonomous System Numbers (ASNs) at the
end of the 16-bit and 32-bit ranges, described in this document as
"Last ASNs", and provides guidance to implementers and operators on
their use. This document updates <a href="./rfc1930#section-10">Section 10 of RFC 1930</a>.
Status of This Memo
This memo documents an Internet Best Current Practice.
This document is a product of the Internet Engineering Task Force
(IETF). It has been approved for publication by the Internet
Engineering Steering Group (IESG). Further information on BCPs is
available in <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
<a href="http://www.rfc-editor.org/info/rfc7300">http://www.rfc-editor.org/info/rfc7300</a>.
Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
<span class="grey">Haas & Mitchell Best Current Practice [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc7300">RFC 7300</a> Last AS Reservation July 2014</span>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
Over a decade ago, IANA reserved the last Autonomous System Number
(ASN) of the 16-bit ASN range, 65535, with the intention that it not
be used by network operators running BGP [<a href="./rfc4271" title=""A Border Gateway Protocol 4 (BGP-4)"">RFC4271</a>]. Since the
introduction of "BGP Support for Four-Octet Autonomous System (AS)
Number Space" [<a href="./rfc6793" title=""BGP Support for Four-Octet Autonomous System (AS) Number Space"">RFC6793</a>], IANA has also reserved the last ASN of the
32-bit autonomous system number range, 4294967295. This reservation
has been documented in the IANA "Autonomous System (AS) Numbers"
registry [<a href="#ref-IANA.AS" title=""Autonomous System (AS) Numbers"">IANA.AS</a>]. Although these "Last ASNs" border on Private Use
ASN [<a href="./rfc6996" title=""Autonomous System (AS) Reservation for Private Use"">RFC6996</a>] ranges, they are not defined or reserved as Private Use
ASNs by [<a href="#ref-IANA.AS" title=""Autonomous System (AS) Numbers"">IANA.AS</a>]. This document describes the reasoning for
reserving Last ASNs and provides guidance both to operators and to
implementers on their use.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Requirements Language</span>
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
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>].
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Reasons for Reservation of the Last ASNs</span>
A subset of the BGP communities of ASN 65535, the last ASN of the
16-bit range, are reserved for use by Well-known Communities as
described in [<a href="./rfc1997" title=""BGP Communities Attribute"">RFC1997</a>] and [<a href="#ref-IANA.WK" title=""Border Gateway Protocol (BGP) Well-known Communities"">IANA.WK</a>]. Although this is not currently
true of ASN 4294967295, if there is a future need for another Special
Use ASN that is not designed to be globally routable, or for the
associated BGP communities of such an ASN, ASN 4294967295 could be a
valid candidate for such purpose. This document does not prescribe
any such Special Use to this ASN at the time of publication.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Operational Considerations</span>
Operators SHOULD NOT use these Last ASNs for any other purpose or as
Private Use ASNs. Operational use of these Last ASNs could have
undesirable results. For example; use of AS 65535 as if it were a
Private Use ASN, may result in inadvertent use of BGP Well-known
Community values [<a href="#ref-IANA.WK" title=""Border Gateway Protocol (BGP) Well-known Communities"">IANA.WK</a>], causing undesirable routing behavior.
Last ASNs MUST NOT be advertised to the global Internet within
AS_PATH or AS4_PATH attributes. Operators SHOULD filter Last ASNs
within the AS_PATH and AS4_PATH attributes.
<span class="grey">Haas & Mitchell Best Current Practice [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc7300">RFC 7300</a> Last AS Reservation July 2014</span>
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Implementation Considerations</span>
While Last ASNs are reserved, they remain valid ASNs from a BGP
perspective. Therefore, implementations of BGP [<a href="./rfc4271" title=""A Border Gateway Protocol 4 (BGP-4)"">RFC4271</a>] SHOULD NOT
treat the use of Last ASNs as any type of protocol error. However,
if a Last ASN is configured as the local AS, implementations MAY
generate a warning message indicating improper use of a reserved ASN.
Implementations that provide tools that filter Private Use ASNs
within the AS_PATH and AS4_PATH attributes MAY also include Last
ASNs.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. IANA Considerations</span>
IANA has reserved last Autonomous System number 65535 from the
"16-bit Autonomous System Numbers" registry for the reasons described
in this document.
IANA has also reserved last Autonomous System number 4294967295 from
the "32-bit Autonomous System Numbers" registry for the reasons
described in this document.
These reservations have been documented in the IANA "Autonomous
System (AS) Numbers" registry [<a href="#ref-IANA.AS" title=""Autonomous System (AS) Numbers"">IANA.AS</a>] and the IANA "Special-Purpose
Autonomous System (AS) Numbers" registry [<a href="#ref-IANA.SpecialAS">IANA.SpecialAS</a>].
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Security Considerations</span>
This document does not introduce any additional security concerns in
regards to usage of Last ASNs. Although the BGP is designed to allow
usage of Last ASNs, security issues related to BGP implementation
errors could be triggered by Last ASN usage.
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. References</span>
<span class="h3"><a class="selflink" id="section-8.1" href="#section-8.1">8.1</a>. Normative References</span>
[<a id="ref-IANA.AS">IANA.AS</a>] IANA, "Autonomous System (AS) Numbers",
<<a href="http://www.iana.org/assignments/as-numbers/">http://www.iana.org/assignments/as-numbers/</a>>.
[<a id="ref-IANA.SpecialAS">IANA.SpecialAS</a>]
IANA, "Special-Purpose Autonomous System (AS) Numbers",
<<a href="http://www.iana.org/assignments/iana-as-numbers-special-registry/">http://www.iana.org/assignments/</a>
<a href="http://www.iana.org/assignments/iana-as-numbers-special-registry/">iana-as-numbers-special-registry/</a>>.
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
<span class="grey">Haas & Mitchell Best Current Practice [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc7300">RFC 7300</a> Last AS Reservation July 2014</span>
[<a id="ref-RFC4271">RFC4271</a>] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway
Protocol 4 (BGP-4)", <a href="./rfc4271">RFC 4271</a>, January 2006.
[<a id="ref-RFC6793">RFC6793</a>] Vohra, Q. and E. Chen, "BGP Support for Four-Octet
Autonomous System (AS) Number Space", <a href="./rfc6793">RFC 6793</a>, December
2012.
<span class="h3"><a class="selflink" id="section-8.2" href="#section-8.2">8.2</a>. Informative References</span>
[<a id="ref-IANA.WK">IANA.WK</a>] IANA, "Border Gateway Protocol (BGP) Well-known
Communities", <<a href="http://www.iana.org/assignments/bgp-well-known-communities/">http://www.iana.org/assignments/</a>
<a href="http://www.iana.org/assignments/bgp-well-known-communities/">bgp-well-known-communities/</a>>.
[<a id="ref-RFC1997">RFC1997</a>] Chandrasekeran, R., Traina, P., and T. Li, "BGP
Communities Attribute", <a href="./rfc1997">RFC 1997</a>, August 1996.
[<a id="ref-RFC6996">RFC6996</a>] Mitchell, J., "Autonomous System (AS) Reservation for
Private Use", <a href="https://www.rfc-editor.org/bcp/bcp6">BCP 6</a>, <a href="./rfc6996">RFC 6996</a>, July 2013.
<span class="grey">Haas & Mitchell Best Current Practice [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc7300">RFC 7300</a> Last AS Reservation July 2014</span>
<span class="h2"><a class="selflink" id="appendix-A" href="#appendix-A">Appendix A</a>. Acknowledgments</span>
The authors would like to thank Michelle Cotton and Elwyn Davies for
encouraging the proper documentation of the reservation of these
ASNs, and David Farmer for his contributions to the document.
Authors' Addresses
Jeffrey Haas
Juniper Networks
EMail: jhaas@juniper.net
Jon Mitchell
Microsoft Corporation
One Microsoft Way
Redmond, WA 98052
USA
EMail: Jon.Mitchell@microsoft.com
Haas & Mitchell Best Current Practice [Page 5]
</pre>
|
