RFC 3345: Border Gateway Protocol (BGP) Persistent Route Oscillation Condition
In plain English — editorial summary, not part of the RFC
The Border Gateway Protocol (BGP) [1] is an inter-Autonomous System routing protocol. The primary function of a BGP speaking system is to exchange network reachability information with other BGP systems.
Document record
- Document ID
- RFC3345
- Published
- August 2002
- Authors
- D. McPherson; V. Gill; D. Walton; A. Retana
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 19
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2545Use of BGP-4 Multiprotocol Extensions for IPv6 Inter-Domain RoutingCurrent
March 1999
- RFC 5492Capabilities Advertisement with BGP-4Updated
February 2009
- RFC 5575Dissemination of Flow Specification RulesObsoleted
August 2009
- RFC 6368Internal BGP as the Provider/Customer Edge Protocol for BGP/MPLS IP Virtual Private Networks (VPNs)Updated
September 2011
- RFC 7705Autonomous System Migration Mechanisms and Their Effects on the BGP AS_PATH AttributeCurrent
November 2015
- RFC 7947Internet Exchange BGP Route ServerCurrent
September 2016
- RFC 8538Notification Message Support for BGP Graceful RestartCurrent
March 2019
- RFC 8810Revision to Capability Codes Registration ProceduresCurrent
August 2020
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?