This Internet-Draft is no longer active. Unofficial copies of old Internet-Drafts can be found here:
http://tools.ietf.org/id/draft-ietf-karp-threats-reqs.
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.
Authors:
Gregory Lebovitz <gregory.ietf@gmail.com>
Manav Bhatia <manav.bhatia@alcatel-lucent.com>
Brian Weis <bew@cisco.com>
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid)
datatracker.ietf.org