Route Distinguisher Outbound Route Filter for BGP-4
draft-wang-idr-rd-orf-00

Document Type Active Internet-Draft (individual)
Last updated 2020-05-31
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                                                W. Wang
Internet-Draft                                                   A. Wang
Intended status: Standards Track                           China Telecom
Expires: December 3, 2020                                   June 1, 2020

          Route Distinguisher Outbound Route Filter for BGP-4
                        draft-wang-idr-rd-orf-00

Abstract

   This draft defines a new Outbound Route Filter (ORF) type, called the
   Route Distinguisher ORF (RD-ORF).  RD-ORF is applicable in BGP/MPLS
   IP Virtual Private Networks and Ethernet VPN, in which the Route
   Reflector (RR) and Autonomous System border router (ASBR) do not
   maintain the VPN routes.

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 December 3, 2020.

Copyright Notice

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

Wang & Wang             Expires December 3, 2020                [Page 1]
Internet-Draft                   RD-ORF                        June 2020

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions used in this document . . . . . . . . . . . . . .   3
   3.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  RD-ORF Encoding . . . . . . . . . . . . . . . . . . . . . . .   3
   5.  Operation . . . . . . . . . . . . . . . . . . . . . . . . . .   5
     5.1.  Application in Option B cross-domain scenario . . . . . .   5
     5.2.  Application in Option C cross-domain scenario . . . . . .   8
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  10
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
   8.  Normative References  . . . . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  11

1.  Introduction

   According to the description in [RFC4364], MPLS VPN can cross-domain
   networking in three ways, we usually called them Option A, B and C.
   In Option A, an Autonomous System border router (ASBR) is attached
   directly to an ASBR in another AS, they act as CE/PE of each other
   and exchange VPN route, so they SHOULD maintain VPN route information
   in Virtual Routing Forwarding (VRF).  So, the route control mechanism
   based on Prefix Limit can be used in Option A scenario, to prevent
   the number of routes transmitted by one of them from exceeding the
   maximum number of another's routing tables.  In Option B, a ASBR is
   connected to another via EBGP.  ASBRs only perform VPN routing
   forwarding, the maintenance of VRF is done by PEs.  In Option C, RRs
   are connected each other via MP-EBGP and are responsible for VPN
   routing forwarding, without maintaining VRFs.  Due to ASBRs and RRs
   do not maintain VRFs in Option B and C, the route control mechanism
   based on Prefix Limit does not work.

   [RFC5291] defines a BGP-based mechanism called Outbound Route Filter
   (ORF), which allows a BGP speaker to send a set of ORFs to its BGP
   peers, the peers will constrain the routing information that they
   decide to transmit to the speaker.

   This draft defines a new ORF-type, called the Route Distinguisher ORF
   (RD-ORF).  When the route table of a BGP speaker reaches its maximum,
   the BGP speaker will send a RD-ORF to its BGP peers that carry a RD.
   If a BGP speaker receives a RD-ORF from its BGP peer, it will filter
   the VPN routes it tends to send according to the RD-ORF entry.

   RD-ORF is applicable in BGP/MPLS IP Virtual Private Networks
   [RFC4364], and BGP/MPLS Ethernet VPN (EVPN) networks [RFC7432].

Wang & Wang             Expires December 3, 2020                [Page 2]
Internet-Draft                   RD-ORF                        June 2020
Show full document text