%% You should probably cite rfc6039 instead of this I-D. @techreport{ietf-opsec-routing-protocols-crypto-issues-07, number = {draft-ietf-opsec-routing-protocols-crypto-issues-07}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-ietf-opsec-routing-protocols-crypto-issues/07/}, author = {Manav Bhatia and Vishwas Manral and Russ White and Joel Jaeggli}, title = {{Issues with Existing Cryptographic Protection Methods for Routing Protocols}}, pagetotal = 21, year = 2010, month = aug, day = 31, abstract = {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.}, }