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

Li HUANG <bleuoisou@gmail.com> Thu, 19 September 2019 23:55 UTC

Return-Path: <bleuoisou@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 530EE120043 for <dhcwg@ietfa.amsl.com>; Thu, 19 Sep 2019 16:55:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 THtaF8j97Y9E for <dhcwg@ietfa.amsl.com>; Thu, 19 Sep 2019 16:55:48 -0700 (PDT)
Received: from mail-io1-xd2b.google.com (mail-io1-xd2b.google.com [IPv6:2607:f8b0:4864:20::d2b]) (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 089761200B1 for <dhcwg@ietf.org>; Thu, 19 Sep 2019 16:55:43 -0700 (PDT)
Received: by mail-io1-xd2b.google.com with SMTP id q10so12099457iop.2 for <dhcwg@ietf.org>; Thu, 19 Sep 2019 16:55:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Xu0HMCQbD2iarqIhBw+YiNFkN2bSgbpqKMFlCd26J0s=; b=sFDrd0fvvmLzzYIzEH1FVYYyUCgngwFpXXZ/5Om2GHzGVIMe8jNvN3+3RLw4qfylI4 vtsmrUrJkcVgAC5UmtSLKUmL5NpSqQQEj3FngwSiviq2GCvahyMXAHj2fafVGvAFAkjB a0nD/sg7uxbB9fN4UorqmA4WoyP7NQ8vc7c/Ewn7xfDJhcqNMyVXh03Zz+wj0eu9o96F B2+UwCzsyVFe56e/OdnrBlKnCWk+XB16djhhhmc/tVZpXbit5RAtrj3CkwHUC2cTTGHY BUJdrxQFmsmsRVhaCbaUctj9GO5VXe/wOg0bJpcr8W6gsUVviCPvCmjnAUSiopukHKwq XoNw==
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; bh=Xu0HMCQbD2iarqIhBw+YiNFkN2bSgbpqKMFlCd26J0s=; b=j0r3GNS/9hajHD5cIMuRUS1NenkhiqbeR3o/TxLK/rSPy2SkVKdq693r4OIjysJb32 kLMp528yyhgRMdI//ugjNV6MqH4mQ8b2R+mRUgumpd4S47X5UwItstNRfXxU5RhaqOop 3+JFcQbHpST08urNSvZlEli77CaQiYN4JiC9MRhLOCsP64u/gODZira+DyW7CuyPcHVC vAnPGsGx+aJE30ctsllycU6lttd2cNO+SP2xBBw23m3cRkPDReZUXUIlFhLZRyEsRUPl dXRJWx+S/2T/u2Pr5Hwxaydo0p3blYuRD1wSaaqTt1CqSurBadD/kjU6Qp6xO6cjyfk9 +Pxg==
X-Gm-Message-State: APjAAAUNFswM2r27CYnPYQA5nUmd4BJDIC5i8xcClvpcDGRefsypDZHU 4TUEEr7DJF7enkFoTfOG5G8objZDsRXtgUCno/E=
X-Google-Smtp-Source: APXvYqzVMalwgCgKUEYSE7g7OTqCQJDevnn2mZGvxKGk3CxBm6FEHFoatt5pc9xpvz/6w0pR49WZLEtWmFX+jXZdBfM=
X-Received: by 2002:a05:6638:777:: with SMTP id y23mr15652866jad.111.1568937342169; Thu, 19 Sep 2019 16:55:42 -0700 (PDT)
MIME-Version: 1.0
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> <c32c6804-1e67-2f1d-a27f-4d925dce91df@gmail.com>
In-Reply-To: <c32c6804-1e67-2f1d-a27f-4d925dce91df@gmail.com>
From: Li HUANG <bleuoisou@gmail.com>
Date: Fri, 20 Sep 2019 08:55:30 +0900
Message-ID: <CAGGiuEYcHDs691gzRSVdW_4MK1d7LWzjDRqv7WeBGt81+LWS3w@mail.gmail.com>
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Cc: dhcwg@ietf.org
Content-Type: multipart/alternative; boundary="000000000000f479450592f0b0e3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/BZSV5OeWiXEqIf7dZ0-xhQ4mYsI>
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: Thu, 19 Sep 2019 23:55:54 -0000

08:47.hk S8 Sept 20 2019


continued...,


Thank you rephrasing our diagonose for assuring the points.


Wireless advance for dhcpv6 is imagined to experienced network maps. Which
none wireless devices and plan isp at all decades.


Microsoft who is handing rcf3315 according modified failures,  to changed
board OEM machine, has reached wall to resolve it inside microsoft.


Looking for some where who would enter the juridical like IEFT...etc., in
order to edge out what responsibility taken by who, if in such compromising
rcf rules obeying  in conditions.



Sincerely yours
Li HUANG






On Wed, Sep 18, 2019, 21:05 Alexandre Petrescu <alexandre.petrescu@gmail.com>
wrote:

> 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
>
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg
>