RFC 2082: RIP-2 MD5 Authentication
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 4822.
Current version: RFC 4822 — RIPv2 Cryptographic Authentication
In plain English — editorial summary, not part of the RFC
Growth in the Internet has made us aware of the need for improved authentication of routing information. RIP-2 provides for unauthenticated service (as in classical RIP), or password authentication. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2082
- Published
- January 1997
- Authors
- F. Baker; R. Atkinson
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 12
- Also known as
- —
- Obsoleted by:
- RFC 4822
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2081RIPng Protocol Applicability StatementCurrent
January 1997
- RFC 2080RIPng for IPv6Current
January 1997
- RFC 1923RIPv1 Applicability Statement for Historic StatusCurrent
March 1996
- RFC 2096IP Forwarding Table MIBObsoleted
January 1997
- RFC 2103Mobility Support for Nimrod : Challenges and Solution ApproachesCurrent
February 1997
- RFC 1930Guidelines for creation, selection, and registration of an Autonomous System (AS)Updated
March 1996
- RFC 2236Internet Group Management Protocol, Version 2Updated
November 1997
- RFC 1863A BGP/IDRP Route Server alternative to a full mesh routingObsoleted
October 1995
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?