revolutions per minute - a new metric for measuring responsiveness
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Rpm <rpm@lists.bufferbloat.net>
Subject: [Rpm] Fwd: [ippm] I-D Action: draft-ietf-ippm-responsiveness-01.txt
Date: Mon, 11 Jul 2022 14:56:36 -0700	[thread overview]
Message-ID: <CAA93jw4xZQD0tWh-P2FrUxL7Pp1wrSHbE67G3CriWGUVVhufvA@mail.gmail.com> (raw)
In-Reply-To: <165757486192.5123.15413561746946302005@ietfa.amsl.com>

---------- Forwarded message ---------
From: <internet-drafts@ietf.org>
Date: Mon, Jul 11, 2022 at 2:27 PM
Subject: [ippm] I-D Action: draft-ietf-ippm-responsiveness-01.txt
To: <i-d-announce@ietf.org>
Cc: <ippm@ietf.org>



A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the IP Performance Measurement WG of the IETF.

        Title           : Responsiveness under Working Conditions
        Authors         : Christoph Paasch
                          Randall Meyer
                          Stuart Cheshire
                          Omer Shapira
                          Matt Mathis
  Filename        : draft-ietf-ippm-responsiveness-01.txt
  Pages           : 19
  Date            : 2022-07-11

Abstract:
   For many years, a lack of responsiveness, variously called lag,
   latency, or bufferbloat, has been recognized as an unfortunate, but
   common, symptom in today's networks.  Even after a decade of work on
   standardizing technical solutions, it remains a common problem for
   the end users.

   Everyone "knows" that it is "normal" for a video conference to have
   problems when somebody else at home is watching a 4K movie or
   uploading photos from their phone.  However, there is no technical
   reason for this to be the case.  In fact, various queue management
   solutions (fq_codel, cake, PIE) have solved the problem.

   Our networks remain unresponsive, not from a lack of technical
   solutions, but rather a lack of awareness of the problem and its
   solutions.  We believe that creating a tool whose measurement matches
   people's everyday experience will create the necessary awareness, and
   result in a demand for products that solve the problem.

   This document specifies the "RPM Test" for measuring responsiveness.
   It uses common protocols and mechanisms to measure user experience
   specifically when the network is under working conditions.  The
   measurement is expressed as "Round-trips Per Minute" (RPM) and should
   be included with throughput (up and down) and idle latency as
   critical indicators of network quality.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-ippm-responsiveness/

There is also an htmlized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-ippm-responsiveness-01

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-ippm-responsiveness-01


Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts


_______________________________________________
ippm mailing list
ippm@ietf.org
https://www.ietf.org/mailman/listinfo/ippm


-- 
FQ World Domination pending: https://blog.cerowrt.org/post/state_of_fq_codel/
Dave Täht CEO, TekLibre, LLC

           reply	other threads:[~2022-07-11 21:56 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <165757486192.5123.15413561746946302005@ietfa.amsl.com>]

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=CAA93jw4xZQD0tWh-P2FrUxL7Pp1wrSHbE67G3CriWGUVVhufvA@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --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