Issues with Existing Cryptographic Protection Methods for Routing Protocols (RFC6039)
Original Publication Date: 2010-Oct-01
Included in the Prior Art Database: 2010-Oct-23
Internet Society Requests For Comment (RFCs)
V. Manral: AUTHOR [+4]
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
Internet Engineering Task Force (IETF) V. Manral Request for Comments: 6039 IP Infusion Category: Informational M. Bhatia ISSN: 2070-1721 Alcatel-Lucent J. Jaeggli Nokia Inc. R. White Cisco Systems October 2010
Issues with Existing Cryptographic Protection Methods for Routing Protocols
Routing protocols have been extended over time to use cryptographic mechanisms to ensure that data received from a neighboring router has not been modified in transit and actually originated from an authorized neighboring router.
The cryptographic mechanisms defined to date and described in this document rely on a digest produced with a hash algorithm applied to the payload encapsulated in the routing protocol packet.
This document outlines some of the limitations of the current mechanism, problems with manual keying of these cryptographic algorithms, and possible vectors for the exploitation of these limitations.
Status of This Memo
This document is not an Internet Standards Track specification; it is published for informational purposes.
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Not all documents approved by the IESG are a candidate for any level of Internet Standard; see Section 2 of RFC 5741.
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc6039.
Manral, et al. Informational [Page 1]
RFC 6039 Routing Protocol Protection Issues October 2010
Copyright (c) 2010 IETF Trust and the persons identified as the document authors. All rights reserved....