Autonomous System (AS) Migration Features and Their Effects on the BGP AS_PATH Attribute
draft-ietf-idr-as-migration-02
| The information below is for an old version of the document | |||||
|---|---|---|---|---|---|
| Document | Type | None Internet-Draft (idr WG) | |||
| Last updated | 2014-07-29 | ||||
| Stream | IETF | ||||
| Intended RFC status | (None) | ||||
| Formats |
Expired & archived
pdf
htmlized
bibtex
|
||||
| Reviews | |||||
| Additional URLs |
|
||||
| Stream | WG state | (None) | |||
| Document shepherd | Chris Morrow | ||||
| IESG | IESG state | Unknown state | |||
| Consensus Boilerplate | Yes | ||||
| Telechat date | |||||
| Responsible AD | (None) | ||||
| Send notices to | (None) | ||||
https://www.ietf.org/archive/id/draft-ietf-idr-as-migration-02.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.)