IP Prefix Advertisement in EVPN
draft-ietf-bess-evpn-prefix-advertisement-11

Document Type Active Internet-Draft (bess WG)
Last updated 2018-05-18
Replaces draft-rabadan-l2vpn-evpn-prefix-advertisement
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Zhaohui Zhang
Shepherd write-up Show (last changed 2017-11-23)
IESG IESG state IESG Evaluation::AD Followup
Consensus Boilerplate Yes
Telechat date
Has enough positions to pass.
Responsible AD Alvaro Retana
Send notices to "Zhaohui Zhang" <zzhang@juniper.net>, aretana.ietf@gmail.com
IANA IANA review state Version Changed - Review Needed
IANA action state None
BESS Workgroup                                           J. Rabadan, Ed.
Internet Draft                                             W. Henderickx
Intended status: Standards Track                                   Nokia

                                                                J. Drake
                                                                  W. Lin
                                                                 Juniper

                                                              A. Sajassi
                                                                   Cisco

Expires: November 19, 2018                                  May 18, 2018

                    IP Prefix Advertisement in EVPN
              draft-ietf-bess-evpn-prefix-advertisement-11

Abstract

   The BGP MPLS-based Ethernet VPN (EVPN) [RFC7432] mechanism provides a
   flexible control plane that allows intra-subnet connectivity in an
   MPLS and/or NVO (Network Virtualization Overlay) [RFC7365] network.
   In some networks, there is also a need for a dynamic and efficient
   inter-subnet connectivity across Tenant Systems and End Devices that
   can be physical or virtual and do not necessarily participate in
   dynamic routing protocols. This document defines a new EVPN route
   type for the advertisement of IP Prefixes and explains some use-case
   examples where this new route-type is used.

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), 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
 

Rabadan et al.         Expires November 19, 2018                [Page 1]
Internet-Draft         EVPN Prefix Advertisement            May 18, 2018

   http://www.ietf.org/ietf/1id-abstracts.txt

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

   This Internet-Draft will expire on November 19, 2018.

Copyright Notice

   Copyright (c) 2018 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
   (http://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  . . . . . . . . . . . . . . . . . . . . . . . . .  3
     1.1 Terminology  . . . . . . . . . . . . . . . . . . . . . . . .  3
   2. Problem Statement . . . . . . . . . . . . . . . . . . . . . . .  5
     2.1 Inter-Subnet Connectivity Requirements in Data Centers . . .  5
     2.2 The Need for the EVPN IP Prefix Route  . . . . . . . . . . .  8
   3. The BGP EVPN IP Prefix Route  . . . . . . . . . . . . . . . . . 10
     3.1 IP Prefix Route Encoding . . . . . . . . . . . . . . . . . . 11
     3.2 Overlay Indexes and Recursive Lookup Resolution  . . . . . . 13
   4. Overlay Index Use-Cases . . . . . . . . . . . . . . . . . . . . 15
     4.1 TS IP Address Overlay Index Use-Case . . . . . . . . . . . . 16
     4.2 Floating IP Overlay Index Use-Case . . . . . . . . . . . . . 18
     4.3 Bump-in-the-Wire Use-Case  . . . . . . . . . . . . . . . . . 20
     4.4 IP-VRF-to-IP-VRF Model . . . . . . . . . . . . . . . . . . . 23
       4.4.1 Interface-less IP-VRF-to-IP-VRF Model  . . . . . . . . . 24
       4.4.2 Interface-ful IP-VRF-to-IP-VRF with SBD IRB  . . . . . . 27
       4.4.3 Interface-ful IP-VRF-to-IP-VRF with Unnumbered SBD IRB . 30
   5. Security Considerations . . . . . . . . . . . . . . . . . . . . 33
   6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 33
   7. References  . . . . . . . . . . . . . . . . . . . . . . . . . . 34
     7.1 Normative References . . . . . . . . . . . . . . . . . . . . 34
     7.2 Informative References . . . . . . . . . . . . . . . . . . . 34
   8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 35
   9. Contributors  . . . . . . . . . . . . . . . . . . . . . . . . . 35
   10. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 36
Show full document text