Kevin, I can't fix ipv6 I'll leave that to people that understand the basics. No one, and i mean no one in corp (that's not a super scalar) knows anything about ipv6 and no one and i mean no one cares. They know it's on in there os and there's some mystery that some things will break if it's off. Jamie On Mon., May 4, 2026, 2:27 p.m. Kevin Tillery via NANOG, < nanog@lists.nanog.org> wrote:
Jamie
And ipv8 is no where on there radar. So fix ipv6.
I appreciate your input.
Kevin
On 4 May 2026 08:26:33 CEST, Jamie Thain via NANOG <nanog@lists.nanog.org> wrote:
Marco
And ipv6 is no where on there radar. So fix ipv4.
I appreciate your input.
Jamie
On Sun., May 3, 2026, 4:33 a.m. Marco Moock via NANOG, < nanog@lists.nanog.org> wrote:
Am 03.05.26 um 00:30 schrieb Jamie Thain via NANOG:
* IPv6 wasn't a surgical fix for address exhaustion — it bundled the address-space change with a full redesign of neighbor discovery, autoconfiguration, header structure, and operational tooling.
That wasn't the issue. The issue is that it takes some time to prepare and do the implementation of another network protocol, regardless how it is called or how it works in detail. No one cares about ARP, nor NDP. It is there and works.
Corporate networks need address plan, firewall plans etc. and that needs to be extended if any new protocol is going to be implemented.
-- Gruß Marco
Junk-Mail bitte an trashcan@stinkedores.dorfdsl.de _______________________________________________ NANOG mailing list
https://lists.nanog.org/archives/list/nanog@lists.nanog.org/message/LZX6VCZU... _______________________________________________ NANOG mailing list
https://lists.nanog.org/archives/list/nanog@lists.nanog.org/message/AVIU5UM7... _______________________________________________ NANOG mailing list
https://lists.nanog.org/archives/list/nanog@lists.nanog.org/message/MPYN6YGE...