Search RFCs
RFC 4272
BGP Security Vulnerabilities Analysis,January 2006
Cite this RFC:TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC4272
Discuss this RFC: Send questions or comments to the mailing listidr@ietf.org
Other actions:Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 4272
Abstract
Border Gateway Protocol 4 (BGP-4), along with a host of otherinfrastructure protocols designed before the Internet environment becameperilous, was originally designed with little consideration forprotection of the information it carries. There are no mechanismsinternal to BGP that protect against attacks that modify,delete, forge, or replay data, any of which has the potential to disruptoverall network routing behavior.
This document discusses some of the security issues with BGProuting data dissemination. This document does not discusssecurity issues with forwarding of packets. This memo provides information for the Internet community.
For the definition ofStatus,seeRFC 2026.
For the definition ofStream, seeRFC 8729.