RFC 7454: BGP Operations and Security
In plain English — editorial summary, not part of the RFC
The Border Gateway Protocol (BGP) is the protocol almost exclusively used in the Internet to exchange routing information between network domains. Due to this central nature, it is important to understand the security measures that can and should be deployed to prevent accidental or intentional routing disturbances. This document describes measures to protect the BGP sessions itself such as Time to Live (TTL), the TCP Authentication Option (TCP-AO), and control-plane filtering. It also describes measures to better control the flow of routing information, using prefix filtering and automation of prefix filters, max-prefix filtering, Autonomous System (AS) path filtering, route flap dampening, and BGP community scrubbing.
Document record
- Document ID
- RFC7454
- Published
- February 2015
- Authors
- J. Durand; I. Pepelnjak; G. Doering
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- ops
- Pages
- 26
- Also known as
- BCP194
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7450Automatic Multicast TunnelingUpdated
February 2015
- RFC 7460Monitoring and Control MIB for Power and EnergyCurrent
March 2015
- RFC 7448MIB Transfer from the IETF to the IEEE 802.3 WGCurrent
February 2015
- RFC 7461Energy Object Context MIBCurrent
March 2015
- RFC 7445Analysis of Failure Cases in IPv6 Roaming ScenariosCurrent
March 2015
- RFC 7477Child-to-Parent Synchronization in DNSUpdated
March 2015
- RFC 7424Mechanisms for Optimizing Link Aggregation Group (LAG) and Equal-Cost Multipath (ECMP) Component Link Utilization in NetworksCurrent
January 2015
- RFC 7423Diameter Applications Design GuidelinesCurrent
November 2014
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?