draft-ietf-dmm-ondemand-mobility-03.txt   draft-ietf-dmm-ondemand-mobility-04.txt 
DMM Working Group A. Yegin DMM Working Group A. Yegin
Internet-Draft Unaffiliated Internet-Draft Actility
Intended status: Standards Track K. Kweon Intended status: Standards Track D. Moses
Expires: November 4, 2016 J. Lee Expires: December 16, 2016 Intel
K. Kweon
J. Lee
J. Park J. Park
Samsung Samsung
D. Moses June 14, 2016
Intel
May 3, 2016
On Demand Mobility Management On Demand Mobility Management
draft-ietf-dmm-ondemand-mobility-03 draft-ietf-dmm-ondemand-mobility-04
Abstract Abstract
Applications differ with respect to whether they need IP session Applications differ with respect to whether they need IP session
continuity and/or IP address reachability. The network providing the continuity and/or IP address reachability. The network providing the
same type of service to any mobile host and any application running same type of service to any mobile host and any application running
on the host yields inefficiencies. This document describes a on the host yields inefficiencies. This document describes a
solution for taking the application needs into account in selectively solution for taking the application needs into account in selectively
providing IP session continuity and IP address reachability on a per- providing IP session continuity and IP address reachability on a per-
socket basis. socket basis.
skipping to change at page 1, line 41 skipping to change at page 1, line 41
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on November 4, 2016. This Internet-Draft will expire on December 16, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 25 skipping to change at page 2, line 25
2. Notational Conventions . . . . . . . . . . . . . . . . . . . 4 2. Notational Conventions . . . . . . . . . . . . . . . . . . . 4
3. Solution . . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Solution . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3.1. Types of IP Addresses . . . . . . . . . . . . . . . . . . 4 3.1. Types of IP Addresses . . . . . . . . . . . . . . . . . . 4
3.2. Granularity of Selection . . . . . . . . . . . . . . . . 5 3.2. Granularity of Selection . . . . . . . . . . . . . . . . 5
3.3. On Demand Nature . . . . . . . . . . . . . . . . . . . . 5 3.3. On Demand Nature . . . . . . . . . . . . . . . . . . . . 5
3.4. Conveying the Selection . . . . . . . . . . . . . . . . . 6 3.4. Conveying the Selection . . . . . . . . . . . . . . . . . 6
4. Backwards Compatibility Considerations . . . . . . . . . . . 8 4. Backwards Compatibility Considerations . . . . . . . . . . . 8
4.1. Applications . . . . . . . . . . . . . . . . . . . . . . 8 4.1. Applications . . . . . . . . . . . . . . . . . . . . . . 8
4.2. IP Stack in the Mobile Host . . . . . . . . . . . . . . . 8 4.2. IP Stack in the Mobile Host . . . . . . . . . . . . . . . 8
4.3. Network Infrastructure . . . . . . . . . . . . . . . . . 9 4.3. Network Infrastructure . . . . . . . . . . . . . . . . . 9
5. Security Considerations . . . . . . . . . . . . . . . . . . . 9 5. Summary of New Definitions . . . . . . . . . . . . . . . . . 9
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 6. Security Considerations . . . . . . . . . . . . . . . . . . . 9
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 9 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 9
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 9 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 10
8.1. Normative References . . . . . . . . . . . . . . . . . . 9 8.1. Normative References . . . . . . . . . . . . . . . . . . 10
8.2. Informative References . . . . . . . . . . . . . . . . . 10 8.2. Informative References . . . . . . . . . . . . . . . . . 10
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11
1. Introduction 1. Introduction
In the context of Mobile IP [RFC5563][RFC6275][RFC5213][RFC5944], In the context of Mobile IP [RFC5563][RFC6275][RFC5213][RFC5944],
following two attributes are defined for the IP service provided to following two attributes are defined for the IP service provided to
the mobile hosts: the mobile hosts:
IP session continuity: The ability to maintain an ongoing IP session IP session continuity: The ability to maintain an ongoing IP session
by keeping the same local end-point IP address throughout the session by keeping the same local end-point IP address throughout the session
despite the mobile host chaging its point of attachment within the IP despite the mobile host chaging its point of attachment within the IP
skipping to change at page 4, line 28 skipping to change at page 4, line 28
Three types of IP addresses are defined with respect to the mobility Three types of IP addresses are defined with respect to the mobility
management. management.
- Fixed IP Address - Fixed IP Address
A Fixed IP address is an address assigned to the mobile host by the A Fixed IP address is an address assigned to the mobile host by the
network with a guarantee to be valid for a very long time, regardless network with a guarantee to be valid for a very long time, regardless
of whether it is being used in any packets to/from the mobile host, of whether it is being used in any packets to/from the mobile host,
or whether or not the mobile host is connected to the network, or or whether or not the mobile host is connected to the network, or
whether it moves from one LAN to another (with a different IP prefix) whether it moves from one point-of-attachment to another (with a
while it is connected. different subnet or IP prefix) while it is connected.
Fixed IP address are required by applications that need both IP Fixed IP address are required by applications that need both IP
session continuity and IP address reachability. session continuity and IP address reachability.
- Session-lasting IP Address - Session-lasting IP Address
A session-lasting IP address is an address assigned to the mobile A session-lasting IP address is an address assigned to the mobile
host by the network with a guarantee to be valid through-out the IP host by the network with a guarantee to be valid through-out the IP
session(s) for which it was requested. It is guaranteed to be valid session(s) for which it was requested. It is guaranteed to be valid
even after the mobile host had moved from one LAN to another (with a even after the mobile host had moved from one point-of-attachment to
different IP prefix). another (with a different subnet or IP prefix).
Session-lasting IP addresses are required by applications that need Session-lasting IP addresses are required by applications that need
IP session continuity but do not need IP address reachability. IP session continuity but do not need IP address reachability.
- Non-persistent IP Address - Non-persistent IP Address
This type of IP address provides neither IP session continuity nor IP This type of IP address provides neither IP session continuity nor IP
address reachability. The IP address is obtained from the serving IP address reachability. The IP address is obtained from the serving IP
gateway and it is not maintained across gateway changes. In other gateway and it is not maintained across gateway changes. In other
words, the IP address may be released and replaced by a new IP words, the IP address may be released and replaced by a new IP
skipping to change at page 7, line 36 skipping to change at page 7, line 36
- The Home vs. Care-of Address distinction is not sufficient to - The Home vs. Care-of Address distinction is not sufficient to
capture the three different types of IP addresses described in capture the three different types of IP addresses described in
Section 2.1. Section 2.1.
The following new flags are defined in this document and they shall The following new flags are defined in this document and they shall
be used with Socket API in compliance with the [RFC5014]: be used with Socket API in compliance with the [RFC5014]:
IPV6_REQUIRE_FIXED_IP /* Require a Fixed IP address as source */ IPV6_REQUIRE_FIXED_IP /* Require a Fixed IP address as source */
IPV6_REQUIRE_Session-lasting_IP /* Require a Session-lasting IP IPV6_REQUIRE_SESSION_LASTING_IP /* Require a Session-lasting IP
address as source */ address as source */
IPV6_REQUIRE_Non-persistent_IP /* Require a Non-persistent IP address IPV6_REQUIRE_NON-PERSISTENT_IP /* Require a Non-persistent IP address
as source */ as source */
Only one of these flags may be set on the same socket. If an Only one of these flags may be set on the same socket. If an
application attempts to set more than one flag, the most recent application attempts to set more than one flag, the most recent
setting will be the one in effect. setting will be the one in effect.
When any of these new flags is used, then the IPV6_PREFER_SRC_HOME When any of these new flags is used, then the IPV6_PREFER_SRC_HOME
and IPV6_PREFER_SRC_COA flags, if used, shall be ignored. and IPV6_PREFER_SRC_COA flags, if used, shall be ignored.
These new flags are used with setsockopt()/getsockopt(), These new flags are used with setsockopt()/getsockopt(),
skipping to change at page 9, line 18 skipping to change at page 9, line 18
assigned to legacy applications are outside of the scope of this assigned to legacy applications are outside of the scope of this
specification. specification.
4.3. Network Infrastructure 4.3. Network Infrastructure
The network infrastructure may or may not support the On-Demand The network infrastructure may or may not support the On-Demand
Mobility feature. How the IP stack on the host and the network Mobility feature. How the IP stack on the host and the network
infrastructure behave in case of a compatibility issue is outside the infrastructure behave in case of a compatibility issue is outside the
scope of this API specification. scope of this API specification.
5. Security Considerations 5. Summary of New Definitions
The following list summarizes the new constants definitions discussed
in this memo:
<netdb.h> IPV6_REQUIRE_FIXED_IP
<netdb.h> IPV6_REQUIRE_SESSION_LASTING_IP
<netdb.h> IPV6_REQUIRE_NON_PERSISTENT_IP
<netdb.h> EAI_REQUIREDIPNOTSUPPORTED
<netdb.h> EAI_REQUIREDIPFAILED
<netinet/in.h> IPV6_REQUIRE_FIXED_IP
<netinet/in.h> IPV6_REQUIRE_SESSION_LASTING_IP
<netinet/in.h> IPV6_REQUIRE_NON_PERSISTENT_IP
<netinet/in.h> EAI_REQUIREDIPNOTSUPPORTED
<netinet/in.h> EAI_REQUIREDIPFAILED
6. Security Considerations
The setting of certain IP address type on a given socket may be The setting of certain IP address type on a given socket may be
restricted to privileged applications. For example, a Fixed IP restricted to privileged applications. For example, a Fixed IP
Address may be provided as a premium service and only certain Address may be provided as a premium service and only certain
applications may be allowed to use them. Setting and enforcement of applications may be allowed to use them. Setting and enforcement of
such privileges are outside the scope of this document. such privileges are outside the scope of this document.
6. IANA Considerations
TBD
7. Acknowledgements 7. Acknowledgements
We would like to thank Alexandru Petrescu, John Kaippallimalil, Jouni We would like to thank Alexandru Petrescu, John Kaippallimalil, Jouni
Korhonen, Seil Jeon, and Sri Gundavelli for their valuable comments Korhonen, Seil Jeon, and Sri Gundavelli for their valuable comments
and suggestions on this work. and suggestions on this work.
8. References 8. References
8.1. Normative References 8.1. Normative References
skipping to change at page 11, line 4 skipping to change at page 11, line 15
[RFC6275] Perkins, C., Ed., Johnson, D., and J. Arkko, "Mobility [RFC6275] Perkins, C., Ed., Johnson, D., and J. Arkko, "Mobility
Support in IPv6", RFC 6275, DOI 10.17487/RFC6275, July Support in IPv6", RFC 6275, DOI 10.17487/RFC6275, July
2011, <http://www.rfc-editor.org/info/rfc6275>. 2011, <http://www.rfc-editor.org/info/rfc6275>.
[RFC6824] Ford, A., Raiciu, C., Handley, M., and O. Bonaventure, [RFC6824] Ford, A., Raiciu, C., Handley, M., and O. Bonaventure,
"TCP Extensions for Multipath Operation with Multiple "TCP Extensions for Multipath Operation with Multiple
Addresses", RFC 6824, DOI 10.17487/RFC6824, January 2013, Addresses", RFC 6824, DOI 10.17487/RFC6824, January 2013,
<http://www.rfc-editor.org/info/rfc6824>. <http://www.rfc-editor.org/info/rfc6824>.
Authors' Addresses Authors' Addresses
Alper Yegin Alper Yegin
Unaffiliated Actility
Istanbul Istanbul
Turkey Turkey
Email: alper.yegin@yegin.org Email: alper.yegin@actility.com
Danny Moses
Intel Corporation
Petah Tikva
Israel
Email: danny.moses@intel.com
Kisuk Kweon Kisuk Kweon
Samsung Samsung
Suwon Suwon
South Korea South Korea
Email: kisuk.kweon@samsung.com Email: kisuk.kweon@samsung.com
Jinsung Lee Jinsung Lee
Samsung Samsung
skipping to change at page 11, line 24 skipping to change at page 12, line 4
South Korea South Korea
Email: kisuk.kweon@samsung.com Email: kisuk.kweon@samsung.com
Jinsung Lee Jinsung Lee
Samsung Samsung
Suwon Suwon
South Korea South Korea
Email: js81.lee@samsung.com Email: js81.lee@samsung.com
Jungshin Park Jungshin Park
Samsung Samsung
Suwon Suwon
South Korea South Korea
Email: shin02.park@samsung.com Email: shin02.park@samsung.com
Danny Moses
Intel Corporation
Petah Tikva
Israel
Email: danny.moses@intel.com
 End of changes. 18 change blocks. 
27 lines changed or deleted 47 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/