Re: [xrblock] Poll for progressing the QoE
Shida Schubert <shida@ntt-at.com> Thu, 02 February 2012 00:31 UTC
Return-Path: <shida@ntt-at.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 B5D2B11E811B for <xrblock@ietfa.amsl.com>; Wed, 1 Feb 2012 16:31:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.351
X-Spam-Level:
X-Spam-Status: No, score=-101.351 tagged_above=-999 required=5 tests=[AWL=-0.483, BAYES_00=-2.599, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334, MIME_QP_LONG_LINE=1.396, USER_IN_WHITELIST=-100]
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 9GYO9fU3rYZr for <xrblock@ietfa.amsl.com>; Wed, 1 Feb 2012 16:31:50 -0800 (PST)
Received: from gator465.hostgator.com (gator465.hostgator.com [69.56.174.130]) by ietfa.amsl.com (Postfix) with ESMTP id AA44D11E8132 for <xrblock@ietf.org>; Wed, 1 Feb 2012 16:31:50 -0800 (PST)
Received: from [125.198.20.177] (port=55384 helo=[192.168.1.10]) by gator465.hostgator.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <shida@ntt-at.com>) id 1RskaW-0006ls-4f; Wed, 01 Feb 2012 18:31:44 -0600
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: multipart/alternative; boundary="Apple-Mail=_5A786BF6-72A5-446E-9B6B-8CAE0AE6F4D5"
From: Shida Schubert <shida@ntt-at.com>
In-Reply-To: <580BEA5E3B99744AB1F5BFF5E9A3C67D135D8D23BC@HE111648.emea1.cds.t-internal.com>
Date: Thu, 02 Feb 2012 09:31:44 +0900
Message-Id: <CCF7849A-1914-497A-AB98-EBF23A8B461E@ntt-at.com>
References: <26098421.13561328059452312.JavaMail.root@ent8> <580BEA5E3B99744AB1F5BFF5E9A3C67D135D8D23BC@HE111648.emea1.cds.t-internal.com>
To: Roland.Schott@telekom.de
X-Mailer: Apple Mail (2.1251.1)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gator465.hostgator.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - ntt-at.com
X-BWhitelist: no
X-Source:
X-Source-Args:
X-Source-Dir:
X-Source-Sender: fl1-125-198-20-177.tky.mesh.ad.jp ([192.168.1.10]) [125.198.20.177]:55384
X-Source-Auth: shida@agnada.com
X-Email-Count: 1
X-Source-Cap: c3NoaWRhO3NzaGlkYTtnYXRvcjQ2NS5ob3N0Z2F0b3IuY29t
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: Thu, 02 Feb 2012 00:31:51 -0000
Thank you all for your feedbacks. I think I heard unanimous opinions about adopting the draft as is. I will get the author to submit the next version as a WG draft. Many Thanks and Regards Shida (as co-chair) On Feb 2, 2012, at 1:47 AM, <Roland.Schott@telekom.de> <Roland.Schott@telekom.de> wrote: > 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 > > 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
- [xrblock] Poll for progressing the QoE Shida Schubert
- Re: [xrblock] Poll for progressing the QoE Shida Schubert
- Re: [xrblock] Poll for progressing the QoE Glen Zorn
- Re: [xrblock] Poll for progressing the QoE zhaojing
- Re: [xrblock] Poll for progressing the QoE Roland.Schott
- Re: [xrblock] Poll for progressing the QoE Shida Schubert