Service Selection for Mobile IPv6
RFC 5149
| Document | Type |
RFC - Informational
(February 2008; No errata)
Was draft-korhonen-mip6-service (individual in int area)
|
|
|---|---|---|---|
| Last updated | 2015-10-14 | ||
| Stream | IETF | ||
| Formats | plain text pdf html bibtex | ||
| Stream | WG state | (None) | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | RFC 5149 (Informational) | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | Jari Arkko | ||
| Send notices to | mip6-chairs@ietf.org | ||
Network Working Group J. Korhonen
Request for Comments: 5149 U. Nilsson
Category: Informational TeliaSonera
V. Devarapalli
Azaire
February 2008
Service Selection for Mobile IPv6
Status of This Memo
This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. Distribution of this
memo is unlimited.
Abstract
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.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Service Selection Mobility Option . . . . . . . . . . . . . . . 3
4. Processing Considerations . . . . . . . . . . . . . . . . . . . 4
4.1. Mobile Node Considerations . . . . . . . . . . . . . . . . 4
4.2. Home Agent Considerations . . . . . . . . . . . . . . . . . 5
4.3. Correspondent Node Considerations . . . . . . . . . . . . . 5
5. Security Considerations . . . . . . . . . . . . . . . . . . . . 6
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 6
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6
8.1. Normative References . . . . . . . . . . . . . . . . . . . 6
8.2. Informative References . . . . . . . . . . . . . . . . . . 7
Korhonen, et al. Informational [Page 1]
RFC 5149 Service Selection for MIPv6 February 2008
1. Introduction
Mobile IPv6 [2] can identify mobile nodes in various ways, including
home addresses [2], Network Access Identifiers (NAIs) [6][7], and
credentials suitable for the Internet Key Exchange Protocol version 2
(IKEv2) [10]. In some Mobile IPv6 deployments, identifying the
mobile node or the mobility service subscriber via a Proxy Mobile
IPv6 client [5] (hereafter, the mobile node and the Proxy Mobile IPv6
client are used interchangeably) is not enough to distinguish between
multiple services possibly provisioned to the said mobile node and
its mobility service subscription.
The capability to specify different services in addition to the
mobile node identity can be leveraged to provide flexibility for
mobility service providers to provide multiple services within the
same mobility service subscription. For example:
o Provide an enterprise data access for which the mobility service
provider hosts connectivity and mobility services on behalf of the
enterprise.
o Provide access to service domains that are otherwise not
accessible from public networks because of some mobility service
provider's business reasons.
o Provide simultaneous access to different service domains that are
separated based on policies of the mobility service provider.
o Enable easier policy and quality of service assignment for
mobility service providers based on the subscribed services.
o In the absence of a specifically indicated service, the home agent
MUST act as if the default service, plain Internet access, had
been requested. There is no absolute requirement that this
default service be allowed to all subscribers, but it is highly
RECOMMENDED in order to avoid having normal subscribers employ
operator-specific configuration values in order to get basic
service.
This document describes a Service Selection Mobility Option for
Mobile IPv6 that is intended to assist home agents to make specific
service selections for the mobility service subscription during the
binding registration procedure. The service selection may affect
home agent routing decisions, Home Address or Home Network Prefix
Show full document text