[xrblock] XRBLOCK WG meeting at IETF 93?

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Mon, 27 April 2015 09:10 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 81E651B2F5D for <xrblock@ietfa.amsl.com>; Mon, 27 Apr 2015 02:10:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.909
X-Spam-Level:
X-Spam-Status: No, score=-6.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, 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 jseMuhUMeJu2 for <xrblock@ietfa.amsl.com>; Mon, 27 Apr 2015 02:10:57 -0700 (PDT)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C16E71B2F57 for <xrblock@ietf.org>; Mon, 27 Apr 2015 02:10:56 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjMFAML8PVXGmAcV/2dsb2JhbABcgkUhJlNhtEcFAQaZQQKBMEwBAQEBAQGBC4QiAQEDEhteARUVViYBBBsaiAkBoWeFBp4nDAEfhhaJdoNPgRYFkVWSCI4SI2CDFIIzgQABAQE
X-IronPort-AV: E=Sophos;i="5.11,655,1422939600"; d="scan'208,217";a="117594720"
Received: from unknown (HELO co300216-co-erhwest-exch.avaya.com) ([198.152.7.21]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 27 Apr 2015 05:10:38 -0400
X-OutboundMail_SMTP: 1
Received: from unknown (HELO AZ-FFEXHC04.global.avaya.com) ([135.64.58.14]) by co300216-co-erhwest-out.avaya.com with ESMTP/TLS/AES128-SHA; 27 Apr 2015 05:10:38 -0400
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC04.global.avaya.com ([135.64.58.14]) with mapi id 14.03.0174.001; Mon, 27 Apr 2015 11:10:36 +0200
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "xrblock@ietf.org" <xrblock@ietf.org>
Thread-Topic: XRBLOCK WG meeting at IETF 93?
Thread-Index: AdCAygUWtU7IfXqzSa6Fa5c3cNZIkw==
Date: Mon, 27 Apr 2015 09:10:36 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA5CA00004@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.48]
Content-Type: multipart/alternative; boundary="_000_9904FB1B0159DA42B0B887B7FA8119CA5CA00004AZFFEXMB04globa_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/xrblock/qXPNaPjDJhMsgDfLH3_02URiCrg>
Subject: [xrblock] XRBLOCK WG meeting at IETF 93?
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: Mon, 27 Apr 2015 09:10:58 -0000

Hi,

It's time to discuss scheduling of the meeting for the XRBLOCK WG at IETF 93.


-          Do we need to meet or can we do the work on the list?

-          If yes, is one hour enough?

-          If yes, are there any new conflicts that we MUST avoid? Are there any older conflicts that we can take out of the conflicts (or at least critical conflicts) list?

-          Agenda items

Thanks and Regards,

Dan