Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: dpreed@reed.com
To: "Wesley Eddy" <wes@mti-systems.com>
Cc: bloat-announce@lists.bufferbloat.net,
	bloat <bloat@lists.bufferbloat.net>,
	cerowrt-devel@lists.bufferbloat.net,
	Martin Stiemerling <martin.stiemerling@neclab.eu>
Subject: Re: [Cerowrt-devel] [Bloat] some good bloat related stuff on the ICCRG agenda, IETF #86 Tuesday, March 12 2013, 13:00-15:00, room Caribbean 6
Date: Thu, 28 Feb 2013 13:47:04 -0500 (EST)	[thread overview]
Message-ID: <1362077224.256114355@apps.rackspace.com> (raw)
In-Reply-To: <512F9DB5.60909@mti-systems.com>

[-- Attachment #1: Type: text/plain, Size: 1820 bytes --]


A small suggestion.  Instead of working on *algorithms*, focus on getting something actually *deployed* to fix the very real issues that we have today (preserving the option to upgrade later if need be).
 
The folks who built the Internet (I was there, as you probably know) focused on making stuff that worked and interoperated, not publishing papers or RFCs.
 
-----Original Message-----
From: "Wesley Eddy" <wes@mti-systems.com>
Sent: Thursday, February 28, 2013 1:11pm
To: "Dave Taht" <dave.taht@gmail.com>
Cc: bloat-announce@lists.bufferbloat.net, "Martin Stiemerling" <Martin.Stiemerling@neclab.eu>, cerowrt-devel@lists.bufferbloat.net, "bloat" <bloat@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Bloat] some good bloat related stuff on the ICCRG agenda, IETF #86 Tuesday, March 12 2013, 13:00-15:00, room Caribbean 6



On 2/28/2013 10:53 AM, Dave Taht wrote:
> 
> For those that don't attend ietf meetings in person, there is usually
> live audio and jabber chat hooked up into the presentations.
> 
> See y'all there, next month, in one form or another.
> 


In the TSVAREA meeting, we've also set aside some time to talk
about AQM and whether there's interest and energy to do some
more specific work on AQM algs in the IETF (e.g. like CoDel and
PIE):

https://datatracker.ietf.org/meeting/86/agenda/tsvarea

I'm working with Martin on some slides to seed the discussion,
but we hope that it's mostly the community that we hear from,
following up in the higher-bandwidth face-to-face time from
the thread we had on the tsv-area@ietf.org mailing list a few
months ago.


-- 
Wes Eddy
MTI Systems
_______________________________________________
Cerowrt-devel mailing list
Cerowrt-devel@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/cerowrt-devel

[-- Attachment #2: Type: text/html, Size: 2313 bytes --]

  reply	other threads:[~2013-02-28 18:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-28 15:53 [Cerowrt-devel] " Dave Taht
2013-02-28 18:11 ` [Cerowrt-devel] [Bloat] " Wesley Eddy
2013-02-28 18:47   ` dpreed [this message]
2013-02-28 19:55     ` Matt Mathis
2013-03-01 18:29       ` Wesley Eddy
2013-03-01 18:40         ` dpreed

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=1362077224.256114355@apps.rackspace.com \
    --to=dpreed@reed.com \
    --cc=bloat-announce@lists.bufferbloat.net \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=martin.stiemerling@neclab.eu \
    --cc=wes@mti-systems.com \
    /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