7 ms·
It seems that widely deploying TLS 1.3 and DOH can provide an effective technical end-around the dismantling of net neutrality. So we should be promoting and t
by ilaksh 9y ago
It seems that widely deploying TLS 1.3 and DOH can provide an effective technical end-around the dismantling of net neutrality. So we should be promoting and trying to deploy them as widely as possible.
Of course, they can still block or throttle by IP, so the next step is to increase deployment of content-centric networking systems.
- jstanley 9y agoBy content-centric networking systems do you mean IPFS et al?
- ilaksh 9y agoYes, IPFS, but actually there a huge number of perhaps lesser-known projects that do all sorts of things with content-oriented-networking. It's been a pretty big research topic.
- topspin 9y agoIt seems to me that all of the changes described in this story will contribute to thwarting intermediaries and their agendas. HTTP/2 and its "effective" encryption requirement are proof against things like Comcast's nasty JavaScript injection[1]. QUIC has mandatory encryption all the way down; even ACKs are encrypted, obviating some of the traditional throttling techniques. And as you say TLS 1.3 and DOH further protect traffic from analysis and manipulation by middlemen. Perhaps our best weapon against Internet rent seekers and spooks is technical innovation. It is astonishing to me that Google can invent QUIC, deploy it on their network+Chrome and boom! 7% of all Internet traffic is QUIC. Traditional HTTP over TCP and traditional DNS are becoming a ghetto protocol stack; analysis of such traffic is sold to who knows whom, the content is subject to manipulation by your ISP, throttling is trivial and likely to become commonplace with Ajit Pai et al. Time to pull the plug on these grifters and protect all the traffic. [1] https://news.ycombinator.com/item?id=15890551 https://news.ycombinator.com/item?id=15890551
- zb3 9y agoBut I, as an user, want to be able to block domains, inject scripts and see what Chrome is sending to Google on my own devices (which is what Google doesn't want me to do). That's why I can't support these protocols...
- JoshTriplett 9y agoYou, as a user, absolutely can. An ISP or network administrator who does not control the endpoints, on the other hand, cannot, by design. That's a feature.
- fiddlerwoaroof 9y agoWhat if I want to use my router to block telemetry domains? Or other malware sites? It’s looking like the only way forward is running my own CA to mitm all encrypted traffic.
- JoshTriplett 9y ago> It’s looking like the only way forward is running my own CA to mitm all encrypted traffic. Correct. Middleboxes should be presumed hostile; if you control the endpoints you can install a MITM CA, but it's safer to put what you want directly on the endpoint.
- aoeusnth1 9y agoThat seems superior anyway - you could keep blocking domains even when you're on the go.
- kuschku 9y agoCan I? On Android, apps now can decide if they want to accept user-installed CAs, or not. So if an app is hostile (say, all the Google apps), then I have no way to intercept their traffic anymore.
- lathiat 9y agoUnfortunately not really; Net Neutrality mostly focuses around the semi-bigger services who in most cases will have at least one of a dedicated AS number; dedicated IP ranges or dedicated physical network links they can limit the capacity of. Which is traditionally how the game has been played. Think Netflix/Comcast.. no hiding what that traffic is.
- ori_b 9y ago> It seems that widely deploying TLS 1.3 and DOH can provide an effective technical end-around the dismantling of net neutrality. If you don't think about it, it may seem that way. But until everyone sends all their data over tor, or some other system that obscures which IP you're trying to get to, it's still easy to filter. There's (within epsilon of) zero motion I've seen towards obscuring IP addresses, for good reason.