Service Selection for Mobile IPv6 and Proxy Mobile IPv6
draft-ietf-netext-rfc5149bis-01

The information below is for an old version of the document
Document Type Active Internet-Draft (netext WG)
Last updated 2012-06-12
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state WG Document
Document shepherd None
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network-Based Mobility Extensions                            J. Korhonen
(Netext)                                          Nokia Siemens Networks
Internet-Draft                                                U. Nilsson
Obsoletes: 5149 (if approved)                                TeliaSonera
Updates: 5213 (if approved)                               V. Devarapalli
Intended status: Standards Track                           June 12, 2012
Expires: December 14, 2012

        Service Selection for Mobile IPv6 and Proxy Mobile IPv6
                  draft-ietf-netext-rfc5149bis-01.txt

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 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 and local mobility agents to make a specific
   service selection for the mobility service subscription during the
   binding registration procedure.  This specification updates RFC5213
   and obsoletes RFC5149.

Requirements

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

Korhonen, et al.        Expires December 14, 2012               [Page 1]
Internet-Draft              Service Selection                  June 2012

   This Internet-Draft will expire on December 14, 2012.

Copyright Notice

   Copyright (c) 2012 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.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Korhonen, et al.        Expires December 14, 2012               [Page 2]
Internet-Draft              Service Selection                  June 2012

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
   2.  Service Selection Mobility Option  . . . . . . . . . . . . . .  5
   3.  Processing Considerations  . . . . . . . . . . . . . . . . . .  6
     3.1.  Binding Cache Entry Lookup Considerations  . . . . . . . .  6
     3.2.  Mobile Node Considerations . . . . . . . . . . . . . . . .  7
     3.3.  Home Agent and Local Mobility Agent Considerations . . . .  7
     3.4.  Correspondent Node Considerations  . . . . . . . . . . . .  8
   4.  Configuration Objects  . . . . . . . . . . . . . . . . . . . .  9
   5.  Security Considerations  . . . . . . . . . . . . . . . . . . .  9
   6.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . .  9
   7.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 10
     7.1.  Normative references . . . . . . . . . . . . . . . . . . . 10
     7.2.  Informative references . . . . . . . . . . . . . . . . . . 10
   Appendix A.  Changes from RFC5149  . . . . . . . . . . . . . . . . 11
     A.1.  Service Selection option in a PBA  . . . . . . . . . . . . 11
     A.2.  Service Selection Identifier encoding  . . . . . . . . . . 11
     A.3.  Using Service Selection as a BCE lookup key  . . . . . . . 11
     A.4.  Addition of a new Status Code  . . . . . . . . . . . . . . 11
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 11

Korhonen, et al.        Expires December 14, 2012               [Page 3]
Internet-Draft              Service Selection                  June 2012
Show full document text