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

[Alexandre Petrescu <[e-mail]>]

Hi Li,

IETF is not police of protocols: IETF can not force organisations to 
implement protocols or to fix bugs.  But we can discuss about protocols 
at IETF.

If Microsoft Windows does not implement DHCPv6-PD on wireless links 
(like on cellular), then I have two things to say.

One thing is to say that Microsoft programmers should not worry.  They 
are not the only ones who do not implement DHCPv6-PD on wireless links. 
There is also Qualcomm who refuses to.  It may, or it may not be a 
problem.  But it is not only Microsoft.  An it is a good topic to work on.

The other thing is to say that it is possible to run a linux virtual 
machine on a Microsoft Windows real machine.  In that linux machine, one 
can run DHCPv6-PD, on the wireless interface of the real Microsoft 
Windows machine.  We propose open source to achieve this.  It is 
available at 
https://dmytro.shytyi.net/kd6-danir-lite-kernel-dhcpv6-pd-and-ndp-implementation/

(we have tried to upload it to github, but we hit a 2Gb upload limit; 
this limit is a thing to complain to github, together with its lack of 
IPv6 access; and github is now a Microsoft organisation :-)

Alex and Dmytro


Le 20/09/2019 à 01:55, Li HUANG a écrit :
> 08:47.hk <http://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 
> <[e-mail] <mailto:[e-mail]>> 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 [e-mail]
>     <mailto:[e-mail]>
>     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> <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 <[e-mail]
>     <mailto:[e-mail]>
>      >> <mailto:[e-mail] <mailto:[e-mail]>>> wrote:
>      >>
>      >>     09:39.hk <http://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
>      >>     <[e-mail]
>     <mailto:[e-mail]>
>     <mailto:[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]>>
>      >>         <mailto:[e-mail]
>     <mailto:[e-mail]>>
>      >>         Pour : [e-mail] <mailto:[e-mail]>
>     <mailto:[e-mail] <mailto:[e-mail]>>
>      >> <[e-mail] <mailto:[e-mail]>>
>      >>         <mailto:[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]> <mailto:[e-mail]
>     <mailto:[e-mail]>>
>      >> https://www.ietf.org/mailman/listinfo/dhcwg
>      >>
>      >
>      > _______________________________________________
>      > dhcwg mailing list
>      > [e-mail] <mailto:[e-mail]>
>      > https://www.ietf.org/mailman/listinfo/dhcwg
> 
>     _______________________________________________
>     dhcwg mailing list
>     [e-mail] <mailto:[e-mail]>
>     https://www.ietf.org/mailman/listinfo/dhcwg
>