From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ob0-x232.google.com (mail-ob0-x232.google.com [IPv6:2607:f8b0:4003:c01::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 1FE0821F618 for ; Fri, 19 Jun 2015 09:28:33 -0700 (PDT) Received: by obbgp2 with SMTP id gp2so77597898obb.2 for ; Fri, 19 Jun 2015 09:28:33 -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=6i4GyQ6M6491w/9WR1KrrRXIG1+Nxw42q9xX4Hr2tGI=; b=H9E+mC+QUWUWjcp0v+2gJRmAUP5MUmfBCN/P42ls/Yyi7Ur8OR9OUipOVADpFhTfnN Cfdr5tyZj6wL5lHZ/70GNXwFF5okbsyKCghtVUec8XzXdr+XtSeD09Nu7fKTYj2qb6DB OP3Y5o/Nu8Dje7yddRPlQ+zqmJzwauha+22ykiSLtR6U0ItWrOVyrR38vThUjCfCxyCW /jyfKRSNxz/8aWSXfJ28xjoC/AR9JTqzyzIgqF/ZiBdRp7wWEgJfy6AkowtMDbyFt4/n 1xOlp81GAgBZbq1rlLObawQK7zcWfocNa+bgdfwvCoIGc+OSyWLFp1AUr8pgwDP0X+js YRQw== MIME-Version: 1.0 X-Received: by 10.202.227.15 with SMTP id a15mr13744688oih.59.1434731312999; Fri, 19 Jun 2015 09:28:32 -0700 (PDT) Received: by 10.202.105.129 with HTTP; Fri, 19 Jun 2015 09:28:32 -0700 (PDT) In-Reply-To: <20150618193233.DC547406057@ip-64-139-1-69.sjc.megapath.net> References: <20150618193233.DC547406057@ip-64-139-1-69.sjc.megapath.net> Date: Fri, 19 Jun 2015 09:28:32 -0700 Message-ID: From: Dave Taht To: Hal Murray Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: bloat Subject: Re: [Bloat] backbone loss statistics over the past 15 years or so? 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: Fri, 19 Jun 2015 16:29:02 -0000 On Thu, Jun 18, 2015 at 12:32 PM, Hal Murray wrot= e: > > I don't think you can measure backbone loss using ping unless you control= both ends and ensure that both last-miles are not contributing to the prob= lem. Well, fractional percentages would be nice to have out of this website. I have a great title for a paper one day: "Bufferbloat and the Rise of the Too-Perfect Network". > > I think there are several different areas to investigate. The main one i= s whether your packet gets handed off between two "backbone" IPSs that are = currently squabbling about who is going to pay whom how much. The obvious = example is Netflix vs Comcast. The MIT paper was awesome... But I am thinking that supply (on downlinks) is outstripping demand, along the first world edge, now... it really is hard to imagine how much more bandwidth one can consume... > I don't have any numbers, but I think over the past 5 or 10 years, all th= e major ISPs have set things up so that all their internal links are overpr= ovisioned. You might notice packet loss when a link goes down and the traf= fic patterns get rearranged. (I know you can see changes in transit time u= sing NTP.) > > I have an old/slow DLS link. I get close to 0% packet loss if my last mi= le is not busy and lots of loss when it is overloaded. > > -- > These are my opinions. I hate spam. > > > > _______________________________________________ > Bloat mailing list > Bloat@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/bloat --=20 Dave T=C3=A4ht worldwide bufferbloat report: http://www.dslreports.com/speedtest/results/bufferbloat And: What will it take to vastly improve wifi for everyone? https://plus.google.com/u/0/explore/makewififast