Re: [xrblock] XRBLOCK meeting at IETF-92?

"Huangyihong (Rachel)" <rachel.huang@huawei.com> Tue, 27 January 2015 03:13 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 3853C1A9036 for <xrblock@ietfa.amsl.com>; Mon, 26 Jan 2015 19:13:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.175
X-Spam-Level:
X-Spam-Status: No, score=-2.175 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, LONGWORDS=2.035, 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 WI3hsxJQ9QXy for <xrblock@ietfa.amsl.com>; Mon, 26 Jan 2015 19:13:44 -0800 (PST)
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 EBDEC1A1B98 for <xrblock@ietf.org>; Mon, 26 Jan 2015 19:13:43 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml401-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BOL52282; Tue, 27 Jan 2015 03:13:42 +0000 (GMT)
Received: from NKGEML406-HUB.china.huawei.com (10.98.56.37) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 27 Jan 2015 03:13:40 +0000
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.146]) by nkgeml406-hub.china.huawei.com ([10.98.56.37]) with mapi id 14.03.0158.001; Tue, 27 Jan 2015 11:13:37 +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 meeting at IETF-92?
Thread-Index: AdArUq2Tqi6hpw4iRduBS9PK70Nt8gIjbcYwAXzq/wAAAqAn8A==
Date: Tue, 27 Jan 2015 03:13:37 +0000
Message-ID: <51E6A56BD6A85142B9D172C87FC3ABBB862CE91A@nkgeml501-mbs.china.huawei.com>
References: <9904FB1B0159DA42B0B887B7FA8119CA5C9613C9@AZ-FFEXMB04.global.avaya.com> <9904FB1B0159DA42B0B887B7FA8119CA5C96ECB4@AZ-FFEXMB04.global.avaya.com> <9904FB1B0159DA42B0B887B7FA8119CA5C976CE2@AZ-FFEXMB04.global.avaya.com>
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA5C976CE2@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_51E6A56BD6A85142B9D172C87FC3ABBB862CE91Ankgeml501mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/xrblock/0dM7WLYp5j9zZHKGgfmL-XItWQ0>
Subject: Re: [xrblock] XRBLOCK meeting at IETF-92?
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, 27 Jan 2015 03:13:49 -0000

Hi Dan,

We have submitted a new version of video-lc draft a couple of weeks ago. It intends to solve the issues raised in the last IETF meeting and we authors think it's ready for adoption. We want to push it forward. If there's no meeting in IETF-92, I'd like to request for adoption on the mailing list then.

BR,
Rachel

From: xrblock [mailto:xrblock-bounces@ietf.org] On Behalf Of Romascanu, Dan (Dan)
Sent: Tuesday, January 27, 2015 9:55 AM
To: xrblock@ietf.org
Subject: Re: [xrblock] XRBLOCK meeting at IETF-92?

There was no answer to this Last Call message either, so I am pushing the 'Not meeting at IETF-92' button.

Regards,

Dan


From: xrblock [mailto:xrblock-bounces@ietf.org] On Behalf Of Romascanu, Dan (Dan)
Sent: Monday, January 19, 2015 2:09 PM
To: xrblock@ietf.org<mailto:xrblock@ietf.org>
Subject: Re: [xrblock] XRBLOCK meeting at IETF-92?

Hi,

I did not see any answer to this message, and more important - no proposals for agenda items.
If nothing comes up in the next few days I will send a notification that the group does not plan to hold a session at IETF 92.
Regards,
Dan


From: xrblock [mailto:xrblock-bounces@ietf.org] On Behalf Of Romascanu, Dan (Dan)
Sent: Thursday, January 08, 2015 4:52 PM
To: xrblock@ietf.org<mailto:xrblock@ietf.org>
Subject: [xrblock] XRBLOCK meeting at IETF-92?

Hi,

It's time to request a meeting slot at IETF-92 if we plan to meet. Before making a request I would suggest to discuss what would be the agenda.

As a reminder - we met for one hour at IETF-91.

Our list of conflicts at IETF-91 included:

trill siprec rtcweb raiarea payload opsawg opsarea netmod netconf mmusic lmap ippm insipid codec bmwg bfcpbis avtext avtcore tsvarea sacm alto spring pce mpls i2rs idr

Thanks and Regards,

Dan