Autonomous System (AS) Migration Features and Their Effects on the BGP AS_PATH Attribute
draft-ga-idr-as-migration-03

Document Type Replaced Internet-Draft (individual)
Last updated 2014-07-21 (latest revision 2014-01-06)
Replaced by draft-ietf-idr-as-migration
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-idr-as-migration
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-ga-idr-as-migration-03.txt

Abstract

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 future BGP protocol work such as BGPSec.

Authors

Wesley George (wesley.george@twcable.com)
Shane Amante (samante@apple.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)