RFC 5291: Outbound Route Filtering Capability for BGP-4
In plain English — editorial summary, not part of the RFC
This document defines a BGP-based mechanism that allows a BGP speaker to send to its BGP peer a set of Outbound Route Filters (ORFs) that the peer would use to constrain/filter its outbound routing updates to the speaker. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5291
- Published
- August 2008
- Authors
- E. Chen; Y. Rekhter
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 12
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5292Address-Prefix-Based Outbound Route Filter for BGP-4Current
August 2008
- RFC 7543Covering Prefixes Outbound Route Filter for BGP-4Current
May 2015
- RFC 5294Host Threats to Protocol Independent Multicast (PIM)Current
August 2008
- RFC 5287Control Protocol Extensions for the Setup of Time-Division Multiplexing (TDM) Pseudowires in MPLS NetworksCurrent
August 2008
- RFC 5286Basic Specification for IP Fast Reroute: Loop-Free AlternatesUpdated
September 2008
- RFC 5298Analysis of Inter-Domain Label Switched Path (LSP) RecoveryCurrent
August 2008
- RFC 5283LDP Extension for Inter-Area Label Switched Paths (LSPs)Current
July 2008
- RFC 5301Dynamic Hostname Exchange Mechanism for IS-ISUpdated
October 2008
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?