Re: [DMM] I-D Action: draft-ietf-dmm-ondemand-mobility-17.txt

"Moses, Danny" <> Mon, 04 March 2019 12:24 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 6673F13103B for <>; Mon, 4 Mar 2019 04:24:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 7NHD6kPDUfQP for <>; Mon, 4 Mar 2019 04:24:36 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id ECF8D130FF4 for <>; Mon, 4 Mar 2019 04:24:35 -0800 (PST)
X-Amp-Result: SKIPPED(no attachment in message)
X-Amp-File-Uploaded: False
Received: from ([]) by with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 04 Mar 2019 04:24:35 -0800
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.58,440,1544515200"; d="scan'208";a="149079898"
Received: from ([]) by with ESMTP; 04 Mar 2019 04:24:35 -0800
Received: from ( by ( with Microsoft SMTP Server (TLS) id 14.3.408.0; Mon, 4 Mar 2019 04:24:35 -0800
Received: from ( by ( with Microsoft SMTP Server (TLS) id 14.3.408.0; Mon, 4 Mar 2019 04:24:34 -0800
Received: from ([]) by ([]) with mapi id 14.03.0415.000; Mon, 4 Mar 2019 14:24:32 +0200
From: "Moses, Danny" <>
To: Tom Herbert <>, dmm <>
Thread-Topic: [DMM] I-D Action: draft-ietf-dmm-ondemand-mobility-17.txt
Thread-Index: AQHUyrmscsUmoytC/UStnPPAN5r0DKXsHcAAgA9XEzA=
Date: Mon, 4 Mar 2019 12:24:32 +0000
Message-ID: <>
References: <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-ctpclassification: CTP_NT
x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiYjJiNzJlMzktMTgyMC00Y2EzLTkyY2ItYmVkMGIwMDI1MThkIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjEwLjE4MDQuNDkiLCJUcnVzdGVkTGFiZWxIYXNoIjoiWDFlVzNVZHFtbmtNZXZsXC9vWG9pczJlTkVaWUYrS29JNUxveFl2eTJGQ0RDbHRnRE10Z0pYSG4yODl6U2NWSHQifQ==
dlp-product: dlpe-windows
dlp-version: 11.0.400.15
dlp-reaction: no-action
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Archived-At: <>
Subject: Re: [DMM] I-D Action: draft-ietf-dmm-ondemand-mobility-17.txt
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Distributed Mobility Management Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 04 Mar 2019 12:24:38 -0000

Hi Tom,

Fair question.

I believe I mentioned that in one of my responses. The original definition was to use setsockopt() with new flags. However, some people raised the concern that this new feature changes the behavior of the function in a way that may confuse programmers and requested to use a new function (setsc()).

The issue was due to the time it takes the function to process the request. In current Socket implementation, setsockopt() is a function that returns immediately to the caller. On the other hand, this new feature may trigger an exchange of packets between the IP stack in the mobile node and the network allocating the IP prefix. This exchange takes time and the function can return only after the exchange is completed. They insisted that we maintain the current 'immediate' return behavior of setsockopt() and introduce a new function that might 'block' the calling thread until it completes.


-----Original Message-----
From: dmm [] On Behalf Of Tom Herbert
Sent: Friday, February 22, 2019 22:08
To: dmm <>
Subject: Re: [DMM] I-D Action: draft-ietf-dmm-ondemand-mobility-17.txt

Out of curiosity, why is the new API being portrayed as a system call
(setsc) instead of a socket option (the bar for adding a socket option is much lower ).


On Fri, Feb 22, 2019 at 6:19 AM <> wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Distributed Mobility Management WG of the IETF.
>         Title           : On Demand Mobility Management
>         Authors         : Alper Yegin
>                           Danny Moses
>                           Seil Jeon
>         Filename        : draft-ietf-dmm-ondemand-mobility-17.txt
>         Pages           : 18
>         Date            : 2019-02-22
> 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.
> The IETF datatracker status page for this draft is:
> There are also htmlized versions available at:
> -17
> A diff from the previous version is available at:
> Please note that it may take a couple of minutes from the time of 
> submission until the htmlized version and diff are available at
> Internet-Drafts are also available by anonymous FTP at:
> _______________________________________________
> dmm mailing list

dmm mailing list
A member of the Intel Corporation group of companies

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.