From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wg0-x232.google.com (mail-wg0-x232.google.com [IPv6:2a00:1450:400c:c00::232]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 740E821F164; Tue, 29 Apr 2014 08:46:48 -0700 (PDT) Received: by mail-wg0-f50.google.com with SMTP id k14so410155wgh.21 for ; Tue, 29 Apr 2014 08:46:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=BONCxR/spyWM5/uTx0EhoJGPlOJRdmeTFON8M+mFjII=; b=TEpEIzbgwOAH6TH1AmKIES1tRPl/yahNhDSGzIQKyx9KBi7ZX7L6+PDamNfY0Y0BRU +eogcHv6DzADk5v77EalO50Rd3H/bRex0DqklS120PgBvra/KoB1z3CIRiW2ooxGADDf K8/9vtOe6bTPt2pjCPGRTB+YgVa0a31JcaEqNyI34uMqxY6XG0nYehoBX/+36SYCAv0q 0qJBq5v+bLCRgbk/M/mR5+lXU/BezUrs6MRiunSlyklurXvHVJDDNdoBGCT4VNVB91f2 n6joQcCJx0MUaeZrwttHx30zERfc/yLQtKGBozczX1PMPDgpKIDQU8StUTdF2xKKQMIC UqXg== MIME-Version: 1.0 X-Received: by 10.194.6.106 with SMTP id z10mr79312wjz.1.1398786406224; Tue, 29 Apr 2014 08:46:46 -0700 (PDT) Received: by 10.216.207.82 with HTTP; Tue, 29 Apr 2014 08:46:46 -0700 (PDT) In-Reply-To: References: <4130D000-FE28-4A5E-B824-3371C1602472@cisco.com> Date: Tue, 29 Apr 2014 08:46:46 -0700 Message-ID: From: Dave Taht To: Mikael Abrahamsson Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: bloat , "cerowrt-devel@lists.bufferbloat.net" , "aqm@ietf.org" Subject: Re: [Bloat] [aqm] the side effects of 330ms lag in the real world X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Apr 2014 15:46:49 -0000 On Tue, Apr 29, 2014 at 12:56 AM, Mikael Abrahamsson wro= te: > On Tue, 29 Apr 2014, Fred Baker (fred) wrote: A couple points here. 1) The video went viral, and garnered over 600,000 new hits in the 12 hours since I posted it here. there is pent up demand for less latency. While the ad conflates bandwidth with latency, they could have published their RTTs on their local fiber network, which is probably a great deal less than dsl or cable. That counts for a lot when accessing local services. 2) There is a lot of things an ISP can do to improve apparent latency on the long haul A) co-locating with a major dns server like f-root to reduce dns latency B) co-locating with major services like google and netflix publishing ping times to google for example might be a good tactic. C) Better peering >> Well, we could discuss international communications. I happen to be at >> Infocom in Toronto, VPN=E2=80=99d into Cisco San Jose, and did a ping to= you: > > > Yes, but as soon as you hit the long distance network the latency is the > same regardless of access method. So while I agree that understanding the > effect of latency is important, it's no longer a meaningful way of sellin= g > fiber access. If your last-mile is fiber instead of ADSL2+ won't improve > your long distance latency. Well, it chops a great deal from the baseline physical latency, and most people tend to access resources closer to them than farther away. An american in paris might want to access the NYT, but Parisians La Monde. Similarly most major websites are replicated and use CDNs to distribute their data closer to the user. The physical RTT matters more and more in the last mile the more resources are co-located in the local data center= . --=20 Dave T=C3=A4ht