draft-ietf-dmm-ondemand-mobility-12.txt		draft-ietf-dmm-ondemand-mobility-13.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 31, 2018 Intel		Expires: July 28, 2018 Intel
	K. Kweon		K. Kweon
	J. Lee		J. Lee
	J. Park		J. Park
	Samsung		Samsung
	S. Jeon		S. Jeon
	Sungkyunkwan University		Sungkyunkwan University
	July 30, 2017		January 24, 2018
	On Demand Mobility Management		On Demand Mobility Management
	draft-ietf-dmm-ondemand-mobility-12		draft-ietf-dmm-ondemand-mobility-13
	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 by selectively		solution for taking the application needs into account by 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.
	Status of This Memo		Status of This Memo
	This Internet-Draft is submitted in full conformance with the		This Internet-Draft is submitted in full conformance with the
	provisions of BCP 78 and BCP 79.		provisions of BCP 78 and BCP 79.
	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 https://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 31, 2018.		This Internet-Draft will expire on July 28, 2018.
	Copyright Notice		Copyright Notice
	Copyright (c) 2017 IETF Trust and the persons identified as the		Copyright (c) 2018 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		(https://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
	carefully, as they describe your rights and restrictions with respect		carefully, as they describe your rights and restrictions with respect
	to this document. Code Components extracted from this document must		to this document. Code Components extracted from this document must
	include Simplified BSD License text as described in Section 4.e of		include Simplified BSD License text as described in Section 4.e of
	the Trust Legal Provisions and are provided without warranty as		the Trust Legal Provisions and are provided without warranty as
	described in the Simplified BSD License.		described in the Simplified BSD License.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
	skipping to change at page 13, line 48 ¶		skipping to change at page 13, line 48 ¶
	Korhonen, Sri Gundavelli, Dave Dolson and Lorenzo Colitti for their		Korhonen, Sri Gundavelli, Dave Dolson and Lorenzo Colitti for their
	valuable comments and suggestions on this work.		valuable comments and suggestions on this work.
	11. References		11. References
	11.1. Normative References		11.1. Normative References
	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate		[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", BCP 14, RFC 2119,		Requirement Levels", BCP 14, RFC 2119,
	DOI 10.17487/RFC2119, March 1997,		DOI 10.17487/RFC2119, March 1997,
	<http://www.rfc-editor.org/info/rfc2119>.		<https://www.rfc-editor.org/info/rfc2119>.
	[RFC5014] Nordmark, E., Chakrabarti, S., and J. Laganier, "IPv6		[RFC5014] Nordmark, E., Chakrabarti, S., and J. Laganier, "IPv6
	Socket API for Source Address Selection", RFC 5014,		Socket API for Source Address Selection", RFC 5014,
	DOI 10.17487/RFC5014, September 2007,		DOI 10.17487/RFC5014, September 2007,
	<http://www.rfc-editor.org/info/rfc5014>.		<https://www.rfc-editor.org/info/rfc5014>.
	[RFC6724] Thaler, D., Ed., Draves, R., Matsumoto, A., and T. Chown,		[RFC6724] Thaler, D., Ed., Draves, R., Matsumoto, A., and T. Chown,
	"Default Address Selection for Internet Protocol Version 6		"Default Address Selection for Internet Protocol Version 6
	(IPv6)", RFC 6724, DOI 10.17487/RFC6724, September 2012,		(IPv6)", RFC 6724, DOI 10.17487/RFC6724, September 2012,
	<http://www.rfc-editor.org/info/rfc6724>.		<https://www.rfc-editor.org/info/rfc6724>.
	11.2. Informative References		11.2. Informative References
	[I-D.sijeon-dmm-use-cases-api-source]		[I-D.sijeon-dmm-use-cases-api-source]
	Jeon, S., Figueiredo, S., Kim, Y., and J. Kaippallimalil,		Jeon, S., Figueiredo, S., Kim, Y., and J. Kaippallimalil,
	"Use Cases and API Extension for Source IP Address		"Use Cases and API Extension for Source IP Address
	Selection", draft-sijeon-dmm-use-cases-api-source-06 (work		Selection", draft-sijeon-dmm-use-cases-api-source-07 (work
	in progress), March 2017.		in progress), September 2017.
	[RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston,		[RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston,
	A., Peterson, J., Sparks, R., Handley, M., and E.		A., Peterson, J., Sparks, R., Handley, M., and E.
	Schooler, "SIP: Session Initiation Protocol", RFC 3261,		Schooler, "SIP: Session Initiation Protocol", RFC 3261,
	DOI 10.17487/RFC3261, June 2002,		DOI 10.17487/RFC3261, June 2002,
	<http://www.rfc-editor.org/info/rfc3261>.		<https://www.rfc-editor.org/info/rfc3261>.
	[RFC5213] Gundavelli, S., Ed., Leung, K., Devarapalli, V.,		[RFC5213] Gundavelli, S., Ed., Leung, K., Devarapalli, V.,
	Chowdhury, K., and B. Patil, "Proxy Mobile IPv6",		Chowdhury, K., and B. Patil, "Proxy Mobile IPv6",
	RFC 5213, DOI 10.17487/RFC5213, August 2008,		RFC 5213, DOI 10.17487/RFC5213, August 2008,
	<http://www.rfc-editor.org/info/rfc5213>.		<https://www.rfc-editor.org/info/rfc5213>.
	[RFC5563] Leung, K., Dommety, G., Yegani, P., and K. Chowdhury,		[RFC5563] Leung, K., Dommety, G., Yegani, P., and K. Chowdhury,
	"WiMAX Forum / 3GPP2 Proxy Mobile IPv4", RFC 5563,		"WiMAX Forum / 3GPP2 Proxy Mobile IPv4", RFC 5563,
	DOI 10.17487/RFC5563, February 2010,		DOI 10.17487/RFC5563, February 2010,
	<http://www.rfc-editor.org/info/rfc5563>.		<https://www.rfc-editor.org/info/rfc5563>.
	[RFC5944] Perkins, C., Ed., "IP Mobility Support for IPv4, Revised",		[RFC5944] Perkins, C., Ed., "IP Mobility Support for IPv4, Revised",
	RFC 5944, DOI 10.17487/RFC5944, November 2010,		RFC 5944, DOI 10.17487/RFC5944, November 2010,
	<http://www.rfc-editor.org/info/rfc5944>.		<https://www.rfc-editor.org/info/rfc5944>.
	[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, <https://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>.		<https://www.rfc-editor.org/info/rfc6824>.
	[RFC7333] Chan, H., Ed., Liu, D., Seite, P., Yokota, H., and J.		[RFC7333] Chan, H., Ed., Liu, D., Seite, P., Yokota, H., and J.
	Korhonen, "Requirements for Distributed Mobility		Korhonen, "Requirements for Distributed Mobility
	Management", RFC 7333, DOI 10.17487/RFC7333, August 2014,		Management", RFC 7333, DOI 10.17487/RFC7333, August 2014,
	<http://www.rfc-editor.org/info/rfc7333>.		<https://www.rfc-editor.org/info/rfc7333>.
	Authors' Addresses		Authors' Addresses
	Alper Yegin		Alper Yegin
	Actility		Actility
	Istanbul		Istanbul
	Turkey		Turkey
	Email: alper.yegin@actility.com		Email: alper.yegin@actility.com
End of changes. 18 change blocks.
	19 lines changed or deleted		19 lines changed or added
This html diff was produced by rfcdiff 1.46. The latest version is available from http://tools.ietf.org/tools/rfcdiff/