RFC 6862: Keying and Authentication for Routing Protocols (KARP) Overview, Threats, and Requirements
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC6862
- Published
- March 2013
- Authors
- G. Lebovitz; M. Bhatia; B. Weis
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 26
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6863Analysis of OSPF Security According to the Keying and Authentication for Routing Protocols (KARP) Design GuideCurrent
March 2013
- RFC 6860Hiding Transit-Only Networks in OSPFCurrent
January 2013
- RFC 6870Pseudowire Preferential Forwarding Status BitUpdated
February 2013
- RFC 6850Definitions of Managed Objects for Routing Bridges (RBridges)Current
January 2013
- RFC 6845OSPF Hybrid Broadcast and Point-to-Multipoint Interface TypeCurrent
January 2013
- RFC 6836Locator/ID Separation Protocol Alternative Logical Topology (LISP+ALT)Current
January 2013
- RFC 6835The Locator/ID Separation Protocol Internet Groper (LIG)Current
January 2013
- RFC 6834Locator/ID Separation Protocol (LISP) Map-VersioningObsoleted
January 2013
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?