draft-ietf-dmm-ondemand-mobility-00.txt		draft-ietf-dmm-ondemand-mobility-01.txt
	DMM Working Group A. Yegin		DMM Working Group A. Yegin
	Internet-Draft Unaffiliated		Internet-Draft Unaffiliated
	Intended status: Standards Track K. Kweon		Intended status: Standards Track K. Kweon
	Expires: November 7, 2015 J. Lee		Expires: May 7, 2016 J. Lee
	J. Park		J. Park
	Samsung		Samsung
	D. Moses		D. Moses
	Intel		Intel
	May 6, 2015		November 4, 2015
	On Demand Mobility Management		On Demand Mobility Management
	draft-ietf-dmm-ondemand-mobility-00		draft-ietf-dmm-ondemand-mobility-01
	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 7, 2015.		This Internet-Draft will expire on May 7, 2016.
	Copyright Notice		Copyright Notice
	Copyright (c) 2015 IETF Trust and the persons identified as the		Copyright (c) 2015 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 9, line 20		skipping to change at page 9, line 20
	We would like to thank Alexandru Petrescu, Dapeng Liu, John		We would like to thank Alexandru Petrescu, Dapeng Liu, John
	Kaippallimalil, Jouni Korhonen, Seil Jeon, Sri Gundavelli, and		Kaippallimalil, Jouni Korhonen, Seil Jeon, Sri Gundavelli, and
	Xinpeng Wei for their valuable comments and suggestions on this work.		Xinpeng Wei for their valuable comments and suggestions on this work.
	8. References		8. References
	8.1. Normative References		8.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, March 1997.		Requirement Levels", BCP 14, RFC 2119,
			DOI 10.17487/RFC2119, March 1997,
			<http://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,
	September 2007.		DOI 10.17487/RFC5014, September 2007,
			<http://www.rfc-editor.org/info/rfc5014>.
	[RFC6724] Thaler, D., 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, September 2012.		(IPv6)", RFC 6724, DOI 10.17487/RFC6724, September 2012,
			<http://www.rfc-editor.org/info/rfc6724>.
	8.2. Informative References		8.2. Informative References
	[I-D.ietf-dmm-requirements]		[I-D.ietf-dmm-requirements]
	Chan, A., Liu, D., Seite, P., Yokota, H., and J. Korhonen,		Chan, A., Liu, D., Seite, P., Yokota, H., and J. Korhonen,
	"Requirements for Distributed Mobility Management", draft-		"Requirements for Distributed Mobility Management", draft-
	ietf-dmm-requirements-17 (work in progress), June 2014.		ietf-dmm-requirements-17 (work in progress), June 2014.
	[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,
	June 2002.		DOI 10.17487/RFC3261, June 2002,
			<http://www.rfc-editor.org/info/rfc3261>.
	[RFC5213] Gundavelli, S., Leung, K., Devarapalli, V., Chowdhury, K.,		[RFC5213] Gundavelli, S., Ed., Leung, K., Devarapalli, V.,
	and B. Patil, "Proxy Mobile IPv6", RFC 5213, August 2008.		Chowdhury, K., and B. Patil, "Proxy Mobile IPv6",
			RFC 5213, DOI 10.17487/RFC5213, August 2008,
			<http://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,
	February 2010.		DOI 10.17487/RFC5563, February 2010,
			<http://www.rfc-editor.org/info/rfc5563>.
	[RFC5944] Perkins, C., "IP Mobility Support for IPv4, Revised", RFC		[RFC5944] Perkins, C., Ed., "IP Mobility Support for IPv4, Revised",
	5944, November 2010.		RFC 5944, DOI 10.17487/RFC5944, November 2010,
			<http://www.rfc-editor.org/info/rfc5944>.
	[RFC6275] Perkins, C., Johnson, D., and J. Arkko, "Mobility Support		[RFC6275] Perkins, C., Ed., Johnson, D., and J. Arkko, "Mobility
	in IPv6", RFC 6275, July 2011.		Support in IPv6", RFC 6275, DOI 10.17487/RFC6275, July
			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, January 2013.		Addresses", RFC 6824, DOI 10.17487/RFC6824, January 2013,
			<http://www.rfc-editor.org/info/rfc6824>.
	Authors' Addresses		Authors' Addresses
	Alper Yegin		Alper Yegin
	Unaffiliated		Unaffiliated
	Istanbul		Istanbul
	Turkey		Turkey
	Email: alper.yegin@yegin.org		Email: alper.yegin@yegin.org
End of changes. 14 change blocks.
	17 lines changed or deleted		28 lines changed or added
This html diff was produced by rfcdiff 1.42. The latest version is available from http://tools.ietf.org/tools/rfcdiff/