Re: [Mtgvenue] Disposition of the group

Jay Daley <jay@ietf.org> Thu, 05 March 2020 19:52 UTC

Return-Path: <jay@ietf.org>
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 F3F473A0A9E; Thu, 5 Mar 2020 11:52:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 8RgnyijzKMMa; Thu, 5 Mar 2020 11:52:52 -0800 (PST)
Received: from jays-mbp.localdomain (unknown [158.140.230.105]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPSA id 933F93A0A99; Thu, 5 Mar 2020 11:52:51 -0800 (PST)
From: Jay Daley <jay@ietf.org>
Message-Id: <C0E65A83-1752-4A2E-B2AA-C7EBC38A5780@ietf.org>
Content-Type: multipart/alternative; boundary="Apple-Mail=_0AAADAAF-867F-4B8C-A673-E9ED37191F31"
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.60.0.2.5\))
Date: Fri, 6 Mar 2020 08:52:48 +1300
In-Reply-To: <42D0AD47-B53F-4356-BD54-F57664F7F73B@cisco.com>
Cc: Alissa Cooper <alissa@cooperw.in>, mtgvenue@ietf.org
To: Eliot Lear <lear=40cisco.com@dmarc.ietf.org>
References: <9B937623-5E7C-4BF1-AC9B-9CFFD5C33F93@cooperw.in> <42D0AD47-B53F-4356-BD54-F57664F7F73B@cisco.com>
X-Mailer: Apple Mail (2.3608.60.0.2.5)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/mbISdT1tG0QbAFgJkjfSGA8Bn3w>
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: Thu, 05 Mar 2020 19:52:54 -0000

Eliot

> On 6/03/2020, at 8:17 AM, Eliot Lear <lear=40cisco.com@dmarc.ietf.org> wrote:
> 
> Hi Alissa,
> 
> For sure we need the mailing list.  I don’t think we need the WG.  At least not yet.
> 
> We need some running code, and so we should be conservative about reopening those documents too quickly.  This having been said, as you know, I’ve been somewhat interested in figuring out new modalities for meetings, or at least getting data to have the discussion.  Part of that was environment, part of that was effectiveness.  I don’t think any of us really considered the situation we are in today, and perhaps in April we will have a better idea as to whether additional process would be helpful.   Well, really you, Jay and the leadership will have war stories to tell us.

Just to be clear on roles, the choice of modalities sits with the IESG and the role of the LLC is to deliver what the IESG want.

> 
> An AI now rests with Jay on this to collect some data, and as I recall, there was another AI in which he would hire someone to help (but my memory could be faulty).  It may be premature for this group to engage with that person.  If my memory is correct, then perhaps we have to wait a few months, presumably until after Madrid, before even beginning to have the discussion about what we can reasonably consider improving.

The project I am initiating is to have the carbon footprint of IETF meetings measured.  This will then hopefully leading to a strategy that combines minimisation with offset in order to achieve carbon neutrality for meetings.  We may also be able to take it further to look at historical carbon contribution with a view to achieving lifetime carbon zero for IETF meetings.  I’m at the stage of talking to a few firms who specialise in this area of consulting.

Jay

> 
> Eliot
> 
>> On 5 Mar 2020, at 20:01, Alissa Cooper <alissa@cooperw.in> 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
>> _______________________________________________
>> Mtgvenue mailing list
>> Mtgvenue@ietf.org
>> https://www.ietf.org/mailman/listinfo/mtgvenue
> 
> _______________________________________________
> Mtgvenue mailing list
> Mtgvenue@ietf.org
> https://www.ietf.org/mailman/listinfo/mtgvenue

-- 
Jay Daley
IETF Executive Director
jay@ietf.org
+64 21 678840