<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-ippm-responsiveness" target="https://datatracker.ietf.org/doc/html/draft-ietf-ippm-responsiveness-08">
   <front>
      <title>Responsiveness under Working Conditions</title>
      <author initials="C." surname="Paasch" fullname="Christoph Paasch">
         </author>
      <author initials="R." surname="Meyer" fullname="Randall Meyer">
         <organization>Apple Inc.</organization>
      </author>
      <author initials="S." surname="Cheshire" fullname="Stuart Cheshire">
         <organization>Apple Inc.</organization>
      </author>
      <author initials="W." surname="Hawkins" fullname="Will Hawkins">
         <organization>University of Cincinnati</organization>
      </author>
      <date month="October" day="20" year="2025" />
      <abstract>
	 <t>   For many years, a lack of responsiveness, variously called lag,
   latency, or bufferbloat, has been recognized as an unfortunate, but
   common, symptom in today&#x27;s networks.  Even after a decade of work on
   standardizing technical solutions, it remains a common problem for
   the end users.

   Everyone &quot;knows&quot; that it is &quot;normal&quot; 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 have solved the problem.

   Our network connections continue to suffer from an unacceptable
   amount of delay, not for a lack of technical solutions, but rather a
   lack of awareness of the problem and deployment of its solutions.  We
   believe that creating a tool that measures the problem and matches
   people&#x27;s everyday experience will create the necessary awareness, and
   result in a demand for solutions.

   This document specifies the &quot;Responsiveness Test&quot; 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 &quot;Round-trips Per Minute&quot;
   (RPM) and should be included with goodput (up and down) and idle
   latency as critical indicators of network quality.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-ippm-responsiveness-08" />
   
</reference>
