[Rpm] Fwd: New Version Notification for draft-cpaasch-ippm-responsiveness-00.txt

[Christoph Paasch <cpaasch@apple.com>]

Hello RPM-list,

please see below our IETF-draft submission that specifies the methodology
used to measure "Responsiveness under working conditions" the way it is
currently implemented in the upcoming iOS and macOS releases.

We believe that this document could be a good starting point to create a
formal specification for a methodology to quantify bufferbloat from the
end-user's perspective (meaning, the way end-users most commonly experience
it).


Feedback is very welcome!

Thanks,
Christoph & co-authors


----- Forwarded message from internet-drafts@ietf.org -----

From: internet-drafts@ietf.org
To: Christoph Paasch <cpaasch@apple.com>, Omer Shapira <oesh@apple.com>, Randall Meyer <rrm@apple.com>, Stuart Cheshire <cheshire@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 -----