EVPN VPWS as VRF Attachment Circuit
draft-wz-bess-evpn-vpws-as-vrf-ac-00

Document Type Active Internet-Draft (individual)
Authors Yubao(Bob) Wang  , Zheng Zhang 
Last updated 2020-09-15
Stream (None)
Intended RFC status (None)
Formats plain text html 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)
BESS WG                                                          Y. Wang
Internet-Draft                                                  Z. Zhang
Intended status: Standards Track                         ZTE Corporation
Expires: 19 March 2021                                 15 September 2020

                  EVPN VPWS as VRF Attachment Circuit
                  draft-wz-bess-evpn-vpws-as-vrf-ac-00

Abstract

   When a VRF Attachment Cirucit (VRF-AC) is far away from its IP-VRF
   instance, we can deploy an EVPN VPWS ([RFC8214]) between that VRF-AC
   and its IP-VRF instance.  From the viewpoint of the IP-VRF instance,
   a local virtual interface takes the place of that remote "VRF-AC".
   The intended IP address for that VRF-AC is now configured to the
   virtual interface, in other words, the virtual interface is the
   actual VRF-AC of the IP-VRF instance.  The virtual interface is also
   the AC of that VPWS instance, in other words, the virtual interface
   is cross-connected to that remote "VRF-AC" by the VPWS instance.

   This document proposes an extension to [RFC7432] to support this
   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 19 March 2021.

Copyright Notice

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

Wang & Zhang              Expires 19 March 2021                 [Page 1]
Internet-Draft             EVPN VPWS as VRF-AC            September 2020

   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
     1.1.  Integrated Routing and Cross-connecting . . . . . . . . .   3
     1.2.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   4
   2.  ARP/ND Synching and IP Prefix Synching  . . . . . . . . . . .   5
     2.1.  Constructing MAC/IP Advertisement Route . . . . . . . . .   6
     2.2.  Constructing Ethernet A-D Route . . . . . . . . . . . . .   6
     2.3.  Constructing IP Prefix Advertisement Route  . . . . . . .   6
   3.  Packet Walk Through . . . . . . . . . . . . . . . . . . . . .   7
   4.  Fast Convergence for Routed Traffic . . . . . . . . . . . . .   8
   5.  Considerations on ABRs and Route Reflectors . . . . . . . . .   8
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   8.  Normative References  . . . . . . . . . . . . . . . . . . . .   8
   9.  Informative References  . . . . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   When a VRF Attachment Cirucit (VRF-AC) is far away from its IP-VRF
   instance, we can deploy an EVPN VPWS ([RFC8214]) between that VRF-AC
   and its IP-VRF instance.  From the viewpoint of the IP-VRF instance,
   a local virtual interface takes the place of that remote "VRF-AC".
   The intended IP address for that VRF-AC is now configured to the
   virtual interface, in other words, the virtual interface is the
   actual VRF-AC of the IP-VRF instance.  The virtual interface is also
   the AC of that VPWS instance, in other words, the virtual interface
   is cross-connected to that remote "VRF-AC" by the VPWS instance.

   The requirements of this scenario is described in Section 1.1.

Wang & Zhang              Expires 19 March 2021                 [Page 2]
Internet-Draft             EVPN VPWS as VRF-AC            September 2020

1.1.  Integrated Routing and Cross-connecting

   When an IP-VRF instance and an EVPN VPWS instance are connected by an
   virtual-interface, We call such scenarios as Integrated Routing and
   Cross-connecting (IRC) use-case, and the virtual-interface connecting
   EVPN VPWS and IP-VRF is called as IRC interface, because that the
Show full document text