IETF Logo Mail Archive

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

Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com> Wed, 16 November 2011 15:35 UTC

Return-Path: <stefan.lk.hakansson@ericsson.com>
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 3C65311E8096 for <rtcweb@ietfa.amsl.com>; Wed, 16 Nov 2011 07:35:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.153
X-Spam-Level:
X-Spam-Status: No, score=-6.153 tagged_above=-999 required=5 tests=[AWL=0.146, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
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 Di6pkLI155rK for <rtcweb@ietfa.amsl.com>; Wed, 16 Nov 2011 07:35:13 -0800 (PST)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by ietfa.amsl.com (Postfix) with ESMTP id 3842A11E8095 for <rtcweb@ietf.org>; Wed, 16 Nov 2011 07:35:12 -0800 (PST)
X-AuditID: c1b4fb3d-b7c26ae0000035b9-f5-4ec3d82ed25f
Received: from esessmw0197.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id C6.AB.13753.E28D3CE4; Wed, 16 Nov 2011 16:35:11 +0100 (CET)
Received: from [150.132.142.220] (153.88.115.8) by esessmw0197.eemea.ericsson.se (153.88.115.88) with Microsoft SMTP Server id 8.3.137.0; Wed, 16 Nov 2011 16:35:10 +0100
Message-ID: <4EC3D82D.8040902@ericsson.com>
Date: Wed, 16 Nov 2011 16:35:09 +0100
From: Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.23) Gecko/20110922 Lightning/1.0b2 Thunderbird/3.1.15
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <CAAJUQMjP1aTk6T_angdjt0v6p1FSQPHzjppe1_SRNKBmoHdNJA@mail.gmail.com>
In-Reply-To: <CAAJUQMjP1aTk6T_angdjt0v6p1FSQPHzjppe1_SRNKBmoHdNJA@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAA==
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 15:35:14 -0000

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!

>
>
> Wolfgang Beck
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb

v2.23.0 | Report a Bug | By Email