[103140] in North American Network Operators' Group
Re: Customer-facing ACLs
daemon@ATHENA.MIT.EDU (Andy Davidson)
Tue Mar 18 15:59:38 2008
Cc: <nanog@merit.edu>
From: Andy Davidson <andy@nosignal.org>
To: <surfer@mauigateway.com>
In-Reply-To: <20080307155713.6D5C48A6@resin17.mta.everyone.net>
Date: Tue, 18 Mar 2008 19:58:30 +0000
Errors-To: owner-nanog@merit.edu
On 7 Mar 2008, at 23:57, Scott Weeks wrote:
> Might as well do TCP 20, 21 and 23, too. Woah, that slope's getting
> slippery!
Oh, no, this one again.
*** The Internet Is Not The Web. ***
Could someone put that onto a t-shirt ?
If it becomes normal for home users to only have 80 and 443, then how
can I innovate and design something that needs a new protocol ? What
happens to the new voice and video services for example ?
On 11 Mar 2008, at 02:33, Christopher Morrow wrote:
> vpns fix this...
They stop fixing stuff when they stop working. If you start running
vpn services on tcp/80 (yuck, yuck, yuck), and naturally because it's
the only port open lots of other non http protocol stuff does too,
will filter-happy domestic providers start proxying the web instead of
just filtering the rest of the traffic ..?
Andy
