| 1 |
<pre>Network Working Group J. Stewart |
| 2 |
Request for Comments: 2270 ISI |
| 3 |
Category: Informational T. Bates |
| 4 |
R. Chandra |
| 5 |
E. Chen |
| 6 |
Cisco |
| 7 |
January 1998 |
| 8 |
|
| 9 |
|
| 10 |
<span class="h1">Using a Dedicated AS for Sites Homed to a Single Provider</span> |
| 11 |
|
| 12 |
Status of this Memo |
| 13 |
|
| 14 |
This memo provides information for the Internet community. It does |
| 15 |
not specify an Internet standard of any kind. Distribution of this |
| 16 |
memo is unlimited. |
| 17 |
|
| 18 |
Copyright Notice |
| 19 |
|
| 20 |
Copyright (C) The Internet Society (1998). All Rights Reserved. |
| 21 |
|
| 22 |
Abstract |
| 23 |
|
| 24 |
With the increased growth of the Internet, the number of customers |
| 25 |
using BGP4 has grown significantly. <a href="./rfc1930">RFC1930</a> outlines a set of |
| 26 |
guidelines for when one needs and should use an AS. However, the |
| 27 |
customer and service provider (ISP) are left with a problem as a |
| 28 |
result of this in that while there is no need for an allocated AS |
| 29 |
under the guidelines, certain conditions make the use of BGP4 a very |
| 30 |
pragmatic and perhaps only way to connect a customer homed to a |
| 31 |
single ISP. This paper proposes a solution to this problem in line |
| 32 |
with recommendations set forth in <a href="./rfc1930">RFC1930</a>. |
| 33 |
|
| 34 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Problems</span> |
| 35 |
|
| 36 |
With the increased growth of the Internet, the number of customers |
| 37 |
using BGP4 [<a href="#ref-1" title=""A Border Gateway Protocol 4 (BGP-4)"">1</a>],[<a href="#ref-2" title=""Application of the Border Gateway Protocol in the Internet"">2</a>] has grown significantly. <a href="./rfc1930">RFC1930</a> [<a href="#ref-4" title=""Guidelines for creation, selection, and registration of an Autonomous System (AS)"">4</a>] outlines a |
| 38 |
set of guidelines for when one needs and should use an AS. However, |
| 39 |
the customer and service provider (ISP) are left with a problem as a |
| 40 |
result of this in that while there is no need for an allocated AS |
| 41 |
under the guidelines, certain conditions make the use of BGP4 a very |
| 42 |
pragmatic and perhaps only way to connect a customer homed to a |
| 43 |
single ISP. These conditions are as follows: |
| 44 |
|
| 45 |
1) Customers multi-homed to single provider |
| 46 |
|
| 47 |
|
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Stewart, et. al. Informational [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc2270">RFC 2270</a> Dedicated AS January 1998</span> |
| 55 |
|
| 56 |
|
| 57 |
Consider the scenario outlined in Figure 1 below. |
| 58 |
|
| 59 |
|
| 60 |
|
| 61 |
+-------+ +-------+ |
| 62 |
+----+ | | | |
| 63 |
+------+ | | ISP A +------+ ISP B | |
| 64 |
| Cust.+---+ | | | | |
| 65 |
| X +--------+ | | | |
| 66 |
+------+ ++-----++\ +-------+ |
| 67 |
| | \ |
| 68 |
| | \ +--------+ |
| 69 |
++-----++ +-| | |
| 70 |
| Cust. | | ISP C | |
| 71 |
| Y | | | |
| 72 |
+-------+ +--------+ |
| 73 |
|
| 74 |
Figure 1: Customers multi-home to a single provider |
| 75 |
|
| 76 |
Here both customer X and customer Y are multi-homed to a single |
| 77 |
provider, ISP A. Because these multiple connections are "localized" |
| 78 |
between the ISP A and its customers, the rest of the routing system |
| 79 |
(ISP B and ISP C in this case) doesn't need to see routing |
| 80 |
information for a single multi-homed customer any differently than a |
| 81 |
singly-homed customer as it has the same routing policy as ISP A |
| 82 |
relative to ISP B and ISP C. In other words, with respect to the |
| 83 |
rest of the Internet routing system the organization is singly-homed, |
| 84 |
so the complexity of the multiple connections is not relevant in a |
| 85 |
global sense. Autonomous System Numbers (AS) are identifiers used in |
| 86 |
routing protocols and are needed by routing domains as part of the |
| 87 |
global routing system. However, as [<a href="#ref-4" title=""Guidelines for creation, selection, and registration of an Autonomous System (AS)"">4</a>] correctly outlines, |
| 88 |
organizations with the same routing policy as their upstream provider |
| 89 |
do not need an AS. |
| 90 |
|
| 91 |
Despite this fact, a problem exists in that many ISPs can only |
| 92 |
support the load-sharing and reliability requirements of a multi- |
| 93 |
homed customer if that customer exchanges routing information using |
| 94 |
BGP-4 which does require an AS as part of the protocol. |
| 95 |
|
| 96 |
2) Singly-homed customers requiring dynamic advertisement of NLRI's |
| 97 |
|
| 98 |
While this is not a common case as static routing is generally |
| 99 |
used for this purpose, if a large amount of NLRI's need to be |
| 100 |
advertised from the customer to the ISP it is often |
| 101 |
administratively easier for these prefixes to be advertised using |
| 102 |
a dynamic routing protocol. Today, the only exterior gateway |
| 103 |
protocol (EGP) that is able to do this is BGP. This leads to the |
| 104 |
same problem outlined in condition 1 above. |
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Stewart, et. al. Informational [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc2270">RFC 2270</a> Dedicated AS January 1998</span> |
| 111 |
|
| 112 |
|
| 113 |
As can be seen there is clearly a problem with the recommendations |
| 114 |
set forth in [<a href="#ref-4" title=""Guidelines for creation, selection, and registration of an Autonomous System (AS)"">4</a>] and the practice of using BGP4 in the scenarios |
| 115 |
above. <a href="#section-2">Section 2</a> proposes a solution to this problem with following |
| 116 |
sections describing the implications and application of the proposed |
| 117 |
solution. |
| 118 |
|
| 119 |
It should also be noted that if a customer is multi-homed to more |
| 120 |
than one ISP then they are advised to obtain an official allocated AS |
| 121 |
from their allocation registry. |
| 122 |
|
| 123 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Solution</span> |
| 124 |
|
| 125 |
The solution we are proposing is that all BGP customers homed to the |
| 126 |
same single ISP use a single, dedicated AS specified by the ISP. |
| 127 |
|
| 128 |
Logically, this solution results in an ISP having many peers with the |
| 129 |
same AS, although that AS exists in "islands" completely disconnected |
| 130 |
from one another. |
| 131 |
|
| 132 |
Several practical implications of this solution are discussed in the |
| 133 |
next section. |
| 134 |
|
| 135 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Implications</span> |
| 136 |
|
| 137 |
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a> Full Routing Table Announcement</span> |
| 138 |
|
| 139 |
The solution precludes the ability for a BGP customer using the |
| 140 |
dedicated AS to receive 100% full routes. Because of routing loop |
| 141 |
detection of AS path, a BGP speaker rejects routes with its own AS |
| 142 |
number in the AS path. Imagine Customer X and Customer Y maintain |
| 143 |
BGP peers with Provider A using AS number N. Then, Customer X will |
| 144 |
not be able to received routes of Customer Y. We do not believe that |
| 145 |
this would cause a problem for Customer X, though, because Customer X |
| 146 |
and Customer Y are both stub networks so default routing is adequate, |
| 147 |
and the absence of a very small portion of the full routing table is |
| 148 |
unlikely to have a noticeable impact on traffic patterns guided by |
| 149 |
MEDs received. |
| 150 |
|
| 151 |
A BGP customer using the dedicated AS must carry a default route |
| 152 |
(preferably receiving from its provider via BGP). |
| 153 |
|
| 154 |
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a> Change of External Connectivity</span> |
| 155 |
|
| 156 |
The dedicated AS specified by a provider is purely for use in peering |
| 157 |
between its customers and the provider. When a customer using the |
| 158 |
dedicated AS changes its external connectivity, it may be necessary |
| 159 |
for the customer to reconfigure their network to use a different AS |
| 160 |
number (either a globally unique one if homed to multiple providers, |
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Stewart, et. al. Informational [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc2270">RFC 2270</a> Dedicated AS January 1998</span> |
| 167 |
|
| 168 |
|
| 169 |
or a dedicated AS of a different provider). |
| 170 |
|
| 171 |
<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a> Aggregation</span> |
| 172 |
|
| 173 |
As BGP customers using this dedicated AS are only homed to one ISP, |
| 174 |
their routes allocated from its providers CIDR block do not need to |
| 175 |
be announced upstream by its provider as the providers will already |
| 176 |
be originating the larger block. [<a href="#ref-6" title=""A Framework for Inter-Domain Route Aggregation"">6</a>]. |
| 177 |
|
| 178 |
<span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a> Routing Registries</span> |
| 179 |
|
| 180 |
The Internet Routing Registry (IRR) [<a href="#ref-5" title=""Representation of IP Routing Policies in a Routing Registry (ripe-81++)"">5</a>] is used by providers to |
| 181 |
generate route filtering lists. Such lists are derived primarily |
| 182 |
from the "origin" attribute of the route objects. The "origin" is |
| 183 |
the AS that originates the route. With multiple customers using the |
| 184 |
same AS, finer granularity will be necessary to generate the correct |
| 185 |
route filtering. For example, the "mntner" attribute or the |
| 186 |
"community" attribute of a route object can be used along with the |
| 187 |
"origin" attribute in generating the filtering lists. |
| 188 |
|
| 189 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Practice</span> |
| 190 |
|
| 191 |
The AS number specified by a provider can either be an AS from the |
| 192 |
private AS space (64512 - 65535) [<a href="#ref-4" title=""Guidelines for creation, selection, and registration of an Autonomous System (AS)"">4</a>], or be an AS previously |
| 193 |
allocated to the provider. With the former, the dedicated AS like |
| 194 |
all other private AS's should be stripped from its AS path while the |
| 195 |
route is being propagated to the rest of the Internet routing system. |
| 196 |
|
| 197 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Security Considerations</span> |
| 198 |
|
| 199 |
The usage of AS numbers described in this document has no effective |
| 200 |
security impact. Acceptance and filtering of AS numbers from |
| 201 |
customers is an issue dealt with in other documents. |
| 202 |
|
| 203 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Acknowledgments</span> |
| 204 |
|
| 205 |
The authors would like to thank Roy Alcala of MCI and Arpakorn |
| 206 |
Boonkongchuen for their input to this document. The members of the |
| 207 |
IDR Working Group also provided helpful comments. |
| 208 |
|
| 209 |
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. References</span> |
| 210 |
|
| 211 |
[<a id="ref-1">1</a>] Rekhter, Y., and T. Li, "A Border Gateway Protocol 4 (BGP-4)", |
| 212 |
<a href="./rfc1771">RFC 1771</a>, March 1995. |
| 213 |
|
| 214 |
[<a id="ref-2">2</a>] Rekhter, Y., and P. Gross, "Application of the Border Gateway |
| 215 |
Protocol in the Internet", <a href="./rfc1772">RFC 1772</a>, March 1995. |
| 216 |
|
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Stewart, et. al. Informational [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc2270">RFC 2270</a> Dedicated AS January 1998</span> |
| 223 |
|
| 224 |
|
| 225 |
[<a id="ref-3">3</a>] Rekhter, Y., "Routing in a Multi-provider Internet", <a href="./rfc1787">RFC 1787</a>, |
| 226 |
April 1995. |
| 227 |
|
| 228 |
[<a id="ref-4">4</a>] Hawkinson, J., and T. Bates, "Guidelines for creation, selection, |
| 229 |
and registration of an Autonomous System (AS)", <a href="./rfc1930">RFC 1930</a>, March 1996. |
| 230 |
|
| 231 |
[<a id="ref-5">5</a>] Bates, T., Gerich, E., Joncheray, L., Jouanigot, J-M, Karrenberg, |
| 232 |
D., Terpstra, M., and J. Yu., "Representation of IP Routing Policies |
| 233 |
in a Routing Registry (ripe-81++)", <a href="./rfc1786">RFC 1786</a>, March 1995. |
| 234 |
|
| 235 |
[<a id="ref-6">6</a>] Chen, E., and J. Stewart., "A Framework for Inter-Domain Route |
| 236 |
Aggregation", Work in Progress. |
| 237 |
|
| 238 |
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Authors' Addresses</span> |
| 239 |
|
| 240 |
John Stewart |
| 241 |
USC/ISI |
| 242 |
4350 North Fairfax Drive |
| 243 |
Suite 620 |
| 244 |
Arlington, VA 22203 |
| 245 |
|
| 246 |
EMail: [email protected] |
| 247 |
|
| 248 |
|
| 249 |
Tony Bates |
| 250 |
Cisco Systems, Inc. |
| 251 |
170 West Tasman Drive |
| 252 |
San Jose, CA 95134 |
| 253 |
|
| 254 |
EMail: [email protected] |
| 255 |
|
| 256 |
|
| 257 |
Ravi Chandra |
| 258 |
Cisco Systems, Inc. |
| 259 |
170 West Tasman Drive |
| 260 |
San Jose, CA 95134 |
| 261 |
|
| 262 |
EMail: [email protected] |
| 263 |
|
| 264 |
|
| 265 |
Enke Chen |
| 266 |
Cisco Systems, Inc. |
| 267 |
170 West Tasman Drive |
| 268 |
San Jose, CA 95134 |
| 269 |
|
| 270 |
EMail: [email protected] |
| 271 |
|
| 272 |
|
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Stewart, et. al. Informational [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc2270">RFC 2270</a> Dedicated AS January 1998</span> |
| 279 |
|
| 280 |
|
| 281 |
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Full Copyright Statement</span> |
| 282 |
|
| 283 |
Copyright (C) The Internet Society (1998). All Rights Reserved. |
| 284 |
|
| 285 |
This document and translations of it may be copied and furnished to |
| 286 |
others, and derivative works that comment on or otherwise explain it |
| 287 |
or assist in its implementation may be prepared, copied, published |
| 288 |
and distributed, in whole or in part, without restriction of any |
| 289 |
kind, provided that the above copyright notice and this paragraph are |
| 290 |
included on all such copies and derivative works. However, this |
| 291 |
document itself may not be modified in any way, such as by removing |
| 292 |
the copyright notice or references to the Internet Society or other |
| 293 |
Internet organizations, except as needed for the purpose of |
| 294 |
developing Internet standards in which case the procedures for |
| 295 |
copyrights defined in the Internet Standards process must be |
| 296 |
followed, or as required to translate it into languages other than |
| 297 |
English. |
| 298 |
|
| 299 |
The limited permissions granted above are perpetual and will not be |
| 300 |
revoked by the Internet Society or its successors or assigns. |
| 301 |
|
| 302 |
This document and the information contained herein is provided on an |
| 303 |
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING |
| 304 |
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING |
| 305 |
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION |
| 306 |
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF |
| 307 |
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. |
| 308 |
|
| 309 |
|
| 310 |
|
| 311 |
|
| 312 |
|
| 313 |
|
| 314 |
|
| 315 |
|
| 316 |
|
| 317 |
|
| 318 |
|
| 319 |
|
| 320 |
|
| 321 |
|
| 322 |
|
| 323 |
|
| 324 |
|
| 325 |
|
| 326 |
|
| 327 |
|
| 328 |
|
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
Stewart, et. al. Informational [Page 6] |
| 333 |
</pre> |