RFC 4822: RIPv2 Cryptographic Authentication
In plain English — editorial summary, not part of the RFC
This note describes a revision to the RIPv2 Cryptographic Authentication mechanism originally specified in RFC 2082. This document obsoletes RFC 2082 and updates RFC 2453. This document adds details of how the SHA family of hash algorithms can be used with RIPv2 Cryptographic Authentication, whereas the original document only specified the use of Keyed-MD5. Also, this document clarifies a potential issue with an active attack on this mechanism and adds significant text to the Security Considerations section. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4822
- Published
- February 2007
- Authors
- R. Atkinson; M. Fanto
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 22
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4752The Kerberos V5 ("GSSAPI") Simple Authentication and Security Layer (SASL) MechanismCurrent
November 2006
- RFC 4642Using Transport Layer Security (TLS) with Network News Transfer Protocol (NNTP)Updated
October 2006
- RFC 5091Identity-Based Cryptography Standard (IBCS) #1: Supersingular Curve Implementations of the BF and BB1 CryptosystemsUpdated
December 2007
- RFC 5116An Interface and Algorithms for Authenticated EncryptionCurrent
January 2008
- RFC 4491Using the GOST R 34.10-94, GOST R 34.10-2001, and GOST R 34.11-94 Algorithms with the Internet X.509 Public Key Infrastructure Certificate and CRL ProfileCurrent
May 2006
- RFC 4490Using the GOST 28147-89, GOST R 34.11-94, GOST R 34.10-94, and GOST R 34.10-2001 Algorithms with Cryptographic Message Syntax (CMS)Current
May 2006
- RFC 4422Simple Authentication and Security Layer (SASL)Current
June 2006
- RFC 4253The Secure Shell (SSH) Transport Layer ProtocolUpdated
January 2006
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?