IPv6 zones in URLs are a mistake
Summary
An article arguing that IPv6 zone identifiers in URLs are a design mistake, likely discussing the technical pitfalls and issues they cause in networking and Go's URL handling.
View Cached Full Text
Cached at: 06/05/26, 02:11 AM
Similar Articles
Hacking the Go compiler to efficiently map IPv4 to IPv6
Vincent Bernat explores how to efficiently map IPv4 addresses to IPv6 in Go's netip.Addr, comparing a standard library addition, an unsafe helper, and hacking the Go compiler to optimize the netip.AddrFrom16(ip.As16()) pattern that maintainers prefer.
Show HN: We Implemented the IPv8 Internet-Draft in Linux, Libc, and BGP
The team at goonhost.rocks implemented the IPv8 Internet-Draft across the Linux kernel, Musl libc, iproute2, FRRouting, and a Go zone server, then deployed it on a 10-node multi-AS testbed with 112k+ routes. It works in isolated lab conditions but breaks in real-world scenarios.
A Farewell to ARPs: IPv4 Service on IPv6-Only Networks
This article presents an IETF draft proposal to eliminate ARP and IPv4 subnets on IPv6-only networks, allowing IPv4 to run as a pure /32 service over IPv6 infrastructure without translation or tunnelling, addressing operational pain points like ARP storms and IPv4 address scarcity.
A rant about phishing: It's not the user's fault (and not DNS either)
The article critiques common phishing vulnerabilities by highlighting how fragmented authentication flows and poor URL practices make it difficult for users to distinguish legitimate sites from scams, advocating for consistent domain usage to improve security.
Closing the IPv6 first-packet gap with GRAND
The article presents GRAND as a method to address IPv6 first-packet latency issues, improving network performance by closing the gap in initial packet transmission.