IETF Logo Mail Archive

[Mtgvenue] discussion regarding time-of-year of meetings

Mikael Abrahamsson <swmike@swm.pp.se> Tue, 10 July 2018 02:02 UTC

Return-Path: <swmike@swm.pp.se>
X-Original-To: mtgvenue@ietfa.amsl.com
Delivered-To: mtgvenue@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BAA7D130EC0 for <mtgvenue@ietfa.amsl.com>; Mon, 9 Jul 2018 19:02:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.401
X-Spam-Level:
X-Spam-Status: No, score=-2.401 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=swm.pp.se
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 hurMYxfKgRJx for <mtgvenue@ietfa.amsl.com>; Mon, 9 Jul 2018 19:02:44 -0700 (PDT)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 278A0130ED0 for <mtgvenue@ietf.org>; Mon, 9 Jul 2018 19:02:44 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id D760CB0; Tue, 10 Jul 2018 04:02:41 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1531188161; bh=iNQ//g10ILgJuiNfbmYc3eYme2vKOlsp0xmMQZDoBDo=; h=Date:From:To:Subject:From; b=Owqfv1NJcosRLvhPIkvri8lzfdK9yEfQY3yP0cMjICSLuH9vakmAptJaWrj70QC86 jNw+Y147+vVbKmu41NlABLCbmyQkhrgzBcJhyxP+LJv4YbJ36C3jy7V2wsfI1wM2w+ kK5R+DOatX10PhO9ZeOqyRfAW3PopUElZnC6qUBU=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id D5C439F for <mtgvenue@ietf.org>; Tue, 10 Jul 2018 04:02:41 +0200 (CEST)
Date: Tue, 10 Jul 2018 04:02:41 +0200
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: mtgvenue@ietf.org
Message-ID: <alpine.DEB.2.20.1807100359250.14354@uplift.swm.pp.se>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="US-ASCII"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/MWET71_8jPkV2WjyAEkYNsVmZfQ>
Subject: [Mtgvenue] discussion regarding time-of-year of meetings
X-BeenThere: mtgvenue@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: "List for email discussion of the IAOC meeting venue selection process." <mtgvenue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mtgvenue>, <mailto:mtgvenue-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mtgvenue/>
List-Post: <mailto:mtgvenue@ietf.org>
List-Help: <mailto:mtgvenue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mtgvenue>, <mailto:mtgvenue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Jul 2018 02:02:48 -0000

Hi,

I just had a discussion with another regular IETF attendee, and we both 
agreed that the july meeting is in a bad time. For myself, it's right in 
the middle of the summer school vacation for my son, the other person had 
other reasons for July being a bad time.

Is there a specific reason we're meeting at the current time of year, and 
why we couldn't meet for instance june-october-february or 
may-september-january?

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se

v2.23.0 | Report a Bug | By Email