Route Distinguisher Outbound Route Filter (RD-ORF) for BGP-4
draft-wang-idr-rd-orf-03

Document Type Active Internet-Draft (individual)
Last updated 2020-08-23
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: February 25, 2021                                       H. Wang
                                                     Huawei Technologies
                                                               G. Mishra
                                                            Verizon Inc.
                                                               S. Zhuang
                                                                 J. Dong
                                                     Huawei Technologies
                                                         August 24, 2020

      Route Distinguisher Outbound Route Filter (RD-ORF) for BGP-4
                        draft-wang-idr-rd-orf-03

Abstract

   This draft defines a new Outbound Route Filter (ORF) type, called the
   Route Distinguisher ORF (RD-ORF).  RD-ORF is applicable when the
   routers do not exchange VPN routing information directly (e.g.
   routers in single-domain connect via Route Reflector, or routers in
   Option B/Option AB/Option C cross-domain scenario).

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 February 25, 2021.

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

Wang, et al.            Expires February 25, 2021               [Page 1]
Internet-Draft                   RD-ORF                      August 2020

   (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.  Conventions used in this document . . . . . . . . . . . . . .   4
   3.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  RD-ORF Encoding . . . . . . . . . . . . . . . . . . . . . . .   5
   5.  Application in single-domain scenario . . . . . . . . . . . .   7
     5.1.  Addition of RD-ORF entries  . . . . . . . . . . . . . . .   7
       5.1.1.  Operation process of RD-ORF mechanism on source PE  .   7
       5.1.2.  Operation process of RD-ORF mechanism on RR . . . . .   8
       5.1.3.  Operation process of RD-ORF mechanism on target PE  .   8
     5.2.  Withdraw of RD-ORF entries  . . . . . . . . . . . . . . .   9
   6.  Applications in cross-domain scenarios  . . . . . . . . . . .   9
     6.1.  Application in Option B/Option AB cross-domain scenario .   9
     6.2.  Application in Option C cross-domain scenario . . . . . .  10
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  11
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  12
   9.  Acknowledgement . . . . . . . . . . . . . . . . . . . . . . .  12
   10. Normative References  . . . . . . . . . . . . . . . . . . . .  12
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  13

1.  Introduction

   With the rapid growth of network scale, Route Reflector is introduced
   in order to reduce the network complexity.  Routers in the same
   Autonomous System only need to establish iBGP session with RR to
   transmit routes.

   In VPN scenario shown in Figure 1, PE1 - PE4 establish IBGP sessions
   with RR to ensure the routes can be transmitted within AS100, where
   PE1 and PE3 maintain VRFs of VPN1 and VPN2, PE2 maintains VPN1's VRF
   and PE4 maintains VPN2's VRF.  RR don not maintain any VRFs.

Wang, et al.            Expires February 25, 2021               [Page 2]
Internet-Draft                   RD-ORF                      August 2020

              +----------------------------------------------+
              |                                              |
              |                                              |
Show full document text