Keying and Authentication for Routing Protocols (KARP) Overview, Threats, and Requirements
Metadata
- Publisher
- IETF
- Doc Type
- Informational
- Pages
- 26
- 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.
- Publication Date
- 2013-03-01
- Status Note
- Informational
- DOI
10.17487/RFC6862- Link
- https://doi.org/10.17487/RFC6862
- Author(s)
- Gregory M. LebovitzManav BhatiaBrian Weis
Latest version of IETF RFC 6862
Document Versions — IETF RFC 6862
-
▶ IETF RFC 6862 (2013-03-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 2119 [Active*]
- IETF RFC 4593 [Active*]
- IETF RFC 4948 [Active*]
Bibliographic Reference(s)
- NIST.SP.800-131A — NIST-SP800-131A EXTERNAL
- McPherson, D. and C. Labovitz, "Worldwide Infrastructure Security Report", October 2008, < http://pages.arbornetworks.com/rs/arbor/images/ ISR2008_EN.pdf >. EXTERNAL
- IETF RFC 1195 [Active*]
- IETF RFC 2328 [Active*]
- IETF RFC 2453 [Active*]
- IETF RFC 3562 [Active*]
- IETF RFC 4271 [Active*]
- IETF RFC 4301 [Active, Amended*]
- IETF RFC 4822 [Active*]
- IETF RFC 4949 [Active*]
- IETF RFC 5036 [Active*]
- IETF RFC 5310 [Active*]
- IETF RFC 5709 [Active*]
- IETF RFC 5880 [Active*]
- IETF RFC 5925 [Active*]
- IETF RFC 6039 [Active*]
- IETF RFC 6518 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC6862.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 6862, Keying and Authentication for Routing Protocols (KARP) Overview, Threats, and Requirements. Available at https://doi.org/10.17487/RFC6862
Snippet:
IETF RFC 6862, Keying and Authentication for Routing Protocols (KARP) Overview, Threats, and Requirements. Available at https://doi.org/10.17487/RFC6862
HTML (ISO 690 compliant)
Preview:
IETF RFC 6862, Keying and Authentication for Routing Protocols (KARP) Overview, Threats, and Requirements. Available at https://doi.org/10.17487/RFC6862
Snippet:
<span class="citation"><cite>IETF RFC 6862</cite>, Keying and Authentication for Routing Protocols (KARP) Overview, Threats, and Requirements. Available at <a href="https://doi.org/10.17487/RFC6862" target="_blank" rel="noopener">https://doi.org/10.17487/RFC6862</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 6862, Keying and Authentication for Routing Protocols (KARP) Overview, Threats, and Requirements
doi: 10.17487/RFC6862
url: https://doi.org/10.17487/RFC6862
doi: 10.17487/RFC6862
url: https://doi.org/10.17487/RFC6862
Snippet:
<li> <cite id="bib-rfc6862">IETF RFC 6862</cite>, Keying and Authentication for Routing Protocols (KARP) Overview, Threats, and Requirements <span class="doi">10.17487/RFC6862</span> </li>
Referenced By
- IETF RFC 6863 [Active*]
- IETF RFC 7474 [Active*]