On Demand Mobility Management
draft-ietf-dmm-ondemand-mobility-00
DMM Working Group A. Yegin
Internet-Draft Unaffiliated
Intended status: Standards Track K. Kweon
Expires: November 7, 2015 J. Lee
J. Park
Samsung
D. Moses
Intel
May 6, 2015
On Demand Mobility Management
draft-ietf-dmm-ondemand-mobility-00
Abstract
Applications differ with respect to whether they need IP session
continuity and/or IP address reachability. The network providing the
same type of service to any mobile host and any application running
on the host yields inefficiencies. This document describes a
solution for taking the application needs into account in selectively
providing IP session continuity and IP address reachability on a per-
socket basis.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on November 7, 2015.
Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
Yegin, et al. Expires November 7, 2015 [Page 1]
Internet-Draft On Demand Mobility May 2015
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Notational Conventions . . . . . . . . . . . . . . . . . . . 4
3. Solution . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3.1. Types of IP Addresses . . . . . . . . . . . . . . . . . . 4
3.2. Granularity of Selection . . . . . . . . . . . . . . . . 5
3.3. On Demand Nature . . . . . . . . . . . . . . . . . . . . 5
3.4. Conveying the Selection . . . . . . . . . . . . . . . . . 6
4. Backwards Compatibility Considerations . . . . . . . . . . . 7
4.1. Applications . . . . . . . . . . . . . . . . . . . . . . 8
4.2. IP Stack in the Mobile Host . . . . . . . . . . . . . . . 8
4.3. Network Infrastructure . . . . . . . . . . . . . . . . . 8
5. Security Considerations . . . . . . . . . . . . . . . . . . . 8
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 9
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 9
8.1. Normative References . . . . . . . . . . . . . . . . . . 9
8.2. Informative References . . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10
1. Introduction
In the context of Mobile IP [RFC5563][RFC6275][RFC5213][RFC5944],
following two attributes are defined for the IP service provided to
the mobile hosts:
IP session continuity: The ability to maintain an ongoing IP session
by keeping the same local end-point IP address throughout the session
despite the mobile host chaging its point of attachment within the IP
network topology. The IP address of the host may change between two
independent IP sessions, but that does not jeopardize the IP session
continuity. IP session continuity is essential for mobile hosts to
maintain ongoing flows without any interruption.
IP address reachability: The ability to maintain the same IP address
for an extended period of time. The IP address stays the same across
independent IP sessions, and even in the absence of any IP session.
Show full document text