Search RFCs

RFC Editor

File formats:

Status:

INFORMATIONAL

Authors:

G. Lebovitz
M. Bhatia
B. Weis

Stream:

IETF

Source:

karp (rtg)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC6862

Discuss this RFC: Send questions or comments to the mailing listkarp@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 6862

Abstract

Different routing protocols employ different mechanisms for securingprotocol packets on the wire. While most already have some methodfor accomplishing cryptographic message authentication, in many casesthe existing methods are dated, vulnerable to attack, and employcryptographic algorithms that have been deprecated. The "Keying and Authentication for Routing Protocols" (KARP) effort aims to overhauland improve these mechanisms. This document does not containprotocol specifications. Instead, it defines the areas whereprotocol specification work is needed. This document is a companiondocument to RFC 6518, "Keying and Authentication for RoutingProtocols (KARP) Design Guidelines"; together they form the guidanceand instruction KARP design teams will use to review and overhaulrouting protocol transport security.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.