Problems? I can think of a few.... ---- Besides the silicon speed/forwarding which was already touched on, which effectively makes this a non-starter for a good 15-20 years anyway until hardware catches up...... and this is a huge problem on its own. ----- I can see no way in which this is not a still dual-stack 'like' environment. Except now instead of just IPv4 vs IPv6, you've got IPv4 vs IPv8 vs IPv6 vs IPv4 inside IPv8.AS12345 versus..... and so on and so forth, rendering the IPv4 internet essentially useless. I've got machines or software that are in critical roles that are over 20 years old and speak IPv6 and IPv4 just fine. They'll be hit by that problem easily. So will almost anything existing and current today, for that matter. For a thought exercise example - If I have 1.2.3.4 inside my AS, but a device or software wants 1.2.3.4 from the old IPv4 internet, how does it get there? The IPv4 packets coming from the endpoint all just still say 1.2.3.4. They get my 1.2.3.4 and can't ever get to the 'old' ipv4 1.2.3.4 without explicit management/policy based routing type scenarios, and that's just unacceptable from a corporate network management perspective. And neigh impossible from an ISP perspective. Plus, what if the device should be able to get to both? Remember, the device only speaks IPv4 and IPv6. So, I need to have an IPv8, IPv6 and IPv4 stack, where non-aware applications only use the IPv4 and IPv6 stacks and only receive the 'old' global IPv4. Only aware devices/applications could access both the 'inside AS' service and 'outside AS' old global IPv4 service. So, in 20 years, it might be tenable, whereas IPv6 was tenable from 1998 onwards after most of the standards development/dust has settled. My AIX manufacturing systems with software from 1999 and 2001 work just fine in today's IPv6/IPv4 environment, but would be limited in this IPv8 world. ----- Security tooling. That's a big one. That'd be a long discussion. A lot of extra logic to add/handle here. 'peering is now optional' - are we all just running our own giant intranets now? The whole point of the internet is massive interconnection - aka peering.
But do you think you should build an ietf standard in 2026 with out llm.
Absolutely, then you put some thought and skill into it. LLMs are effectively useless at producing something durable and quality if you don't have the skill to do it yourself given a reasonable amount of time in the current state they're in. And I utilize the hell out of them every day. But never for anything so critical, not without taking the draft and re-writing it entirely myself at a minimum to ensure it makes logical sense and is compliant with sanity. Throwing three different models at a specific problem, filtering down the results, and producing an excellent result? That, that it can do just fine. But that's 'diagnose why X doesn't do Y in this specific code, except for ABC condition, when it should do it also for XYZ condition' type work.
If your not using llm everyday your competitors are.
And they're hurting all the more for relying on entirely or over-using it, burning money, and giving me with limited contextual usage a huge advantage and I thank them for it. Because now they're making awesome mistakes they'd never made before. If you could do something in two days, an LLM *might* help you do it in an hour. A week? Shortened to a day of careful babysitting. If it's something you couldn't do entirely yourself, however, the LLM will give you rank garbage and give others huge openings to take advantage of, if it produces something sensical and working at all. I for one welcome the rampant unconstrained AI adoption. It's already gotten me great business opportunities. -----Original Message----- From: Jamie Thain via NANOG <nanog@lists.nanog.org> Sent: Thursday, April 30, 2026 8:58 AM To: Saku Ytti <saku@ytti.fi> Cc: North American Network Operators Group <nanog@lists.nanog.org>; Jamie Thain <jamie@one.bm> Subject: Re: IPv8 / BGP8 / CF Saku You think you can type into an llm build a better protocol and it will snap one out of the air. But do you think you should build an ietf standard in 2026 with out llm. If your not using llm everyday your competitors are. But further to my problem what else do i need to solve. I solved route growth as peering is now optional, Vpns by making vpn over quic And best path by cost factor. Anything else need to be fixed? On Thu., Apr. 30, 2026, 3:25 a.m. Saku Ytti, <saku@ytti.fi> wrote:
Tough love is needed here, and the list is not providing it. You're not being polite, you're enabling.
Stop supporting this LLM psychosis.
-- ++ytti
_______________________________________________ NANOG mailing list https://lists.nanog.org/archives/list/nanog@lists.nanog.org/message/AKF4M2DQ...