Internet DRAFT - draft-liu-dmm-mobility-api
draft-liu-dmm-mobility-api
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]
Internet-Draft draft-liu-dmm-mobility-api-02 November 2013
A socket API extension defined in [RFC5014] is used for IPv6 source
address selection. An application can use this API to override the
default source address selection mechanism for IPv6. Currently, the
following types of source address selection preference are defined in
[RFC5014]:
IPV6_PREFER_SRC_HOME /* Prefer Home address as source */
IPV6_PREFER_SRC_COA /* Prefer Care-of address as source */
IPV6_PREFER_SRC_TMP /* Prefer Temporary address as source */
IPV6_PREFER_SRC_PUBLIC /* Prefer Public address as source */
IPV6_PREFER_SRC_CGA /* Prefer CGA address as source */
IPV6_PREFER_SRC_NONCGA /* Prefer a non-CGA address as source */
This document proposes the addition of two new flags:
IPV6_PREFER_SRC_LOCAL_HNP /* Prefer a local home prefix */
IPV6_PREFER_SRC_REMOTE_HNP /* Prefer a remote home prefix */
The local home prefix may be preferred by applications which are
likely to discontinue operations before the device travels to distant
networks. On the other hand, a remote home prefix may be more
suitable for continued operation over wide areas, but at potentially
increased cost for mobiilty management.
4. Usage Example
This section gives usage examples for the new flags API extension.
Relevant distributed mobility management practices are discussed in
[I-D.draft-ietf-dmm-best-practices-gap-analysis-01] and
[I-D.draft-seite-dmm-dma-06]. The concept of dynamic anchoring
concept is introduced, which means that the mobile node can have
multiple mobility anchor points. Then, the mobile node can select a
locally allocated IP address for newly launched applications for
optimized routing. When the application continues communications
while the mobile node moves to a new point of attachment, the mobile
node can nevertheless stilluse the IP address allocated by previous
anchor point for the on going communications. When the application
terminates, the mobile node will release the IP address allocated by
the previous anchor point.
Liu, et al. Expires May 10, 2014 [Page 3]
Internet-Draft draft-liu-dmm-mobility-api-02 November 2013
In the dynamic anchoring scenario, the newly started application
should use an IP address allocated by the local mobility anchor. The
application can use IPV6_PREFER_SRC_LOCAL_HNP flag to select the
local allocated IP address. For more long-lived communications, the
application can use IPV6_PREFER_SRC_REMOTE_HNP flag to select the
home address allocated by the previous mobility anchor to enable
session continuity.
5. IANA Considerations
This document makes no request of IANA.
Note to RFC Editor: this section may be removed on publication as an
RFC.
6. Security Considerations
TBD
7. Acknowledgements
TBD
8. References
8.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC5014] Nordmark, E., Chakrabarti, S., and J. Laganier, "IPv6
Socket API for Source Address Selection", RFC 5014,
September 2007.
8.2. Informative References
[I-D.draft-bhandari-dhc-class-based-prefix-04]
, "DHCPv6 class based prefix ", draft-bhandari-dhc-class-
based-prefix-04 (work in progress), February 2013.
[I-D.draft-ietf-dmm-best-practices-gap-analysis-01]
, "Distributed Mobility Management: Current practices and
gap analysis ", draft-ietf-dmm-best-practices-gap-
analysis-01 (work in progress), June 2013.
[I-D.draft-korhonen-6man-prfix-properties]
, "IPv6 Prefix Properties", draft-korhonen-6man-prfix-
properties (work in progress), February 2013.
Liu, et al. Expires May 10, 2014 [Page 4]
Internet-Draft draft-liu-dmm-mobility-api-02 November 2013
[I-D.draft-seite-dmm-dma-06]
, "Distributed Mobility Anchoring", draft-seite-dmm-dma-06
(work in progress), Nov 2013.
Authors' Addresses
Dapeng Liu
China Mobile
32 Xuanwumen West Street
Beijng, Xicheng District 100053
China
Phone: +86-13911788933
Email: liudapeng@chinamobile.com
Hui Deng
China Mobile
32 Xuanwumen West Street
Beijng, Xicheng District 100053
China
Email: denghui@chinamobile.com
Charles E. Perkins
Futurewei Inc.
2330 Central Expressway
Santa Clara, CA 95050
USA
Phone: +1-408-330-5305
Email: charliep@computer.org
Liu, et al. Expires May 10, 2014 [Page 5]