IETF Logo Mail Archive

Re: [xrblock] XRBLOCK WG meeting at IETF 93?

"Huangyihong (Rachel)" <rachel.huang@huawei.com> Tue, 12 May 2015 00:36 UTC

Return-Path: <rachel.huang@huawei.com>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 91C531A89E0 for <xrblock@ietfa.amsl.com>; Mon, 11 May 2015 17:36:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z42T7JkuBxMR for <xrblock@ietfa.amsl.com>; Mon, 11 May 2015 17:36:25 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C91B71A89D3 for <xrblock@ietf.org>; Mon, 11 May 2015 17:36:24 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml404-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BSJ90516; Tue, 12 May 2015 00:36:23 +0000 (GMT)
Received: from nkgeml409-hub.china.huawei.com (10.98.56.40) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 12 May 2015 01:36:22 +0100
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.244]) by nkgeml409-hub.china.huawei.com ([10.98.56.40]) with mapi id 14.03.0158.001; Tue, 12 May 2015 08:36:18 +0800
From: "Huangyihong (Rachel)" <rachel.huang@huawei.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>, "xrblock@ietf.org" <xrblock@ietf.org>
Thread-Topic: [xrblock] XRBLOCK WG meeting at IETF 93?
Thread-Index: AdCAygUWtU7IfXqzSa6Fa5c3cNZIkwK/UwxgACD9jkA=
Date: Tue, 12 May 2015 00:36:17 +0000
Message-ID: <51E6A56BD6A85142B9D172C87FC3ABBB86311513@nkgeml501-mbs.china.huawei.com>
References: <9904FB1B0159DA42B0B887B7FA8119CA5CA00004@AZ-FFEXMB04.global.avaya.com> <9904FB1B0159DA42B0B887B7FA8119CA5CA278BE@AZ-FFEXMB04.global.avaya.com>
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA5CA278BE@AZ-FFEXMB04.global.avaya.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.138.41.144]
Content-Type: multipart/alternative; boundary="_000_51E6A56BD6A85142B9D172C87FC3ABBB86311513nkgeml501mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/xrblock/9IFEDKFXfiUOtx5CQPsN2uOk8dY>
Subject: Re: [xrblock] XRBLOCK WG meeting at IETF 93?
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.15
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, 12 May 2015 00:36:28 -0000

Hi Dan,

Sorry to miss this email. I think video loss concealment should be discussed in next meeting. Maybe one hour is enough. Old conflicts are okay to me.

BR,
Rachel

From: xrblock [mailto:xrblock-bounces@ietf.org] On Behalf Of Romascanu, Dan (Dan)
Sent: Monday, May 11, 2015 4:55 PM
To: xrblock@ietf.org
Subject: Re: [xrblock] XRBLOCK WG meeting at IETF 93?

Hi,

I did not see any reply to this mail, no opinion one way or another. No answer is interpreted as 'no need to meet' - but I would like to avoid the situation at IETF 92 when we decided not to meet based on the same non-responses to the chairs call and a few folks came later (and too late) and said that they would have used a meeting.

We have two active documents, which actually should be revised soon, and possibly sent to WGLC.

http://datatracker.ietf.org/doc/draft-ietf-xrblock-rtcp-xr-video-lc/
http://datatracker.ietf.org/doc/draft-ietf-xrblock-rtcweb-rtcp-xr-metrics/

So, please let the WG know if you believe we should meet at IETF 93 or if you believe that we should not meet at IETF 93.

Thanks and Regards,

Dan



From: xrblock [mailto:xrblock-bounces@ietf.org] On Behalf Of Romascanu, Dan (Dan)
Sent: Monday, April 27, 2015 12:11 PM
To: xrblock@ietf.org<mailto:xrblock@ietf.org>
Subject: [xrblock] XRBLOCK WG meeting at IETF 93?

Hi,

It's time to discuss scheduling of the meeting for the XRBLOCK WG at IETF 93.


-          Do we need to meet or can we do the work on the list?

-          If yes, is one hour enough?

-          If yes, are there any new conflicts that we MUST avoid? Are there any older conflicts that we can take out of the conflicts (or at least critical conflicts) list?

-          Agenda items

Thanks and Regards,

Dan

v2.23.0 | Report a Bug | By Email