Re: [xrblock] Call for adopting xr-quality-monitoring-06 as WG item

zhangyx@sttri.com.cn Tue, 20 December 2011 06:34 UTC

Return-Path: <zhangyx@sttri.com.cn>
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 381AC11E80CA for <xrblock@ietfa.amsl.com>; Mon, 19 Dec 2011 22:34:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.802
X-Spam-Level: *
X-Spam-Status: No, score=1.802 tagged_above=-999 required=5 tests=[AWL=1.300, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_HTML_ONLY=1.457, RCVD_IN_NJABL_PROXY=1.643]
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 oTLu4QYmVvxr for <xrblock@ietfa.amsl.com>; Mon, 19 Dec 2011 22:34:42 -0800 (PST)
Received: from corp.21cn.com (corp.forptr.21cn.com [121.14.129.40]) by ietfa.amsl.com (Postfix) with ESMTP id EEFED11E809D for <xrblock@ietf.org>; Mon, 19 Dec 2011 22:34:40 -0800 (PST)
Received: from ip?218.2.129.2? (entas7.inner-hermes.com [10.27.101.7]) by corp.21cn.com (HERMES) with ESMTP id B98751A48C7 for <xrblock@ietf.org>; Tue, 20 Dec 2011 14:34:34 +0800 (CST)
HMM_ATTACHE_NUM: 0000
HMM_SOURCE_IP: wmail.10.27.101.7.70368187
HMM_SOURCE_TYPE: WEBMAIL
Received: from ip<218.2.129.2> ([218.2.129.2]) by 21CN-ent7(Yuwen filter gate 10.27.101.7) with ESMTP id 1324362872.9242 for xrblock@ietf.org ; Tue Dec 20 14:34:40 2011
0/X-Total-Score: 3:
X-FILTER-SCORE: to=<xrblock@ietf.org>, score=<1324362880aBBFBhp7YaF5yjBB7BBYBB4MMJMlyFB4Jqg+MMFMMBMM>
Date: Tue, 20 Dec 2011 14:34:31 +0800
From: zhangyx@sttri.com.cn
To: xrblock <xrblock@ietf.org>
Message-ID: <7394309.1341324362874840.JavaMail.root@ent11>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----=_Part_140_23275436.1324362871648"
HMM_WEBCLN_IP: 218.2.129.2
X-HERMES-SENDMODE: normal
Subject: Re: [xrblock] Call for adopting xr-quality-monitoring-06 as WG item
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: Tue, 20 Dec 2011 06:34:43 -0000

Hi, :
The new update of xr-quality-monitoring-06 reflects merging outcome and supports each MoS type reporting in a single XR Block. Also in our understanding, this draft supports per SSRC reporting and per sub stream reporting, per audio channel reporting. all these changes look reasonable to us, comparing with the previous version.
As we indicated before, we support this work being moved forward.
 
 Regards!
Sunshine
Shanghai Institute of China Telecom
________________________________________
发件人: xrblock-bounces@ietf.org [xrblock-bounces@ietf.org] 代表 Shida Schubert [shida@ntt-at.com]
发送时间: 2011年12月19日 19:55
到: xrblock@ietf.org
主题: [xrblock] Call for adopting xr-quality-monitoring-06 as WG item
 This is a call to see whether people are happy
with the latest xr-quality-monitoring-06 draft for addressing
the milestone "QoE Metrics Reporting".
 xr-que-00 which used to be an AVT draft also addresses
the same milestone.
 The xr-quality-monitoring-06 claims to merge the two
into one.
 Please response to express your option for the followings.
 1. Adopt the draft-wu-xrblock-rtcp-xr-quality-monitoring-06 as a WG item.
 2. Not ready to adopt.
   * Would be very helpful if you provide your reasonings.
 Regards
  Shida (as chair)
_______________________________________________
xrblock mailing list
xrblock@ietf.org
https://www.ietf.org/mailman/listinfo/xrblock" rel="nofollow">https://www.ietf.org/mailman/listinfo/xrblock