draft-ietf-dmm-ondemand-mobility-05.txt		draft-ietf-dmm-ondemand-mobility-06.txt
	DMM Working Group A. Yegin		DMM Working Group A. Yegin
	Internet-Draft Actility		Internet-Draft Actility
	Intended status: Standards Track D. Moses		Intended status: Informational D. Moses
	Expires: December 17, 2016 Intel		Expires: January 1, 2017 Intel
	K. Kweon		K. Kweon
	J. Lee		J. Lee
	J. Park		J. Park
	Samsung		Samsung
	June 15, 2016		June 30, 2016
	On Demand Mobility Management		On Demand Mobility Management
	draft-ietf-dmm-ondemand-mobility-05		draft-ietf-dmm-ondemand-mobility-06
	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 December 17, 2016.		This Internet-Draft will expire on January 1, 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 8, line 51 ¶		skipping to change at page 8, line 51 ¶
	API will return an error code and the invoking applications must		API will return an error code and the invoking applications must
	respond with using legacy calls without On-Demand Mobility feature.		respond with using legacy calls without On-Demand Mobility feature.
	4.2. IP Stack in the Mobile Host		4.2. IP Stack in the Mobile Host
	New IP stacks must continue to support all legacy operations. If an		New IP stacks must continue to support all legacy operations. If an
	application does not use On-Demand Mobility feature, the IP stack		application does not use On-Demand Mobility feature, the IP stack
	must respond in a legacy manner.		must respond in a legacy manner.
	If the network infrastructure supports On-Demand Mobility feature,		If the network infrastructure supports On-Demand Mobility feature,
	the IP stack may still request specific types of source IP address		the IP stack should follow the application request: If the
	transparently to legacy applications. This may be useful for		application requests a specific address type, the stack should
	environments in which both legacy and new applications are executed.		forward this request to the network. If the application does not
			request an address type, the IP stack must not request an address
	The definition of what type of addresses to request and how they are		type and leave it to the network's default behavior to choose the
	assigned to legacy applications are outside of the scope of this		type of the allocated IP address. If an IP address was already
	specification.		allocated to the host, the IP stack uses it and may not request a new
			one from the network.
	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. Summary of New Definitions		5. Summary of New Definitions
End of changes. 5 change blocks.
	12 lines changed or deleted		13 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/