RFC 1688: IPng Mobility Considerations
In plain English — editorial summary, not part of the RFC
This RFC specifies criteria related to mobility for consideration in design and selection of the Next Generation of IP. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
Document record
- Document ID
- RFC1688
- Published
- August 1994
- Authors
- W. Simpson
- Status
- INFORMATIONAL
- Stream
- Legacy
- Area
- —
- Pages
- 9
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1687A Large Corporate User's View of IPngCurrent
August 1994
- RFC 1686IPng Requirements: A Cable Television Industry ViewpointCurrent
August 1994
- RFC 1683Multiprotocol Interoperability In IPngCurrent
August 1994
- RFC 1682IPng BSD Host Implementation AnalysisCurrent
August 1994
- RFC 1681On Many Addresses per HostCurrent
August 1994
- RFC 1680IPng Support for ATM ServicesCurrent
August 1994
- RFC 1679HPN Working Group Input to the IPng Requirements SolicitationCurrent
August 1994
- RFC 1678IPng Requirements of Large Corporate NetworksCurrent
August 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?