RFC 8212: Default External BGP (EBGP) Route Propagation Behavior without Policies
In plain English — editorial summary, not part of the RFC
This document updates RFC 4271 by defining the default behavior of a BGP speaker when there is no Import or Export Policy associated with an External BGP session.
Document record
- Document ID
- RFC8212
- Published
- July 2017
- Authors
- J. Mauch; J. Snijders; G. Hankins
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 7
- Also known as
- —
- Updates:
- RFC 4271
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8327Mitigating the Negative Impact of Maintenance through BGP Session CullingCurrent
March 2018
- RFC 8195Use of BGP Large CommunitiesCurrent
June 2017
- RFC 8313Use of Multicast across Inter-domain Peering PointsCurrent
January 2018
- RFC 7908Problem Definition and Classification of BGP Route LeaksCurrent
June 2016
- RFC 8549Export of BGP Community Information in IP Flow Information Export (IPFIX)Current
April 2019
- RFC 7854BGP Monitoring Protocol (BMP)Updated
June 2016
- RFC 8704Enhanced Feasible-Path Unicast Reverse Path ForwardingCurrent
February 2020
- RFC 9069Support for Local RIB in the BGP Monitoring Protocol (BMP)Updated
February 2022
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?