RFC 4272

BGP Security Vulnerabilities Analysis, January 2006

Canonical URL:
https://www.rfc-editor.org/rfc/rfc4272.txt
File formats:
Plain TextPDF
Status:
INFORMATIONAL
Author:
S. Murphy
Stream:
IETF
Source:
idr (rtg)

Cite this RFC: TXT  |  XML

DOI:  10.17487/RFC4272

Discuss this RFC: Send questions or comments to idr@ietf.org

Other actions: Submit Errata  |  Find IPR Disclosures from the IETF


Abstract

Border Gateway Protocol 4 (BGP-4), along with a host of other infrastructure protocols designed before the Internet environment became perilous, was originally designed with little consideration for protection of the information it carries. There are no mechanisms internal to BGP that protect against attacks that modify, delete, forge, or replay data, any of which has the potential to disrupt overall network routing behavior. This document discusses some of the security issues with BGP routing data dissemination. This document does not discuss security issues with forwarding of packets. This memo provides information for the Internet community.


For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 4844.


Download PDF Reader