General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Simon Leinen <simon.leinen@switch.ch>
To: mallman@icir.org
Cc: "Shawn Ostermann" <ostermann@cs.ohiou.edu>,
	"Toke Høiland-Jørgensen" <toke@toke.dk>,
	bloat@lists.bufferbloat.net
Subject: [Bloat] Passive RTT measurements [was: Re:  Bufferbloat Paper]
Date: Thu, 17 Jan 2013 15:03:55 +0100	[thread overview]
Message-ID: <aar4ljx5x0.fsf@switch.ch> (raw)
In-Reply-To: <20130109033920.C47B95B2B40@lawyers.icir.org> (Mark Allman's message of "Tue, 08 Jan 2013 22:39:20 -0500")

[CC'ing Shawn as the author of tcptrace]

Mark Allman writes:
[Toke Høiland-Jørgensen:]
>> Incidentally, are the data extraction scripts available somewhere?
>> Might be worthwhile to distribute them as some kind of tool that
>> people with interesting vantage points could apply to get useful data?

> Well, they are not readily available.  I used a non-public extension
> to Bro (that is not mine) to get the RTT samples.

I have found that with "tcptrace -Z -lrn", I can extract lots of RTT
samples and also some per-connection statistics (which are useful but
not as detailed as I'd like to or as in your paper).  This even works in
finite time, like a couple minutes per 100Mpacket trace of mostly HTTP
traffic taken near a popular archive server.  As a bonus, it supports IPv6.

So it seems that tcptrace (6.6.7) does *almost* what we need.  But you
probably have reasons why you haven't extended Bro rather than using
tcptrace (possibly after improving it somehow).  Care to elaborate?

Maybe we can add the necessary improvements to tcptrace and make it even
more awesome.  (I'm sure Bro is awesome too, I'm just not as familiar
with it.)

> So, that is a sticking point.  And, then there is a ball of goop to
> analyze those.  If folks have a place they can monitor and are
> interested in doing so, please contact me.

* raises hand *

> I can probably get this in shape enough to give you.  But, I doubt
> I'll be able to somehow package this for general consumption any time
> soon.

Understood.
-- 
Simon.

  parent reply	other threads:[~2013-01-17 14:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87r4lvgss4.fsf@toke.dk>
2013-01-09  3:39 ` [Bloat] Bufferbloat Paper Mark Allman
2013-01-09  5:02   ` David Lang
2013-01-18  1:23     ` grenville armitage
2013-01-17 14:03   ` Simon Leinen [this message]
2013-01-17 14:08     ` [Bloat] Passive RTT measurements [was: Re: Bufferbloat Paper] Simon Leinen
2013-01-18 23:16     ` Hagen Paul Pfeifer

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=aar4ljx5x0.fsf@switch.ch \
    --to=simon.leinen@switch.ch \
    --cc=bloat@lists.bufferbloat.net \
    --cc=mallman@icir.org \
    --cc=ostermann@cs.ohiou.edu \
    --cc=toke@toke.dk \
    /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