Why? Sane networks shouldn't block anything. Even super dangerous stuff like ports 135-139 and 445 are a morally gray area.
> The idea of uninspectable client traffic is somewhat unhinged, and is already heavily used by malicious actors.
How is privacy unhinged? Isn't that basically the same as the argument that we need to gut the Fourth Amendment because of terrorists and pedophiles?
No. ISPs provide internet service to customers who pay them for it. The entire situation is different. The ISPs are under no obligation to break and inspect encrypted traffic. Owners and operators of home and corporate networks have an entirely different(and justifiable) set of concerns.
But beyond legal obligations which anyone permitting this over their network would be grossly negligent in meeting, there's simply no way to maintain a secure network with some idea what's going over it. If you want to notice mass exfiltration of private data (something you must do to protect people's privacy), you absolutely want to avoid making it impossible to distinguish different types of traffic and their destinations.
Whether it's a personal network, a corporate network, or a major backbone, it's ethically and morally obligatory to be able to classify behavior at least well enough to stop security issues and illegal activity. Cloudflare doesn't have this problem, or course, as it sees all the decrypted SNIs...
EDIT: In fact, before you go in defensive of this... answer this: Do you think Cloudflare will serve kiwifarms or switter over this? Or is this privacy and freedom strategy really just about centralizing control? Networks are supposed to be decentralized, each with different authorities. Perhaps the narrative of one big open Internet is one sold you to by people who are trying to be the only ones in control.
I would say if ECH is implemented the correct response would unfortunately be to MITM it if too many providers implement it to just block it entirely. I suspect large companies won't force it to maintain a wide customer base, and again, any reasonable network operator should just block anyone who does.
ISPs absolutely have all sorts of regulatory needs and network performance reasons to classify traffic. It's an unpopular view, but it's reality. (And I would encourage you to investigate who pays the people telling you otherwise, before someone links Mike Masnick here.)
No, it’s not.
ISPs have no right to know who I am speaking to or why.
Is Chrome, which aggressively supports and promotes HTTP a "privacy focused app"?
Huh? What? Ever had to administer a corporate network for non-tech staff? Malware is everywhere. People are stupid. AND my assumption on a corporate network has always been that you have no expectation of privacy - its a work network, don't use it for personal stuff! Pretty simple.
That certainly isn’t true in the EU. You cannot spy on employees computers without a cause.
The problem is that what starts as a strong desire to conduct copyright infringement (or sure, some light personal web browsing on work computers) along with a dash of free speech extremism, has turned into a militant expectation of very handy passageways for actual crimes.
Instagram on your phone while at work. Don’t expect privacy on managed work machines. You company can see your emails. They can install CA on your managed machine and MITM your https traffic.
I hate the trend of also managing personal devices. But I get that it’s a complicated subject.
The natural alternative if blocking these protocols becomes unsustainable will absolutely be to require full decryption at our security edge. And that will provide drastically more information to us than we have now and will absolutely feel invasive.
The idea of uninspectable client traffic is somewhat unhinged, and is already heavily used by malicious actors.