Re: [xrblock] Poll for progressing the QoE

zhaojing@sttri.com.cn Wed, 01 February 2012 01:24 UTC

Return-Path: <zhaojing@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 1EDBD21F8450 for <xrblock@ietfa.amsl.com>; Tue, 31 Jan 2012 17:24:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.378
X-Spam-Level: **
X-Spam-Status: No, score=2.378 tagged_above=-999 required=5 tests=[AWL=-0.746, BAYES_50=0.001, HTML_MESSAGE=0.001, MIME_HTML_ONLY=1.457, SARE_RECV_IP_218078=1.666]
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 N1Qk6smBHHN2 for <xrblock@ietfa.amsl.com>; Tue, 31 Jan 2012 17:24:21 -0800 (PST)
Received: from corp.21cn.com (corp.forptr.21cn.com [121.14.129.40]) by ietfa.amsl.com (Postfix) with ESMTP id 97F7B21F844A for <xrblock@ietf.org>; Tue, 31 Jan 2012 17:24:19 -0800 (PST)
Received: from ip?218.80.215.132? (entas7.inner-hermes.com [10.27.101.7]) by corp.21cn.com (HERMES) with ESMTP id 2858D1A484B; Wed, 1 Feb 2012 09:24:12 +0800 (CST)
HMM_ATTACHE_NUM: 0000
HMM_SOURCE_IP: wmail.10.27.101.7.1021024556
HMM_SOURCE_TYPE: WEBMAIL
Received: from ip<218.80.215.132> ([218.80.215.132]) by 21CN-ent7(Yuwen filter gate 10.27.101.7) with ESMTP id 1328059447.30129 for shida@ntt-at.com ; Wed Feb 1 09:24:18 2012
X-FILTER-SCORE: to=<shida@ntt-at.comxrblock@ietf.org>, score=<1328059458udHEufGwh6RdddddHddEddx6kU2EOIbtxxxxx6xxkxxU>
Date: Wed, 01 Feb 2012 09:24:07 +0800
From: zhaojing@sttri.com.cn
To: Shida Schubert <shida@ntt-at.com>, xrblock <xrblock@ietf.org>
Message-ID: <26098421.13561328059452312.JavaMail.root@ent8>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----=_Part_1175_20397511.1328059447043"
HMM_WEBCLN_IP: 218.80.215.132
X-HERMES-SENDMODE: normal
Subject: Re: [xrblock] Poll for progressing the QoE
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: Wed, 01 Feb 2012 01:24:22 -0000

I have no strong opinion on which way to follow.
But I can see the 1st segment type can be widely supported
by various applications and used. The other two are complementary
to the first one. Especially the multi-channel audio segment type,
wouldn't VOIP implementer like to see this be standardized as being
measurement tool for stereo audio application?
 
Cheers!
JingZhao
------------------------------------------
 
----- Original Message -----
From: "Shida Schubert" <shida@ntt-at.com>
To: "xrblock" <xrblock@ietf.org>
Sent: Tuesday, January 31, 2012 1:34 PM
Subject: Re: [xrblock] Poll for progressing the QoE
 
 
>
> All;
>
> I need to see what WG thinks on the matter below for
> us to progress the QoE milestone.
>
> If you have no opinions on the matter, please indicate
> it as well.
>
> Many Thanks
>  Shida
>
> On Jan 19, 2012, at 8:58 PM, Shida Schubert wrote:
>
>>
>> All;
>>
>> Although a poll for draft-wu-xrblock-rtcp-xr-quality-monitoring ended in
>> favor of adopting the draft, the comments provided by Colin are worth
>> noting as we move forward.
>>
>> I do have some questions which I think will help us clarify
>> the way forward.
>>
>> A. There are three segment types defined (1. each media
>>   sent in separate RTP stream, 2. Layered video session,
>>   3. Multi-channel audio) in the draft,  do we see a need for
>>   all three right now or in near  future (say next 12 months) ?
>>
>> B. OR are we happy with only covering one for now (Likely
>>   the 1. as I understand people are most interested in the 1.)
>>   and create a draft when there is a real need for 2. and 3.?
>>
>> C. If answer is yes to question A., do we want to see the
>>   draft split into three as Colin proposed or have them all
>>   defined in single draft as it currently is.
>>
>> I asked the AD if we can split the drafts into 3 drafts under
>> single milestone but I want to make sure we do that after
>> we agree as a WG that we need all three segment types
>> RIGHT NOW before we do so.
>>
>> We have a lot of new items that people are interested in
>> working on that are not covered in our milestones, so I
>> want to make sure we focus on items that are "MUST
>> have" rather than "MAY need it in future" or "NICE to have".
>>
>> Regards
>> Shida
>> _______________________________________________
>> xrblock mailing list
>
> _______________________________________________
> xrblock mailing list