CoDel AQM discussions
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: jzp-bufbloat@rsuc.gweep.net
Cc: codel@lists.bufferbloat.net, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Codel] [Bloat] interesting/useful networking related conferences?
Date: Sun, 10 Jun 2012 00:30:32 -0400	[thread overview]
Message-ID: <CAA93jw51mFdSrN0qom6qxDRBN3xEcZg5g2z997874aRmeGJKcg@mail.gmail.com> (raw)
In-Reply-To: <20120610021030.GA51381@gweep.net>

On Sat, Jun 9, 2012 at 10:10 PM, Joe Provo <jzp-bufbloat@rsuc.gweep.net> wrote:
> On Sat, Jun 09, 2012 at 09:41:06PM -0400, Dave Taht wrote:
>> I am trying to figure out travel schedules for the next 7 months, to
>> continue to spread the codel word, so I'm looking for government or
>> academic conferences worth members of the bloat team attending or
>> presenting at, between now and December. We have the linux and ietf
>> worlds prettu covered, so... also reaching out to BSD, apple, and
>> microsoft conferences seems worthwhile.
>
> Interesting you mention 'networking' in the subject, and skip the
> operator's events [where many network gear vendors have serious
> presence]. NANOG in October?

Nanog for sure!

When it came time to divvy up monitoring mailing lists, jg got
nanog and I ended up with linux netdev and wireless - and to keep up
with the load, I had to drop arocket, which was kind of difficult given what
an excellent year the last year in space was...

Given some of the data that has gone by recently (from stanford,
and others) it appears that the core is overbuffered significantly too.

But fixing that involves either the middle tier vendors stepping up,
or substantial
rework of existing line cards, etc, for the big boys. I'd be really
surprised (and delighted) if any of those guys had fq + codel based
solutions in that timeframe.

Sure hope the olympics go ok. The preliminary analysis of thegathering's data
was pretty scary...

>> I haven't decided if I'm going to travel personally, actually, but
>> knowing what options are good, would be good for those that might want
>> to show up and/or talk in various venues.
>>
>> Suggestions? This is what I have so far as potential stops on the "world tour".
>>
>> * Google Bloat San Jose
>>   Jun 16th
>> * Redhat Summit - Boston
>>   Jun 26-29
>> * IETF Vancouver
>>   July 29-Aug 03
>> * Debconf Managua
>>   Jun 30 - Jul 14
>> * ClueCon - Chicago
>>   Aug 7-9
>> * linux plumbers - San Diego, Ca
>>   Aug 28-31
>> * AES 133
>>   Oct 26-29 (I'm on a panel, apparently)
>> * Linuxcon europe - Barcelona, Spain
>>   November 5 - 7, 2012
>>
>>
>>
>>
>> --
>> Dave T?ht
>> SKYPE: davetaht
>> http://ronsravings.blogspot.com/
>> _______________________________________________
>> Bloat mailing list
>> Bloat@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/bloat
>
> --
>         RSUC / GweepNet / Spunk / FnB / Usenix / SAGE / NewNOG



-- 
Dave Täht
SKYPE: davetaht
http://ronsravings.blogspot.com/

      reply	other threads:[~2012-06-10  4:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-10  1:41 [Codel] " Dave Taht
2012-06-10  2:10 ` [Codel] [Bloat] " Joe Provo
2012-06-10  4:30   ` Dave Taht [this message]

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

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

  git send-email \
    --in-reply-to=CAA93jw51mFdSrN0qom6qxDRBN3xEcZg5g2z997874aRmeGJKcg@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=codel@lists.bufferbloat.net \
    --cc=jzp-bufbloat@rsuc.gweep.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