From: Dave Hart <davehart@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: Jacopo Cesareo <jcesareo@cs.princeton.edu>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Testing wireless broadcast/multicast within cerowrt
Date: Wed, 3 Aug 2011 19:18:27 +0000 [thread overview]
Message-ID: <CAMbSiYAUZ14w=Om__Lx3C7Dwk4ABiUFU-shxUZD7MbG3Du5kUA@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw7gcZwB-sWtvr9ZTPknRjd__5LntdW7neAwn853Mvp9wg@mail.gmail.com>
On Wed, Aug 3, 2011 at 15:39, Dave Taht <dave.taht@gmail.com> wrote:
> And suggestions on other multicast/broadcast tools generating data worth
> analyzing is highly desired.
I don't know if they qualify as "worth analyzing", but how about
IPv6's substantial use of multicast, for ND, RA, and likely DHCP6?
Also, NTP broadcast/multicast and manycast (which uses multicast to
find servers, then unicast client/server for ongoing operation).
Cheers,
Dave Hart
next prev parent reply other threads:[~2011-08-03 18:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-03 15:39 Dave Taht
2011-08-03 19:18 ` Dave Hart [this message]
2011-08-03 19:23 ` Dave Taht
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAMbSiYAUZ14w=Om__Lx3C7Dwk4ABiUFU-shxUZD7MbG3Du5kUA@mail.gmail.com' \
--to=davehart@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=davehart_gmail_exchange_tee@davehart.net \
--cc=jcesareo@cs.princeton.edu \
/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