draft-ietf-dmm-ondemand-mobility-06.txt   draft-ietf-dmm-ondemand-mobility-07.txt 
DMM Working Group A. Yegin DMM Working Group A. Yegin
Internet-Draft Actility Internet-Draft Actility
Intended status: Informational D. Moses Intended status: Informational D. Moses
Expires: January 1, 2017 Intel Expires: January 7, 2017 Intel
K. Kweon K. Kweon
J. Lee J. Lee
J. Park J. Park
Samsung Samsung
June 30, 2016 July 6, 2016
On Demand Mobility Management On Demand Mobility Management
draft-ietf-dmm-ondemand-mobility-06 draft-ietf-dmm-ondemand-mobility-07
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 January 1, 2017. This Internet-Draft will expire on January 7, 2017.
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 23 skipping to change at page 2, line 23
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
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 . . . . . . . . . . . . . . . 9
4.3. Network Infrastructure . . . . . . . . . . . . . . . . . 9 4.3. Network Infrastructure . . . . . . . . . . . . . . . . . 9
5. Summary of New Definitions . . . . . . . . . . . . . . . . . 9 5. Summary of New Definitions . . . . . . . . . . . . . . . . . 9
6. Security Considerations . . . . . . . . . . . . . . . . . . . 9 6. Security Considerations . . . . . . . . . . . . . . . . . . . 9
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 10 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 10
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 10 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 10
9.1. Normative References . . . . . . . . . . . . . . . . . . 10 9.1. Normative References . . . . . . . . . . . . . . . . . . 10
9.2. Informative References . . . . . . . . . . . . . . . . . 10 9.2. Informative References . . . . . . . . . . . . . . . . . 10
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11 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
skipping to change at page 4, line 25 skipping to change at page 4, line 25
3. Solution 3. Solution
3.1. Types of IP Addresses 3.1. Types of IP Addresses
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 with a guarantee to be valid for a
network with a guarantee to be valid for a very long time, regardless very long time, regardless of whether it is being used in any packet
of whether it is being used in any packets to/from the mobile host, to/from the mobile host, or whether or not the mobile host is
or whether or not the mobile host is connected to the network, or connected to the network, or whether it moves from one point-of-
whether it moves from one point-of-attachment to another (with a attachment to another (with a different subnet or IP prefix) while it
different subnet or IP prefix) while it is connected. 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 with a guarantee to be
host by the network with a guarantee to be valid through-out the IP valid through-out the IP session(s) for which it was requested. It
session(s) for which it was requested. It is guaranteed to be valid is guaranteed to be valid even after the mobile host had moved from
even after the mobile host had moved from one point-of-attachment to one point-of-attachment to another (with a different subnet or IP
another (with a different subnet or IP prefix). 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 5, line 22 skipping to change at page 5, line 22
Applications with short-lived transient IP sessions can use Session- Applications with short-lived transient IP sessions can use Session-
lasting IP Addresses. For example: Web browsers. lasting IP Addresses. For example: Web browsers.
Applications with very short IP sessions, such as DNS client and Applications with very short IP sessions, such as DNS client and
instant messengers, can utilize Non-persistent IP Addresses. Even instant messengers, can utilize Non-persistent IP Addresses. Even
though they could very well use a Fixed of Session-lasting IP though they could very well use a Fixed of Session-lasting IP
Addresses, the transmission latency would be minimized when a Non- Addresses, the transmission latency would be minimized when a Non-
persistent IP Address is used. 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 3.2. Granularity of Selection
The IP address type selection is made on a per-socket granularity. The IP address type selection is made on a per-socket granularity.
Different parts of the same application may have different needs. Different parts of the same application may have different needs.
For example, control-plane of an application may require a Fixed IP For example, control-plane of an application may require a Fixed IP
Address in order to stay reachable, whereas data-plane of the same Address in order to stay reachable, whereas data-plane of the same
application may be satisfied with a Session-lasting IP Address. application may be satisfied with a Session-lasting IP Address.
3.3. On Demand Nature 3.3. On Demand Nature
 End of changes. 9 change blocks. 
17 lines changed or deleted 22 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/