[xrblock] XRBLOCK meeting at IETF-92?

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Thu, 08 January 2015 14:52 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 66C251A8990 for <xrblock@ietfa.amsl.com>; Thu, 8 Jan 2015 06:52:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.874
X-Spam-Status: No, score=-4.874 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, LONGWORDS=2.035, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 40JtAff_IqGt for <xrblock@ietfa.amsl.com>; Thu, 8 Jan 2015 06:52:32 -0800 (PST)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.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 ACE561A1DBE for <xrblock@ietf.org>; Thu, 8 Jan 2015 06:52:31 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos; i="5.07,723,1413259200"; d="scan'208,217"; a="87114899"
Received: from unknown (HELO co300216-co-erhwest-exch.avaya.com) ([]) by de307622-de-outbound.net.avaya.com with ESMTP; 08 Jan 2015 09:52:29 -0500
X-OutboundMail_SMTP: 1
Received: from unknown (HELO AZ-FFEXHC04.global.avaya.com) ([]) by co300216-co-erhwest-out.avaya.com with ESMTP/TLS/AES128-SHA; 08 Jan 2015 09:52:15 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC04.global.avaya.com ([]) with mapi id 14.03.0174.001; Thu, 8 Jan 2015 15:52:14 +0100
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "xrblock@ietf.org" <xrblock@ietf.org>
Thread-Topic: XRBLOCK meeting at IETF-92?
Thread-Index: AdArUq2Tqi6hpw4iRduBS9PK70Nt8g==
Date: Thu, 08 Jan 2015 14:52:12 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA5C9613C9@AZ-FFEXMB04.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_9904FB1B0159DA42B0B887B7FA8119CA5C9613C9AZFFEXMB04globa_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/xrblock/RXDAhXavKVNJPYVNj8fYXPaIL1g>
Subject: [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: Thu, 08 Jan 2015 14:52:34 -0000


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,