Keying and Authentication for Routing Protocols (KARP) Design Guidelines

Metadata

Publisher: IETF
Doc Type: Informational
Pages: 30
Abstract: This document is one of a series concerned with defining a roadmap of protocol specification work for the use of modern cryptographic mechanisms and algorithms for message authentication in routing protocols. In particular, it defines the framework for a key management protocol that may be used to create and manage session keys for message authentication and integrity. This document is not an Internet Standards Track specification; it is published for informational purposes.
Publication Date: 2012-02-01
Status Note: Informational
DOI: 10.17487/RFC6518
Link: https://doi.org/10.17487/RFC6518
Author(s): Gregory M. Lebovitz
Manav Bhatia
Keyword(s): MAC, Hash Security, Authorization, Harden, Infrastructure, Routers, Cryptography, Message, Protocol

Latest version of IETF RFC 6518

Document Versions — IETF RFC 6518

▶ IETF RFC 6518 (2012-02-01)

THIS DOC [ACTIVE] [LATEST VERSION]

Normative Reference(s)

IETF RFC 2119 [Active*]
IETF RFC 4948 [Active*]

Bibliographic Reference(s)

NIST.SP.800-57 — NIST.SP800-57 EXTERNAL
NIST.SP.800-118 — NIST-800-118 EXTERNAL
Lebovitz, G., "The Threat Analysis and Requirements for Cryptographic Authentication of Routing Protocols' Transports", Work in Progress, June 2011. EXTERNAL
Merit Network Inc , "Internet Routing Registry Routing Assets Database", 2006, http://www.irr.net/ . EXTERNAL
Weis, B. and S. Rowles, "GDOI Generic Message Authentication Code Policy", Work in Progress, September 2011. EXTERNAL
Housley, R. and Polk, T., "Database of Long-Lived Symmetric Cryptographic Keys", Work in Progress, October 2011 EXTERNAL
IETF RFC 1195 [Active*]
IETF RFC 2205 [Active*]
IETF RFC 2328 [Active*]
IETF RFC 2453 [Active*]
IETF RFC 2747 [Active*]
IETF RFC 3097 [Active*]
IETF RFC 3209 [Active*]
IETF RFC 3473 [Active*]
IETF RFC 3618 [Active*]
IETF RFC 3766 [Active*]
IETF RFC 3973 [Active*]
IETF RFC 4086 [Active*]
IETF RFC 4107 [Active*]
IETF RFC 4230 [Active*]
IETF RFC 4252 [Active*]
IETF RFC 4253 [Active*]
IETF RFC 4271 [Active*]
IETF RFC 4492 [Superseded*]
IETF RFC 4601 [Superseded*]
IETF RFC 4615 [Active*]
IETF RFC 4726 [Active*]
IETF RFC 5036 [Active*]
IETF RFC 5082 [Active*]
IETF RFC 5151 [Active*]
IETF RFC 5280 [Active, Amended*]
IETF RFC 5440 [Active*]
IETF RFC 5796 [Active*]
IETF RFC 5880 [Active*]
IETF RFC 5925 [Active*]
IETF RFC 5926 [Active*]
IETF RFC 6039 [Active*]
IETF RFC 6407 [Superseded*]

Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC6518.json

Reference Tree

Explore all references and references to this document, as a navigable tree.

Open Reference Tree

Reference this Doc

Plain text (ISO 690 compliant)

Preview:

IETF RFC 6518, Keying and Authentication for Routing Protocols (KARP) Design Guidelines. Available at https://doi.org/10.17487/RFC6518

Snippet:

IETF RFC 6518, Keying and Authentication for Routing Protocols (KARP) Design Guidelines. Available at https://doi.org/10.17487/RFC6518

HTML (ISO 690 compliant)

Preview:

IETF RFC 6518, Keying and Authentication for Routing Protocols (KARP) Design Guidelines. Available at https://doi.org/10.17487/RFC6518

Snippet:

<span class="citation"><cite>IETF RFC 6518</cite>, Keying and Authentication for Routing Protocols (KARP) Design Guidelines. Available at <a href="https://doi.org/10.17487/RFC6518" target="_blank" rel="noopener">https://doi.org/10.17487/RFC6518</a></span>

SMPTE's HTML Pub

Preview:

IETF RFC 6518, Keying and Authentication for Routing Protocols (KARP) Design Guidelines
doi: 10.17487/RFC6518
url: https://doi.org/10.17487/RFC6518

Snippet:

<li>
<cite id="bib-rfc6518">IETF RFC 6518</cite>, Keying and Authentication for Routing Protocols (KARP) Design Guidelines
<span class="doi">10.17487/RFC6518</span>
</li>

Referenced By

IETF RFC 6827 [Active*]
IETF RFC 6830 [Superseded*]
IETF RFC 6862 [Active*]
IETF RFC 6863 [Active*]
IETF RFC 6952 [Active*]