[rtcweb] draft-ietf-rtcweb-use-cases-and-requirements-06.txt, A12, monitoring quality
Wolfgang Beck <wolfgang.beck01@googlemail.com> Wed, 02 November 2011 14:33 UTC
Return-Path: <wolfgang.beck01@googlemail.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 21E5B11E80DA for <rtcweb@ietfa.amsl.com>; Wed, 2 Nov 2011 07:33:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.94
X-Spam-Level:
X-Spam-Status: No, score=-2.94 tagged_above=-999 required=5 tests=[AWL=0.037, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
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 ymTHbD0sksDb for <rtcweb@ietfa.amsl.com>; Wed, 2 Nov 2011 07:33:52 -0700 (PDT)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by ietfa.amsl.com (Postfix) with ESMTP id 785BD11E808A for <rtcweb@ietf.org>; Wed, 2 Nov 2011 07:33:52 -0700 (PDT)
Received: by qadc10 with SMTP id c10so284910qad.31 for <rtcweb@ietf.org>; Wed, 02 Nov 2011 07:33:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=gb4wb8ZOJ8IGaJ5pKjLbZJ6dDIUGYHuh4FCESW8kkWI=; b=GNgw8Bq1VqQF7BCsVFJKjldSOWW/j7oU0JLLMUXsqncoCI1d68RigIQZ6xzU4LEexs OhZoScIlhTncGZDZaM411cM7/iYqwDJmsBU1+gexFRfQ7+c4mRfu+/hcVDNNwSmEGRXH D8BxU/nQoFKPZjsWzrrWVHJVBkQml579tuOng=
MIME-Version: 1.0
Received: by 10.68.12.104 with SMTP id x8mr5200888pbb.79.1320244431481; Wed, 02 Nov 2011 07:33:51 -0700 (PDT)
Received: by 10.68.64.66 with HTTP; Wed, 2 Nov 2011 07:33:51 -0700 (PDT)
Date: Wed, 02 Nov 2011 15:33:51 +0100
Message-ID: <CAAJUQMjP1aTk6T_angdjt0v6p1FSQPHzjppe1_SRNKBmoHdNJA@mail.gmail.com>
From: Wolfgang Beck <wolfgang.beck01@googlemail.com>
To: "<rtcweb@ietf.org>" <rtcweb@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"
Subject: [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, 02 Nov 2011 14:33:53 -0000
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.
Wolfgang Beck
- [rtcweb] draft-ietf-rtcweb-use-cases-and-requirem… Wolfgang Beck
- Re: [rtcweb] draft-ietf-rtcweb-use-cases-and-requ… Harald Alvestrand
- Re: [rtcweb] draft-ietf-rtcweb-use-cases-and-requ… Stefan Håkansson LK
- Re: [rtcweb] draft-ietf-rtcweb-use-cases-and-requ… Harald Alvestrand