RFC 4064: Experimental Message, Extensions, and Error Codes for Mobile IPv4
In plain English — editorial summary, not part of the RFC
Mobile IPv4 message types range from 0 to 255. This document reserves a message type for use by an individual, company, or organization for experimental purposes, to evaluate enhancements to Mobile IPv4 messages before a formal standards proposal is issued. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4064
- Published
- May 2005
- Authors
- A. Patel; K. Leung
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 11
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4076Renumbering Requirements for Stateless Dynamic Host Configuration Protocol for IPv6 (DHCPv6)Current
May 2005
- RFC 4087IP Tunnel MIBCurrent
June 2005
- RFC 4113Management Information Base for the User Datagram Protocol (UDP)Current
June 2005
- RFC 4193Unique Local IPv6 Unicast AddressesCurrent
October 2005
- RFC 4242Information Refresh Time Option for Dynamic Host Configuration Protocol for IPv6 (DHCPv6)Obsoleted
November 2005
- RFC 3879Deprecating Site Local AddressesCurrent
September 2004
- RFC 3846Mobile IPv4 Extension for Carrying Network Access IdentifiersCurrent
June 2004
- RFC 4292IP Forwarding Table MIBCurrent
April 2006
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?