A new Request for Comments is now available in online RFC libraries.
RFC 4272
Title: BGP Security Vulnerabilities Analysis
Author(s): S. Murphy
Status: Informational
Date: January 2006
Mailbox: Sandy@tislabs.com
Pages: 22
Characters: 53119
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-idr-bgp-vuln-01.txt
URL: ftp://ftp.rfc-editor.org/in-notes/rfc4272.txt
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 document is a product of the Inter-Domain Routing Working Group
of the IETF.
This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. Distribution of this
memo is unlimited.
This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info@RFC-EDITOR.ORG
Subject: getting rfcs
help: ways_to_get_rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
Authors, for further information.
Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute
...
Below is the data which will enable a MIME compliant Mail Reader
implementation to automatically retrieve the ASCII version
of the RFCs.
- <ftp://ftp.isi.edu/in-notes/rfc4272.txt>
-
_______________________________________________
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce
