RFC 1387: RIP Version 2 Protocol Analysis
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 1721.
Current version: RFC 1721 — RIP Version 2 Protocol Analysis
In plain English — editorial summary, not part of the RFC
As required by Routing Protocol Criteria (RFC 1264), this report documents the key features of the RIP-2 protocol and the current implementation experience. This memo provides information for the Internet community. It does not specify an Internet standard.
Document record
- Document ID
- RFC1387
- Published
- January 1993
- Authors
- G. Malkin
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 3
- Also known as
- —
- Obsoleted by:
- RFC 1721
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 1388RIP Version 2 Carrying Additional InformationObsoleted
January 1993
- RFC 1389RIP Version 2 MIB ExtensionsObsoleted
January 1993
- RFC 1722RIP Version 2 Protocol Applicability StatementCurrent
November 1994
- RFC 1723RIP Version 2 - Carrying Additional InformationObsoleted
November 1994
- RFC 1724RIP Version 2 MIB ExtensionCurrent
November 1994
- RFC 2453RIP Version 2Updated
November 1998
- RFC 1397Default Route Advertisement In BGP2 and BGP3 Version of The Border Gateway ProtocolCurrent
January 1993
- RFC 1364BGP OSPF InteractionObsoleted
September 1992
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?