[142511] in North American Network Operators' Group
Re: Strange TCP connection behavior 2.0 RC2 (+3)
daemon@ATHENA.MIT.EDU (Ryan Malayter)
Wed Jun 29 08:59:59 2011
Date: Wed, 29 Jun 2011 05:59:49 -0700 (PDT)
In-Reply-To: <BANLkTin4RBcVAZaz9kwoBouHmT1TBndkbQ_xc9E=OFFx4GEr5w@mail.gmail.com>
From: Ryan Malayter <malayter@gmail.com>
To: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Jun 28, 3:35=A0pm, Cameron Byrne <cb.li...@gmail.com> wrote:
>
> AFAIK, Verizon and all the other 4 largest mobile networks in the USA
> have transparent TCP proxies in place.
Do you have a reference for that information? Neither AT&T nor Sprint
seem to have transparent *HTTP* proxies according to
http://www.lagado.com/tools/cache-test. I would have thought that
would be the first and most important optimization a mobile carrier
could make. I used to see "mobile-optimized" images and HTTP
compression for sites that weren't using it at the origin on Verizon's
3G network a few years ago, so Verizon clearly had some form of HTTP
proxy in effect.
Aside from that, how would one check for a transparent *TCP* proxy? By
looking at IP or TCP option fingerprints at the receiver? Or comparing
TCP ACK RTT versus ICMP ping RTT?
