7/13/2026 at 12:58:07 PM
by speckx
7/13/2026 at 7:21:29 PM
ARP is not an issue at smaller scales, but at larger ones it can cause problems. Reducing the L2 broadcast 'blast radius' is one of the touted benefits of EVPN (which use may be worth considering once you get above ~20 switches):by throw0101d
7/13/2026 at 7:57:45 PM
Saw this in IETF already but it's not clear why it's useful especially as the old path still needs to be implemented for compatibility. TFA is obviously LLMslop, which is very disappointing from RIPE.by inigyou
7/14/2026 at 12:19:27 PM
For corporate networks, where you control what devices get onto non-guest VLANs/subnets, you'll have better control over devices that support this new functionality. See for example Google's work on removing IPv4 on corporate networks:* https://www.youtube.com/watch?v=UTRsi6mbAWM
Even in organizations where IT cannot control devices, like universities which are largely student-BYOD, IPv6 take-up can reach 80%:
* https://www.youtube.com/watch?v=2B-liebzcOMmkm&t=10m
"Obviously" in what way?
by throw0101d
7/14/2026 at 2:38:30 PM
But why is this little hack advantageous over dual-stack? Advanced switches already don't forward ARPs they can handle locally.by inigyou
7/14/2026 at 6:28:26 PM
Because dual-stack means having to deal with stand up IPv4, which entails more configuration, more address planning, more infra, etc. See perhaps "ยง5.1 IPv6-only Compared to Dual-Stack":* https://datatracker.ietf.org/doc/html/draft-ietf-v6ops-6mops
Fewer IPv4 deployed subnets means those addresses can be used where they're 'really' needed instead of being 'wasted'.
by throw0101d
7/14/2026 at 7:13:25 AM
I don't get your question? If you use a /32 then there is no broadcast address and no ARP. And the /32 are then announced by your internal routing protocol.by _bernd
7/13/2026 at 5:59:28 PM
> That's real, but it understates the problem.It's all so tiresome.
by alhidade
7/14/2026 at 10:44:24 AM
What drives people to post blatant slop like this?by illliillll