Analysis of VPN Routes Control in Shared BGP Session
draft-wang-idr-vpn-routes-control-analysis-03

Document Type Active Internet-Draft (individual)
Authors Aijun Wang  , Wei Wang  , Gyan Mishra  , Haibo Wang  , Shunwan Zhuang  , Jie Dong 
Last updated 2021-03-07
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized (tools) htmlized 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)
IDR Working Group                                                A. Wang
Internet-Draft                                                   W. Wang
Intended status: Informational                             China Telecom
Expires: September 9, 2021                                     G. Mishra
                                                            Verizon Inc.
                                                                 H. Wang
                                                               S. Zhuang
                                                                 J. Dong
                                                     Huawei Technologies
                                                           March 8, 2021

          Analysis of VPN Routes Control in Shared BGP Session
             draft-wang-idr-vpn-routes-control-analysis-03

Abstract

   This draft analyzes some scenarios and the necessaries for VPN routes
   control in the shared BGP session, which can be the used as the base
   for the design of related solutions.

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 September 9, 2021.

Copyright Notice

   Copyright (c) 2021 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
   (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

Wang, et al.            Expires September 9, 2021               [Page 1]
Internet-Draft       Analysis of VPN routes control           March 2021

   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.  Conventions used in this document . . . . . . . . . . . . . .   2
   3.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   2
   4.  Inter-AS VPN Option B/AB Scenario . . . . . . . . . . . . . .   3
   5.  Inter-AS VPN Option C Scenario  . . . . . . . . . . . . . . .   4
   6.  Intra-AS VPN RR Deployment Scenario . . . . . . . . . . . . .   5
   7.  VPN Routes Shared on one PE . . . . . . . . . . . . . . . . .   6
   8.  Requirements for the solutions  . . . . . . . . . . . . . . .   7
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   10. IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   11. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . .   8
   12. Normative References  . . . . . . . . . . . . . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   BGP Maximum Prefix feature [RFC4486] is often used at the network
   boundary to control the number of prefixes to be injected into the
   network.  But for some scenarios when the VPN routes from several
   VRFs are advertised via one shared BGP session, there is lack of
   appropriate methods to control the flooding of VPN routes within one
   VRF to overwhelm the process of VPN routes in other VRFs.  That is to
   say, the excessive VPN routes advertisement should be controlled
   individually for each VRF in such shared BGP session.

   The following sections analyzes the scenarios that are necessary to
   such mechanism.

2.  Conventions used in this document

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119] .

3.  Terminology

   The following terms are defined in this draft:

   o  RD: Route Distinguisher, defined in [RFC4364]

Wang, et al.            Expires September 9, 2021               [Page 2]
Internet-Draft       Analysis of VPN routes control           March 2021

   o  RR: Router Reflector, provides a simple solution to the problem of
      IBGP full mesh connection in large-scale IBGP implementation.

   o  VRF: Virtual Routing Forwarding, a virtual routing table based on
      VPN instance.
Show full document text