Discussion of explicit congestion notification's impact on the Internet
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: ECN-Sane <ecn-sane@lists.bufferbloat.net>
Subject: [Ecn-sane] Fwd: [bbr-dev] BBR v2 Alpha/Preview Release (slides and code)
Date: Tue, 23 Jul 2019 04:04:10 -0700	[thread overview]
Message-ID: <CAA93jw59NvWk3uqL4Z-EaWEQ6bwaFwiuKdeZS__Eu_6CtmsNCg@mail.gmail.com> (raw)
In-Reply-To: <CADVnQyn-EP=rUfwc96yiqzFKCkysxufdY5h0-A18-ZZX2o=YZw@mail.gmail.com>

---------- Forwarded message ---------
From: 'Neal Cardwell' via BBR Development <bbr-dev@googlegroups.com>
Date: Mon, Jul 22, 2019 at 9:28 PM
Subject: [bbr-dev] BBR v2 Alpha/Preview Release (slides and code)
To: BBR Development <bbr-dev@googlegroups.com>, iccrg IRTF list <iccrg@irtf.org>


We wanted to mention these updates:

o TCP BBR v2 Alpha/Preview Release:
  https://github.com/google/bbr/blob/v2alpha/README.md
  (Chromium QUIC release is coming soon.)

o Slides for an update on BBR work at Google, including this release,
at the IETF 105 ICCRG session tomorrow:
  https://datatracker.ietf.org/meeting/105/materials/slides-105-iccrg-bbr-v2-a-model-based-congestion-control-00

cheers,
neal

--
You received this message because you are subscribed to the Google
Groups "BBR Development" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to bbr-dev+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/bbr-dev/CADVnQyn-EP%3DrUfwc96yiqzFKCkysxufdY5h0-A18-ZZX2o%3DYZw%40mail.gmail.com.


-- 

Dave Täht
CTO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-831-205-9740

           reply	other threads:[~2019-07-23 11:04 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CADVnQyn-EP=rUfwc96yiqzFKCkysxufdY5h0-A18-ZZX2o=YZw@mail.gmail.com>]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/ecn-sane.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAA93jw59NvWk3uqL4Z-EaWEQ6bwaFwiuKdeZS__Eu_6CtmsNCg@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=ecn-sane@lists.bufferbloat.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox