[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Thank you, Comcast.



On 2/26/16 7:31 AM, Keith Medcalf wrote:
> ISP's should block nothing, to or from the customer, unless they make it clear*before*  selling the service (and include it in the Terms and Conditions of Service Contract), that they are not selling an Internet connection but are selling a partially functional Internet connection (or a limited Internet Service), and specifying exactly what the built-in deficiencies are.
>
> Deficiencies may include:
>    port/protocol blockage toward the customer (destination blocks)
>    port/protocol blockage toward the internet (source blocks)
>    DNS diddling (filtering of responses, NXDOMAIN redirection/wildcards, etc)
>    Traffic Shaping/Policing/Congestion policies, inbound and outbound
>
> Some ISPs are good at this and provide opt-in/out methods for at least the first three on the list.  Others not so much.


Thumbs up to this one.  I like how CenturyLink gives me the option of 
turning off port 25 blocking quickly if you know where to go, but it is 
on by default.

I can live with blocks on by default, but easily be able to be turned 
off (if you are smart enough to know where to look to disable the options).

Only thing I dislike is that they don't seem to remember it between 
service upgrades, and every time I bump my customer speeds I have to 
remember to go reset it or they can't send e-mail.  :-)

-- 
Brielle Bruns
The Summit Open Source Development Group
http://www.sosdg.org    /     http://www.ahbl.org