| Essential internet infrastructure should not be content-neutral. Content neutrality is a higher bar than you think it is. Content-neutral means the rules cannot take content into account at all. If the content is millions of ssh login requests on thousands of servers with ec2-user and the top 10000 most used passwords, the infrastructure should be able to block that. Content-neutrality would probably make it illegal to prevent DDoS attacks. At some levels of infrastructure, sure, but broadly speaking, content-neutrality seems like a bad requirement. Viewpoint-neutral, however, is a better goal. https://www.law.cornell.edu/constitution-conan/amendment-1/o... |
Anyway, I think the details are in intent and the nature of the communication. Service providers shouldn't actively block communications where the only intent of the communication is consensual exchange of information between two or more parties (such as visiting a website) regardless of the content of the exchanged information.
SPAM would qualify as non-consensual from one party, so it would be exempt.
The intent of DDoS isn't to exchange information, so it would also be exempt.
I'm sure that it would need pages legalese to make this work, like ironing out the circumstances when ISPs can assume intent or consent. SPAM block lists should be reasonable.