3 ms·

The complexity is already paid for since you aren't going to be able, or even want to, wholly rip and replace IPv4 since it gains very little and risks a lot. I

by nimish 3y ago

The complexity is already paid for since you aren't going to be able, or even want to, wholly rip and replace IPv4 since it gains very little and risks a lot. IPv6 would have been great if it didn't have to work in a brownfield environment. Unfortunately, nobody is going to change because it's conceptually purer to not have those ancillary protocols. This is what the creators of v6 failed to consider: IPv4 was entrenched, it's not 1982 with ARPANET connecting a handful of systems all managed by people who knew each other. And DHCP does a bunch of stuff that's irritatingly dumb to do with IPv6, to the extent that v6 ended up shoving partial compromises _anyway_ like RDNSS. It's classic second-system effect and design by people without production experience or skin in the game.

throw0101b 3y ago
> The complexity is already paid for since you aren't going to be able, or even want to, wholly rip and replace IPv4 since it gains very little and risks a lot. You should tell that to Microsoft: * https://www.arin.net/blog/2019/04/03/microsoft-works-toward-ipv6-only-single-stack-network/ https://www.arin.net/blog/2019/04/03/microsoft-works-toward-... Veronika McKillop is now President of the UK IPv6 Council: * https://www.youtube.com/@ukipv6council468/videos https://www.youtube.com/@ukipv6council468/videos * https://fr.linkedin.com/in/veronika-mckillop-ipv6 https://fr.linkedin.com/in/veronika-mckillop-ipv6 > It's classic second-system effect and design by people without production experience or skin in the game. Begin with "TCP and UDP with Bigger Addresses (TUBA), A Simple Proposal for Internet Addressing and Routing" for part of the discussion from back in the day (1993): * https://datatracker.ietf.org/doc/html/rfc1347 https://datatracker.ietf.org/doc/html/rfc1347 The author of that document attended the first IETF meeting in 1986; interview: > He’s now a Distinguished Engineer at Juniper Networks, author of 14 RFCs, and chair of the MPLS Working Group at IETF. * https://www.internetsociety.org/blog/2016/02/interview-ross-callon-celebrates-the-ietfs-30th-anniversary/ https://www.internetsociety.org/blog/2016/02/interview-ross-... * https://www.linkedin.com/in/ross-callon-b8383695 https://www.linkedin.com/in/ross-callon-b8383695 He co-edited the MPLS architectural document: * https://datatracker.ietf.org/doc/html/rfc3031 https://datatracker.ietf.org/doc/html/rfc3031 But sure: "without production experience or skin in the game".

by nimish 3y ago

throw0101b 3y ago

> The complexity is already paid for since you aren't going to be able, or even want to, wholly rip and replace IPv4 since it gains very little and risks a lot. You should tell that to Microsoft: * https://www.arin.net/blog/2019/04/03/microsoft-works-toward-ipv6-only-single-stack-network/ https://www.arin.net/blog/2019/04/03/microsoft-works-toward-... Veronika McKillop is now President of the UK IPv6 Council: * https://www.youtube.com/@ukipv6council468/videos https://www.youtube.com/@ukipv6council468/videos * https://fr.linkedin.com/in/veronika-mckillop-ipv6 https://fr.linkedin.com/in/veronika-mckillop-ipv6 > It's classic second-system effect and design by people without production experience or skin in the game. Begin with "TCP and UDP with Bigger Addresses (TUBA), A Simple Proposal for Internet Addressing and Routing" for part of the discussion from back in the day (1993): * https://datatracker.ietf.org/doc/html/rfc1347 https://datatracker.ietf.org/doc/html/rfc1347 The author of that document attended the first IETF meeting in 1986; interview: > He’s now a Distinguished Engineer at Juniper Networks, author of 14 RFCs, and chair of the MPLS Working Group at IETF. * https://www.internetsociety.org/blog/2016/02/interview-ross-callon-celebrates-the-ietfs-30th-anniversary/ https://www.internetsociety.org/blog/2016/02/interview-ross-... * https://www.linkedin.com/in/ross-callon-b8383695 https://www.linkedin.com/in/ross-callon-b8383695 He co-edited the MPLS architectural document: * https://datatracker.ietf.org/doc/html/rfc3031 https://datatracker.ietf.org/doc/html/rfc3031 But sure: "without production experience or skin in the game".