Comcast

[gaf-mNDKBlG2WHs at public.gmane.org (Jerry Feldman)]

Basically, Comcast is providing you with residential, not commercial
service. Historically, well before Comcast arrived here in Boston, cable
providers were having trouble with kids setting up IRC servers (or being
hacked to set them up). Another historical reason not to allow servers
on Cable TV circuits is that historically, cable TV was one way, and
while there was equipment that allowed upside traffic, that was very
limited, which is another reason why we have asymmetric speeds. Today,
this is probably not true in most of Comcast's metro areas we still have
mostly unsophisticated users with sophisticated kids.

I would prefer that Comcast continue to block some of the main ports,
but unlock them on request. While all of us are running Linux, most of
us are reasonably sophisticated, and can manage our systems.

On 11/12/2009 12:56 PM, Richard Pieri wrote:
> On Nov 12, 2009, at 11:35 AM, Laura Conrad wrote:
>  =20
>> But the TOS doesn't actually prohibit all servers.  It just says you
>>    =20
> Quote from http://www.comcast.net/terms/use/#prohibited
> * use or run dedicated, stand-alone equipment or servers from the Premi=
ses that provide network content or any other services to anyone outside =
of your Premises local area network (=93Premises LAN=94), also commonly r=
eferred to as public services or servers. Examples of prohibited equipmen=
t and servers include, but are not limited to, e-mail, Web hosting, file =
sharing, and proxy services and servers;
> * use or run programs from the Premises that provide network content or=
 any other services to anyone outside of your Premises LAN, except for pe=
rsonal and non-commercial residential use;
>
>  =20


--=20
Jerry Feldman <gaf-mNDKBlG2WHs at public.gmane.org>
Boston Linux and Unix
PGP key id: 537C5846
PGP Key fingerprint: 3D1B 8377 A3C0 A5F2 ECBB  CA3B 4607 4319 537C 5846