Controlling VPN Routes More Precisely by ORF Extension
draft-sun-bess-vpn-orf-extension-00

Document Type Active Internet-Draft (individual)
Last updated 2018-10-22
Stream (None)
Intended RFC status (None)
Formats plain text 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)
INTERNET-DRAFT                                               Chunxia Sun
Intended status: Proposed Standard                          Yaokun Zhang
                                                     Donald Eastlake 3rd
                                                                  Huawei
Expires: April 21, 2019                                 October 22, 2018

         Controlling VPN Routes More Precisely by ORF Extension
                  draft-sun-bess-vpn-orf-extension-00

Abstract

   RFC 4684 defines Multi-Protocol BGP (MP-BGP) procedures that allow
   BGP speakers to exchange Route Target reachability information which
   can be used to build a route distribution graph in order to limit the
   propagation of Virtual Private Network (VPN) Network Layer
   Reachability Information (NLRI) between different autonomous systems
   or distinct clusters of the same autonomous system.

   However, according to RFC 4684, in some scenarios, more routes will
   be sent than need to be sent.

   This document extends RFC 4684. This extension allows a BGP speaker
   to advertise VPN routes more precisely.

Status of this Memo

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

   Distribution of this document is unlimited. Comments should be sent
   to the authors or the BESS working group mailing list: bess@ietf.org.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   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."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/1id-abstracts.html. The list of Internet-Draft
   Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

Sun, Zhang, & Eastlake                                          [Page 1]
Internet-Draft                                         VPN ORF Extension

Table of Contents

      1. Introduction............................................3
      1.1 Requirements Language..................................3
      1.2 Terminology............................................3

      2. Solution................................................5
      3. BGP Encoding............................................6

      4. Security Considerations.................................7
      5. IANA Considerations.....................................7

      Normative References.......................................8
      Informative References.....................................8

      Acknowledgments............................................8
      Authors' Addresses.........................................9

Sun, Zhang, & Eastlake                                          [Page 2]
Internet-Draft                                         VPN ORF Extension

1. Introduction

   [RFC4684] defines Multi-Protocol BGP (MP-BGP) procedures that allow
   BGP speakers to exchange Route Target reachability information which
   can be used to build a route distribution graph in order to limit the
   propagation of Virtual Private Network (VPN) Network Layer
   Reachability Information (NLRI) between different autonomous systems
   or distinct clusters of the same autonomous system.

   However, according to the extension of BGP protocol by [RFC4684], in
   some scenarios, for example, when the same route targets exist in
   different BGP address families, more routes will be sent than need to
   be sent, which violates the original intention of the ORF
   implementation.

   This document extends [RFC4684]. This extension allows a BGP speaker
   to advertise VPN routes more precisely when BGP speaker has the same
   route target in different address families.

1.1 Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in BCP
   14 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

1.2 Terminology

   AFI: Address Family Identifier(a BGP address type)

   SAFI: Subsequence Address Family Identifier (a BGP address sub-type)

   BGP: Border Gateway Protocol

   VPN: Virtual Private Network

   PE:  Provider Edge device

   CE:  Customer Edge(router)

   EVPN: Ethernet Virtual Private Network

   L3VPN: Layer 3 Virtual Private Network

Sun, Zhang, & Eastlake                                          [Page 3]
Internet-Draft                                         VPN ORF Extension

   iBGP: Internal BGP (i.e., a BGP peering session that connects two
Show full document text