Service Selection for Mobile IPv4
RFC 5446

 
Document
Type RFC - Informational (February 2009; No errata)
Was draft-korhonen-mip4-service (individual in int area)
Last updated 2013-03-02
Stream IETF
Formats plain text pdf html
Stream
WG state (None)
Consensus Unknown
Document shepherd No shepherd assigned
IESG
IESG state RFC 5446 (Informational)
Telechat date
Responsible AD Jari Arkko
Send notices to ulf.s.nilsson@teliasonera.com, jouni.nospam@gmail.com, draft-korhonen-mip4-service@ietf.org, mip4-chairs@ietf.org

Email authors IPR References Referenced by Nits Search lists

Network Working Group                                        J. Korhonen
Request for Comments: 5446                        Nokia Siemens Networks
Category: Informational                                       U. Nilsson
                                                             TeliaSonera
                                                           February 2009

                   Service Selection for Mobile IPv4

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.

Copyright Notice

   Copyright (c) 2009 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents (http://trustee.ietf.org/
   license-info) in effect on the date of publication of this document.
   Please review these documents carefully, as they describe your rights
   and restrictions with respect to this document.

Abstract

   In some Mobile IPv4 deployments, identifying the mobile node or the
   mobility service subscriber is not enough to distinguish among the
   multiple services possibly provisioned to the mobile node.  The
   capability to specify different services in addition to the mobile
   node's identity can be leveraged to provide flexibility for mobility
   service providers to provide multiple services within a single
   mobility service subscription.  This document describes a Service
   Selection extension for Mobile IPv4 that is intended to assist home
   agents to make specific service selections for their mobility service
   subscriptions during the registration procedure.

Korhonen & Nilsson           Informational                      [Page 1]
RFC 5446              Service Selection for MIPv4          February 2009

Table of Contents

   1. Introduction ....................................................2
   2. Requirements ....................................................3
   3. Service Selection Extension .....................................3
   4. Processing Considerations .......................................5
      4.1. Mobile Node Considerations .................................5
      4.2. Home Agent Considerations ..................................5
      4.3. Foreign Agent Considerations ...............................6
   5. Security Considerations .........................................7
   6. IANA Considerations .............................................7
   7. Acknowledgments .................................................7
   8. References ......................................................8
      8.1. Normative References .......................................8
      8.2. Informative References .....................................8

1.  Introduction

   Mobile IPv4 [RFC3344] can identify mobile nodes in various ways,
   including home addresses [RFC3344] and Network Access Identifiers
   (NAIs) [RFC4282] [RFC2794].  In some Mobile IPv4 deployments,
   identifying the mobile node (MN) or the mobility service subscriber
   via a Proxy Mobile IPv4 client [LEUNG] (hereafter, the mobile node
   and the Proxy Mobile IPv4 client are used interchangeably) is not
   enough to distinguish among the multiple services possibly
   provisioned to the mobile node.

   The capability to specify different services in addition to the
   mobile node's 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
      providers' 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 assignment for mobility service providers
      based on the subscribed services.

Korhonen & Nilsson           Informational                      [Page 2]
RFC 5446              Service Selection for MIPv4          February 2009

   This document describes a Service Selection extension for Mobile IPv4
   that is intended to assist home agents to make specific service
   selections for their mobility service subscriptions during the
   registration procedure.  A Mobile IPv6-equivalent Service Selection
   Mobility Option has been described in [RFC5149].  The service
   selection may affect home agent routing decisions, Home Address
Show full document text