From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from jabiru.ens-lyon.fr (jabiru.ens-lyon.fr [140.77.51.2]) by huchra.bufferbloat.net (Postfix) with ESMTP id 8A8A021F2E9 for ; Wed, 2 Jul 2014 01:21:10 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by jabiru.ens-lyon.fr (Postfix) with ESMTP id A9671A3B2B for ; Wed, 2 Jul 2014 10:21:08 +0200 (CEST) X-Virus-Scanned: by amavisd-new-2.7.1 (20120429) (Debian) at ens-lyon.fr Received: from jabiru.ens-lyon.fr ([127.0.0.1]) by localhost (jabiru.ens-lyon.fr [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NElJy6Bruhnx for ; Wed, 2 Jul 2014 10:21:08 +0200 (CEST) Received: from localhost (second.degre.polyno.me [91.224.149.26]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by jabiru.ens-lyon.fr (Postfix) with ESMTPSA id 8BC531EB226 for ; Wed, 2 Jul 2014 10:21:07 +0200 (CEST) Date: Wed, 2 Jul 2014 17:21:01 +0900 From: Baptiste Jonglez To: cerowrt-devel@lists.bufferbloat.net Message-ID: <20140702082101.GC12461@ens-lyon.fr> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="B4IIlcmfBL/1gGOG" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Subject: Re: [Cerowrt-devel] [Bloat] viability of the data center in the internet of the future X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jul 2014 08:21:10 -0000 --B4IIlcmfBL/1gGOG Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jul 01, 2014 at 04:38:47PM +0000, Fred Baker (fred) wrote: > Were I Netflix and company, and for that matter Youtube, I would handle > delay at the TCP sender by using a delay-based TCP congestion control > algorithm. There is at least one common data center provider that I > think does that; they told me that they had purchased a congestion > control algorithm (although the guy I was speaking with didn=E2=80=99t kn= ow what > they bought or from whom), and the only one I know of that is for sale > in that sense is a pretty effective delay-based algorithm. Oh, people actually using FASP [1]? Or is it something else? (don't look too hard at the description if you are allergic to marketing bu= llshit) [1] http://asperasoft.com/technology/transport/fasp --B4IIlcmfBL/1gGOG Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJTs8DtAAoJEGB4mfgsWgTWZuMP/3ATkJ3ocIlF+bFkKzK2wy+/ 8YpaCrDwTV/BTCGMKKXSles1mxiP2Dz4KQz/45KAxSjtQlNVRrikxjtFK8HW/Zl0 E723tUm9QUafIfCY49JrH9NLzmUXhsW7ug9kbJVA6KS5LghTJVzcau9Y8eEr/fOJ UkA2THLNRc/NMTawYAH/9BC+4OKNO4OI90G5lZz8EdQQJx2ZVMX6bNAeQ2gt3os7 gr5xfWNqLPRfEmclIE34c/1z3QnB8bnbpEueVzv7PPXnm5EPSAG03KWEU19DBvt/ RXko1C29XskqpOmpeHSVANiSEznAR5yKi7H65kX/ami9JMEdAUekAJGDKbh4m2wu 1YGDzVANCBbtZe9uJMgkVHd7M9K7KFwWDNx5HxEY7lvKVerFnO7O9R82zNmcxBjB BIORAHuun/mspQNfJ3vPAVv6b+T2eRy7W1e4vfIc+qH26QsPzVw2sB5h3jDSE+/f E7YNRtkMEh84sCD2QnKSUxW3bJmCGusplE1Qx6ZICi176rpPoXsNGXbuWDY6kFQA iSt2V3rfdUzezY2l9G1KqPkZ8sSGd3JgHZhIKUWfa0z+TC9EhOFNkhGcv1Qzmtct 53XYzt5jLozJ9baaxpL5AyHHy+smWgERlSBaxrBqi+7HBt6PnOp3j8yehiL3b67r DQ6ZH421x+zx8wrTRQT/ =wCaT -----END PGP SIGNATURE----- --B4IIlcmfBL/1gGOG--