Summary of Cryptographic Authentication Algorithm Implementation Requirements for Routing Protocols
Metadata
- Publisher
- IETF
- Doc Type
- Informational
- Pages
- 11
- Abstract
- The routing protocols Open Shortest Path First version 2 (OSPFv2), Intermediate System to Intermediate System (IS-IS), and Routing Information Protocol (RIP) currently define cleartext and MD5 (Message Digest 5) methods for authenticating protocol packets. Recently, effort has been made to add support for the SHA (Secure Hash Algorithm) family of hash functions for the purpose of authenticating routing protocol packets for RIP, IS-IS, and OSPF. To encourage interoperability between disparate implementations, it is imperative that we specify the expected minimal set of algorithms, thereby ensuring that there is at least one algorithm that all implementations will have in common. Similarly, RIP for IPv6 (RIPng) and OSPFv3 support IPsec algorithms for authenticating their protocol packets. This document examines the current set of available algorithms, with interoperability and effective cryptographic authentication protection being the principal considerations. Cryptographic authentication of these routing protocols requires the availability of the same algorithms in disparate implementations. It is desirable that newly specified algorithms should be implemented and available in routing protocol implementations because they may be promoted to requirements at some future time. This document is not an Internet Standards Track specification; it is published for informational purposes.
- Publication Date
- 2011-02-01
- Status Note
- Informational
- DOI
10.17487/RFC6094- Link
- https://doi.org/10.17487/RFC6094
- Author(s)
- Manav BhatiaVishwas Manral
- Keyword(s)
- IGP Security
Latest version of IETF RFC 6094
Document Versions — IETF RFC 6094
-
▶ IETF RFC 6094 (2011-02-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- ISO.10589.1992 — 1 EXTERNAL
- IETF RFC 1195 [Active*]
- IETF RFC 2080 [Active*]
- IETF RFC 2328 [Active*]
- IETF RFC 2453 [Active*]
- IETF RFC 4822 [Active*]
- IETF RFC 4835 [Superseded*]
- IETF RFC 5304 [Active*]
- IETF RFC 5310 [Active*]
- IETF RFC 5340 [Active*]
- IETF RFC 5709 [Active*]
Bibliographic Reference(s)
- NIST FIPS 180-3 [Withdrawn]
- IETF RFC 1321 [Active*]
- IETF RFC 1388 [Superseded*]
- IETF RFC 1723 [Superseded*]
- IETF RFC 2082 [Superseded*]
- IETF RFC 2404 [Active*]
- IETF RFC 3566 [Active*]
- IETF RFC 4270 [Active*]
- IETF RFC 4302 [Active*]
- IETF RFC 4303 [Active*]
- IETF RFC 4552 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC6094.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 6094, Summary of Cryptographic Authentication Algorithm Implementation Requirements for Routing Protocols. Available at https://doi.org/10.17487/RFC6094
Snippet:
IETF RFC 6094, Summary of Cryptographic Authentication Algorithm Implementation Requirements for Routing Protocols. Available at https://doi.org/10.17487/RFC6094
HTML (ISO 690 compliant)
Preview:
IETF RFC 6094, Summary of Cryptographic Authentication Algorithm Implementation Requirements for Routing Protocols. Available at https://doi.org/10.17487/RFC6094
Snippet:
<span class="citation"><cite>IETF RFC 6094</cite>, Summary of Cryptographic Authentication Algorithm Implementation Requirements for Routing Protocols. Available at <a href="https://doi.org/10.17487/RFC6094" target="_blank" rel="noopener">https://doi.org/10.17487/RFC6094</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 6094, Summary of Cryptographic Authentication Algorithm Implementation Requirements for Routing Protocols
doi: 10.17487/RFC6094
url: https://doi.org/10.17487/RFC6094
doi: 10.17487/RFC6094
url: https://doi.org/10.17487/RFC6094
Snippet:
<li> <cite id="bib-rfc6094">IETF RFC 6094</cite>, Summary of Cryptographic Authentication Algorithm Implementation Requirements for Routing Protocols <span class="doi">10.17487/RFC6094</span> </li>
Referenced By
- IETF RFC 7474 [Active*]