Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] ietf report (Brief)
Date: Thu, 14 Nov 2013 12:21:01 -0800	[thread overview]
Message-ID: <CAA93jw6+wexn_ZSyi+6Rb0uionXyV9BF_p5Ronq9m-sbW-xMkQ@mail.gmail.com> (raw)

I think I should take the time to write down and sort out all that
happened at ietf. But that will take time I don't have (I dictated)
right now.

The big thing worth watching is bruce schneier's plenary talk...

http://recordings.conf.meetecho.com/Recordings/watch.jsp?recording=IETF88_TECH_PLENARY&chapter=part_7

I am increasingly annoyed about the actions of various intelligence agencies.

Some highlights from the aqm wg.

1) The pie folk announced the selection of a variant of pie as the
default and mandatory *on* aqm algorithm for docsis 3.1 cable modems.
There is support for alternate algos, and nothing has been decided for
CMTSes or docsis 3.0. It's going to take years for hardware to appear
on this...

I am very happy for something to be defaulting on.

2) Jim and I gave a preso based on cero + netem in the yurtlab
documenting some of the work we've been doing to evaluate fq_codel vs
pie vs drop tail

http://www.ietf.org/proceedings/88/slides/slides-88-aqm-3.pdf

(I really, really, really appreciate you all helping to make cero
stable enough to generate data we can trust on this and the atm fixes
in particular)

At RMCAT I got volunteered to look hard at the various proposals for
webrtc congestion control. If you haven't fiddled with it yet, load up
a current chrome or firefox web browser and tr
At ICCRG the presentation that grabbed my eye was google's on paced
tcp and the tcp reordering fixes. In particular I hope the reordering
stuff at the tcp layer gets rid of the need for it to happen at the
wireless later. I look forward, very much, to ripping that code out.

At TSVWG the Quic presentation was awesome. I got a chance for a more
private and in-depth brief the night before from jim roberts. He has
much passion and much data.... I encourage y'all to turn it on in
chrome and try it....

You can browse through the proceedings here:

https://datatracker.ietf.org/meeting/88/materials.html


-- 
Dave Täht

Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html

             reply	other threads:[~2013-11-14 20:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-14 20:21 Dave Taht [this message]
2013-11-14 21:58 ` Török Edwin
2013-11-15 10:01 ` Maciej Soltysiak

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/cerowrt-devel.lists.bufferbloat.net/

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

  git send-email \
    --in-reply-to=CAA93jw6+wexn_ZSyi+6Rb0uionXyV9BF_p5Ronq9m-sbW-xMkQ@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@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