RFC 5094: Mobile IPv6 Vendor Specific Option
In plain English — editorial summary, not part of the RFC
There is a need for vendor-specific extensions to Mobility Header messages so that Mobile IPv6 vendors are able to extend the protocol for research or deployment purposes. This document defines a new vendor-specific mobility option. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5094
- Published
- December 2007
- Authors
- V. Devarapalli; A. Patel; K. Leung
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 7
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5096Mobile IPv6 Experimental MessagesCurrent
December 2007
- RFC 4877Mobile IPv6 Operation with IKEv2 and the Revised IPsec ArchitectureCurrent
April 2007
- RFC 5026Mobile IPv6 Bootstrapping in Split ScenarioUpdated
October 2007
- RFC 4977Problem Statement: Dual Stack MobilityCurrent
August 2007
- RFC 5268Mobile IPv6 Fast HandoversObsoleted
June 2008
- RFC 5555Mobile IPv6 Support for Dual Stack Hosts and RoutersUpdated
June 2009
- RFC 5637Authentication, Authorization, and Accounting (AAA) Goals for Mobile IPv6Current
September 2009
- RFC 5846Binding Revocation for IPv6 MobilityCurrent
June 2010
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?