General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Juliusz Chroboczek <jch@irif.fr>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: Bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] goresponsiveness learned a few tricks...
Date: Mon, 08 Jan 2024 22:04:23 +0100	[thread overview]
Message-ID: <871qareduw.wl-jch@irif.fr> (raw)
In-Reply-To: <E4D12B5F-8888-4D87-A71F-9E28CEA35145@gmx.de>

> (h++ps://github.com/network-quality/draft-ietf-ippm-responsiveness).

There's quite a few good ideas in this draft, but the one that I find
intriguing is reporting RTT values in RPM (units of 1/60 Hz) rather than
milliseconds.

I wonder how well this works.  I'll experiment with undergrads.

-- Juliusz

  reply	other threads:[~2024-01-08 21:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-08 19:41 Sebastian Moeller
2024-01-08 21:04 ` Juliusz Chroboczek [this message]
2024-01-08 21:53   ` Sebastian Moeller
2024-01-08 23:15     ` David Schinazi
2024-01-09  7:18       ` Sebastian Moeller
2024-01-09 14:05       ` Michael Richardson

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=871qareduw.wl-jch@irif.fr \
    --to=jch@irif.fr \
    --cc=bloat@lists.bufferbloat.net \
    --cc=moeller0@gmx.de \
    /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