[xrblock] scheduling conflict
"Romascanu, Dan (Dan)" <dromasca@avaya.com> Tue, 24 June 2014 11:57 UTC
Return-Path: <dromasca@avaya.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 131F41B2878 for <xrblock@ietfa.amsl.com>; Tue, 24 Jun 2014 04:57:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.25
X-Spam-Level:
X-Spam-Status: No, score=-3.25 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.651] 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 BiwxNPpy0pV3 for <xrblock@ietfa.amsl.com>; Tue, 24 Jun 2014 04:57:31 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4CF851B2833 for <xrblock@ietf.org>; Tue, 24 Jun 2014 04:57:31 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Am8FAG9mqVPGmAcV/2dsb2JhbABagkYjJFJaqkAGmTUBgQUWdYQFAQEDEhteAQwJFVYfBwEEGxqIIAGWd4RcqEIXhWOIaINlgRYEoXKMPYNCgjA
X-IronPort-AV: E=Sophos; i="5.01,537,1400040000"; d="scan'208,217"; a="70557235"
Received: from unknown (HELO co300216-co-erhwest-exch.avaya.com) ([198.152.7.21]) by co300216-co-outbound.net.avaya.com with ESMTP; 24 Jun 2014 07:57:30 -0400
X-OutboundMail_SMTP: 1
Received: from unknown (HELO AZ-FFEXHC02.global.avaya.com) ([135.64.58.12]) by co300216-co-erhwest-out.avaya.com with ESMTP/TLS/AES128-SHA; 24 Jun 2014 07:38:18 -0400
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC02.global.avaya.com ([135.64.58.12]) with mapi id 14.03.0174.001; Tue, 24 Jun 2014 13:57:28 +0200
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "xrblock@ietf.org" <xrblock@ietf.org>
Thread-Topic: scheduling conflict
Thread-Index: Ac+Po3VGo8OPio3vQwaA50woK6ZsxQ==
Date: Tue, 24 Jun 2014 11:57:27 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA5C819561@AZ-FFEXMB04.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.64.58.46]
Content-Type: multipart/alternative; boundary="_000_9904FB1B0159DA42B0B887B7FA8119CA5C819561AZFFEXMB04globa_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/xrblock/l79VKtzpHM1IyVFwOvBIkok1qZg
Subject: [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 11:57:33 -0000
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