RFC 1955: New Scheme for Internet Routing and Addressing (ENCAPS) for IPNG
In plain English — editorial summary, not part of the RFC
This paper proposes a new scheme which I believe is a good medium term solution to the routing and address problems of the internet. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
Document record
- Document ID
- RFC1955
- Published
- June 1996
- Authors
- R. Hinden
- Status
- INFORMATIONAL
- Stream
- Legacy
- Area
- —
- Pages
- 5
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1752The Recommendation for the IP Next Generation ProtocolCurrent
January 1995
- RFC 2103Mobility Support for Nimrod : Challenges and Solution ApproachesCurrent
February 1997
- RFC 6179The Internet Routing Overlay Network (IRON)Current
March 2011
- RFC 1953Ipsilon Flow Management Protocol Specification for IPv4 Version 1.0Current
May 1996
- RFC 1900Renumbering Needs WorkCurrent
February 1996
- RFC 1817CIDR and Classful RoutingCurrent
August 1995
- RFC 1771A Border Gateway Protocol 4 (BGP-4)Obsoleted
March 1995
- RFC 1753IPng Technical Requirements Of the Nimrod Routing and Addressing ArchitectureCurrent
December 1994
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?