Re: [xrblock] scheduling conflict
Qin Wu <bill.wu@huawei.com> Tue, 24 June 2014 12:14 UTC
Return-Path: <bill.wu@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 071A21B2871 for <xrblock@ietfa.amsl.com>; Tue, 24 Jun 2014 05:14:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.401
X-Spam-Level:
X-Spam-Status: No, score=-2.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] 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 trJHi2T_sqL0 for <xrblock@ietfa.amsl.com>; Tue, 24 Jun 2014 05:14:15 -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 7E91A1B2844 for <xrblock@ietf.org>; Tue, 24 Jun 2014 05:14:14 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml406-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BJE33956; Tue, 24 Jun 2014 12:14:11 +0000 (GMT)
Received: from nkgeml407-hub.china.huawei.com (10.98.56.38) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 24 Jun 2014 13:14:10 +0100
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.155]) by nkgeml407-hub.china.huawei.com ([10.98.56.38]) with mapi id 14.03.0158.001; Tue, 24 Jun 2014 20:14:05 +0800
From: Qin Wu <bill.wu@huawei.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>, "xrblock@ietf.org" <xrblock@ietf.org>
Thread-Topic: scheduling conflict
Thread-Index: Ac+Po3VGo8OPio3vQwaA50woK6ZsxQAAZAEg
Date: Tue, 24 Jun 2014 12:14:05 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA8457307B@nkgeml501-mbs.china.huawei.com>
References: <9904FB1B0159DA42B0B887B7FA8119CA5C819561@AZ-FFEXMB04.global.avaya.com>
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA5C819561@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.180]
Content-Type: multipart/alternative; boundary="_000_B8F9A780D330094D99AF023C5877DABA8457307Bnkgeml501mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/xrblock/NFM0dd5RvsiXQ6isRXYzVkbm2rU
Subject: Re: [xrblock] scheduling conflict
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, 24 Jun 2014 12:14:17 -0000
Hi, Dan: It looks I get more involved into Routing area (especially in PCE) besides attending xrblock meeting. But I am okay with the meeting being scheduled in conflict with the working groups you listed. Please go ahead. Regards! -Qin 发件人: xrblock [mailto:xrblock-bounces@ietf.org] 代表 Romascanu, Dan (Dan) 发送时间: 2014年6月24日 19:57 收件人: xrblock@ietf.org 主题: [xrblock] scheduling conflict The ADs in RAI and Routing are asking why we have RTG working groups (i2rs,mpls, pce, spring, idr) on the XRBLOCK conflicts list. Will any of the key contributors be upset if the meeting is scheduled in conflict with these? Thanks and Regards, Dan
- [xrblock] scheduling conflict Romascanu, Dan (Dan)
- Re: [xrblock] scheduling conflict Qin Wu