> Simply net neutrality is your ISP ignoring the contents of your packets and simply routing them to their intended destination.
That doesn't make sense. ISPs have long blocked "dangerous" or "premium" ports, like 445 (SMB) or 25 (SMTP). Those are parts of the contents of your internet packets and yet even the net neutrality regulation didn't prohibit doing that. And you can't argue those are "headers" rather than "contents" because then throttling packets based on IP addresses would not require looking at packet contents. So I think your definition is incorrect?
What people do and what is legislated are two different things. The point is that with a law on the books you can fight about your SMTP connection being closed, but without the law then there is no framework to even complain.
> What people do and what is legislated are two different things. The point is that with a law on the books you can fight about your SMTP connection being closed, but without the law then there is no framework to even complain.
That seems orthogonal to my comment. I was responding to the parent comment on what net neutrality even is, not trying to debate its merits.
That doesn't make sense. ISPs have long blocked "dangerous" or "premium" ports, like 445 (SMB) or 25 (SMTP). Those are parts of the contents of your internet packets and yet even the net neutrality regulation didn't prohibit doing that. And you can't argue those are "headers" rather than "contents" because then throttling packets based on IP addresses would not require looking at packet contents. So I think your definition is incorrect?