RFC 8365 on A Network Virtualization Overlay Solution Using Ethernet VPN (EVPN)
rfc-editor@rfc-editor.org Fri, 30 March 2018 01:01 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B334C127775; Thu, 29 Mar 2018 18:01:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pXtYN7Pq9eCZ; Thu, 29 Mar 2018 18:01:57 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4586D126579; Thu, 29 Mar 2018 18:01:57 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 21D49B80D0E; Thu, 29 Mar 2018 18:01:36 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8365 on A Network Virtualization Overlay Solution Using Ethernet VPN (EVPN)
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, bess@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20180330010136.21D49B80D0E@rfc-editor.org>
Date: Thu, 29 Mar 2018 18:01:36 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/zi4xKq5EZUz6cNpEHdH5uVyPVHw>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Mar 2018 01:01:59 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8365
Title: A Network Virtualization Overlay Solution
Using Ethernet VPN (EVPN)
Author: A. Sajassi, Ed.,
J. Drake, Ed.,
N. Bitar,
R. Shekhar,
J. Uttaro,
W. Henderickx
Status: Standards Track
Stream: IETF
Date: March 2018
Mailbox: sajassi@cisco.com,
jdrake@juniper.net,
nabil.bitar@nokia.com,
rshekhar@juniper.net,
uttaro@att.com,
wim.henderickx@nokia.com
Pages: 33
Characters: 76766
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-bess-evpn-overlay-12.txt
URL: https://www.rfc-editor.org/info/rfc8365
DOI: 10.17487/RFC8365
This document specifies how Ethernet VPN (EVPN) can be used as a
Network Virtualization Overlay (NVO) solution and explores the
various tunnel encapsulation options over IP and their impact on the
EVPN control plane and procedures. In particular, the following
encapsulation options are analyzed: Virtual Extensible LAN (VXLAN),
Network Virtualization using Generic Routing Encapsulation (NVGRE),
and MPLS over GRE. This specification is also applicable to Generic
Network Virtualization Encapsulation (GENEVE); however, some
incremental work is required, which will be covered in a separate
document. This document also specifies new multihoming procedures
for split-horizon filtering and mass withdrawal. It also specifies
EVPN route constructions for VXLAN/NVGRE encapsulations and
Autonomous System Border Router (ASBR) procedures for multihoming of
Network Virtualization Edge (NVE) devices.
This document is a product of the BGP Enabled Services Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC