4 ms·
> How does making it harder for them to identify traffic for my app/service/whatever stop them from doing that? You can masquerade your protocol as HTTPS with
by codedokode 10mo ago
> How does making it harder for them to identify traffic for my app/service/whatever stop them from doing that?
You can masquerade your protocol as HTTPS with SNI of that company, for example. Filtering by IP is very inconvenient (they change all the time), so the telecom would probably look at SNI.
- saghm 10mo agoI still think I'm missing something. My understanding of how telecoms would abuse identifying traffic to violate net neutrality would be that they need to identify the traffic they want to prioritize, not deprioritize. Is your understanding different, or does this somehow give the ability to make your traffic indistinguishable to traffic that they favor (and therefore would either control directly or would be able to provide instructions to the controller to be able to make identifiable in some way)? What you're describing to me sounds like you're saying my traffic isn't possible to distinguish from other random traffic, but my argument is that they're never going to be prioritizing random traffic; they'll be prioritizing traffic that they can identify, which will likely not act in the way you describe precisely because it would make it impossible to prioritize. My traffic being anonymous doesn't somehow stop them from throwing it in to the lower priority lanes with everyone else because they don't recognize it; if anything, it seems like it's likely to guarantee it as well, because anything not recognizably a VIP doesn't get to go in the VIP lane.