--- 1/draft-ietf-dmm-ondemand-mobility-05.txt	2016-06-30 02:15:52.867276669 -0700
+++ 2/draft-ietf-dmm-ondemand-mobility-06.txt	2016-06-30 02:15:52.891277272 -0700
@@ -1,23 +1,23 @@
 
 DMM Working Group                                               A. Yegin
 Internet-Draft                                                  Actility
-Intended status: Standards Track                                D. Moses
-Expires: December 17, 2016                                         Intel
+Intended status: Informational                                  D. Moses
+Expires: January 1, 2017                                           Intel
                                                                 K. Kweon
                                                                   J. Lee
                                                                  J. Park
                                                                  Samsung
-                                                           June 15, 2016
+                                                           June 30, 2016
 
                      On Demand Mobility Management
-                  draft-ietf-dmm-ondemand-mobility-05
+                  draft-ietf-dmm-ondemand-mobility-06
 
 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.
@@ -30,21 +30,21 @@
    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 December 17, 2016.
+   This Internet-Draft will expire on January 1, 2017.
 
 Copyright Notice
 
    Copyright (c) 2016 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
    (http://trustee.ietf.org/license-info) in effect on the date of
    publication of this document.  Please review these documents
@@ -375,27 +375,28 @@
    API will return an error code and the invoking applications must
    respond with using legacy calls without On-Demand Mobility feature.
 
 4.2.  IP Stack in the Mobile Host
 
    New IP stacks must continue to support all legacy operations.  If an
    application does not use On-Demand Mobility feature, the IP stack
    must respond in a legacy manner.
 
    If the network infrastructure supports On-Demand Mobility feature,
-   the IP stack may still request specific types of source IP address
-   transparently to legacy applications.  This may be useful for
-   environments in which both legacy and new applications are executed.
-
-   The definition of what type of addresses to request and how they are
-   assigned to legacy applications are outside of the scope of this
-   specification.
+   the IP stack should follow the application request: If the
+   application requests a specific address type, the stack should
+   forward this request to the network.  If the application does not
+   request an address type, the IP stack must not request an address
+   type and leave it to the network's default behavior to choose the
+   type of the allocated IP address.  If an IP address was already
+   allocated to the host, the IP stack uses it and may not request a new
+   one from the network.
 
 4.3.  Network Infrastructure
 
    The network infrastructure may or may not support the On-Demand
    Mobility feature.  How the IP stack on the host and the network
    infrastructure behave in case of a compatibility issue is outside the
    scope of this API specification.
 
 5.  Summary of New Definitions