revolutions per minute - a new metric for measuring responsiveness
 help / color / mirror / Atom feed
From: "Lucas Pardue" <lucas@lucaspardue.com>
To: rjmcmahon <rjmcmahon=40rjmcmahon.com@dmarc.ietf.org>,
	"Christoph Paasch" <cpaasch@apple.com>
Cc: Rpm <rpm@lists.bufferbloat.net>, "IETF IPPM WG" <ippm@ietf.org>
Subject: Re: [Rpm] [ippm]   draft-ietf-ippm-responsiveness
Date: Fri, 19 Jan 2024 21:40:27 +0000	[thread overview]
Message-ID: <d2561d74-a9bf-4995-9f83-5994db31b53a@app.fastmail.com> (raw)
In-Reply-To: <966b41f794e95ca8675d613ca84d22a8@rjmcmahon.com>

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

Punting on OWD seems fine to me. It's nice but it's more work. This draft is close to done. We can extend RPM directly or indirectly with enhancements in this WG, sounds exciting potential.

I'm partly suggestion OWD punting because we've have had proposals presented in the QUIC WG for how to do that in the transport layer. Measurements methods defined in IPPM could benefit from that. I see a document giving sufficient treatment to the options as some that deserves ample time time to gather consensus.

Cheers
Lucas


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

      reply	other threads:[~2024-01-19 21:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-03 18:13 [Rpm] draft-ietf-ippm-responsiveness Sebastian Moeller
2024-01-16 19:01 ` [Rpm] [ippm] draft-ietf-ippm-responsiveness Christoph Paasch
2024-01-19 13:14   ` Sebastian Moeller
2024-01-19 18:57     ` Christoph Paasch
2024-01-19 20:35       ` rjmcmahon
2024-01-19 21:40         ` Lucas Pardue [this message]

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/rpm.lists.bufferbloat.net/

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

  git send-email \
    --in-reply-to=d2561d74-a9bf-4995-9f83-5994db31b53a@app.fastmail.com \
    --to=lucas@lucaspardue.com \
    --cc=cpaasch@apple.com \
    --cc=ippm@ietf.org \
    --cc=rjmcmahon=40rjmcmahon.com@dmarc.ietf.org \
    --cc=rpm@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