RFC 6094: Summary of Cryptographic Authentication Algorithm Implementation Requirements for Routing Protocols
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC6094
- Published
- February 2011
- Authors
- M. Bhatia; V. Manral
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 11
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6092Recommended Simple Security Capabilities in Customer Premises Equipment (CPE) for Providing Residential IPv6 Internet ServiceCurrent
January 2011
- RFC 6087Guidelines for Authors and Reviewers of YANG Data Model DocumentsObsoleted
January 2011
- RFC 6104Rogue IPv6 Router Advertisement Problem StatementCurrent
February 2011
- RFC 6105IPv6 Router Advertisement GuardUpdated
February 2011
- RFC 6110Mapping YANG to Document Schema Definition Languages and Validating NETCONF ContentUpdated
February 2011
- RFC 6076Basic Telephony SIP End-to-End Performance MetricsCurrent
January 2011
- RFC 6049Spatial Composition of MetricsUpdated
January 2011
- RFC 6039Issues with Existing Cryptographic Protection Methods for Routing ProtocolsCurrent
October 2010
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?