IETF Logo Mail Archive

Re: [rtcweb] draft-ietf-rtcweb-use-cases-and-requirements-06.txt, A12, monitoring quality

Harald Alvestrand <harald@alvestrand.no> Wed, 16 November 2011 16:21 UTC

Return-Path: <harald@alvestrand.no>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB75A21F8E5F for <rtcweb@ietfa.amsl.com>; Wed, 16 Nov 2011 08:21:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.432
X-Spam-Level:
X-Spam-Status: No, score=-110.432 tagged_above=-999 required=5 tests=[AWL=-0.133, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Rz8+nzgJNH+S for <rtcweb@ietfa.amsl.com>; Wed, 16 Nov 2011 08:21:30 -0800 (PST)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id 54C7121F8E60 for <rtcweb@ietf.org>; Wed, 16 Nov 2011 08:21:30 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 3F87839E11A; Wed, 16 Nov 2011 17:21:29 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QjNjdZ8D9KIx; Wed, 16 Nov 2011 17:21:28 +0100 (CET)
Received: from [130.129.67.10] (dhcp-430a.meeting.ietf.org [130.129.67.10]) by eikenes.alvestrand.no (Postfix) with ESMTPS id EA6FA39E072; Wed, 16 Nov 2011 17:21:27 +0100 (CET)
Message-ID: <4EC3E305.6080808@alvestrand.no>
Date: Thu, 17 Nov 2011 00:21:25 +0800
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.23) Gecko/20110921 Thunderbird/3.1.15
MIME-Version: 1.0
To: Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>
References: <CAAJUQMjP1aTk6T_angdjt0v6p1FSQPHzjppe1_SRNKBmoHdNJA@mail.gmail.com> <4EC3D82D.8040902@ericsson.com>
In-Reply-To: <4EC3D82D.8040902@ericsson.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] draft-ietf-rtcweb-use-cases-and-requirements-06.txt, A12, monitoring quality
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Nov 2011 16:21:31 -0000

On 11/16/2011 11:35 PM, Stefan Håkansson LK wrote:
> On 11/02/2011 03:33 PM, Wolfgang Beck wrote:
>> Section 5.2, Browser Requirements
>> "   A12             The Web API MUST provide means for
>>                     informing the web application when high
>>                     loss rates occur."
>>
>> Wouldn't it make sense to have a more general API that provides access
>> to RTP/RTCP performance counters? A smart JS client might analyze the
>> counters and suggest solutions, like 'fix your fine NAT
>> configuration'. Providers like to see that data to detect and fix
>> problems, too.
>
> Sounds like a good idea to me, and we reasoned along these lines at 
> the W3C meeting the other week. I think there is even an action on 
> someone to draft that API!
It's even in the WEBRTC Tracker, assigned to Adam Bergkvist on behalf of 
the editing team:

http://www.w3.org/2011/04/webrtc/track/actions/12

All input is welcome - on public-webrtc@w3.org!

                     Harald

v2.23.0 | Report a Bug | By Email