Re: [xrblock] Poll for progressing the QoE

<Roland.Schott@telekom.de> Wed, 01 February 2012 16:47 UTC

Return-Path: <Roland.Schott@telekom.de>
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 F20D921F87F8 for <xrblock@ietfa.amsl.com>; Wed, 1 Feb 2012 08:47:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.949
X-Spam-Level:
X-Spam-Status: No, score=-1.949 tagged_above=-999 required=5 tests=[AWL=1.300, BAYES_00=-2.599, HELO_EQ_DE=0.35, HTML_MESSAGE=0.001, 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 5Gfk5tVXuSr7 for <xrblock@ietfa.amsl.com>; Wed, 1 Feb 2012 08:47:42 -0800 (PST)
Received: from tcmail73.telekom.de (tcmail73.telekom.de [217.243.239.135]) by ietfa.amsl.com (Postfix) with ESMTP id 530A621F87AD for <xrblock@ietf.org>; Wed, 1 Feb 2012 08:47:39 -0800 (PST)
Received: from he111628.emea1.cds.t-internal.com ([10.134.93.20]) by tcmail71.telekom.de with ESMTP/TLS/AES128-SHA; 01 Feb 2012 17:47:37 +0100
Received: from HE111648.emea1.cds.t-internal.com ([169.254.5.157]) by HE111628.emea1.cds.t-internal.com ([::1]) with mapi; Wed, 1 Feb 2012 17:47:37 +0100
From: Roland.Schott@telekom.de
To: zhaojing@sttri.com.cn, shida@ntt-at.com
Date: Wed, 01 Feb 2012 17:47:36 +0100
Thread-Topic: [xrblock] Poll for progressing the QoE
Thread-Index: AczggFGAPjFgXJd7RS61HcpR0zlOdgAfjIvw
Message-ID: <580BEA5E3B99744AB1F5BFF5E9A3C67D135D8D23BC@HE111648.emea1.cds.t-internal.com>
References: <26098421.13561328059452312.JavaMail.root@ent8>
In-Reply-To: <26098421.13561328059452312.JavaMail.root@ent8>
Accept-Language: en-US, de-DE
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US, de-DE
Content-Type: multipart/alternative; boundary="_000_580BEA5E3B99744AB1F5BFF5E9A3C67D135D8D23BCHE111648emea1_"
MIME-Version: 1.0
Cc: xrblock@ietf.org
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 16:47:45 -0000

Dear all,

in my opinion one should start with the draft as it is.
The different report types fit into the monitoring architecture
and it makes sense to have them within one year.
I think the other two media types are complementary to the first one.
Since one do not want to combine them it makes sense to have them in
one standard making this standard more complete.

A split into different drafts is in the end more effort.

Best Regards

Roland Schott

Deutsche Telekom Netzproduktion GmbH
Fixed Mobile Engineering Germany
Roland Schott
Heinrich-Hertz-Straße 3-7, 64295 Darmstadt, Germany
+49 6151 581 2823 (Tel.)
+49 6151 581 3393 (Fax)
+49 170   586 7840 (Mobil)
http://www.telekom.com<http://www.telekom.com/>

Deutsche Telekom Netzproduktion GmbH
Supervisory Board: Timotheus Höttges (Chairman)
Managing Board: Dr. Bruno Jacobfeuerborn (Chairman), Albert Matheis, Klaus Peren
Commercial register: Amtsgericht Bonn HRB 14190
Registered office: Bonn
VAT ident. no.: DE 814645262

Life is for sharing.




________________________________
Von: xrblock-bounces@ietf.org [mailto:xrblock-bounces@ietf.org] Im Auftrag von zhaojing@sttri.com.cn
Gesendet: Mittwoch, 1. Februar 2012 02:24
An: Shida Schubert; xrblock
Betreff: Re: [xrblock] Poll for progressing the QoE

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@ietf.org
>> https://www.ietf.org/mailman/listinfo/xrblock
>
> _______________________________________________
> xrblock mailing list
> xrblock@ietf.org
> https://www.ietf.org/mailman/listinfo/xrblock