Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>,
	cerowrt-devel@lists.bufferbloat.net,
	 Felix Fietkau <nbd@nbd.name>, John Crispin <blogic@openwrt.org>
Subject: [Cerowrt-devel] Fwd: [homenet] Fwd: videos and blog posts on home networking, buffer bloat
Date: Tue, 9 Apr 2013 07:23:20 -0700	[thread overview]
Message-ID: <CAA93jw7dd6GCqdCKKoYQNO0tjn9ZnPEyQhhW28p4f5XXZ=9FzQ@mail.gmail.com> (raw)
In-Reply-To: <DF661C0C-E2B8-43A8-977F-4E0AD71EFF6D@piuha.net>

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

All three homenet demos ran openwrt.

---------- Forwarded message ----------
From: Jari Arkko <jari.arkko@piuha.net>
Date: Tue, Apr 9, 2013 at 6:03 AM
Subject: [homenet] Fwd: videos and blog posts on home networking, buffer
bloat
To: homenet@ietf.org


FYI, there were some homenet-related videos that were shot in the BnB event
at the IETF. Great videos, Mark and John! The bufferbloat stuff was also
very interesting.

Jari

Begin forwarded message:

> From: IETF Chair <chair@ietf.org>
> Subject: videos and blog posts on home networking, buffer bloat
> Date: April 9, 2013 1:27:36 PM GMT+03:00
> To: "ietf@ietf.org Discussion" <ietf@ietf.org>
> Cc: John Brzozowski <John_Brzozowski@Cable.Comcast.com>
>
> The good folks at ISOC shot a number of videos during IETF-86 with
experts on various topics. These videos are now available, take a look at
the blog post John and I wrote:
>
> http://www.ietf.org/blog/2013/04/bits-n-bytes-on-video/
>
> The videos can also be accessed directly at:
>
> http://www.youtube.com/watch?v=3SvhtLl8aTg (John Brzozowski on HIPnet)
> http://www.youtube.com/watch?v=d-vwdD3Xtyg (Mark Townsley on HOMENET)
> http://www.youtube.com/watch?v=NuHYOu4aAqg (Chris Griffiths and Dave Täht
on buffer bloat)
>
> There was also an earlier blog post that focused on the importance on
running code, written together with Chris:
>
> http://www.ietf.org/blog/2013/03/running-code-at-ietf-86-2/
>
> All in all, I thought these demos and videos were very interesting. It is
excellent that we are building implementations of the things that we
specify in the working groups. And interestingly, Bits-n-Bytes has become a
place to show some these results. Thanks to everyone who was involved, and
the sponsors who made it possible! I also think it would be great to have
even more of this in the coming IETFs. If you have ideas, let us know!
>
> Jari Arkko
>

_______________________________________________
homenet mailing list
homenet@ietf.org
https://www.ietf.org/mailman/listinfo/homenet



-- 
Dave Täht

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

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

           reply	other threads:[~2013-04-09 14:23 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <DF661C0C-E2B8-43A8-977F-4E0AD71EFF6D@piuha.net>]

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='CAA93jw7dd6GCqdCKKoYQNO0tjn9ZnPEyQhhW28p4f5XXZ=9FzQ@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=blogic@openwrt.org \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=nbd@nbd.name \
    /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