One document matched: draft-ga-idr-as-migration-02.xml
<?xml version="1.0" encoding="US-ASCII"?>
<!-- This template is for creating an Internet Draft using xml2rfc,
which is available here: http://xml.resource.org. -->
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!-- One method to get references from the online citation libraries.
There has to be one entity for each item to be referenced.
An alternate method (rfc include) is described in the references. -->
<!ENTITY RFC1930 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.1930.xml">
<!ENTITY RFC4271 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4271.xml">
<!ENTITY RFC4456 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4456.xml">
<!ENTITY RFC5065 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5065.xml">
<!ENTITY RFC5398 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5398.xml">
]>
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<!-- used by XSLT processors -->
<!-- For a complete list and description of processing instructions (PIs),
please see http://xml.resource.org/authoring/README.html. -->
<!-- Below are generally applicable Processing Instructions (PIs) that most I-Ds might want to use.
(Here they are set differently than their defaults in xml2rfc v1.32) -->
<?rfc strict="yes" ?>
<!-- give errors regarding ID-nits and DTD validation -->
<!-- control the table of contents (ToC) -->
<?rfc toc="yes"?>
<!-- generate a ToC -->
<?rfc tocdepth="4"?>
<!-- the number of levels of subsections in ToC. default: 3 -->
<!-- control references -->
<?rfc symrefs="yes"?>
<!-- use symbolic references tags, i.e, [RFC2119] instead of [1] -->
<?rfc sortrefs="yes" ?>
<!-- sort the reference entries alphabetically -->
<!-- control vertical white space
(using these PIs as follows is recommended by the RFC Editor) -->
<?rfc compact="yes" ?>
<!-- do not start each main section on a new page -->
<?rfc subcompact="no" ?>
<!-- keep one blank line between list items -->
<!-- end of list of popular I-D processing instructions -->
<rfc category="info" docName="draft-ga-idr-as-migration-02" ipr="trust200902">
<!-- category values: std, bcp, info, exp, and historic
ipr values: full3667, noModification3667, noDerivatives3667
you can add the attributes updates="NNNN" and obsoletes="NNNN"
they will automatically be output with "(if approved)" -->
<!-- ***** FRONT MATTER ***** -->
<front>
<!-- The abbreviated title is used in the page header - it is only necessary if the
full title is longer than 39 characters -->
<title abbrev="AS Migration Features">Autonomous System (AS) Migration
Features and Their Effects on the BGP AS_PATH Attribute</title>
<!-- add 'role="editor"' below for the editors if appropriate -->
<!-- Another author who claims to be an editor -->
<author fullname="Wesley George" initials="W" surname="George">
<organization>Time Warner Cable</organization>
<address>
<postal>
<street>13820 Sunrise Valley Drive</street>
<!-- Reorder these if your country does things differently -->
<city>Herndon</city>
<region>VA</region>
<code>20171</code>
<country>US</country>
</postal>
<phone>+1 703-561-2540</phone>
<email>wesley.george@twcable.com</email>
<!-- uri and facsimile elements may also be added -->
</address>
</author>
<author fullname="Shane Amante" initials="S" surname="Amante">
<organization>Level 3 Communications</organization>
<address>
<postal>
<street>1025 Eldorado Blvd</street>
<!-- Reorder these if your country does things differently -->
<city>Broomfield</city>
<region>CO</region>
<code>80021</code>
<country>US</country>
</postal>
<phone/>
<email>shane@level3.net</email>
<!-- uri and facsimile elements may also be added -->
</address>
</author>
<date year="2013"/>
<!-- If the month and year are both specified and are the current ones, xml2rfc will fill
in the current day for you. If only the current year is specified, xml2rfc will fill
in the current day and month for you. If the year is not the current one, it is
necessary to specify at least a month (xml2rfc assumes day="1" if not specified for the
purpose of calculating the expiry date). With drafts it is normally sufficient to
specify just the year. -->
<!-- Meta-data Declarations -->
<area>General</area>
<workgroup>Internet Engineering Task Force</workgroup>
<!-- WG name at the upperleft corner of the doc,
IETF is fine for individual submissions.
If this element is not present, the default is "Network Working Group",
which is used by the RFC Editor as a nod to the history of the IETF. -->
<keyword>as-migration, AS-migration, AS_migration, AS migration, IDR,
BGP</keyword>
<!-- Keywords will be incorporated into HTML output
files in a meta tag but they have no effect on text or nroff
output. If you submit your draft to the RFC Editor, the
keywords will be used for the search engine. -->
<abstract>
<t>This draft discusses common methods of managing an ASN migration
using some BGP feaures that while commonly-used are not formally part of
the BGP4 protocol specification and may be vendor-specific in exact
implementation. It is necessary to document these de facto standards to
ensure that they are properly supported in BGPSec.</t>
</abstract>
</front>
<middle>
<section title="Introduction">
<t>This draft discusses common methods of managing an ASN migration
using some BGP features that while commonly-used are not formally part
of the <xref target="RFC4271">BGP4</xref> protocol specification and may
be vendor-specific in exact implementation. This draft does not attempt
to standardize these features, because they are local to given
implementation and do not require negotiation with or cooperation of BGP
neighbors. The deployment of these features do not need to interwork
with one another to accomplish the desired results. However, it is
necessary to document these de facto standards to ensure that any future
protocol enhancements to BGP that propose to read, copy, manipulate or
compare the AS_PATH attribute can do so without inhibiting the use of
these very widely used ASN migration features.</t>
<t>It is important to understand the business need for these features
and illustrate why they are critical, particularly for ISP's operations.
However, these features are not limited to ISP's and that organizations
of all sizes use these features for similar reasons to ISPs. During a
merger, acquisition or divestiture involving two organizations it is
necessary to seamlessly migrate BGP speakers from one ASN to a second
ASN. The overall goal in doing so, particularly in the case of a merger
or acquisition, is to achieve a uniform operational model through
consistent configurations across all BGP speakers in the combined
network. In addition, and perhaps more imporantly, it is common practice
in the industry for ISPs to bill customers based on utilization. ISPs
bill customers based on the 95th percentile of the greater of the
traffic sent or received, over the course of a 1-month period, on the
customer's PE-CE access circuit. Given that the BGP Path Selection
algorithm selects routes with the shortest AS_PATH attribute, it is
critical for the ISP to not increase AS_PATH length during or after ASN
migration, toward both downstream transit customers as well as
settlement-free peers, who are likely sending or receiving traffic from
those transit customers. This would not only result in sudden changes in
traffic patterns in the network, but also (substantially) decrease
utilization driven revenue at the ISP.</t>
<t>Lastly, it is important to note that by default, the BGP protocol
requires an operator to configure a single remote ASN for the eBGP
neighbor inside a router, in order to successfully negotiate and
establish an eBGP session. Prior to the existence of these features, it
would have required an ISP to work with, in some cases, tens of
thousands of customers. In particular, the ISP would have to encourage
those customers to change their CE router configs to use the new ASN, in
a very short period of time, when the customer has no business incentive
to do so. Thus, it because critical to allow the ISP to make this
process a bit more asymmetric, so that it could seamlessly migrate the
ASN within its network(s), but not disturb existing customers, and allow
the customers to gradually migrate to the ISP's new ASN at their
leisure.</t>
<section title="Documentation note">
<t>This draft uses Autonomous System Numbers (ASNs) from the range
reserved for documentation as described in <xref target="RFC5398">RFC
5398</xref>. In the examples used here, they are intended to represent
Globally Unique ASNs, not private ASNs as documented in <xref
target="RFC1930">RFC 1930</xref> section 10.</t>
</section>
</section>
<section title="ASN Migration Scenario Overview">
<t>The use case being discussed here is an ISP merging two or more ASNs,
where eventually one ASN subsumes the other(s). In this use case, we
will assume the most common case where there are two ISPs, A and B, that
use AS 64500 and 64510, respectively, before the ASN migration is to
occur. AS 64500 will be the permanently retained ASN used going forward
across the consolidated set of both ISPs network equipment and AS 64510
will be retired. Thus, at the conclusion of the ASN migration, there
will be a single ISP A' with all internal BGP speakers configured to use
AS 64500. To all external BGP speakers, the AS_PATH length will not be
increased.</t>
<t>In this same scenario, AS 64496 and AS 64499 represent two, separate
customer networks: C and D, respectively. Originally, customer C (AS
64496) is attached to ISP B, which will undergo ASN migration from AS
64510 to AS 64500. Furthermore, customer D (AS 64496) is attached to ISP
A, which does not undergo ASN migration since ISP A's ASN will remain
constant, (AS 64500). Although this example refers to AS 64496 and 64499
as customer networks, either or both may be settlement-free or other
types of peers. In this use case they are referred to as "customers"
merely for convenience.</t>
<figure align="center" anchor="premigration" title="Before Migration">
<artwork><![CDATA[ ------ ------
/ ISP A \ / ISP B \
| AS 64500 | | AS 64510 |
\ / \ /
------- -------
| |
| |
------------ -------------
| Cust D | | Cust C |
| AS 64499 | | AS 64496 |
------------ -------------]]></artwork>
</figure>
<figure align="center" anchor="postmigration" title="After Migration">
<artwork><![CDATA[ ---------------
/ \
| ISP A' |
| AS 64500 |
\ /
---------------
/ \
/ \
| |
------------ -------------
| Cust D | | Cust C |
| AS 64499 | | AS 64496 |
------------ -------------]]></artwork>
</figure>
<t>The general order of operations, typically carried out in a single
maintenance window by the network undergoing ASN migration, ISP B, are
as follows. First, ISP B, will change the global BGP ASN used by a PE
router, from ASN 64510 to 64500. At this point, the router will no
longer be able to establish eBGP sessions toward the existing CE devices
that are attached to it and still using AS 64510. Second, ISP B will
configure two separate, but related ASN migration features discussed in
this document on all eBGP sessions toward all CE devices. These features
modify the AS_PATH attribute received from and transmitted toward CE
devices to acheive the desired effect of not increasing the length of
the AS_PATH.</t>
<t>At the conclusion of the ASN migration, the CE devices at the edge of
the network are not aware of and do not observe any change in the length
of the AS_PATH attribute. However, after the changes discussed in this
document are put in place by ISP A', there is a change to the contents
of the AS_PATH attribute to ensure the AS_PATH is not artifically
lengthened for the duration of time that these AS migration parameters
are used.</t>
<t>In this use case, neither ISP is using BGP Confederations <xref
target="RFC5065">RFC 5065</xref> internally.</t>
<t>Additional information about this scenario, including vendor-specific
implementation details can be found as follows:</t>
<t><list style="symbols">
<t><xref target="CISCO">Cisco</xref></t>
<t><xref target="JUNIPER">Juniper</xref></t>
<t><xref target="ALU">Alcatel-Lucent</xref></t>
</list>Equivalent features do exist in other implementations, however
the authors were unable to find publicly available documentation of the
vendor-specific implementation to reference. Finally, the examples cited
below use Cisco IOS CLI for ease of illustration purposes only.</t>
</section>
<section anchor="ebgp-features"
title="External BGP Autonomous System Migration Features">
<t>The following section addresses features that are specific to
modifying the AS_PATH attribute at the Autonomous System Border Routers
(ASBRs) of an organization, (typically a single Service Provider). This
ensures that external BGP customers/peers are not forced to make any
configuration changes on their CE routers before or during the exact
time the Service Provider wishes to migrate to a new, permanently
retained ASN. Furthermore, these features eliminate the artificial
lengthening of the AS_PATH both transmitted from and received by the
Service Provider that is undergoing AS Migration, which would have
negative implications on path selection by external networks.</t>
<section title="Local AS: Modify Inbound BGP AS_PATH Attribute">
<t>ISP B needs to reconfigure its router(s) to participate as an
internal BGP speaker in AS 64500, to realize the business goal of
becoming a single Service Provider: ISP A'. ISP B needs to do this
without coordinating the change of its ASN with all of its eBGP peers,
simultaneously. The first step is for ISP B to change the global AS in
its router configuration, used by the local BGP process as the
system-wide Autonomous System ID, from AS 64510 to AS 64500. The next
step is for ISP B to establish iBGP sessions with ISP A's existing
routers, thus consolidating ISP B into ISP A resulting in operating
under a single AS: ISP A', (AS 64500).</t>
<t>The next step is for ISP B to reconfigure its PE router(s) so that
each of its eBGP sessions toward all eBGP speakers with a feature
called "Local AS". This feature allows ISP B's PE router to
re-establish a eBGP session toward the existing CE devices using the
legacy AS, AS 64510, in the eBGP session establishment. Ultimately,
the CE devices, (i.e.: customer C), are completely unaware that ISP B
has reconfigured its router to participate as a member of a new AS.
Within the context of ISP B's PE router, the second effect this
feature has is that, by default, it prepends all received BGP UPDATE's
with the legacy AS of ISP B: AS 64510. Thus, within ISP A' the AS_PATH
toward customer C would appear as: 64510 64496, which is an increase
in AS_PATH length from previously. Therefore, a secondary feature "No
Prepend" is required to be added to the "Local AS" configuration
toward every eBGP neighbor on ISP B's PE router. The "No Prepend"
feature causes ISP B's PE router to not prepend the legacy AS, AS
64510, on all received eBGP UPDATE's from customer C. This restores
the AS_PATH within ISP A' toward customer C so that it is just one ASN
in length: 64496.</t>
<t>In the direction of CE -> PE (inbound):</t>
<t><list style="numbers">
<t>'local-as <old_ASN>': appends the <old_ASN> value
to the AS_PATH of routes received from the CE</t>
<t>'local-as <old_ASN> no-prepend': does not prepend
<old_ASN> value to the AS_PATH of routes received from the
CE</t>
</list></t>
<t>As stated previously, local-as <old_ASN> no-prepend,
(configuration #2), is critical because it does not increase the
AS_PATH length. Ultimately, this ensures that routes learned from ISP
B's legacy customers will be transmitted through legacy eBGP sessions
of ISP A, toward both customers and peers, will contain only two AS'es
in the AS_PATH: 64500 64496. Thus, the legacy customers and peers of
ISP A will not see an increase in the AS_PATH length to reach ISP B's
legacy customers. Ultimately, it is considered mandatory by operators
that both the "Local AS" and "No Prepend" configuration parameters
always be used in conjunction with each other in order to ensure the
AS_PATH length is not increased.</t>
<t>PE-1 is a PE that was originally in ISP B. PE-1 has had its global
configuration ASN changed from AS 64510 to AS 64500 to make it part of
the permanently retained ASN. This now makes PE-1 a member of ISP A'.
PE-2 is a PE that was originally in ISP A. Although its global
configuration ASN remains AS 64500, throughout this exercise we also
consider PE-2 a member of ISP A'.</t>
<figure align="left" anchor="local_as"
title="Local AS BGP UPDATE Diagram">
<artwork align="left"><![CDATA[ ISP A' ISP A'
CE-1 ---> PE-1 -------------------> PE-2 ---> CE-2
64496 Old_ASN: 64510 New_ASN: 64500 64499
New_ASN: 64500
]]></artwork>
<postamble>Note: Direction of BGP UPDATE as per the
arrows.</postamble>
</figure>
<t/>
<t>The final configuration on PE-1 after completing the "Local AS"
portion of the AS migration is as follows: <figure align="left">
<artwork align="left"><![CDATA[ router bgp 64500
neighbor <CE-1_IP> remote-as 64496
neighbor <CE-1_IP> local-as 64510 no-prepend
]]></artwork>
</figure></t>
<t>As a result of the "Local AS No Prepend" configuration, on PE-1,
CE-2 will see an AS_PATH of: 64500 64496. CE-2 will not receive a BGP
UPDATE containing AS 64510 in the AS_PATH. (If only the "local-as
64510" feature was configured without the keyword "no-prepend" on
PE-1, then CE-2 would see an AS_PATH of: 64496 64510 64500, which is
unacceptable).</t>
</section>
<section title="Replace AS: Modify Outbound BGP AS_PATH Attribute">
<t>The previous feature, "Local AS No Prepend", was only designed to
modify the AS_PATH Attribute received from CE devices by the ISP, when
CE devices still have an eBGP session established with the ISPs legacy
AS, (AS64510). Use of "Local AS No Prepend" has an unfortunate side
effect where its use does not concurrently modify the AS_PATH
Attribute for BGP UPDATEs that are transmitted by the ISP to CE
devices. Specifically, with "Local AS No Prepend" enabled on ISP A's
PE-1, it automatically causes a lengthening of the AS_PATH in outbound
BGP UPDATEs from ISP A' toward directly attached eBGP speakers,
(Customer C in AS 64496). This is the result of the "Local AS No
Prepend" feature automatically appending the new global configuration
ASN, AS64500, after the legacy ASN, AS64510, on ISP A' PE-1 in BGP
UPDATEs that are transmitted by PE-1 to CE-1. The end result is that
customer C, in AS 64496, will receive the following AS_PATH: 64510
64500 64499. Therefore, if ISP A' takes no further action, it will
cause an increase in AS_PATH length within customer's networks
directly attached to ISP A', which is unacceptable.</t>
<t>A second feature, called "Replace AS", was designed to resolve this
problem. This feature allows ISP A' to not append the global
configured AS in outbound BGP UPDATEs toward its customer's networks
configured with the "Local AS" feature. Instead, only the historical
(or, legacy) AS will be prepended in the outbound BGP UPDATE toward
customer's network, restoring the AS_PATH length to what it what was
before AS Migration occurred.</t>
<t>To re-use the above diagram, but in the opposite direction, we
have:</t>
<figure align="left" anchor="replace_as"
title="Replace AS BGP UPDATE Diagram">
<artwork align="left"><![CDATA[ ISP A' ISP A'
CE-1 <--- PE-1 <------------------- PE-2 <--- CE-2
64496 Old_ASN: 64510 New_ASN: 64500 64499
New_ASN: 64500 ]]></artwork>
<postamble>Note: Direction of BGP UPDATE as per the
arrows.</postamble>
</figure>
<t>The final configuration on PE-1 after completing the "Replace AS"
portion of the AS migration is as follows: <figure align="left">
<artwork align="left"><![CDATA[ router bgp 64500
neighbor <CE-1_IP> remote-as 64496
neighbor <CE-1_IP> local-as 64510 no-prepend replace-as ]]></artwork>
</figure></t>
<t>By default, without "Replace AS" enabled, CE-1 would see an AS_PATH
of: 64510 64500 64499, which is artificially lengthened by the ASN
Migration. After ISP A' changes PE-1 to include the "Replace AS"
feature, CE-1 would receive an AS_PATH of: 64510 64499, which is the
same AS_PATH length pre-AS migration.</t>
</section>
</section>
<!-- EOS: ebgp-features -->
<section anchor="ibgp-features"
title="Internal BGP Autonomous System Migration Features">
<t>The following section describes features that are specific to
performing an ASN migration within medium to large networks in order to
realize the business and operational benefits of a single network using
one, globally unique Autonomous System. These features assist with a
gradual and least service impacting migration of Internal BGP sessions
from a legacy ASN to the permanently retained ASN. It should be noted
that the following feature is very valuable to networks undergoing AS
migration, but its use does not cause changes to the AS_PATH
attribute.</t>
<section title="Internal BGP Alias">
<t>In this case, all of the routers to be consolidated into a single,
permanently retained ASN are under the administrative control of a
single entity. Unfortunately, though, the traditional method of
migrating all Internal BGP speakers, particularly within larger
networks, is both time consuming and widely service impacting.</t>
<t>The traditional method to migrate Internal BGP sessions was
strictly limited to reconfiguration of the global configuration ASN
and, concurrently, changing of iBGP neighbor's remote ASN from the
legacy ASN to the new, permanently retained ASN on each router within
the legacy AS. These changes can be challenging to swiftly execute in
networks with with more than a few dozen internal BGP speakers. There
is also the concomitant service interruptions as these changes are
made to routers within the network, resulting in a reset of iBGP
sessions and subsequent reconvergence times to reestablish optimal
routing paths. Operators do not and, in some cases, cannot make such
changes given the associated risks and highly visible service
interruption; rather, they require a more gradual method to migrate
Internal BGP sessions, from one ASN to a second, permanently retained
ASN, that is not visibly service-impacting to its customers.</t>
<t>With the <xref target="JUNIPER">"Internal BGP Alias"</xref>
feature, it allows an Internal BGP speaker to form a single iBGP
session using either the old, legacy ASN or the new, permanently
retained ASN. The benefits of using this feature are several fold.
First, it allows for a more gradual and less service-impacting
migration away from the legacy ASN to the permanently retained ASN.
Second, it (temporarily) permits the coexistence of the legacy and
permanently retained ASN within a single network, allowing for uniform
BGP path selection among all routers within the consolidated
network.</t>
<t>When the "Internal BGP Alias" feature is enabled, typically just on
one side of a iBGP session, it allows that iBGP speaker to establish a
single iBGP session with either the legacy ASN or the new, permanently
retained ASN, depending on which one it receives in the "My Autonomous
System" field of the BGP OPEN message from its iBGP session neighbor.
It is important to recognize that enablement of the "Internal BGP
Alias" feature preserves the semantics of a regular iBGP session,
(using identical ASNs). Thus, the BGP attributes transmitted by and
the acceptable methods of operation on BGP attributes received from
iBGP sessions configured with "Internal BGP Alias" are no different
than those exchanged across an iBGP session without "Internal BGP
Alias" configured, as defined by <xref target="RFC4271"/> and <xref
target="RFC4456"/>.</t>
<t>Typically, in medium to large networks, <xref target="RFC4456">BGP
Route Reflectors</xref> (RRs) are used to aid in reduction of
configuration of iBGP sessions and scalability with respect to overall
TCP (and, BGP) session maintenance between adjacent iBGP speakers.
Furthermore, BGP Route Reflectors are typically deployed in pairs
within a single Route Reflection cluster to ensure high reliability of
the BGP Control Plane. As such, the following example will use Route
Reflectors to aid in understanding the use of the "Internal BGP Alias"
feature. It should be noted that Route Reflectors are not a
prerequisite to enable "Internal BGP Alias" and this feature can be
enabled independent of the use of Route Reflectors.</t>
<t>The general order of operations is as follows:</t>
<t><list style="numbers">
<t>Within the legacy network, (the routers comprising the set of
devices that still have a globally configured legacy ASN), take
one member of a redundant pair of RRs and change its global
configuration ASN to the permanently retained ASN. Concurrently,
enable use of "Internal BGP Alias" on all iBGP sessions. This will
comprise Non-Client iBGP sessions to other RRs as well as Client
iBGP sessions, typically to PE devices, both still utilizing the
legacy ASN. Note that during this step there will be a reset and
reconvergence event on all iBGP sessions on the RRs whose
configuration was modified; however, this should not be service
impacting due to the use of redundant RRs in each RR Cluster.</t>
<t>Repeat the above step for the other side of the redundant pair
of RRs. The one alteration to the above procedure is to disable
use of "Internal BGP Alias" on the Non-Client iBGP sessions toward
the other (previously reconfigured) RRs, since it is no longer
needed. "Internal BGP Alias" is still required on all RRs for all
RR Client iBGP sessions. Also during this step, there will be a
reset and reconvergence event on all iBGP sessions whose
configuration was modified, but this should not be service
impacting. At the conclusion of this step, all RRs should now have
their globally configured ASN set to the permanently retained ASN
and "Internal BGP Alias" enabled and in use toward RR Clients.</t>
<t>At this point, the network administrators would then be able to
establish iBGP sessions between all Route Reflectors in both the
legacy and permanently retained networks. This would allow the
network to appear to function, both internally and externally, as
a single, consolidated network using the permanently retained
network.</t>
<t>The next steps to complete the AS migration are to gradually
modify each RR Client, (PE), in the legacy network still utilizing
the legacy ASN. Specifically, each legacy PE would have its
globally configured ASN changed to use the permanently retained
ASN. The ASN used by the PE for the iBGP sessions, toward each RR,
would be changed to use the permanently retained ASN. (It is
unnecessary to enable "Internal BGP Alias" on the migrated iBGP
sessions). During the same maintenance window, External BGP
sessions would be modified to include the above "Local AS No
Prepend" and "Replace-AS" features, since all of the changes are
service interrupting to the eBGP sessions of the PE. At this
point, all PE's will have been migrated to the permanently
retained ASN.</t>
<t>The final step is to excise the "Internal BGP Alias"
configuration from the first half of the legacy RR Client pair --
this will expunge "Internal BGP Alias" configuration from all
devices in the network. After this is complete, all routers in the
network will be using the new, permanently retained ASN for all
iBGP sessions with no vestiges of the legacy ASN on any iBGP
sessions.</t>
</list></t>
<t>The benefit of using "Internal BGP Alias" is a more gradual and
less externally visible, service-impacting change to accomplish an AS
migration. Previously, without "Internal BGP Alias", such an AS
migration change would carry a high risk and need to be successfully
accomplished in a very short timeframe, (e.g.: at most several hours).
In addition, it would cause substantial routing churn and, likely,
rapid fluctuations in traffic carried -- potentially causing periods
of congestion and resultant packet loss -- during the period the
configuration changes are underway to complete the AS Migration. On
the other hand, with "Internal BGP Alias", the migration from the
legacy ASN to the permanently retained ASN can occur over a period of
days or weeks with little disruption experienced by customers of the
network undergoing AS migration. (The only observable service
disruption should be when each PE undergoes the changes discussed in
step 4 above.)</t>
</section>
</section>
<!-- EOS: ibgp-features -->
<section title="Additional Operational Considerations">
<t>This document describes several implementation-specific features to
support ISP's and other organizations that need to perform ASN
migrations. Other variations of these features may exist, for example,
in legacy router software that has not been upgraded or reached End of
Life, but continues to operate in the network. Such variations are
beyond the scope of this document.</t>
<t>Companies routinely go through periods of mergers, acquisitions and
divestitures, which in the case of the former cause them to accumulate
several legacy ASNs over time. ISPs often do not have control over the
configuration of customer's devices, (i.e.: the ISPs are often not
providing a managed CE router service, particularly to medium and large
customers that require eBGP). Furthermore, ISPs are using methods to
perform ASN migration that do not require coordination with customers.
Ultimately, this means there is not a finite period of time after which
legacy ASNs will be completely expunged from the ISP's network. In fact,
it is common that legacy ASNs and the associated External BGP AS
Migration features discussed in this document can and do persist for
several years, if not longer. Thus, it is prudent to plan that legacy
ASNs and associated External BGP AS Migration features will persist in a
operational network indefinitely.</t>
<t>With respect to the Internal BGP AS Migration Features, all of the
routers to be consolidated into a single, permanently retained ASN are
under the administrative control of a single entity. Thus, completing
the migration from iBGP sessions using the legacy ASN to the permanently
retained ASN is more straightforward and could be accomplished in a
matter of days to months. Finally, good operational hygiene would
dictate that it is good practice to avoid using "Internal BGP Alias"
over a long period of time for reasons of not only operational
simplicity of the network, but also reduced reliance on that feature
during the ongoing lifecycle management of software, features and
configurations that are maintained on the network.</t>
</section>
<section title="Conclusion">
<t>Although the features discussed in this document are not formally
recognized as part of the BGP4 specification, they have been in
existence in commercial implementations for well over a decade. These
features are widely known by the operational community and will continue
to be a critical necessity in the support of network integration
activities going forward. Therefore, these features are extremely
unlikely to be deprecated by vendors. As a result, these features must
be acknowledged by protocol designers, particularly when there are
proposals to modify BGP's behavior with respect to handling or
manipulation of the AS_PATH Attribute. More specifically, assumptions
should not be made with respect to the preservation or consistency of
the AS_PATH Attribute as it is transmitted along a sequence of ASN's. In
addition, proposals to manipulate the AS_PATH that would gratuitously
increase AS_PATH length or remove the capability to use these features
described in this document will not be accepted by the operational
community.</t>
</section>
<!-- This PI places the pagebreak correctly (before the section title) in the text output. -->
<?rfc needLines="8" ?>
<section anchor="Acknowledgements" title="Acknowledgements">
<t>Thanks to Kotikalapudi Sriram, Stephane Litkowski, and Terry
Manderson for their comments.</t>
</section>
<!-- Possibly a 'Contributors' section ... -->
<section anchor="IANA" title="IANA Considerations">
<t>This memo includes no request to IANA.</t>
</section>
<section anchor="Security" title="Security Considerations">
<t>This draft discusses a process by which one ASN is migrated into and
subsumed by another. This involves manipulating the AS_PATH Attribute
with the intent of not increasing the AS_PATH length, which would
typically cause the BGP route to no longer be selected by BGP's Path
Selection Algorithm in other's networks. This could result in a loss of
revenue if the ISP is billing based on measured utilization of traffic
sent to/from entities attached to its network. This could also result in
sudden, and unexpected shifts in traffic patterns in the network,
potentially resulting in congestion, in the most extreme cases.</t>
<t>Given that these features can only be enabled through configuration
of router's within a single network, standard security measures should
be taken to restrict access to the management interface(s) of routers
that implement these features.</t>
</section>
</middle>
<!-- *****BACK MATTER ***** -->
<back>
<!-- References split into informative and normative -->
<!-- There are 2 ways to insert reference entries from the citation libraries:
1. define an ENTITY at the top, and use "ampersand character"RFC2629; here (as shown)
2. simply use a PI "less than character"?rfc include="reference.RFC.2119.xml"?> here
(for I-Ds: include="reference.I-D.narten-iana-considerations-rfc2434bis.xml")
Both are cited textually in the same manner: by using xref elements.
If you use the PI option, xml2rfc will, by default, try to find included files in the same
directory as the including file. You can also define the XML_LIBRARY environment variable
with a value containing a set of directories to search. These can be either in the local
filing system or remote ones accessed by http (http://domain/dir/... ).-->
<references title="Normative References">
<!--?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml"?-->
&RFC5398;
</references>
<references title="Informative References">
<!-- Here we use entities that we defined at the beginning. -->
&RFC1930;
&RFC4271;
&RFC4456;
&RFC5065;
<!-- A reference written by by an organization not a person. -->
<reference anchor="CISCO"
target="http://www.cisco.com/en/US/docs/ios/12_3t/12_3t11/feature/guide/gtbgpdas.html">
<front>
<title>BGP Support for Dual AS Configuration for Network AS
Migrations</title>
<author>
<organization>Cisco Systems, Inc.</organization>
</author>
<date year="2003"/>
</front>
</reference>
<reference anchor="JUNIPER"
target="https://www.juniper.net/techpubs/en_US/junos12.3/topics/reference/configuration-statement/local-as-edit-protocols-bgp.html">
<front>
<title>Configuring the BGP Local Autonomous System Attribute</title>
<author>
<organization>Juniper Networks, Inc.</organization>
</author>
<date year="2012"/>
</front>
</reference>
<reference anchor="ALU"
target="https://infoproducts.alcatel-lucent.com/html/0_add-h-f/93-0074-10-01/7750_SR_OS_Routing_Protocols_Guide/BGP-CLI.html#709567">
<front>
<title>BGP Local AS attribute</title>
<author>
<organization>Alcatel-Lucent</organization>
</author>
<date year="2006-2012"/>
</front>
</reference>
</references>
<!-- Change Log
v00 2006-03-15 EBD Initial version
v01 2006-04-03 EBD Moved PI location back to position 1 -
v3.1 of XMLmind is better with them at this location.
v02 2007-03-07 AH removed extraneous nested_list attribute,
other minor corrections
v03 2007-03-09 EBD Added comments on null IANA sections and fixed heading capitalization.
Modified comments around figure to reflect non-implementation of
figure indent control. Put in reference using anchor="DOMINATION".
Fixed up the date specification comments to reflect current truth.
v04 2007-03-09 AH Major changes: shortened discussion of PIs,
added discussion of rfc include.
v05 2007-03-10 EBD Added preamble to C program example to tell about ABNF and alternative
images. Removed meta-characters from comments (causes problems). -->
</back>
</rfc>
| PAFTECH AB 2003-2026 | 2026-04-23 04:54:54 |