3 ms·
> These regulations should be fairly basic: pass all IPv6 traffic unmodified, pass all IPv4 traffic unmodified except for NAT. Erm, pretty much NOBODY does thi
by exelius 11y ago
> These regulations should be fairly basic: pass all IPv6 traffic unmodified, pass all IPv4 traffic unmodified except for NAT.
Erm, pretty much NOBODY does this - even today. Every packet you send out from your ISP has (and has had for at least 4 years - probably longer) headers, cookies, etc. injected long before it reaches the public Internet. Then along the way more companies inject things into it. Then the load balancers at the other end likely do as well.
This is not all for evil purposes, either: lots of DDOS and botnet traffic gets blackholed thanks to these optimizations. Trouble is, the ability / need for legitimate network management requires tools that can also be used for less awesome purposes, and those less awesome purposes are usually how you can justify the money for the tools in the first place.
A lot of people on HN seem to have a purist view about how Internet traffic should be handled once it leaves your house. The companies that actually manage said traffic haven't shared this view or even operated a network that looks remotely like it for a decade or more. Your data is everywhere; and if it's not being sold by your ISP (which it is) it's being sold by your bank, by Amazon, by Google -- pretty much anyone you do business with on or off line.
- ploxiln 11y agoEvery packet you send has headers, cookies, etc. injected long before it reaches the public internet? really? Not for TLS (https). Not for vpn connections. Really, pretty much never. It was big news when it came out that Verizon was doing this to mobile data connections. All that happens to the IP header and everything inside is perhaps the ECN bit being fiddled, TOS bits being zeroed, that's it usually. And, as mentioned before, NAT. For home cable or fiber internet connections, the NAT usually happens on your device, on your local network (and under your control if you reject the ISP-provided cable modem and use your own, or put the FIOS router in bridge mode).
- exelius 11y ago> It was big news when it came out that Verizon was doing this to mobile data connections. Because the other ISPs were sneakier and were only injecting their tokens when the user was visiting a site that was paying for the service. Other ISPs had been running similar schemes for years, but it flew under the radar because it was only active when the user visited certain sites. Verizon fucked up and released a half-baked solution and people caught on. Other companies were better at it. > For home cable or fiber internet connections, the NAT usually happens on your device, on your local network (and under your control if you reject the ISP-provided cable modem and use your own, or put the FIOS router in bridge mode). Most ISPs are running a carrier-grade NAT solution of some sort. A lot more happens in the access layer than most people realize.
- ploxiln 11y agoMaybe wireless ISPs, maybe wired ISPs in Asia, but not wired ISPs in the US or Europe.