Movatterモバイル変換


[0]ホーム

URL:


Search RFCs

Advanced Search

RFC Editor

RFC 9136

IP Prefix Advertisement in Ethernet VPN (EVPN),October 2021

File formats:

icon for HTMLicon for text fileicon for v3pdficon for XML
Also available:XML file for editing
 
Status:
PROPOSED STANDARD
Authors:
J. Rabadan, Ed.
W. Henderickx
J. Drake
W. Lin
A. Sajassi
Stream:
IETF
Source:
bess (rtg)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC9136

Discuss this RFC: Send questions or comments to the mailing listbess@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 9136


Abstract

The BGP MPLS-based Ethernet VPN (EVPN) (RFC 7432) mechanism providesa flexible control plane that allows intra-subnet connectivity in anMPLS and/or Network Virtualization Overlay (NVO) (RFC 7365) network.In some networks, there is also a need for dynamic and efficientinter-subnet connectivity across Tenant Systems and end devices thatcan be physical or virtual and do not necessarily participate indynamic routing protocols. This document defines a new EVPN routetype for the advertisement of IP prefixes and explains some use-caseexamples where this new route type is used.


For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.




IABIANAIETFIRTFISEISOCIETF Trust
ReportsPrivacy StatementSite MapContact Us

Advanced Search

[8]ページ先頭

©2009-2025 Movatter.jp