[bess] RFC 9135 on Integrated Routing and Bridging in Ethernet VPN (EVPN)
rfc-editor@rfc-editor.org Wed, 13 October 2021 20:28 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: bess@ietfa.amsl.com
Delivered-To: bess@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2904F3A0DE8; Wed, 13 Oct 2021 13:28:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-0.001, 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 plnG97fZlDxa; Wed, 13 Oct 2021 13:28:39 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0A2953A0DD9; Wed, 13 Oct 2021 13:28:39 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 499) id A4286133108; Wed, 13 Oct 2021 13:28:38 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
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: <20211013202838.A4286133108@rfc-editor.org>
Date: Wed, 13 Oct 2021 13:28:38 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/tHDqIpzYVUH38qBt7DDHRAl0pms>
Subject: [bess] RFC 9135 on Integrated Routing and Bridging in Ethernet VPN (EVPN)
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bess>, <mailto:bess-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess/>
List-Post: <mailto:bess@ietf.org>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bess>, <mailto:bess-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Oct 2021 20:28:46 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 9135
Title: Integrated Routing and Bridging in
Ethernet VPN (EVPN)
Author: A. Sajassi,
S. Salam,
S. Thoria,
J. Drake,
J. Rabadan
Status: Standards Track
Stream: IETF
Date: October 2021
Mailbox: sajassi@cisco.com,
ssalam@cisco.com,
sthoria@cisco.com,
jdrake@juniper.net,
jorge.rabadan@nokia.com
Pages: 30
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-bess-evpn-inter-subnet-forwarding-15.txt
URL: https://www.rfc-editor.org/info/rfc9135
DOI: 10.17487/RFC9135
Ethernet VPN (EVPN) provides an extensible and flexible multihoming
VPN solution over an MPLS/IP network for intra-subnet connectivity
among Tenant Systems and end devices that can be physical or virtual.
However, there are scenarios for which there is a need for a dynamic
and efficient inter-subnet connectivity among these Tenant Systems
and end devices while maintaining the multihoming capabilities of
EVPN. This document describes an Integrated Routing and Bridging
(IRB) solution based on EVPN to address such requirements.
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