datatracker.ietf.org
Sign in
Version 5.4.0, 2014-04-22
Report a bug

Mobility API Extension for Distributed Mobility Management
draft-liu-dmm-mobility-api-02

Document type: Active Internet-Draft (individual)
Document stream: No stream defined
Last updated: 2013-11-05
Intended RFC status: Unknown
Other versions: plain text, xml, pdf, html

Stream State:No stream defined
Document shepherd: No shepherd assigned

IESG State: I-D Exists
Responsible AD: (None)
Send notices to: No addresses provided

Distributed Mobility Managment Working Group                      D. Liu
Internet-Draft                                                   H. Deng
Updates: 5014 (if approved)                                 China Mobile
Intended status: Standards Track                              C. Perkins
Expires: May 10, 2014                                          Futurewei
                                                       November 06, 2013

       Mobility API Extension for Distributed Mobility Management
                     draft-liu-dmm-mobility-api-02

Abstract

   In order to provide an appropriate level of mobility support that a
   mobile node may require for proper performance of various
   applications, it is important to enable applications to select
   addresses that will be managed properly by the mobility management
   infrastructure.  Previous documents have enabled address selection on
   the basis of certain characteristics such as randomness, temporary
   usage, scope of validity, and so on.  This document proposes new
   classes of addresses in addition to those already available, to
   enable an application to receive certain kinds of mobility support.

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."

   This Internet-Draft will expire on May 10, 2014.

Copyright Notice

   Copyright (c) 2013 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

Liu, et al.               Expires May 10, 2014                  [Page 1]
Internet-Draft        draft-liu-dmm-mobility-api-02        November 2013

   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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Proposed Extension of RFC 5014  . . . . . . . . . . . . . . .   2
   4.  Usage Example . . . . . . . . . . . . . . . . . . . . . . . .   3
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   4
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   4
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   4
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   An extension to the socket API (see [RFC5014]) has been specified to
   allow an application to identify its preference among multiple source
   addresses.  Furthermore, there are proposals
   ([I-D.draft-korhonen-6man-prfix-properties] and
   [I-D.draft-bhandari-dhc-class-based-prefix-04]) to extend router
   advertisement to carry property and class information for the
   advertised prefixes.  Those proposals enable a mobile node to learn
   the property and class information for the prefix from the router
   advertisement message.  This document proposes an extension to
   [RFC5014] which would add more prefix classes so that an application
   could select prefixes with properties that are important for
   distributed mobility management.

2.  Terminology

   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].

3.  Proposed Extension of RFC 5014

Liu, et al.               Expires May 10, 2014                  [Page 2]

[include full document text]