EVPN Vendor-Specific Route Type
draft-rabadan-bess-vendor-evpn-route-03

Document Type Active Internet-Draft (individual)
Last updated 2017-03-13
Stream (None)
Intended RFC status (None)
Formats plain text pdf html 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 Workgroup                                           J. Rabadan, Ed.
Internet Draft                                              M. Vigoureux
Intended status: Standards Track                               M. Gautam
                                                                   Nokia

                                                            S. Dindorkar
                                                          Nuage Networks

Expires: September 14, 2017                               March 13, 2017

                    EVPN Vendor-Specific Route Type
                draft-rabadan-bess-vendor-evpn-route-03

Abstract

   RFC7432 defines Ethernet VPN as a BGP address family that makes use
   of Typed NLRIs. IANA has a registry called "EVPN Route Types" that
   allocates values to Route Types. The purpose of this document is to
   solicit IANA the registration of a route type value for a vendor
   specific usage, as well as the definition of the EVPN NLRI for that
   route.

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

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

 

Rabadan et al.         Expires September 14, 2017               [Page 1]
Internet-Draft      EVPN Vendor Specific Route Type       March 13, 2017

   This Internet-Draft will expire on September 14, 2017.

Copyright Notice

   Copyright (c) 2017 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  . . . . . . . . . . . . . . . . . . . . . . . . .  2
   2. The EVPN Vendor-Specific Route Type . . . . . . . . . . . . . .  3
   3. Conventions used in this document . . . . . . . . . . . . . . .  4
   4. Security Considerations . . . . . . . . . . . . . . . . . . . .  4
   5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . .  4
   6. References  . . . . . . . . . . . . . . . . . . . . . . . . . .  4
     6.1 Normative References . . . . . . . . . . . . . . . . . . . .  4
   7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . .  5
   8. Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . .  5

1. Introduction

   RFC7432 creates an IANA managed registry called "EVPN Route Types"
   and makes the initial registrations for different NLRIs. The ability
   to define Typed NLRIs makes EVPN a flexible and extensible technology
   that can be used for multiple purposes. This document solicits the
   value 255 for a new Route Type that will be called "EVPN Vendor
   Specific" Route Type. 

   The intend of this new Type is to allow operators and vendors to
   design rapidly new EVPN applications/prototypes and experiment with
   them in deployed networks before standardizing the specific
   application. Software Defined Networks (SDN) are evolving fast and
   the flexibility allowed by this new Route Type will contribute to the
   SDN control plane evolution.
 

Rabadan et al.         Expires September 14, 2017               [Page 2]
Internet-Draft      EVPN Vendor Specific Route Type       March 13, 2017

   Another motivation for this new Route Type is the exchange of vendor
   specific information that may be relevant only for the vendor using
   it. Other vendors may convey the information in a different way, or
   they simply don't need to exchange it.  

   In order to allow multiple applications, the new NLRI contains a
   Organizational Unique Identifier (OUI) field for which the IEEE
   registers and maintains values.
Show full document text