BGP operations and security

Document Type Replaced Internet-Draft (individual)
Authors Jerome Durand  , Ivan Pepelnjak , Gert Döring
Last updated 2013-03-20 (latest revision 2012-09-21)
Replaced by RFC 7454
Stream (None)
Intended RFC status (None)
Expired & archived
plain text xml htmlized pdfized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-opsec-bgp-security
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


BGP (Border Gateway Protocol) is the protocol almost exclusively used in the Internet to exchange routing information between network domains. Due to this central nature, it's 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 (like TTL, MD5, control plane filtering) and to better control the flow of routing information, using prefix filtering and automatization of prefix filters, max-prefix filtering, AS path filtering, route flap dampening and BGP community scrubbing.


Jerome Durand (
Ivan Pepelnjak (
Gert Döring (

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)