BGP operations and security
draft-jdurand-bgp-security-02

Document Type Replaced Internet-Draft (individual)
Last updated 2013-03-20 (latest revision 2012-09-21)
Replaced by draft-ietf-opsec-bgp-security
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html 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
https://www.ietf.org/archive/id/draft-jdurand-bgp-security-02.txt

Abstract

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.

Authors

Jerome Durand (jerduran@cisco.com)
Ivan Pepelnjak (ip@nil.com)
Gert Doering (gert@space.net)

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