| 1 |
<pre>Network Working Group P. Traina |
| 2 |
Request for Comments: 1965 cisco Systems |
| 3 |
Category: Experimental June 1996 |
| 4 |
|
| 5 |
|
| 6 |
<span class="h1">Autonomous System Confederations for BGP</span> |
| 7 |
|
| 8 |
Status of this Memo |
| 9 |
|
| 10 |
This memo defines an Experimental Protocol for the Internet |
| 11 |
community. This memo does not specify an Internet standard of any |
| 12 |
kind. Discussion and suggestions for improvement are requested. |
| 13 |
Distribution of this memo is unlimited. |
| 14 |
|
| 15 |
Abstract |
| 16 |
|
| 17 |
Border Gateway Protocol [<a href="#ref-1" title=""A Border Gateway Protocol 4 (BGP-4)"">1</a>] is an inter-autonomous system routing |
| 18 |
protocol designed for TCP/IP networks. |
| 19 |
|
| 20 |
This document describes an extension to BGP which may be used to |
| 21 |
create a confederation of autonomous systems which is represented as |
| 22 |
one single autonomous system to BGP peers external to the |
| 23 |
confederation. |
| 24 |
|
| 25 |
The intention of this extension is to aid in policy administration |
| 26 |
and reduce the management complexity of maintaining a large |
| 27 |
autonomous system. |
| 28 |
|
| 29 |
The extension this document describes is widely deployed in the |
| 30 |
Internet today. |
| 31 |
|
| 32 |
Introduction |
| 33 |
|
| 34 |
It may be useful to subdivide autonomous systems with a very large |
| 35 |
number of BGP speakers into smaller domains for purposes of |
| 36 |
controlling routing policy via information contained in the BGP |
| 37 |
AS_PATH attribute. For example, one may chose to consider all BGP |
| 38 |
speakers in a geographic region as a single entity. |
| 39 |
|
| 40 |
In addition to improvements in routing policy control, current |
| 41 |
techniques for deploying BGP among speakers in the same autonomous |
| 42 |
system establish a full mesh of TCP connections among all speakers |
| 43 |
for the purpose of exchanging exterior routing information. In |
| 44 |
autonomous systems the number of intra-domain connections that need |
| 45 |
to be maintained by each border router can become significant. |
| 46 |
|
| 47 |
Subdividing a large autonomous system allows a significant reduction |
| 48 |
in the total number of intra-domain BGP connections, as the |
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Traina Experimental [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc1965">RFC 1965</a> AS Confederations for BGP June 1996</span> |
| 55 |
|
| 56 |
|
| 57 |
connectivity requirements simplify to the model used for inter-domain |
| 58 |
connections. |
| 59 |
|
| 60 |
Unfortunately subdividing an autonomous system may increase the |
| 61 |
complexity of policy routing based on AS_PATH information for all |
| 62 |
members of the Internet. Additionally, this division increases the |
| 63 |
maintenance overhead of coordinating external peering when the |
| 64 |
internal topology of this collection of autonomous systems is |
| 65 |
modified. |
| 66 |
|
| 67 |
Finally, dividing a large AS may unnecessarily increase the length of |
| 68 |
the sequence portions of the AS_PATH attribute. Several common BGP |
| 69 |
implementations can use the number of "hops" required to reach a |
| 70 |
given destination as part of the path selection criteria. While this |
| 71 |
is not an optimal method of determining route preference, given the |
| 72 |
lack of other in-band information, it provides a reasonable default |
| 73 |
behavior which is widely used across the Internet. Therefore, |
| 74 |
division of an autonomous system into separate systems may adversely |
| 75 |
affect optimal routing of packets through the Internet. |
| 76 |
|
| 77 |
However, there is usually no need to expose the internal topology of |
| 78 |
this divided autonomous system, which means it is possible to regard |
| 79 |
a collection of autonomous systems under a common administration as a |
| 80 |
single entity or autonomous system when viewed from outside the |
| 81 |
confines of the confederation of autonomous systems itself. |
| 82 |
|
| 83 |
Terms and Definitions |
| 84 |
|
| 85 |
AS Confederation |
| 86 |
A collection of autonomous systems advertised as a single AS |
| 87 |
number to BGP speakers that are not members of the confederation. |
| 88 |
|
| 89 |
AS Confederation Identifier |
| 90 |
An externally visible autonomous system number that identifies the |
| 91 |
confederation as a whole. |
| 92 |
|
| 93 |
Member-AS |
| 94 |
An autonomous system that is contained in a given AS |
| 95 |
confederation. |
| 96 |
|
| 97 |
Overview |
| 98 |
|
| 99 |
IDRP[2] has the concept of a routing domain confederation. An IDRP |
| 100 |
routing domain confederation appears to IDRP speakers external to the |
| 101 |
confederation as a single administrative entity. This extension is |
| 102 |
based upon that work. |
| 103 |
|
| 104 |
|
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Traina Experimental [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc1965">RFC 1965</a> AS Confederations for BGP June 1996</span> |
| 111 |
|
| 112 |
|
| 113 |
In IDRP, routing domain confederations may be nested within each |
| 114 |
other or disjoint portions of still larger confederations. The |
| 115 |
algorithm BGP defines for additions to the AS_PATH attribute imposes |
| 116 |
an additional restriction that AS confederations must be strictly |
| 117 |
hierarchical in nature. |
| 118 |
|
| 119 |
AS_CONFED segment type extension |
| 120 |
|
| 121 |
Currently, BGP specifies that the AS_PATH attribute is a well-known |
| 122 |
mandatory attribute that is composed of a sequence of AS path |
| 123 |
segments. Each AS path segment is represented by a type/length/value |
| 124 |
triple. |
| 125 |
|
| 126 |
In [<a href="#ref-1" title=""A Border Gateway Protocol 4 (BGP-4)"">1</a>], the path segment type is a 1-octet long field with the two |
| 127 |
following values defined: |
| 128 |
|
| 129 |
Value Segment Type |
| 130 |
|
| 131 |
1 AS_SET: unordered set of ASs a route in the |
| 132 |
UPDATE message has traversed |
| 133 |
|
| 134 |
2 AS_SEQUENCE: ordered set of ASs a route in |
| 135 |
the UPDATE message has traversed |
| 136 |
|
| 137 |
This document reserves two additional segment types: |
| 138 |
|
| 139 |
3 AS_CONFED_SET: unordered set of ASs in the local |
| 140 |
confederation that the UPDATE message |
| 141 |
has traversed |
| 142 |
|
| 143 |
4 AS_CONFED_SEQUENCE: ordered set of ASs in the |
| 144 |
local confederation that the UPDATE |
| 145 |
message has traversed |
| 146 |
|
| 147 |
Operation |
| 148 |
|
| 149 |
A member of a BGP confederation will use its confederation identifier |
| 150 |
in all transactions with peers that are not members of its |
| 151 |
confederation. This confederation identifier is considered to be the |
| 152 |
"externally visible" AS number and this number is used in OPEN |
| 153 |
messages and advertised in the AS_PATH attribute. |
| 154 |
|
| 155 |
A member of a BGP confederation will use its routing domain |
| 156 |
identifier (the internally visible AS number) in all transactions |
| 157 |
with peers that are members of the same confederation as the given |
| 158 |
router. |
| 159 |
|
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Traina Experimental [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc1965">RFC 1965</a> AS Confederations for BGP June 1996</span> |
| 167 |
|
| 168 |
|
| 169 |
A BGP speaker receiving an AS_PATH attribute containing a |
| 170 |
confederation ID matching its own confederation shall treat the path |
| 171 |
in the same fashion as if it had received a path containing its own |
| 172 |
AS number. |
| 173 |
|
| 174 |
AS_PATH modification rules |
| 175 |
|
| 176 |
Section 5.1.2 of [<a href="#ref-1" title=""A Border Gateway Protocol 4 (BGP-4)"">1</a>] is replaced with the following text. |
| 177 |
|
| 178 |
When a BGP speaker propagates a route which it has learned from |
| 179 |
another BGP speaker's UPDATE message, it shall modify the route's |
| 180 |
AS_PATH attribute based on the location of the BGP speaker to which |
| 181 |
the route will be sent: |
| 182 |
|
| 183 |
a) When a given BGP speaker advertises the route to another BGP |
| 184 |
speaker located in its own autonomous system, the advertising |
| 185 |
speaker shall not modify the AS_PATH attribute associated with |
| 186 |
the route. |
| 187 |
|
| 188 |
b) When a given BGP speaker advertises the route to a BGP |
| 189 |
speaker located in a neighboring autonomous system that is a |
| 190 |
member of the local autonomous system confederation, then the |
| 191 |
advertising speaker shall update the AS_PATH attribute as |
| 192 |
follows: |
| 193 |
|
| 194 |
1) if the first path segment of the AS_PATH is of type |
| 195 |
AS_CONFED_SEQUENCE, the local system shall prepend its own AS |
| 196 |
number as the last element of the sequence (put it in the |
| 197 |
leftmost position). |
| 198 |
|
| 199 |
2) if the first path segment of the AS_PATH is not of type |
| 200 |
AS_CONFED_SEQUENCE the local system shall prepend a new path |
| 201 |
segment of type AS_CONFED_SEQUENCE to the AS_PATH, including |
| 202 |
its own confederation identifier in that segment. |
| 203 |
|
| 204 |
c) When a given BGP speaker advertises the route to a BGP |
| 205 |
speaker located in a neighboring autonomous system that is not a |
| 206 |
member of the current routing domain confederation, then the |
| 207 |
advertising speaker shall update the AS_PATH attribute as |
| 208 |
follows: |
| 209 |
|
| 210 |
1) if the first path segment of the AS_PATH is of type |
| 211 |
AS_CONFED_SEQUENCE, that segment and any immediately |
| 212 |
following segments of the type AS_CONFED_SET are removed from |
| 213 |
the AS_PATH attribute, leaving the sanitized AS_PATH |
| 214 |
attribute to be operated on by steps 2, or 3. |
| 215 |
|
| 216 |
|
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Traina Experimental [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc1965">RFC 1965</a> AS Confederations for BGP June 1996</span> |
| 223 |
|
| 224 |
|
| 225 |
2) if the first path segment of the remaining AS_PATH is of |
| 226 |
type AS_SEQUENCE, the local system shall prepend its own |
| 227 |
confederation identifier as the last element of the sequence |
| 228 |
(put it in the leftmost position). |
| 229 |
|
| 230 |
3) if there are no path segments following the removal of the |
| 231 |
first AS_CONFED_SET/AS_CONFED_SEQUENCE segments, or if the |
| 232 |
first path segment of the remaining AS_PATH is of type AS_SET |
| 233 |
the local system shall prepend a new path segment of type |
| 234 |
AS_SEQUENCE to the AS_PATH, including its own confederation |
| 235 |
identifier in that segment. |
| 236 |
|
| 237 |
When a BGP speaker originates a route: |
| 238 |
|
| 239 |
a) the originating speaker shall include an empty AS_PATH |
| 240 |
attribute in all UPDATE messages sent to BGP speakers located in |
| 241 |
its own autonomous system. (An empty AS_PATH attribute is one |
| 242 |
whose length field contains the value zero). |
| 243 |
|
| 244 |
b) the originating speaker shall include its own AS number in an |
| 245 |
AS_CONFED_SEQUENCE segment of the AS_PATH attribute of all |
| 246 |
UPDATE messages sent to BGP speakers located in neighboring |
| 247 |
autonomous systems that are members of the local confederation. |
| 248 |
(In this case, the AS number of the originating speaker's member |
| 249 |
autonomous system number will be the only entry in the AS_PATH |
| 250 |
attribute). |
| 251 |
|
| 252 |
c) the originating speaker shall include its own confederation |
| 253 |
identifier in a AS_SEQUENCE segment of the AS_PATH attribute of |
| 254 |
all UPDATE messages sent to BGP speakers located in neighboring |
| 255 |
autonomous systems that are not members of the local |
| 256 |
confederation. (In this case, the confederation identifier of |
| 257 |
the originating speaker's member confederation will be the only |
| 258 |
entry in the AS_PATH attribute). |
| 259 |
|
| 260 |
Common Administration Issues |
| 261 |
|
| 262 |
It is reasonable for member ASs of a confederation to share a common |
| 263 |
administration and IGP information for the entire confederation. |
| 264 |
|
| 265 |
It shall be legal for a BGP speaker to advertise an unchanged |
| 266 |
NEXT_HOP and MULTI_EXIT_DISCRIMINATOR attribute to peers in a |
| 267 |
neighboring AS within the same confederation. In addition, the |
| 268 |
restriction against sending the LOCAL_PREFERENCE attribute to peers |
| 269 |
in a neighboring AS within the same confederation is removed. Path |
| 270 |
selection criteria for information received from members inside a |
| 271 |
confederation may follow the same rules used for information received |
| 272 |
from members inside the same autonomous system. |
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Traina Experimental [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc1965">RFC 1965</a> AS Confederations for BGP June 1996</span> |
| 279 |
|
| 280 |
|
| 281 |
Compatibility |
| 282 |
|
| 283 |
All BGP speakers participating in a confederation must recognize the |
| 284 |
AS_CONFED_SET and AS_CONFED_SEQUENCE segment type extensions to the |
| 285 |
AS_PATH attribute. |
| 286 |
|
| 287 |
Any BGP speaker not supporting these extensions will generate a |
| 288 |
notification message specifying an "UPDATE Message Error" and a sub- |
| 289 |
code of "Malformed AS_PATH". |
| 290 |
|
| 291 |
This compatibility issue implies that all BGP speakers participating |
| 292 |
in a confederation must support BGP confederations, however BGP |
| 293 |
speakers outside the confederation need not support these extensions. |
| 294 |
|
| 295 |
Compatibility Discussion |
| 296 |
|
| 297 |
We considered the use of a distinct, optional, transitive attribute |
| 298 |
to carry AS confederation information as opposed to specifying new |
| 299 |
types in the existing AS path attribute. This would relax the |
| 300 |
requirement that all BGP speakers participating in a confederation to |
| 301 |
allow the use of legacy units provided they have no external (i.e. |
| 302 |
neither inter-AS nor intra-confederation) connectivity. |
| 303 |
|
| 304 |
At the time of this writing, an implementation of this extension as |
| 305 |
documented is widely deployed throughout the Internet, therefore the |
| 306 |
value of any change that is incompatible with this document must be |
| 307 |
weighed against the benefit gained from a relaxation of this |
| 308 |
restriction. |
| 309 |
|
| 310 |
References |
| 311 |
|
| 312 |
[<a id="ref-1">1</a>] Rekhter, Y., and T. Li, "A Border Gateway Protocol 4 (BGP-4)", |
| 313 |
<a href="./rfc1771">RFC 1771</a>, March 1995. |
| 314 |
|
| 315 |
[<a id="ref-2">2</a>] Kunzinger, C. Editor, "Inter-Domain Routing Protocol", ISO/IEC |
| 316 |
10747, October 1993. |
| 317 |
|
| 318 |
Security Considerations |
| 319 |
|
| 320 |
Security issues are not discussed in this memo. |
| 321 |
|
| 322 |
Acknowledgments |
| 323 |
|
| 324 |
Ravi Chandra and Yakov Rekhter reviewed this document and provided |
| 325 |
constructive and valuable comments. |
| 326 |
|
| 327 |
|
| 328 |
|
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Traina Experimental [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc1965">RFC 1965</a> AS Confederations for BGP June 1996</span> |
| 335 |
|
| 336 |
|
| 337 |
Author's Address |
| 338 |
|
| 339 |
Paul Traina |
| 340 |
cisco Systems, Inc. |
| 341 |
170 W. Tasman Dr. |
| 342 |
San Jose, CA 95134 |
| 343 |
|
| 344 |
EMail: [email protected] |
| 345 |
|
| 346 |
|
| 347 |
|
| 348 |
|
| 349 |
|
| 350 |
|
| 351 |
|
| 352 |
|
| 353 |
|
| 354 |
|
| 355 |
|
| 356 |
|
| 357 |
|
| 358 |
|
| 359 |
|
| 360 |
|
| 361 |
|
| 362 |
|
| 363 |
|
| 364 |
|
| 365 |
|
| 366 |
|
| 367 |
|
| 368 |
|
| 369 |
|
| 370 |
|
| 371 |
|
| 372 |
|
| 373 |
|
| 374 |
|
| 375 |
|
| 376 |
|
| 377 |
|
| 378 |
|
| 379 |
|
| 380 |
|
| 381 |
|
| 382 |
|
| 383 |
|
| 384 |
|
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
Traina Experimental [Page 7] |
| 389 |
</pre> |