RFC 5149: Service Selection for Mobile IPv6
In plain English — editorial summary, not part of the RFC
In some Mobile IPv6 deployments, identifying the mobile node or the mobility service subscriber is not enough to distinguish between multiple services possibly provisioned to the said mobile node and its mobility service subscription. A capability to specify different services in addition to the mobile node identity can be leveraged to provide flexibility for mobility service providers on provisioning multiple services to one mobility service subscription. This document describes a Service Selection Mobility Option for both conventional Mobile IPv6 and Proxy Mobile IPv6 that is intended to assist home agents to make a specific service selection for the mobility service subscription during the binding registration procedure. This memo provides information for the Internet community.
Document record
- Document ID
- RFC5149
- Published
- February 2008
- Authors
- J. Korhonen; U. Nilsson; V. Devarapalli
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- —
- Pages
- 9
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6496Secure Proxy ND Support for SEcure Neighbor Discovery (SEND)Current
February 2012
- RFC 5096Mobile IPv6 Experimental MessagesCurrent
December 2007
- RFC 5094Mobile IPv6 Vendor Specific OptionCurrent
December 2007
- RFC 5268Mobile IPv6 Fast HandoversObsoleted
June 2008
- RFC 4977Problem Statement: Dual Stack MobilityCurrent
August 2007
- 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 4295Mobile IPv6 Management Information BaseCurrent
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?