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

[Alexandre Petrescu <[e-mail]>]

Hi Li,
Thank you for the message.

Le 17/09/2019 à 03:48, 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 ...

Indeed.  An IoT Router is a device of class IoT, but has several IP 
interfaces, hence it is a router.

An IoT Router uses the wireless egress interface (either wlan, or 
cellular) to send DHCPv6-PD request.

> 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?

Please separate the phrases into sentences, by using terminating dots. 
If you do, I will understand you better.  Did you mean this:

"About the kernel part: OEM user would in principle follow the system 
updates.  The updates could be performed by using an IP address obtained 
by dhcpv6.  But how would clients obey protocol rfc3315, 8415, 6260? 
They need to maintain warranty and avoid conflicts".

Let me try to answer.

In an IoT router there is indeed a modem of an OEM.  For example a 
Huawei or a Qualcomm modem.  This modem often updates its software, in 
order to move from 4G+ to 4G++, for example.  Typically it updates by 
using over-the-air software update technology.  It needs an IP address 
for itself.  This IP address is just one of multiple addresses of an IoT 
router.   Multiple addresses make for a prefix.  To obtain a prefix one 
uses DHCPv6-PD, not just SLAAC.

So, the OEM user needs to run DHCPv6-PD.  It must do so in accordance 
with RFC3315 and then RFC8415.  It needs to update its software from 
RFC3315 to RFC8415.

> Microsoft is one putting on tracking, it must be forwarded to them about.

A Microsoft computer, like a Windows 10 tablet, also uses a 4G modem. 
Windows does implement DHCPv6.

Do you know whether Windows 10 implements DHCPv6-PD?

> Let have your kind advises on it please .

I would like to learn whether I can put this open source DHCPv6-PD plus 
ND linux kernel implementation into the Windows kernel?

https://github.com/dmytroshytyi/KD6-DHCPv6-PD-DANIR

Or maybe in a BSD OS?

Or maybe run this linux kernel software as a virtual machine on windows 
and link its virtual interface to the real interface?

Alex

> 
> 
> 
> Sincerely yours
> Li HUANG
> 
> 
> On Tue, Sep 17, 2019, 00:18 Alexandre Petrescu 
> <[e-mail] <mailto:[e-mail]>> 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 <[e-mail]>
>     <mailto:[e-mail]>
>     Pour : 	[e-mail] <mailto:[e-mail]> <[e-mail]>
>     <mailto:[e-mail]>
> 
> 
> 
>     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
>     [e-mail] <mailto:[e-mail]>
>     https://www.ietf.org/mailman/listinfo/dhcwg
>