> upload filter Your upload is my download. A user uploads an HTTP request to a server, and the server uploads an HTTP response to the user. Of course that sou

> upload filter Your upload is my download. A user uploads an HTTP request to a server, and the server uploads an HTTP response to the user. Of course that sounds unnatural compared to the user downloading the HTTP response. But the difference between upload/download is purely semantic and only distinguishes the intent of the user. Regardless of terms used, data flows in one direction, then back in another. The only distinguishing factor is its direction and whether or not both sides can establish the initial connection. So in that sense, a server uploads data to the user, who implicitly permitted the sever to do so when establishing the connection. This misappropriation of technical language to advance a policy goal is revealing in that it shows the concept is fundamentally unlegislatable and therefore unenforceable, or worse, arbitrarily enforceable. This is just part of an ongoing legislative pattern of the past 5-10 years. My reading of its trajectory is that regulatory regimes will eventually require licenses to run any service behind public IP addresses, to register domain names, and to advertise BGP routes or run public DNS resolvers. When coupled with centralization of inbound routing infrastructure (transatlantic fiber) and/or increased regulation of IP transit companies, this licensing legislature will work effectively.