[xrblock] do we need to meet at IETF 94?

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Thu, 10 September 2015 18:51 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 87B6C1B6124 for <xrblock@ietfa.amsl.com>; Thu, 10 Sep 2015 11:51:19 -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 kiNJRFd_hoQg for <xrblock@ietfa.amsl.com>; Thu, 10 Sep 2015 11:51:17 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4CF731B6113 for <xrblock@ietf.org>; Thu, 10 Sep 2015 11:51:17 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A2CSBQBBP8ZV/xUHmMZbGQSCMSEsVG+pbgYFkzqHfQKBJjoSAQEBAQEBAYEKhCUBAQMSG14BFRVWJgEEGxqIDAGnbYULoEoBH4YfiWkBAR+DUIEUBYcZhmeHCwGOK4QlgwuNHoNmFw+DfYF9OoEEAQEB
X-IPAS-Result: A2CSBQBBP8ZV/xUHmMZbGQSCMSEsVG+pbgYFkzqHfQKBJjoSAQEBAQEBAYEKhCUBAQMSG14BFRVWJgEEGxqIDAGnbYULoEoBH4YfiWkBAR+DUIEUBYcZhmeHCwGOK4QlgwuNHoNmFw+DfYF9OoEEAQEB
X-IronPort-AV: E=Sophos;i="5.15,634,1432612800"; d="scan'208,217";a="119593162"
Received: from unknown (HELO co300216-co-erhwest-exch.avaya.com) ([198.152.7.21]) by de307622-de-outbound.net.avaya.com with ESMTP; 10 Sep 2015 14:51:14 -0400
X-OutboundMail_SMTP: 1
Received: from unknown (HELO AZ-FFEXHC01.global.avaya.com) ([135.64.58.11]) by co300216-co-erhwest-out.avaya.com with ESMTP/TLS/AES128-SHA; 10 Sep 2015 14:51:14 -0400
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC01.global.avaya.com ([135.64.58.11]) with mapi id 14.03.0174.001; Thu, 10 Sep 2015 20:51:12 +0200
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: xrblock <xrblock@ietf.org>
Thread-Topic: do we need to meet at IETF 94?
Thread-Index: AdDr+abjtAhG/47pR7qsbpm8rnxX8w==
Date: Thu, 10 Sep 2015 18:51:11 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA5CB216EA@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_9904FB1B0159DA42B0B887B7FA8119CA5CB216EAAZFFEXMB04globa_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/xrblock/09PqaUJKadVqinBYTDynsoHI3oA>
Subject: [xrblock] do we need to meet at IETF 94?
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: <https://mailarchive.ietf.org/arch/browse/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, 10 Sep 2015 18:51:19 -0000

Hi,

Our AD asked if we can consider alternatives to a f2f meeting in Yokohama at IETF 94. As you know meeting space is an expensive resource, and scheduling became more and more difficult with the increase in the number of active WGs. Assuming that video-lc  will be by then sent to the IESG, we have as potential agenda items draft-ietf-xrblock-rtcweb-rtcp-xr-metrics (which expired and needs to be updated) and the errata to RFC 7003.

Possible options:


1.       Keep the current plans which are meeting at IETF 94 for one hour (request was submitted)

2.       Organizing a virtual interim instead

3.       Working on the mail list only

Please express your preferences.

Thanks and Regards,

Dan