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

The information below is for an old version of the document
Document Type Active Internet-Draft (dmm WG)
Last updated 2019-02-21 (latest revision 2019-02-08)
Replaces draft-yegin-dmm-ondemand-mobility
Stream IETF
Intended RFC status Informational
Formats plain text pdf html bibtex
Additional URLs
- Mailing list discussion
Stream WG state Submitted to IESG for Publication (wg milestone: May 2015 - Submit 'Exposing mob... )
Document shepherd Sri Gundavelli
Shepherd write-up Show (last changed 2018-05-02)
IESG IESG state IESG Evaluation::Revised I-D Needed
Consensus Boilerplate Yes
Telechat date
Has 2 DISCUSSes. Has enough positions to pass once DISCUSS positions are resolved.
Responsible AD Suresh Krishnan
Send notices to "Dapeng Liu" <max.ldp@alibaba-inc.com>, Sri Gundavelli <sgundave@cisco.com>
IANA IANA review state IANA OK - No Actions Needed
IANA action state None
DMM Working Group                                               A. Yegin
Internet-Draft                                                  Actility
Intended status: Informational                                  D. Moses
Expires: August 12, 2019                                           Intel
                                                                K. Kweon
                                                                  J. Lee
                                                                 J. Park
                                                                 Samsung
                                                                 S. Jeon
                                                 Sungkyunkwan University
                                                        February 8, 2019

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

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 section 4 of
   [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 August 12, 2019.

Yegin, et al.            Expires August 12, 2019                [Page 1]
Internet-Draft             On Demand Mobility              February 2019

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
   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  . . . . . . . . . . . . . . . . . . . . . . . .   3
   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  . . . . . . . . . . . . . . . .   7
     3.4.  On Demand Nature  . . . . . . . . . . . . . . . . . . . .   7
     3.5.  Conveying the Desired Address Type  . . . . . . . . . . .   8
   4.  Usage example . . . . . . . . . . . . . . . . . . . . . . . .   9
     4.1.  Pseudo-code example . . . . . . . . . . . . . . . . . . .   9
     4.2.  Message Flow example  . . . . . . . . . . . . . . . . . .  11
   5.  Backwards Compatibility Considerations  . . . . . . . . . . .  12
     5.1.  Applications  . . . . . . . . . . . . . . . . . . . . . .  12
     5.2.  IP Stack in the Mobile Host . . . . . . . . . . . . . . .  13
     5.3.  Network Infrastructure  . . . . . . . . . . . . . . . . .  13
     5.4.  Merging this work with RFC5014  . . . . . . . . . . . . .  13
   6.  Summary of New Definitions  . . . . . . . . . . . . . . . . .  14
     6.1.  New APIs  . . . . . . . . . . . . . . . . . . . . . . . .  14
     6.2.  New Flags . . . . . . . . . . . . . . . . . . . . . . . .  14
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  15
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  15
   9.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .  15
   10. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  15
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .  15
     11.1.  Normative References . . . . . . . . . . . . . . . . . .  16
     11.2.  Informative References . . . . . . . . . . . . . . . . .  16
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  17
Show full document text