RFC 1621: Pip Near-term Architecture
In plain English — editorial summary, not part of the RFC
The purpose of this RFC and the companion RFC "Pip Header Processing" are to record the ideas (good and bad) of Pip. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
Document record
- Document ID
- RFC1621
- Published
- May 1994
- Authors
- P. Francis
- Status
- HISTORIC
- Stream
- IETF
- Area
- int
- Pages
- 51
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1622Pip Header ProcessingCurrent
May 1994
- RFC 1752The Recommendation for the IP Next Generation ProtocolCurrent
January 1995
- RFC 1475TP/IX: The Next InternetObsoleted
June 1993
- RFC 1883Internet Protocol, Version 6 (IPv6) SpecificationObsoleted
December 1995
- RFC 1884IP Version 6 Addressing ArchitectureObsoleted
December 1995
- RFC 1885Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6)Obsoleted
December 1995
- RFC 1886DNS Extensions to support IP version 6Obsoleted
December 1995
- RFC 1887An Architecture for IPv6 Unicast Address AllocationCurrent
December 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?