>The only far ressemblance with 6to4 is the thing that was actually nice in the
> design, the automatic word in automatic tunnel. Which for the rest of us mean
>s stateless. Compared to CGNATs that is huge.
Any form of communication with the current IPv4 internet requires some
sort of CGNAT. We
> > If there is a magical transition technology that allows an IPv6-only host t
> o
> > talk to an IPv4-only host, then let's deploy it.
>
> DNS64/NAT64, DS-Lite, 6rd, 464XLAT, MAP-T, MAP-E, ? pick a transition
> protocol and see what happens! (with more coming every year...)
The problem with
>A host in the Internet that wants to talk to a host in China would require an
>update to parse new DNS double-A (realm, address) records to encapsulate the p
>acket IP-in-IP, outer src= 240.0.0.1 outer dest=240.0.0.2. The router that ser
>ves the shaft at level 1 attracts 240.0.0.0/8 within
>If by ?straightforward transition plan? one means a clear and rational set of
>options that allows networks to plan their own migration from IPv4-only to IPv
>6, while maintaining connectivity to IPv4-only hosts and with a level of effor
>t reasonable comparable to just running IPv4, then I
>What I mostly meant is that there should be a regulated, industry-wide
>effort in order to provide a stable and active pool program. With the
>current models, a protocol that is widely used by commercial devices is
>being supported by the time and effort of volunteers around the world.
My
In your letter dated Wed, 24 Jun 2015 08:33:14 +0200 you wrote:
Leap years and DST ladjustments have never caused us any major
issues. It seems these code paths are well tested and work fine.
I seem to remember that they were not tested that well on a certain brand of
mobile devices a few years
In your letter dated Wed, 24 Jun 2015 14:05:34 +0100 you wrote:
Philip Homburg pch-na...@u-1.phicoh.com wrote:
For UTC the analog approach would be to keep time in TAI internally and
convert to UTC when required.
This is much less of a solution than you might hope, because most APIs,
protocols
7 matches
Mail list logo
