Re: [dhcwg] Fwd: Kernel implementation of DANIR for IoT Router - DHCPv6-PD and ND

Alexandre Petrescu <alexandre.petrescu@gmail.com> Wed, 18 September 2019 12:05 UTC

Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB60E120232 for <dhcwg@ietfa.amsl.com>; Wed, 18 Sep 2019 05:05:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.631
X-Spam-Level:
X-Spam-Status: No, score=-2.631 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 2PvS1U_D0b_3 for <dhcwg@ietfa.amsl.com>; Wed, 18 Sep 2019 05:05:04 -0700 (PDT)
Received: from sainfoin-smtp-out.extra.cea.fr (sainfoin-smtp-out.extra.cea.fr [132.167.192.228]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F09A012004D for <dhcwg@ietf.org>; Wed, 18 Sep 2019 05:05:03 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id x8IC52oQ021792 for <dhcwg@ietf.org>; Wed, 18 Sep 2019 14:05:02 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 08130204367 for <dhcwg@ietf.org>; Wed, 18 Sep 2019 14:05:02 +0200 (CEST)
Received: from muguet1-smtp-out.intra.cea.fr (muguet1-smtp-out.intra.cea.fr [132.166.192.12]) by pisaure.intra.cea.fr (Postfix) with ESMTP id F06A920436E for <dhcwg@ietf.org>; Wed, 18 Sep 2019 14:05:01 +0200 (CEST)
Received: from [10.8.35.150] (is154594.intra.cea.fr [10.8.35.150]) by muguet1-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id x8IC511N005785 for <dhcwg@ietf.org>; Wed, 18 Sep 2019 14:05:01 +0200
To: dhcwg@ietf.org
References: <c7e54351-9096-53e7-0322-cf7d0abc58f2@gmail.com> <740671f9-6e68-70ac-8dd2-91f9d24b965d@gmail.com> <CAGGiuEbxbw67MgKUCcZcp0KsYoiewXogrynFU7b3HThOY6FD-Q@mail.gmail.com> <CAGGiuEbksPxKV6GLA06A7untZOrwpYKnb_Ycu50ibb9cvzNtxg@mail.gmail.com> <4561ca6d-4611-27e8-5cb3-16e72075fa65@gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <c32c6804-1e67-2f1d-a27f-4d925dce91df@gmail.com>
Date: Wed, 18 Sep 2019 14:05:01 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <4561ca6d-4611-27e8-5cb3-16e72075fa65@gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/hM18CU0jCHuGK_-uE4aP0FoXrI0>
Subject: Re: [dhcwg] Fwd: Kernel implementation of DANIR for IoT Router - DHCPv6-PD and ND
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Sep 2019 12:05:07 -0000

Dear Li,

Thank you for the partial clarification you sent in private about 'apt 
windows'.  I understand that by 'apt windows' you mean 'apart from 
windows', which means 'with the exception of Windows'.

So, I think you mean that we in our draft have a preference to run 
DHCPv6-PD over the wireless interface, like with a phone.  You also mean 
that is ok.  You also mean that only Windows runs DHCPv6 on a wired 
interface; because Windows blocked DHCPv6 on wwan and wlan interface.

I think you are saying that this Windows blocking DHCPv6-PD on the 
wireless interfaces caused you a lot of trouble, even after system updates.

Because of that I think you are asking that we make and forward to 
Microsoft, a request to make DHCPv6-PD on the wireless interface.

I may be wrong though.

I would like to ask you: do you know somebody at Microsoft who cares 
about DHCPv6?  Or should I write simply to postmaster@microsoft.com 
hoping they will direct the message to people in charge?

Alex

Le 18/09/2019 à 09:45, Alexandre Petrescu a écrit :
> Dear Li,
> 
> Please help me understand:
> 
> What do you mean by 'apt windows'?
> 
> Alex
> 
> Le 18/09/2019 à 07:39, Li HUANG a écrit :
>> 09:39.hk <http://39.hk/> S8 Sept 17th 2019
>>
>>
>> Thank you dhcwg returning on this,
>>
>>
>>
>> IoT either PTP to dhcpv6 pd server sounds very like the running 
>> preferially to wireless, or phone networks instead of apt windows that 
>> blocked wwan, wlan services of it ...
>>
>>
>> To the kernel apart, OEM user would principle following its offered 
>> updates of system, in case dhcpv6 required update, how would clients 
>> obey protocol rcf 3315, 8415, 6260 whilst OEM warranty contract to get 
>> all none conflicts?
>>
>>
>> Microsoft is one putting on tracking, it must be forwarded to them about.
>>
>>
>> Let have your kind advises on it please .
>>
>>
>>
>> Sincerely yours
>> Li HUANG
>>
>> On Tue, Sep 17, 2019, 10:48 Li HUANG <bleuoisou@gmail.com 
>> <mailto:bleuoisou@gmail.com>> wrote:
>>
>>     09:39.hk <http://39.hk> S8 Sept 17th 2019
>>
>>
>>     Thank you dhcwg returning on this,
>>
>>
>>
>>     IoT either PTP to dhcpv6 pd server sounds very like the running
>>     preferially to wireless, or phone networks instead of apt windows
>>     that blocked wwan, wlan services of it ...
>>
>>
>>     To the kernel apart, OEM user would principle following its offered
>>     updates of system, in case dhcpv6 required update, how would clients
>>     obey protocol rcf 3315, 8415, 6260 whilst OEM warranty contract to
>>     get all none conflicts?
>>
>>
>>     Microsoft is one putting on tracking, it must be forwarded to them
>>     about.
>>
>>
>>     Let have your kind advises on it please .
>>
>>
>>
>>     Sincerely yours
>>     Li HUANG
>>
>>
>>     On Tue, Sep 17, 2019, 00:18 Alexandre Petrescu
>>     <alexandre.petrescu@gmail.com <mailto:alexandre.petrescu@gmail.com>>
>>     wrote:
>>
>>         Hello to participants in DHC WG,
>>
>>         One might be interested in this kernel implementation of
>>         DHCPv6-PD parts.
>>
>>         Yours,
>>
>>         Alex and Dmytro
>>
>>
>>         -------- Message transféré --------
>>         Sujet :     Kernel implementation of DANIR for IoT Router -
>>         DHCPv6-PD and ND
>>         Date :     Mon, 16 Sep 2019 09:21:46 +0200
>>         De :     Alexandre Petrescu <alexandre.petrescu@gmail.com>
>>         <mailto:alexandre.petrescu@gmail.com>
>>         Pour :     v6ops@ietf.org <mailto:v6ops@ietf.org> 
>> <v6ops@ietf.org>
>>         <mailto:v6ops@ietf.org>
>>
>>
>>
>>         Hi,
>>
>>         The kernel implementation of DANIR for IoT Router was finally
>>         working a few weeks ago.
>>
>>         It is an implementation of draft-shytyi-v6ops-danir-03.txt. 
>>         This is the right thing to do, instead of '64share' RFC7278.
>>
>>         In this video one can see the kernel in the IoT Router issues a
>>         DHCPv6 PD request on its egress and obtains a /56; it then makes
>>         several /64s out of it and subsequently sends RAs with these on
>>         the ingress interfaces.
>>
>>         The DHCPv6 server is took off-the-shelf.  The PDP part is not
>>         present in the IoT Router, but we expect it to work ok on a ptp
>>         link on a cellular network to a smartphone.
>>
>>         The video recorded the virtual machines output on the IoT Router
>>         (featured below), the Client device behind it, and the DHCPv6-PD
>>         server.
>>
>>         https://youtu.be/DymVQY7bCUM
>>
>>
>>         Yours,
>>
>>         Alexandre PETRESCU and Dmytro SHYTYI
>>
>>         PS: we will soon post the source code on github.
>>
>>         _______________________________________________
>>         dhcwg mailing list
>>         dhcwg@ietf.org <mailto:dhcwg@ietf.org>
>>         https://www.ietf.org/mailman/listinfo/dhcwg
>>
> 
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg