3 ms·
Contrary to probably most people, I've actually got experience using a lot more than 127.0.0.1. I needed to support an HTTPS service built as a TLS terminating
by toast0 5y ago
Contrary to probably most people, I've actually got experience using a lot more than 127.0.0.1. I needed to support an HTTPS service built as a TLS terminating proxy plus an HTTP server on the same machine, the HTTP server didn't understand unix sockets, and the required max connections goal was 1 million; it would have probably been faster and more effective to teach the http server how to do unix sockets or how to do TLS efficiently, but there was organizational opposition to both at the time. Of course, both are now options.
So that means lots of connections on localhost, but you run into difficulties with managing ports unless you listen on multiple ips. Strategically picking the IPs to listen to helps reduce lock contention in the tcp stack as well. IIRC, I think we used 127.0.X.1 (which would be compatible with this proposal), but I no longer have access to the specifics.
The single loopback address of IPv6 is kind of insufficient, but there's not a whole lot of need for IPv6 over localhost, so if I ran into limits, I'd just use IPv4, or even use one of the IPv4 in IPv6 space mappings with IPv4 loopback addresses.
OTOH, if they're looking at opening up 127/8, why not also open up 0/8 (other than 0/24) and the class E 240/4 (other than 255.255.255.0/24)? There's some use of class E addresses[1], but I don't think it's that much more of a disruption than 127/8.
[1] Cloudflare uses them as Pseudo addresses for IPv6 transition, and I think I've seen that elsewhere too. https://blog.cloudflare.com/supporting-the-transition-to-ipv6-only-networking-services-for-ios/ https://blog.cloudflare.com/supporting-the-transition-to-ipv...
- schoen 5y ago> OTOH, if they're looking at opening up 127/8, why not also open up 0/8 (other than 0/24) and the class E 240/4 (other than 255.255.255.0/24)? There's some use of class E addresses, but I don't think it's that much more of a disruption than 127/8. That's exactly what we're proposing! This draft is just one of four drafts. The other three are https://datatracker.ietf.org/doc/draft-schoen-intarea-unicast-240/ https://datatracker.ietf.org/doc/draft-schoen-intarea-unicas... https://datatracker.ietf.org/doc/draft-schoen-intarea-unicast-0/ https://datatracker.ietf.org/doc/draft-schoen-intarea-unicas... https://datatracker.ietf.org/doc/draft-schoen-intarea-unicast-lowest-address/ https://datatracker.ietf.org/doc/draft-schoen-intarea-unicas...
- ArchOversight 5y agoFor IPv6 you could always generate a ULA and you'd have enough IP's to assign to a loopback interface to last you multiple lifetimes. The fact that ::1 is the only loopback address is not really an issue.