On Demand Mobility Management
draft-ietf-dmm-ondemand-mobility-18

Document Type Active Internet-Draft (dmm WG)
Last updated 2019-08-08 (latest revision 2019-07-31)
Replaces draft-yegin-dmm-ondemand-mobility
Stream IETF
Intended RFC status Informational
Formats plain text xml pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Sri Gundavelli
Shepherd write-up Show (last changed 2018-05-02)
IESG IESG state RFC Ed Queue
Consensus Boilerplate Yes
Telechat date
Responsible AD Suresh Krishnan
Send notices to "Dapeng Liu" <max.ldp@alibaba-inc.com>, Sri Gundavelli <sgundave@cisco.com>
IANA IANA review state Version Changed - Review Needed
IANA action state No IANA Actions
RFC Editor RFC Editor state EDIT
DMM Working Group                                               A. Yegin
Internet-Draft                                                  Actility
Intended status: Informational                                  D. Moses
Expires: January 31, 2020                                          Intel
                                                                 S. Jeon
                                                 Sungkyunkwan University
                                                           July 30, 2019

                     On Demand Mobility Management
                  draft-ietf-dmm-ondemand-mobility-18

Abstract

   Applications differ with respect to whether they need 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, as described in [RFC7333].  This
   document defines a new concep of enabling applications to influence
   the network's mobility services (session continuity and/or IP address
   reachability) on a per-Socket basis, and suggests extensions to the
   networking stack's API to accomodate this concept.

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 https://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 January 31, 2020.

Copyright Notice

   Copyright (c) 2019 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
   (https://trustee.ietf.org/license-info) in effect on the date of

Yegin, et al.           Expires January 31, 2020                [Page 1]
Internet-Draft             On Demand Mobility                  July 2019

   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.  High-level Description  . . . . . . . . . . . . . . . . .   4
     3.2.  Types of IP Addresses . . . . . . . . . . . . . . . . . .   5
     3.3.  Granularity of Selection  . . . . . . . . . . . . . . . .   6
     3.4.  On Demand Nature  . . . . . . . . . . . . . . . . . . . .   6
   4.  Backwards Compatibility Considerations  . . . . . . . . . . .   7
     4.1.  Applications  . . . . . . . . . . . . . . . . . . . . . .   8
     4.2.  IP Stack in the Mobile Host . . . . . . . . . . . . . . .   8
     4.3.  Network Infrastructure  . . . . . . . . . . . . . . . . .   8
     4.4.  Merging this work with RFC5014  . . . . . . . . . . . . .   8
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
   7.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .  10
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  10
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .  10
     9.2.  Informative References  . . . . . . . . . . . . . . . . .  11
   Appendix A.  Conveying the Desired Address Type . . . . . . . . .  11
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  12

1.  Introduction

   In the context of Mobile IP [RFC5563][RFC6275][RFC5213][RFC5944], the
   following two attributes are defined for IP service provided to
   mobile hosts:

   - Session Continuity

   The ability to maintain an ongoing transport interaction by keeping
   the same local end-point IP address throughout the life-time of the
   IP socket despite the mobile host changing its point of attachment
   within the IP network topology.  The IP address of the host may
   change after closing the IP socket and before opening a new one, but
   that does not jeopardize the ability of applications using these IP
   sockets to work flawlessly.  Session continuity is essential for
   mobile hosts to maintain ongoing flows without any interruption.
Show full document text