Autonomous System Migration Features and Their Effects on the BGP AS_PATH Attribute
draft-ietf-idr-as-migration-03

The information below is for an old version of the document
Document Type Active Internet-Draft (idr WG)
Last updated 2015-02-16 (latest revision 2014-09-29)
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Additional URLs
- Mailing list discussion
Stream WG state Submitted to IESG for Publication
Document shepherd Chris Morrow
Shepherd write-up Show (last changed 2014-11-12)
IESG IESG state Waiting for AD Go-Ahead
Consensus Boilerplate Yes
Telechat date
Needs 6 more YES or NO OBJECTION positions to pass.
Responsible AD Alia Atlas
Send notices to morrowc@ops-netman.net, idr@ietf.org, idr-chairs@ietf.org, draft-ietf-idr-as-migration.all@ietf.org
IANA IANA review state IANA OK - No Actions Needed
IANA action state None
Internet Engineering Task Force                                W. George
Internet-Draft                                         Time Warner Cable
Intended status: Standards Track                               S. Amante
Expires: April 2, 2015                                       Apple, Inc.
                                                      September 29, 2014

   Autonomous System Migration Features and Their Effects on the BGP
                           AS_PATH Attribute
                     draft-ietf-idr-as-migration-03

Abstract

   This draft discusses some BGP features for ASN migration 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 April 2, 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
   include Simplified BSD License text as described in Section 4.e of

George & Amante           Expires April 2, 2015                 [Page 1]
Internet-Draft            AS Migration Features           September 2014

   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 . . . . . . . . . .   7
     3.3.  Implementation  . . . . . . . . . . . . . . . . . . . . .   8
   4.  Internal BGP Autonomous System Migration Features . . . . . .   9
     4.1.  Internal BGP Alias  . . . . . . . . . . . . . . . . . . .  10
     4.2.  Implementation  . . . . . . . . . . . . . . . . . . . . .  12
   5.  Additional Operational Considerations . . . . . . . . . . . .  13
   6.  Conclusion  . . . . . . . . . . . . . . . . . . . . . . . . .  14
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  14
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  14
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .  14
   10. Appendix: Implementation report . . . . . . . . . . . . . . .  15
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .  15
     11.1.  Normative References . . . . . . . . . . . . . . . . . .  15
     11.2.  Informative References . . . . . . . . . . . . . . . . .  15
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  16

1.  Introduction

   This draft discusses some BGP features for ASN migration 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, and will not necessarily be harmonized
   due to this document.  However, it is necessary to document these de
   facto standards to ensure that new implementations can be successful,
   and 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.

   The migration features discussed here are useful to ISPs and
Show full document text