--- 1/draft-ietf-dmm-ondemand-mobility-06.txt 2016-07-06 04:19:03.048404279 -0700 +++ 2/draft-ietf-dmm-ondemand-mobility-07.txt 2016-07-06 04:19:05.028454049 -0700 @@ -1,23 +1,23 @@ DMM Working Group A. Yegin Internet-Draft Actility Intended status: Informational D. Moses -Expires: January 1, 2017 Intel +Expires: January 7, 2017 Intel K. Kweon J. Lee J. Park Samsung - June 30, 2016 + July 6, 2016 On Demand Mobility Management - draft-ietf-dmm-ondemand-mobility-06 + draft-ietf-dmm-ondemand-mobility-07 Abstract Applications differ with respect to whether they need IP session continuity and/or IP address reachability. The network providing the same type of service to any mobile host and any application running on the host yields inefficiencies. This document describes a solution for taking the application needs into account in selectively providing IP session continuity and IP address reachability on a per- socket basis. @@ -30,21 +30,21 @@ 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 January 1, 2017. + This Internet-Draft will expire on January 7, 2017. Copyright Notice Copyright (c) 2016 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 @@ -58,25 +58,25 @@ 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Notational Conventions . . . . . . . . . . . . . . . . . . . 4 3. Solution . . . . . . . . . . . . . . . . . . . . . . . . . . 4 3.1. Types of IP Addresses . . . . . . . . . . . . . . . . . . 4 3.2. Granularity of Selection . . . . . . . . . . . . . . . . 5 3.3. On Demand Nature . . . . . . . . . . . . . . . . . . . . 5 3.4. Conveying the Selection . . . . . . . . . . . . . . . . . 6 4. Backwards Compatibility Considerations . . . . . . . . . . . 8 4.1. Applications . . . . . . . . . . . . . . . . . . . . . . 8 - 4.2. IP Stack in the Mobile Host . . . . . . . . . . . . . . . 8 + 4.2. IP Stack in the Mobile Host . . . . . . . . . . . . . . . 9 4.3. Network Infrastructure . . . . . . . . . . . . . . . . . 9 5. Summary of New Definitions . . . . . . . . . . . . . . . . . 9 6. Security Considerations . . . . . . . . . . . . . . . . . . . 9 - 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 + 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 10 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 10 9.1. Normative References . . . . . . . . . . . . . . . . . . 10 9.2. Informative References . . . . . . . . . . . . . . . . . 10 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11 1. Introduction In the context of Mobile IP [RFC5563][RFC6275][RFC5213][RFC5944], following two attributes are defined for the IP service provided to @@ -156,37 +156,37 @@ 3. Solution 3.1. Types of IP Addresses Three types of IP addresses are defined with respect to the mobility management. - Fixed IP Address - 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 - 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 - whether it moves from one point-of-attachment to another (with a - different subnet or IP prefix) while it is connected. + A Fixed IP address is an address with a guarantee to be valid for a + very long time, regardless of whether it is being used in any packet + to/from the mobile host, or whether or not the mobile host is + connected to the network, or whether it moves from one point-of- + attachment to another (with a different subnet or IP prefix) while it + is connected. Fixed IP address are required by applications that need both IP session continuity and IP address reachability. - Session-lasting IP Address - 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 - session(s) for which it was requested. It is guaranteed to be valid - even after the mobile host had moved from one point-of-attachment to - another (with a different subnet or IP prefix). + A session-lasting IP address is an address with a guarantee to be + valid through-out the IP session(s) for which it was requested. It + is guaranteed to be valid even after the mobile host had moved from + one point-of-attachment to another (with a different subnet or IP + prefix). Session-lasting IP addresses are required by applications that need IP session continuity but do not need IP address reachability. - Non-persistent IP Address This type of IP address provides neither IP session continuity nor IP address reachability. The IP address is obtained from the serving IP gateway and it is not maintained across gateway changes. In other words, the IP address may be released and replaced by a new IP @@ -201,20 +201,25 @@ Applications with short-lived transient IP sessions can use Session- lasting IP Addresses. For example: Web browsers. Applications with very short IP sessions, such as DNS client and instant messengers, can utilize Non-persistent IP Addresses. Even though they could very well use a Fixed of Session-lasting IP Addresses, the transmission latency would be minimized when a Non- persistent IP Address is used. + The network creates the desired guarantee (Fixed, Session-lasting or + Non-persistent) by either assigning an IP address (as part of a + stateful IP address generation), or by assigning the address prefix + (as part of a stateless address generation process). + 3.2. Granularity of Selection The IP address type selection is made on a per-socket granularity. Different parts of the same application may have different needs. For example, control-plane of an application may require a Fixed IP Address in order to stay reachable, whereas data-plane of the same application may be satisfied with a Session-lasting IP Address. 3.3. On Demand Nature