%% You should probably cite rfc6862 instead of this I-D. @techreport{ietf-karp-threats-reqs-07, number = {draft-ietf-karp-threats-reqs-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-karp-threats-reqs/07/}, author = {Gregory M. Lebovitz and Manav Bhatia and Brian Weis}, title = {{Keying and Authentication for Routing Protocols (KARP) Overview, Threats, and Requirements}}, pagetotal = 26, year = 2012, month = dec, day = 19, abstract = {Different routing protocols employ different mechanisms for securing protocol packets on the wire. While most already have some method for accomplishing cryptographic message authentication, in many cases the existing methods are dated, vulnerable to attack, and employ cryptographic algorithms that have been deprecated. The "Keying and Authentication for Routing Protocols" (KARP) effort aims to overhaul and improve these mechanisms. This document does not contain protocol specifications. Instead, it defines the areas where protocol specification work is needed. This document is a companion document to RFC 6518, "Keying and Authentication for Routing Protocols (KARP) Design Guidelines"; together they form the guidance and instruction KARP design teams will use to review and overhaul routing protocol transport security.}, }