Historic archive of defunct list bloat-devel@lists.bufferbloat.net
 help / color / mirror / Atom feed
From: d@taht.net (Dave Täht)
To: bloat <bloat@lists.bufferbloat.net>, bloat-devel@lists.bufferbloat.net
Subject: a cosmic background bufferbloat detector
Date: Wed, 09 Feb 2011 09:26:50 -0700	[thread overview]
Message-ID: <87sjvx5g39.fsf@cruithne.co.teklibre.org> (raw)


I've continued to think through the "using ntp to monitor and detect
bufferbloat idea" - and it continues to be discussed on
comp.protocols.time.ntp - but thus far the idea seems to have legs.

I found a very inspirational story:

http://en.wikipedia.org/wiki/Discovery_of_cosmic_microwave_background_radiation

Unless more flaws show up in the idea[1] a start at "cbbd" will be coming soon to a git repo near you.

-- 
Dave Taht
http://nex-6.taht.net

1: one flaw already - ntp rawstats output is inadequate. Parsing  
   tshark -f "src or dst port 123" output would allow us to distinguish 
   between natted and non-natted sources.

             reply	other threads:[~2011-02-09 16:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-09 16:26 Dave Täht [this message]
2011-02-09 18:11 ` Dave Täht

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

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

  git send-email \
    --in-reply-to=87sjvx5g39.fsf@cruithne.co.teklibre.org \
    --to=d@taht.net \
    --cc=bloat-devel@lists.bufferbloat.net \
    --cc=bloat@lists.bufferbloat.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