Am 03.10.19 um 17:11 schrieb Tim
Chown:
On 3 Oct 2019, at 16:02, Jens Link <lists@quux.de> wrote:
Tim Chown <Tim.Chown@jisc.ac.uk> writes:
(Surprised we’re having this conversation in 2019, as the final fumes of
IPv4 address space disappear from Europe…)
If you had told me 10 or even 5 years ago that I would be having the
conversation in 2019 I would have laughed at you. Now it's a very sad
situation. IPv4 has won.
Well, the source for "new" IPv4 addresses is finally drying
out in the RIPE region, so I do not agree with "IPv4 has won"; it
lived an amazing life so far and is, since several years,
transitioning into it's evening of life. I wouldn't bet on a date
when IPv4 in the public Internet will be shut down, though. Not
even a decade, to be honest ...
I had a discussion over lunch about v6 yesterday (which is part of the
reason I started this today) and all I heard "but that is different
then IPv4. I don't like this!"
There will always be a legacy tail. The dinosaurs can wallow in their swamp.
Some of those dinosauers are still in their diapers,
though.
Those who deploy v6 will benefit from it. Others will feel the heat of not moving; here in the UK it’s Sky and BT who have between them ~10M households on IPv6. That’s not failure.
No, it's a start; over here in Germany, most mobile
operators give you RFC6890 or RFC1918 addresses, still. Cable
operators hand out DS (-Lite, mostly) for consumers, (semi-) fixed
IPv4 (no DS) for commercial clients. FritzVPN, the VPN solution of
popular CPE maker AVM, still fails completely with IPv6, both as
transport and as payload. All in all, it's more failure than
success (and even progress is fscking slow; Vodafone is allegedly
starting somethings like DS-lite on mobile these days, o2 on
mobiles uses public v6 a long time already — for VoLTE, but not
data). But then it's Germany, where anything IP is Neuland anyway.
New communities will benefit. For example, the largest science experiments are now migrating to IPv6, e.g., CERN and WLCG is 70% there, SKA will use it.
But will they go the whole way, i. e. make their stuff
accessible from the outside, including informational webservers
and other infrastructure (DNS, MX), v6-only? Until much used
resources go v6-only, there's no chance in hell that "[o]thers
will feel the heat of not moving", as everyone still makes
everything available via v4.
So, why not make ripe.net v6-only by 2020-01-01, as RIPE
NCC's IPv4 pool will have run dry by then anyway?
Am 03.10.19 um 13:11 schrieb Joao
Luis Silva Damas:
On 3 Oct 2019, at 12:58, Uros Gaber <uros@ub330.net>
wrote:
Hi Jens,
Wow, first I had to look at today's
date, I thought this was a April Fools joke mail.
Did you also look at the From?, because that’s not the one I
expected if I instinctively expanded the name to that of
someone I know, like the wg co-chair or so.
Well, off-topic, but more noteworthy, the RIPE NCC mailservers
are, as of today, still running Exim 4.92.2, remotely exploitable
according to CVE-2019-16928.
Am 03.10.19 um 12:34 schrieb Jens
Link:
Hi,
after now almost 12 years using, working and teaching[1]
IPv6 I've come to the conclusion that IPv6 is a mistake and will
not work.
According to the mailing list archive, "[t]he IPv6 Working Group is for anyone with an
interest in the next generation Internet Protocol. The
activities of the WG include education and outreach, sharing
deployment experiences and discussing and fixing operational
issues". So, Jens shared his IPv6 deployment experiences ("isn't
happening"), maybe there's something the IPv6 WG can do to
enforce IPv6 deployment? BTW, at least in terms of availability
v6 is the current, v4 the legacy Internet Protocol, maybe that
wording should be updated?
Regards,
-kai