Re: [ipv6-wg] Clear Guidance for Enterprises

etting their hands dirty with IPv6 and postulate "why should I need IPv6, everything works with IPv4 though". Alexander Koeppe This message and any attachment are confidential and may be privileged or otherwise protected from disclosure. If you are not the intended recipient, you must not c

Re: [ipv6-wg] Clear Guidance for Enterprises

laints), the move to IPv6 will remain at the >micro-steps enthusiasts like me can afford and support. Alexander Koeppe This message and any attachment are confidential and may be privileged or otherwise protected from disclosure. If you are not the intended recipient, you must not copy thi

Re: [ipv6-wg] Have we failed as IPv6 Working Group?

> Am 04.10.2019 um 08:56 schrieb Carlos Friaças via ipv6-wg : > > Some years ago i also did a local test by removing the IPv4 address from my > laptop to see if i could bear with a full day of work without it. I couldn't. > After two hours i placed it back, but at the time i already had a list

Re: [ipv6-wg] Disband IPv6 WG

Am 04.10.2019 um 00:22 schrieb Kai 'wusel' Siering mailto:wusel...@uu.org>>: 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? I like this idea. This message and any attachment are confidential and may be