From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ma1-aaemail-dr-lapp03.apple.com (ma1-aaemail-dr-lapp03.apple.com [17.171.2.72]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 1ED2A3B29D for ; Fri, 13 Aug 2021 14:28:28 -0400 (EDT) Received: from pps.filterd (ma1-aaemail-dr-lapp03.apple.com [127.0.0.1]) by ma1-aaemail-dr-lapp03.apple.com (8.16.0.42/8.16.0.42) with SMTP id 17DIOQ54033562 for ; Fri, 13 Aug 2021 11:28:27 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=date : from : to : cc : subject : message-id : references : mime-version : content-type : in-reply-to; s=20180706; bh=A4+MKj/fUotiZ15m8Rofmt4i6nafVYOJcXjQ6+wZRPA=; b=tO2NlnXopf9W4lBMGZ86Ti0krBva5wX2AfZtsD85tRmyvepFsb7pRGehovi6CNelMbWf QiOaibtE491fSM+VJAKCYDLJG0DaR+PPT1uWvbBxcaefP92bJy5hHVp/5yCWjdvjsTKI niIgDi0z4xledi0VTKyMHi/MTV4m6LDZ68jYQwLrKnHbWWbk3kpMaolHwi6VoZl6uYKw xj1pYA8u9DfW2zfgwP7urixOTaVc+AUDUz0Hm9XJ9EJU3mlSSZFbY1Lqs2tRk7kJxxVx e6Lj00AD/wISnx6cXOoiUr1ja2LaIetJASSAKhCnfsn/wDC4jVuNBQYYmbUH8Df+IpIw sg== Received: from rn-mailsvcp-mta-lapp03.rno.apple.com (rn-mailsvcp-mta-lapp03.rno.apple.com [10.225.203.151]) by ma1-aaemail-dr-lapp03.apple.com with ESMTP id 3a9s5xcmva-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Fri, 13 Aug 2021 11:28:27 -0700 Received: from rn-mailsvcp-mmp-lapp03.rno.apple.com (rn-mailsvcp-mmp-lapp03.rno.apple.com [17.179.253.16]) by rn-mailsvcp-mta-lapp03.rno.apple.com (Oracle Communications Messaging Server 8.1.0.9.20210415 64bit (built Apr 15 2021)) with ESMTPS id <0QXS0079XJBFQL50@rn-mailsvcp-mta-lapp03.rno.apple.com> for rpm@lists.bufferbloat.net; Fri, 13 Aug 2021 11:28:27 -0700 (PDT) Received: from process_milters-daemon.rn-mailsvcp-mmp-lapp03.rno.apple.com by rn-mailsvcp-mmp-lapp03.rno.apple.com (Oracle Communications Messaging Server 8.1.0.9.20210415 64bit (built Apr 15 2021)) id <0QXS00100J4RE900@rn-mailsvcp-mmp-lapp03.rno.apple.com>; Fri, 13 Aug 2021 11:28:27 -0700 (PDT) X-Va-A: X-Va-T-CD: d45ceb60b5a47d7d6a8dc5a84aa7ab12 X-Va-E-CD: 857b3c954b01505a75850072fd1e7a86 X-Va-R-CD: 85ffb5ddaa5ccb972f1a3548bf1c3f1a X-Va-CD: 0 X-Va-ID: 08a4bc5e-5e84-46be-9c35-62a8cd0657d4 X-V-A: X-V-T-CD: d45ceb60b5a47d7d6a8dc5a84aa7ab12 X-V-E-CD: 857b3c954b01505a75850072fd1e7a86 X-V-R-CD: 85ffb5ddaa5ccb972f1a3548bf1c3f1a X-V-CD: 0 X-V-ID: 9d1139cf-1808-4376-a1db-2088c380b21f X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.391, 18.0.790 definitions=2021-08-13_06:2021-08-13, 2021-08-13 signatures=0 Received: from localhost ([17.192.155.152]) by rn-mailsvcp-mmp-lapp03.rno.apple.com (Oracle Communications Messaging Server 8.1.0.9.20210415 64bit (built Apr 15 2021)) with ESMTPSA id <0QXS00ND4JBE9C00@rn-mailsvcp-mmp-lapp03.rno.apple.com>; Fri, 13 Aug 2021 11:28:26 -0700 (PDT) Date: Fri, 13 Aug 2021 11:28:25 -0700 From: Christoph Paasch To: rpm@lists.bufferbloat.net, Omer Shapira Message-id: References: MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline In-reply-to: X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.391, 18.0.790 definitions=2021-08-13_07:2021-08-13, 2021-08-13 signatures=0 Subject: Re: [Rpm] Fwd: New Version Notification for draft-cpaasch-ippm-responsiveness-00.txt X-BeenThere: rpm@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: revolutions per minute - a new metric for measuring responsiveness List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Aug 2021 18:28:28 -0000 ++ the other co-authors that somehow didn't make it on the CC-list :-/ On 08/13/21 - 10:15, Christoph Paasch via Rpm wrote: > 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 , Omer Shapira , Randall Meyer , Stuart Cheshire > 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 ----- > _______________________________________________ > Rpm mailing list > Rpm@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/rpm