RFC 4283: Mobile Node Identifier Option for Mobile IPv6 (MIPv6)
In plain English — editorial summary, not part of the RFC
Mobile IPv6 (MIPv6) defines a new Mobility header that is used by mobile nodes, correspondent nodes, and home agents in all messaging related to the creation and management of bindings. Mobile IPv6 nodes need the capability to identify themselves using an identity other than the default home IP address. Some examples of identifiers include Network Access Identifier (NAI), Fully Qualified Domain Name (FQDN), International Mobile Station Identifier (IMSI), and Mobile Subscriber Number (MSISDN). This document defines a new mobility option that can be used by Mobile IPv6 entities to identify themselves in messages containing a mobility header. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4283
- Published
- December 2005
- Authors
- A. Patel; K. Leung; M. Khalil; H. Akhtar; K. Chowdhury
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 8
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3846Mobile IPv4 Extension for Carrying Network Access IdentifiersCurrent
June 2004
- RFC 4877Mobile IPv6 Operation with IKEv2 and the Revised IPsec ArchitectureCurrent
April 2007
- RFC 5094Mobile IPv6 Vendor Specific OptionCurrent
December 2007
- RFC 5096Mobile IPv6 Experimental MessagesCurrent
December 2007
- RFC 4285Authentication Protocol for Mobile IPv6Current
January 2006
- RFC 4280Dynamic Host Configuration Protocol (DHCP) Options for Broadcast and Multicast Control ServersCurrent
December 2005
- RFC 4286Multicast Router DiscoveryCurrent
December 2005
- RFC 4291IP Version 6 Addressing ArchitectureUpdated
February 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?