[xrblock] 答复: FW: New Version Notification for draft-huang-xrblock-rtcweb-rtcp-xr-metrics-02.txt

Qin Wu <bill.wu@huawei.com> Sat, 02 November 2013 21:26 UTC

Return-Path: <bill.wu@huawei.com>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D5D9421E80E7 for <xrblock@ietfa.amsl.com>; Sat, 2 Nov 2013 14:26:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.567
X-Spam-Level:
X-Spam-Status: No, score=-1.567 tagged_above=-999 required=5 tests=[AWL=-4.355, BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, CN_BODY_35=0.339, MIME_8BIT_HEADER=0.3, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-4, SARE_SUB_ENC_GB2312=1.345]
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 8tNGnjd+D0qg for <xrblock@ietfa.amsl.com>; Sat, 2 Nov 2013 14:26:11 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 5CFAC11E813D for <xrblock@ietf.org>; Sat, 2 Nov 2013 14:26:11 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id AZU24730; Sat, 02 Nov 2013 21:26:09 +0000 (GMT)
Received: from LHREML402-HUB.china.huawei.com (10.201.5.241) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.158.1; Sat, 2 Nov 2013 21:25:39 +0000
Received: from NKGEML401-HUB.china.huawei.com (10.98.56.32) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.3.158.1; Sat, 2 Nov 2013 21:26:07 +0000
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.75]) by nkgeml401-hub.china.huawei.com ([10.98.56.32]) with mapi id 14.03.0158.001; Sun, 3 Nov 2013 05:25:51 +0800
From: Qin Wu <bill.wu@huawei.com>
To: "Huangyihong (Rachel)" <rachel.huang@huawei.com>, xrblock <xrblock@ietf.org>
Thread-Topic: [xrblock] FW: New Version Notification for draft-huang-xrblock-rtcweb-rtcp-xr-metrics-02.txt
Thread-Index: AQHOyuTaTpwMaQRXxEurIjSU/g3h35n4NYzQgBpXVgA=
Date: Sat, 02 Nov 2013 21:25:50 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA43C33630@nkgeml501-mbs.china.huawei.com>
References: <51E6A56BD6A85142B9D172C87FC3ABBB458C3C9F@nkgeml501-mbs.china.huawei.com>
In-Reply-To: <51E6A56BD6A85142B9D172C87FC3ABBB458C3C9F@nkgeml501-mbs.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.47.152.63]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: [xrblock] 答复: FW: New Version Notification for draft-huang-xrblock-rtcweb-rtcp-xr-metrics-02.txt
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xrblock>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 02 Nov 2013 21:26:16 -0000

For browser to browser communication, why statistics related to transport need to be sent to web server using Web API? What web server can do about it if one side of communication quality downgrades or both sides downgrade?
Can web server redirect the statistics collocated by one web browser to another web browser?

Regards!
-Qin
-----邮件原件-----
发件人: xrblock-bounces@ietf.org [mailto:xrblock-bounces@ietf.org] 代表 Huangyihong (Rachel)
发送时间: 2013年10月17日 11:15
收件人: xrblock
主题: [xrblock] FW: New Version Notification for draft-huang-xrblock-rtcweb-rtcp-xr-metrics-02.txt

Dear all,

In this new version, we adjust the organization of the metrics, which are now arranged in the descending order of importance. Comments are appreciated.

Best regards,
Rachel


-----Original Message-----
From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
Sent: Thursday, October 17, 2013 10:59 AM
To: Dan Romascanu; Varun Singh; Huangyihong (Rachel); Roni Even
Subject: New Version Notification for draft-huang-xrblock-rtcweb-rtcp-xr-metrics-02.txt


A new version of I-D, draft-huang-xrblock-rtcweb-rtcp-xr-metrics-02.txt
has been successfully submitted by Rachel Huang and posted to the
IETF repository.

Filename:	 draft-huang-xrblock-rtcweb-rtcp-xr-metrics
Revision:	 02
Title:		 Considerations for Selecting RTCP Extended Report (XR) Metrics for the RTCWEB Statistics API
Creation date:	 2013-10-17
Group:		 Individual Submission
Number of pages: 12
URL:             http://www.ietf.org/internet-drafts/draft-huang-xrblock-rtcweb-rtcp-xr-metrics-02.txt
Status:          http://datatracker.ietf.org/doc/draft-huang-xrblock-rtcweb-rtcp-xr-metrics
Htmlized:        http://tools.ietf.org/html/draft-huang-xrblock-rtcweb-rtcp-xr-metrics-02
Diff:            http://www.ietf.org/rfcdiff?url2=draft-huang-xrblock-rtcweb-rtcp-xr-metrics-02

Abstract:
   This document describes monitoring features related to RTCWEB. It
   provides a list of RTCP XR metrics that are useful and may need to be
   supported in some RTCWEB implementations.


                                                                                  


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat

_______________________________________________
xrblock mailing list
xrblock@ietf.org
https://www.ietf.org/mailman/listinfo/xrblock