Skip to main content

Issues with Existing Cryptographic Protection Methods for Routing Protocols
RFC 6039

Revision differences

Document history

Date By Action
2018-12-20
(System)
Received changes through RFC Editor sync (changed abstract to 'Routing protocols have been extended over time to use cryptographic mechanisms to ensure that data received …
Received changes through RFC Editor sync (changed abstract to '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. This document is not an Internet Standards Track specification; it is published for informational purposes.')
2015-10-14
(System) Notify list changed from opsec-chairs@ietf.org, draft-ietf-opsec-routing-protocols-crypto-issues@ietf.org to (None)
2010-10-25
Cindy Morgan State changed to RFC Published from RFC Ed Queue by Cindy Morgan
2010-10-25
Cindy Morgan [Note]: changed to 'RFC 6039' by Cindy Morgan
2010-10-22
(System) RFC published