IP Prefix Advertisement in EVPN
draft-rabadan-l2vpn-evpn-prefix-advertisement-02

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Authors Jorge Rabadan  , Jorge Rabadan  , Wim Henderickx  , Senad Palislamovic  , Senad Palislamovic  , Florin Balus  , Florin Balus  , Aldrin Isaac 
Last updated 2014-07-04
Replaced by draft-ietf-bess-evpn-prefix-advertisement
Stream (None)
Intended RFC status (None)
Formats 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)
L2VPN Workgroup                                               J. Rabadan
Internet Draft                                             W. Henderickx
                                                         S. Palislamovic
Intended status: Standards Track                          Alcatel-Lucent

J. Drake                                                        F. Balus
Juniper                                                   Nuage Networks

A. Sajassi                                                      A. Isaac
Cisco                                                          Bloomberg

Expires: January 5, 2015                                    July 4, 2014

                    IP Prefix Advertisement in EVPN
            draft-rabadan-l2vpn-evpn-prefix-advertisement-02

Abstract

   EVPN provides a flexible control plane that allows intra-subnet
   connectivity in an IP/MPLS and/or an NVO-based network. In NVO
   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 may not support their own 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
   http://www.ietf.org/ietf/1id-abstracts.txt
 

Rabadan et al.          Expires January 5, 2015                 [Page 1]
Internet-Draft         EVPN Prefix Advertisement            July 4, 2014

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

   This Internet-Draft will expire on January 5, 2015.

Copyright Notice

   Copyright (c) 2014 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. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2. Introduction and problem statement  . . . . . . . . . . . . . .  3
     2.1 Inter-subnet connectivity requirements in Data Centers . . .  4
     2.2 The requirement for advertising IP prefixes in EVPN  . . . .  6
     2.3 The requirement for a new EVPN route type  . . . . . . . . .  7
   3. The BGP EVPN IP Prefix route  . . . . . . . . . . . . . . . . .  9
     3.1 IP Prefix Route encoding . . . . . . . . . . . . . . . . . .  9
   4. Benefits of using the EVPN IP Prefix route  . . . . . . . . . . 11
   5. IP Prefix next-hop use-cases  . . . . . . . . . . . . . . . . . 12
     5.1 TS IP address next-hop use-case  . . . . . . . . . . . . . . 12
     5.2 Floating IP next-hop use-case  . . . . . . . . . . . . . . . 15
     5.3 IRB IP next-hop use-case . . . . . . . . . . . . . . . . . . 16
     5.4 ESI next-hop ("Bump in the wire") use-case . . . . . . . . . 18
     5.5 IRB forwarding without core-facing IRB use-case 
         (VRF-to-VRF) . . . . . . . . . . . . . . . . . . . . . . . . 20
   6. Conclusions . . . . . . . . . . . . . . . . . . . . . . . . . . 23
   7. Conventions used in this document . . . . . . . . . . . . . . . 24
   8. Security Considerations . . . . . . . . . . . . . . . . . . . . 24
   9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 24
   10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 24
     10.1 Normative References  . . . . . . . . . . . . . . . . . . . 24
     10.2 Informative References  . . . . . . . . . . . . . . . . . . 24
   11. Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 24
   12. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 24

 

Rabadan et al.          Expires January 5, 2015                 [Page 2]
Internet-Draft         EVPN Prefix Advertisement            July 4, 2014
Show full document text