Scalable De-Aggregation for Overlays Using the Border Gateway Protocol (BGP)
draft-templin-rtgwg-scalable-bgp-01

Document Type Active Internet-Draft (individual)
Last updated 2019-01-29
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                    F. Templin, Ed.
Internet-Draft                                                G. Saccone
Intended status: Informational              Boeing Research & Technology
Expires: August 2, 2019                                         G. Dawra
                                                                LinkedIn
                                                               A. Lindem
                                                               V. Moreno
                                                     Cisco Systems, Inc.
                                                        January 29, 2019

 Scalable De-Aggregation for Overlays Using the Border Gateway Protocol
                                 (BGP)
                draft-templin-rtgwg-scalable-bgp-01.txt

Abstract

   The Border Gateway Protocol (BGP) has well-known limitations in terms
   of the numbers of routes that can be carried and stability of the
   routing system.  This is especially true when mobile nodes frequently
   change their network attachment points, which in the past has
   resulted in excessive announcements and withdrawals of de-aggregated
   prefixes.  This document discusses a means of accommodating scalable
   de-aggregation of IPv6 prefixes for overlay networks using BGP.

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 https://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 August 2, 2019.

Copyright Notice

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

Templin, et al.          Expires August 2, 2019                 [Page 1]
Internet-Draft       Scalable De-Aggregation for BGP        January 2019

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://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
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Overview and Analysis . . . . . . . . . . . . . . . . . . . .   2
   3.  Opportunities and Limitations . . . . . . . . . . . . . . . .   4
   4.  Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . .   4
   5.  Implementation Status . . . . . . . . . . . . . . . . . . . .   4
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   5
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     9.2.  Informative References  . . . . . . . . . . . . . . . . .   5
   Appendix A.  Change Log . . . . . . . . . . . . . . . . . . . . .   6
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   The Border Gateway Protocol (BGP) [RFC4271] has well-known
   limitations in terms of the numbers of routes that can be carried and
   the stability of the routing system.  This is especially true for
   routing systems that include mobile nodes that frequently change
   their network attachment points, which in the past have resulted in
   excessive announcements and withdrawals of de-aggregated prefixes.
   This document discusses a means of accommodating scalable de-
   aggregation of IPv6 prefixes [RFC8200] for overlay networks using
   BGP.

2.  Overview and Analysis

   As discussed in [I-D.ietf-rtgwg-atn-bgp] and
   [I-D.templin-intarea-6706bis], the method for accommodating de-
   aggregation is to institute an overlay network instance of BGP that
   is separate and independent from the global Internet BGP routing
   system.  The overlay is presented to the global Internet as a small
   number of aggregated IPv6 prefixes (also known as Mobility Service
   Prefixes (MSPs)) that never change.  In this way, the Internet BGP
   routing system sees only stable aggregated MSPs (e.g., 2001:db8::/32)
Show full document text