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

Tom Herbert <tom@quantonium.net> Tue, 05 March 2019 16:25 UTC

Return-Path: <tom@quantonium.net>
X-Original-To: dmm@ietfa.amsl.com
Delivered-To: dmm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C67C913113E for <dmm@ietfa.amsl.com>; Tue, 5 Mar 2019 08:25:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=quantonium-net.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5FO-a98w2FS2 for <dmm@ietfa.amsl.com>; Tue, 5 Mar 2019 08:25:45 -0800 (PST)
Received: from mail-wr1-x429.google.com (mail-wr1-x429.google.com [IPv6:2a00:1450:4864:20::429]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 08CB113105F for <dmm@ietf.org>; Tue, 5 Mar 2019 08:25:44 -0800 (PST)
Received: by mail-wr1-x429.google.com with SMTP id t18so10162612wrx.2 for <dmm@ietf.org>; Tue, 05 Mar 2019 08:25:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=quantonium-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=oeEIJAKINiF5xFCZkqGMndQQkHid+pvlkqp62AT092Q=; b=M7ooiI1GJiTioT7YBpeJ6cjNmTxDidGsavj/j10bhAWQvjPSh5q2/+ya3dPgPhsC2J rPQ8pbV67LCBKMTC5r0YaoOOEns62nR2Qmxf5X7K34SfU6Xt05Y4qJEEQ3auybsJ1cay ldJqg1QeJP3OHqACMRdPLV3/5nd+JOskgxCHKyoD/VOGuBIaLkY/ZJYsQcHY48Kr5Xmm m9w/fWdJh1WAd2SqRmALdvPgibbNK51Cdjsklq8FRsD0tKxQSe5BVJ0PR8uUwfEwYNIo xjNn0PlOVk2PTzyDtubU3ADWiIWGzhAEg0ACo1ss1afMlD9Z4ju3PR4rbjgzslwBr0oj NYDA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=oeEIJAKINiF5xFCZkqGMndQQkHid+pvlkqp62AT092Q=; b=Ld0PTYmsM+VZZM3ZnxAM5sE+fmVwxfQ0ogv3KkAS5EpbJteoNK88Tv5fCpjtf8fXsg CnkDGGhfEKXvwNh/SpSHrv1YuloDlbn38skW1gGew8FMYC123441mCxCqFYEUWIk2+s7 UKIY5uSB1Ua/Y9Wdvv/57VGbTK9wEu3BE6SdXYKzXat3hAqp0p0foNTRfwxepLAmvA04 3+jqGVRXVmP0lg+vvUJgKE5NULJq8xQ2XDOaPGk2sho+ix4DiGjBUqjy3T3yFkQsHPC7 QkJlObcEt+HTsHhhrgP24Q+TX+dav4ZMUkJrZG+RFO0BcgGTw9f+U8Ve7diR2ymPXIUt zJSA==
X-Gm-Message-State: APjAAAUpv+Hrim4eaPp5mKWWhi41e9uZOdMHwGOh1G+6ReRKIcozYSo8 T+3BUFgGgQnR3ZCf4UsuHsF+ZKZr3Q0U+a+eI2j68w==
X-Google-Smtp-Source: APXvYqxWxP7MFD2MmFFtPPbPhWXzaxobWuD9xdUwDEu70OTJuJXJT8YJt0L7ZRcQ7u/GkYVNxBw9qVgGKsWlH9c5qxo=
X-Received: by 2002:adf:ffcd:: with SMTP id x13mr16377171wrs.20.1551803142716; Tue, 05 Mar 2019 08:25:42 -0800 (PST)
MIME-Version: 1.0
References: <155084512373.5443.16190139225888494776@ietfa.amsl.com> <CAPDqMery=rDJhFTPx-YWo4yVybrq3YAjVv7L=2mPiUMP_SeAVA@mail.gmail.com> <F0CF5715D3D1884BAC731EA1103AC281441DCE35@HASMSX106.ger.corp.intel.com> <CAPDqMerXojrc4HNTWU1s0n3k=7+dRWfGn7Hhhu2SZ41Oa=VzOA@mail.gmail.com> <F0CF5715D3D1884BAC731EA1103AC281441E30BE@HASMSX106.ger.corp.intel.com>
In-Reply-To: <F0CF5715D3D1884BAC731EA1103AC281441E30BE@HASMSX106.ger.corp.intel.com>
From: Tom Herbert <tom@quantonium.net>
Date: Tue, 5 Mar 2019 08:25:31 -0800
Message-ID: <CAPDqMeoikbGGyaOwSin_hAEbszA648hwgeaUFvUssvdiDEpamg@mail.gmail.com>
To: "Moses, Danny" <danny.moses@intel.com>
Cc: dmm <dmm@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmm/Ig3wsfx24_JNMLc5CdsrgA6PQVM>
Subject: Re: [DMM] I-D Action: draft-ietf-dmm-ondemand-mobility-17.txt
X-BeenThere: dmm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Distributed Mobility Management Working Group <dmm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmm>, <mailto:dmm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmm/>
List-Post: <mailto:dmm@ietf.org>
List-Help: <mailto:dmm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmm>, <mailto:dmm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Mar 2019 16:25:48 -0000

On Tue, Mar 5, 2019 at 2:29 AM Moses, Danny <danny.moses@intel.com> wrote:
>
> Can you please provide a calling sequence of your proposal?
>

Something like:

s = socket(AF_INET6, SOCK_STREAM, 0) ;
setsockopt(s, IPPROTO_IP, PREFERRED_ADDRESS_TYPE,
IPV6_REQUIRE_SESSION_LASTING_IP)
if (connect(s, &serverInfo, sizeof(serverInfo)) < 0) {
   if (errno == EADDRNOTAVAIL) {
            // Didn't get address for requested type
  }
  ...
}

// To get address local address that was selected...
getsockname(s, &myaddr, &myaddrlen);


> Thanks,
> Danny
>
> -----Original Message-----
> From: Tom Herbert [mailto:tom@quantonium.net]
> Sent: Monday, March 04, 2019 17:17
> To: Moses, Danny <danny.moses@intel.com>
> Cc: dmm <dmm@ietf.org>
> Subject: Re: [DMM] I-D Action: draft-ietf-dmm-ondemand-mobility-17.txt
>
> On Mon, Mar 4, 2019 at 4:25 AM Moses, Danny <danny.moses@intel.com> wrote:
> >
> > 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.
> >
> Hi Danny,
>
> It is unclear to me why address selection has to be done outside of binding the socket. It seems like the required functionality of the draft could be achieved by calling setsockopt to express desired address type and then calling connect on the socket. Connect will bind an address with the requested type and can obviously block if work needs to be done to find an appropriate address. This simplifies the API and addresses an ambiguity in the draft-- when setsc returns it is unclear if the address was somehow reserved for the socket use (e.g.
> this becomes pertinent if we were to add an interface to bind a unique address to a socket).
>
> Tom
>
> > Regards,
> > Danny
> >
> >
> >
> >
> > -----Original Message-----
> > From: dmm [mailto:dmm-bounces@ietf.org] On Behalf Of Tom Herbert
> > Sent: Friday, February 22, 2019 22:08
> > To: dmm <dmm@ietf.org>
> > 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 ).
> >
> > Tom
> >
> > On Fri, Feb 22, 2019 at 6:19 AM <internet-drafts@ietf.org> 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:
> > > https://datatracker.ietf.org/doc/draft-ietf-dmm-ondemand-mobility/
> > >
> > > There are also htmlized versions available at:
> > > https://tools.ietf.org/html/draft-ietf-dmm-ondemand-mobility-17
> > > https://datatracker.ietf.org/doc/html/draft-ietf-dmm-ondemand-mobili
> > > ty
> > > -17
> > >
> > > A diff from the previous version is available at:
> > > https://www.ietf.org/rfcdiff?url2=draft-ietf-dmm-ondemand-mobility-1
> > > 7
> > >
> > >
> > > Please note that it may take a couple of minutes from the time of
> > > submission until the htmlized version and diff are available at tools.ietf.org.
> > >
> > > Internet-Drafts are also available by anonymous FTP at:
> > > ftp://ftp.ietf.org/internet-drafts/
> > >
> > > _______________________________________________
> > > dmm mailing list
> > > dmm@ietf.org
> > > https://www.ietf.org/mailman/listinfo/dmm
> >
> > _______________________________________________
> > dmm mailing list
> > dmm@ietf.org
> > https://www.ietf.org/mailman/listinfo/dmm
> > ---------------------------------------------------------------------
> > 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.
> >
> ---------------------------------------------------------------------
> 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.