RFC 1385: EIP: The Extended Internet Protocol
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 6814.
Current document in this lineage: RFC 6814 — Formally Deprecating Some IPv4 Options
In plain English — editorial summary, not part of the RFC
EIP can substantially reduce the amount of modifications needed to the current Internet systems and greatly ease the difficulties of transition. This is an "idea" paper and discussion is strongly encouraged on Big-Internet@munnari.oz.au. This memo provides information for the Internet community. It does not specify an Internet standard.
Document record
- Document ID
- RFC1385
- Published
- November 1992
- Authors
- Z. Wang
- Status
- HISTORIC
- Stream
- Legacy
- Area
- —
- Pages
- 17
- Also known as
- —
- Obsoleted by:
- RFC 6814
Topics
Standards lineage
This document is one revision in a chain of 5 RFCs, each formally replacing the one before it.
Read the full history of Formally Deprecating Some IPv4 Options →
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 1900Renumbering Needs WorkCurrent
February 1996
- RFC 1955New Scheme for Internet Routing and Addressing (ENCAPS) for IPNGCurrent
June 1996
- RFC 2103Mobility Support for Nimrod : Challenges and Solution ApproachesCurrent
February 1997
- RFC 3102Realm Specific IP: FrameworkCurrent
October 2001
- RFC 3104RSIP Support for End-to-end IPsecCurrent
October 2001
- RFC 3105Finding an RSIP Server with SLPCurrent
October 2001
- RFC 3259A Message Bus for Local CoordinationCurrent
May 2002
- RFC 3531A Flexible Method for Managing the Assignment of Bits of an IPv6 Address BlockCurrent
April 2003
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?