[97319] in North American Network Operators' Group
Re: Network Level Content Blocking (UK)
daemon@ATHENA.MIT.EDU (Chris L. Morrow)
Thu Jun 7 14:26:49 2007
Date: Thu, 07 Jun 2007 18:25:53 +0000 (GMT)
From: "Chris L. Morrow" <christopher.morrow@verizonbusiness.com>
In-reply-to: <Pine.GSO.4.64.0706071139380.17018@clifden.donelan.com>
To: Sean Donelan <sean@donelan.com>
Cc: James Blessing <james.blessing@entagroup.com>,
nanog <nanog@merit.edu>
Errors-To: owner-nanog@merit.edu
On Thu, 7 Jun 2007, Sean Donelan wrote:
>
> On Thu, 7 Jun 2007, James Blessing wrote:
> > 1. Revocation of mere conduit status; by inspecting certain content and
> > preventing access to it the ISP is doing more that just passing packets
> > and is getting involved in the content.
>
> Its not "content" blocking, its source/destination blocking.
oh, so null routes? I got the impression it was application-aware, or
atleast port-aware... If it's proxying or doing anything more than
port-level blocking it's likely it sees content as well, or COULD.
Either way, it's not like it's effective for anything except the m ost
casual of users :(