draft-ietf-dmm-ondemand-mobility-04.txt   draft-ietf-dmm-ondemand-mobility-05.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: Standards Track D. Moses
Expires: December 16, 2016 Intel Expires: December 17, 2016 Intel
K. Kweon K. Kweon
J. Lee J. Lee
J. Park J. Park
Samsung Samsung
June 14, 2016 June 15, 2016
On Demand Mobility Management On Demand Mobility Management
draft-ietf-dmm-ondemand-mobility-04 draft-ietf-dmm-ondemand-mobility-05
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 16, 2016. This Internet-Draft will expire on December 17, 2016.
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 27 skipping to change at page 2, line 27
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 . . . . . . . . . . . . . . . 8
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. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 9 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 10 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 10
8.1. Normative References . . . . . . . . . . . . . . . . . . 10 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 10
8.2. Informative References . . . . . . . . . . . . . . . . . 10 9.1. Normative 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
the mobile hosts: the mobile hosts:
IP session continuity: The ability to maintain an ongoing IP session IP session continuity: The ability to maintain an ongoing IP session
by keeping the same local end-point IP address throughout the session by keeping the same local end-point IP address throughout the session
skipping to change at page 9, line 43 skipping to change at page 9, line 43
<netinet/in.h> EAI_REQUIREDIPFAILED <netinet/in.h> EAI_REQUIREDIPFAILED
6. Security Considerations 6. Security Considerations
The setting of certain IP address type on a given socket may be The setting of certain IP address type on a given socket may be
restricted to privileged applications. For example, a Fixed IP restricted to privileged applications. For example, a Fixed IP
Address may be provided as a premium service and only certain Address may be provided as a premium service and only certain
applications may be allowed to use them. Setting and enforcement of applications may be allowed to use them. Setting and enforcement of
such privileges are outside the scope of this document. such privileges are outside the scope of this document.
7. Acknowledgements 7. IANA Considerations
This document has no IANA considerations.
8. Acknowledgements
We would like to thank Alexandru Petrescu, John Kaippallimalil, Jouni We would like to thank Alexandru Petrescu, John Kaippallimalil, Jouni
Korhonen, Seil Jeon, and Sri Gundavelli for their valuable comments Korhonen, Seil Jeon, and Sri Gundavelli for their valuable comments
and suggestions on this work. and suggestions on this work.
8. References 9. References
8.1. Normative References 9.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>. <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,
DOI 10.17487/RFC5014, September 2007, DOI 10.17487/RFC5014, September 2007,
<http://www.rfc-editor.org/info/rfc5014>. <http://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>. <http://www.rfc-editor.org/info/rfc6724>.
8.2. Informative References 9.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,
DOI 10.17487/RFC3261, June 2002, DOI 10.17487/RFC3261, June 2002,
 End of changes. 9 change blocks. 
12 lines changed or deleted 17 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/