I already posted this to the RPM-list, but the audience here on bloat should
be interested as well.
This is the specification of Apple's responsiveness/RPM test. We believe that it
would be good for the bufferbloat-effort to have a specification of how to
quantify the extend of bufferbloat from a user's perspective. Our
Internet-draft is a first step in that direction and we hope that it will
kick off some collaboration.
Feedback is very welcome!
Cheers,
Christoph
----- Forwarded message from internet-drafts at ietf.org -----
From: internet-drafts at ietf.org
To: Christoph Paasch <cpaasch at apple.com>, Omer Shapira <oesh at apple.com>, Randall Meyer <rrm at apple.com>, Stuart Cheshire
<cheshire at apple.com>
Date: Fri, 13 Aug 2021 09:43:40 -0700
Subject: New Version Notification for draft-cpaasch-ippm-responsiveness-00.txt
A new version of I-D, draft-cpaasch-ippm-responsiveness-00.txt
has been successfully submitted by Christoph Paasch and posted to the
IETF repository.
Name: draft-cpaasch-ippm-responsiveness
Revision: 00
Title: Responsiveness under Working Conditions
Document date: 2021-08-13
Group: Individual Submission
Pages: 12
URL: https://www.ietf.org/archive/id/draft-cpaasch-ippm-responsiveness-00.txt
Status: https://datatracker.ietf.org/doc/draft-cpaasch-ippm-responsiveness/
Htmlized: https://datatracker.ietf.org/doc/html/draft-cpaasch-ippm-responsiveness
Abstract:
Bufferbloat has been a long-standing problem on the Internet with
more than a decade of work on standardizing technical solutions,
implementations and testing. However, to this date, bufferbloat is
still a very common problem for the end-users. Everyone "knows" that
it is "normal" for a video conference to have problems when somebody
else on the same home-network is watching a 4K movie.
The reason for this problem is not the lack of technical solutions,
but rather a lack of awareness of the problem-space, and a lack of
tooling to accurately measure the problem. We believe that exposing
the problem of bufferbloat to the end-user by measuring the end-
users' experience at a high level will help to create the necessary
awareness.
This document is a first attempt at specifying a measurement
methodology to evaluate bufferbloat the way common users are
experiencing it today, using today's most frequently used protocols
and mechanisms to accurately measure the user-experience. We also
provide a way to express the bufferbloat as a measure of "Round-trips
per minute" (RPM) to have a more intuitive way for the users to
understand the notion of bufferbloat.
The IETF Secretariat
----- End forwarded message -----