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 Active Internet-Draft (idr WG)
Last updated 2014-07-29
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Additional URLs
- Mailing list discussion
Stream WG state WG Document
Other - see Comment Log
Document shepherd Chris Morrow
IESG IESG state I-D Exists
Consensus Boilerplate Yes
Telechat date
Responsible AD (None)
Send notices to (None)
Internet Engineering Task Force                                W. George
Internet-Draft                                         Time Warner Cable
Intended status: Standards Track                               S. Amante
Expires: January 30, 2015                                    Apple, Inc.
                                                           July 29, 2014

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

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.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on January 30, 2015.

Copyright Notice

   Copyright (c) 2014 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must

George & Amante         Expires January 30, 2015                [Page 1]
Internet-Draft            AS Migration Features                July 2014

   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
     1.2.  Documentation note  . . . . . . . . . . . . . . . . . . .   3
   2.  ASN Migration Scenario Overview . . . . . . . . . . . . . . .   4
   3.  External BGP Autonomous System Migration Features . . . . . .   6
     3.1.  Modify Inbound BGP AS_PATH Attribute  . . . . . . . . . .   6
     3.2.  Modify Outbound BGP AS_PATH Attribute . . . . . . . . . .   8
     3.3.  Implementation  . . . . . . . . . . . . . . . . . . . . .   9
   4.  Internal BGP Autonomous System Migration Features . . . . . .  10
     4.1.  Internal BGP Alias  . . . . . . . . . . . . . . . . . . .  10
     4.2.  Implementation  . . . . . . . . . . . . . . . . . . . . .  13
   5.  Additional Operational Considerations . . . . . . . . . . . .  14
   6.  Conclusion  . . . . . . . . . . . . . . . . . . . . . . . . .  14
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  15
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  15
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .  15
   10. Appendix: Implementation report . . . . . . . . . . . . . . .  15
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .  16
     11.1.  Normative References . . . . . . . . . . . . . . . . . .  16
     11.2.  Informative References . . . . . . . . . . . . . . . . .  16
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  17

1.  Introduction

   This draft discusses common methods of managing an ASN migration
   using some BGP features that while commonly-used are not formally
   part of the BGP4 [RFC4271] protocol specification and may be vendor-
   specific in exact implementation.  These features are local to a
   given BGP Speaker 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, so
   slight variations between existing vendor implementations exist.
   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.

   It is important to understand the business need for these features
   and illustrate why they are critical, particularly for ISPs'
Show full document text