RFC 9014 on Interconnect Solution for Ethernet VPN (EVPN) Overlay Networks
rfc-editor@rfc-editor.org Thu, 27 May 2021 01:23 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 CED343A07A2; Wed, 26 May 2021 18:23:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, 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 3dvIX-EtzkfZ; Wed, 26 May 2021 18:23:54 -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 9A6663A0794; Wed, 26 May 2021 18:23:54 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id A1CC8F4079D; Wed, 26 May 2021 18:23:41 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9014 on Interconnect Solution for Ethernet VPN (EVPN) Overlay Networks
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: <20210527012341.A1CC8F4079D@rfc-editor.org>
Date: Wed, 26 May 2021 18:23:41 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/F9BaqSOCW90yNafsFL4lH__PDC8>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 27 May 2021 01:24:00 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 9014
Title: Interconnect Solution for Ethernet VPN
(EVPN) Overlay Networks
Author: J. Rabadan, Ed.,
S. Sathappan,
W. Henderickx,
A. Sajassi,
J. Drake
Status: Standards Track
Stream: IETF
Date: May 2021
Mailbox: jorge.rabadan@nokia.com,
senthil.sathappan@nokia.com,
wim.henderickx@nokia.com,
sajassi@cisco.com,
jdrake@juniper.net
Pages: 24
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-bess-dci-evpn-overlay-10.txt
URL: https://www.rfc-editor.org/info/rfc9014
DOI: 10.17487/RFC9014
This document describes how Network Virtualization Overlays (NVOs)
can be connected to a Wide Area Network (WAN) in order to extend the
Layer 2 connectivity required for some tenants. The solution analyzes
the interaction between NVO networks running Ethernet Virtual Private
Networks (EVPNs) and other Layer 2 VPN (L2VPN) technologies used in
the WAN, such as Virtual Private LAN Services (VPLSs), VPLS
extensions for Provider Backbone Bridging (PBB-VPLS), EVPN, or
PBB-EVPN. It also describes how the existing technical specifications
apply to the interconnection and extends the EVPN procedures needed
in some cases. In particular, this document describes how EVPN routes
are processed on Gateways (GWs) that interconnect EVPN-Overlay and
EVPN-MPLS networks, as well as the Interconnect Ethernet Segment
(I-ES), to provide multihoming. This document also describes the use
of the Unknown MAC Route (UMR) to avoid issues of a Media Access
Control (MAC) scale on Data Center 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