[178649] in North American Network Operators' Group
Re: content regulation, was Verizon Policy Statement on Net Neutrality
daemon@ATHENA.MIT.EDU (Dave Taht)
Sun Mar 1 21:03:06 2015
X-Original-To: nanog@nanog.org
In-Reply-To: <A3088829-54C2-4A80-BA65-7151714C5101@delong.com>
Date: Sun, 1 Mar 2015 18:03:03 -0800
From: Dave Taht <dave.taht@gmail.com>
To: Owen DeLong <owen@delong.com>
Cc: "John R. Levine" <johnl@iecc.com>, nanog list <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
On Sun, Mar 1, 2015 at 5:53 PM, Owen DeLong <owen@delong.com> wrote:
>
>> On Mar 1, 2015, at 14:01 , John R. Levine <johnl@iecc.com> wrote:
>>
>>>>>> Well, actually, it does. Every broadband network in the US
>>>>>> currently blocks outgoing port 25 connections from retail customers.
>>>>>
>>>>> Unfortunately, that's not entirely true. (Very) recent direct-to-MX =
spam
>>>>> from Comcast customers:
>>>>
>>>> Well, it's supposed to be blocked, according to people I've talked to
>>>> at Comcast and T-W as recently as a week ago. I can believe that they
>>>> have configuration problems on a networks of that size.
>>>
>>> fairly certain that none of these folk block port 25 on their business
>>> customer links.
>>
>> As I said above, retail customers. Business customers get static IPs an=
d generaly no blocking.
>>
>> R's,
>> John
>
> Business customers only get static from Comcast if they pay extra for it.
I still keep hoping for some way to buy an ipv6/48 from them. Being
dynamically renumbered all the time is a PITA, and yet, when comcast's
ipv6 works - it is GREAT. I had huge amounts of nat pressure from dns
traffic simply vanish once I switched my dns servers over to their
ipv6 (and deployed dnssec and got back NXDOMAIN)
>
> Owen
>
--=20
Dave T=C3=A4ht
Let's make wifi fast, less jittery and reliable again!
https://plus.google.com/u/0/107942175615993706558/posts/TVX3o84jjmb
