[xrblock] scheduling conflicts with routing area WGs

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Wed, 08 October 2014 17:40 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 []) by ietfa.amsl.com (Postfix) with ESMTP id 8A79D1ACD58 for <xrblock@ietfa.amsl.com>; Wed, 8 Oct 2014 10:40:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.685
X-Spam-Status: No, score=-7.685 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.786] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id BAXKiUlvyxc8 for <xrblock@ietfa.amsl.com>; Wed, 8 Oct 2014 10:40:55 -0700 (PDT)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com []) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1E6D91ACD55 for <xrblock@ietf.org>; Wed, 8 Oct 2014 10:40:55 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvAKALt2NVTGmAcV/2dsb2JhbABfgkgjI1Nct1gGmnsCgQoWAQF6hAUBAQMSGzokAQwJFVYmAQQbGogcAaB/hGyfSoYgiXODZYEeBZF3k1uOAINjgjSBAgEBAQ
X-IronPort-AV: E=Sophos; i="5.04,679,1406606400"; d="scan'208,217"; a="88600513"
Received: from unknown (HELO co300216-co-erhwest-exch.avaya.com) ([]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 08 Oct 2014 13:40:53 -0400
X-OutboundMail_SMTP: 1
Received: from unknown (HELO AZ-FFEXHC03.global.avaya.com) ([]) by co300216-co-erhwest-out.avaya.com with ESMTP/TLS/AES128-SHA; 08 Oct 2014 13:40:53 -0400
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC03.global.avaya.com ([]) with mapi id 14.03.0174.001; Wed, 8 Oct 2014 13:40:51 -0400
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: xrblock <xrblock@ietf.org>
Thread-Topic: scheduling conflicts with routing area WGs
Thread-Index: Ac/jHv52Zhg0IjP3T72pt6EQugan0w==
Date: Wed, 08 Oct 2014 17:40:51 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA5C8C3649@AZ-FFEXMB04.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_9904FB1B0159DA42B0B887B7FA8119CA5C8C3649AZFFEXMB04globa_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/xrblock/U5DH8TwnfxE_24DSqWy2EsjhDcQ
Subject: [xrblock] scheduling conflicts with routing area WGs
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: Wed, 08 Oct 2014 17:40:56 -0000


Our scheduling request for IETF-91 includes a number of conflicts to avoid with WGs in the routing area:

alto spring pce mpls i2rs idr

I believe that these request are carried out from previous meetings, but I may be wrong. Does anybody need to avoid these conflicts.

Unless there somebody steps up and asks for these to be avoided, we will let the Secretariat drop these.

Thanks and Regards,