Re: [Mtgvenue] Disposition of the group

Alissa Cooper <alissa@cooperw.in> Wed, 29 April 2020 02:56 UTC

Return-Path: <alissa@cooperw.in>
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 C39C93A0CDE for <mtgvenue@ietfa.amsl.com>; Tue, 28 Apr 2020 19:56:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=cooperw.in header.b=L3x4I1Bt; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=IGhKO+OA
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 Ynuuy75keCii for <mtgvenue@ietfa.amsl.com>; Tue, 28 Apr 2020 19:56:09 -0700 (PDT)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9B9083A0CC6 for <mtgvenue@ietf.org>; Tue, 28 Apr 2020 19:56:09 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id BF36E5C0356; Tue, 28 Apr 2020 22:56:08 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Tue, 28 Apr 2020 22:56:08 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm2; bh=k WtMMo82LUeSVUAD8veo9ndxdIHYwFCw50AAsuQFVeU=; b=L3x4I1BtxC816rA4x lDEwAvz5YeBn68/FFyR/dAFCVdM6kWDImkxNlbYwBHl9oXcEoCD75FMPbWdvMZKn xAg3vUDk0F7rFvSs+3Y6yD5kAPFA3e4OQ5p7qYSDLOKw/rzzLb8ne0GJ3+lmDLbK uiMFb+WPHNB9oRr45K/LdEax92L3R9yFpkVWkc9BxJ4iEOXjVjVmivEldfletDQ0 cgMsMOk9TBPqhrBoYNUlx54MXWqGfiIeuErh7FV67oN8FSVCf3rbQblKbUqyNjOX QUKXUZSWqqV9HMKfc5fNxJa410lYv3o57TaLYcwT4bsQq2V175ZWk8fmzewFP/Jl TYz3Q==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=kWtMMo82LUeSVUAD8veo9ndxdIHYwFCw50AAsuQFV eU=; b=IGhKO+OARrXCHfgpQnUSkV3HapDWhc8MeiNe3OHDQa2Eo2rEk5DspZ9VD K7J0raxSycLr8qyT3wndADru7TPH4Rilf/79BfJsiWSvyHRGBLHkiUUMR6+VMnQJ OCOwd28oVwyhAgj3a609QtyGNBfKx7xZry/gmJEbUwODAlwuR8aixJ1cERWpOqkH jJPAO0Qs9iIPUyt18PgSJRoZybXVUNxoVaXngqKhOCEG5AaLmMGYVQNzgqecM30W 4G1h+8NN8TUppdRoEKFXd8resEa4eh1NDrXQL9oVN/LPoOWJ8XkflE2Pea/V/JnD ogPTvOYeqI0N0NfWZBwH5fbzjdw0A==
X-ME-Sender: <xms:yOyoXjZu6fSp3iqSt3o49nOmEWyhwlPLFX2qZz97mWrTucCf0gUc-w>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedriedvgdeifecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpegtggfuhfgjfffgkfhfvffosehtqhhmtdhhtdejnecuhfhrohhmpeetlhhishhs rgcuvehoohhpvghruceorghlihhsshgrsegtohhophgvrhifrdhinheqnecukfhppeduje efrdefkedruddujedrjedunecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehm rghilhhfrhhomheprghlihhsshgrsegtohhophgvrhifrdhinh
X-ME-Proxy: <xmx:yOyoXuPbYSvZfmNQYPRotRjsfEDcEHGDQT-0-0kux-GvelSmPLe46Q> <xmx:yOyoXhXLzbvEjTU7XmnKpu47MD_YKDgRBbiDBGukn_hTQl0_JJdYCw> <xmx:yOyoXjKTHnt2J3kjzl5Nr-OZuGM8GUCkso5Ugj5yDvJIMXhxba5eFg> <xmx:yOyoXoDOhsnQrEft8C8aFjKVk6HGcz8cpPYK5cZDUXgo8BYsbssdAQ>
Received: from rtp-alcoop-nitro2.cisco.com (unknown [173.38.117.71]) by mail.messagingengine.com (Postfix) with ESMTPA id 2E9FC328005A; Tue, 28 Apr 2020 22:56:08 -0400 (EDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.5\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <D9D305F5-040D-4EF3-914C-0B8D273BA03A@episteme.net>
Date: Tue, 28 Apr 2020 22:56:07 -0400
Cc: mtgvenue@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <BE94E058-B995-4B09-84FB-7E905CDA2D53@cooperw.in>
References: <9B937623-5E7C-4BF1-AC9B-9CFFD5C33F93@cooperw.in> <D9D305F5-040D-4EF3-914C-0B8D273BA03A@episteme.net>
To: Pete Resnick <resnick@episteme.net>
X-Mailer: Apple Mail (2.3445.9.5)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/W-bReYt0uE9zo0zfJNOfOkkO9sg>
Subject: Re: [Mtgvenue] Disposition of the group
X-BeenThere: mtgvenue@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 29 Apr 2020 02:56:11 -0000

Hi Pete,

Indeed, I have been waiting on this since there has been a bunch of activity in the background concerning meeting planning for IETF 107 and 108, and I wanted to get a bit of a clearer picture about that before closing out this thread. I think at this point, though, that closing the group and keeping the list open is the sensible thing to do, and people who have posted in this thread seem to agree. We can always spin back up if necessary, or fold updates to this group's docs into a WG with a broader mandate to look at meeting planning guidance in light of COVID-19.

I’ll hit the close button now. Thanks to everyone for your work and dedication in this group, especially the authors, editors, and chairs.

Alissa


> On Apr 26, 2020, at 5:58 PM, Pete Resnick <resnick@episteme.net> wrote:
> 
> Hi Alissa,
> 
> There was quite a bit of excitement between when you sent this message and now (to say the least) that you had to work on, but I was wondering if you made a decision on this. I personally think it would be reasonable to leave the mailing list live, close down the group, and then create a new charter if we find some more work that needs to be done in the future, and I don't think I've heard anyone on the list say anything particularly different. On the other hand, I'm also fine with going into a dormant mode as a WG and re-chartering when the time comes, if that is easier administratively. Whatever works for you.
> 
> pr
> 
> On 5 Mar 2020, at 13:01, Alissa Cooper wrote:
> 
>> Hi all,
>> 
>> The two deliverables for this group have been published: RFC 8718 and RFC 8719. Thanks to everyone who contributed.
>> 
>> At this point we could close the group. If we do that, I think we should keep the mailing list open. Or we could keep the group open in case people want to propose updates to the documents in the future. Or we could talk about a re-charter if there are other related work items people want to pursue. Please share your thoughts about the disposition of the group.
>> 
>> Thanks,
>> Alissa