Re: [Manycouches] Stay Home Meet Online (SHMO) draft and proposed WG

Michael Richardson <mcr+ietf@sandelman.ca> Thu, 14 May 2020 18:50 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: manycouches@ietfa.amsl.com
Delivered-To: manycouches@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 478183A0B2F for <manycouches@ietfa.amsl.com>; Thu, 14 May 2020 11:50:04 -0700 (PDT)
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, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 eJ4Eo-VH1F4H for <manycouches@ietfa.amsl.com>; Thu, 14 May 2020 11:50:01 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3ED953A0B25 for <manycouches@ietf.org>; Thu, 14 May 2020 11:50:00 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 9CCC6389E0; Thu, 14 May 2020 14:47:52 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id SfnS4ebtKRaX; Thu, 14 May 2020 14:47:48 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 4526E389D1; Thu, 14 May 2020 14:47:48 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 379013FB; Thu, 14 May 2020 14:49:54 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Alissa Cooper <alissa@cooperw.in>, manycouches@ietf.org
In-Reply-To: <27533110-8E7A-4D9B-ACDD-6B7CAA50EDEF@cooperw.in>
References: <E103897C-F9D9-4ED3-AB45-FD2967D7F49E@cooperw.in> <3844.1589465784@localhost> <27533110-8E7A-4D9B-ACDD-6B7CAA50EDEF@cooperw.in>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Thu, 14 May 2020 14:49:54 -0400
Message-ID: <3156.1589482194@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/manycouches/mVW_PFnLKW6haanA38hfZHpMtqc>
Subject: Re: [Manycouches] Stay Home Meet Online (SHMO) draft and proposed WG
X-BeenThere: manycouches@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List is a design team list to identify issues that would arise should an IETF meeting ever be held with O\(1000\) 'remote' participants." <manycouches.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manycouches>, <mailto:manycouches-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/manycouches/>
List-Post: <mailto:manycouches@ietf.org>
List-Help: <mailto:manycouches-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manycouches>, <mailto:manycouches-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 May 2020 18:50:04 -0000

Alissa Cooper <alissa@cooperw.in> wrote:
    >> On May 14, 2020, at 10:16 AM, Michael Richardson
    >> <mcr+ietf@sandelman.ca> wrote:
    >>
    >>
    >> Alissa Cooper <alissa@cooperw.in> wrote:
    >>> The charter is scoped narrowly to only deal with cancellation of
    >>> previously planned in-person meetings. There are other related topics
    >>> that need community guidance — the nomcom eligibility criteria that
    >>> is already being worked on (see elgibility-discuss@ietf.org
    >>> <mailto:elgibility-discuss@ietf.org>), the overall meeting cadence
    >>> and mix of in-person versus virtual meetings in the future, how to
    >>> craft the meeting experience at an in-person meeting when
    >>> significantly more people are remote, etc. But just the cancellation
    >>> topics on their own will require a bunch of work and may attract
    >>> different participants than those interested in other topics, so the
    >>> boundary is drawn there.
    >>
    >> ...  eligibility-discuss is not a WG, so it's been hard to arrange a
    >> virtual interim, and I think that as a result, we have gone as far as
    >> that we can.

    > I don’t think this is true. My understanding is that Stephen Farrell is
    > working on further data analysis to support the ongoing discussion of
    > draft-carpenter-eligibility-expand.

yes, there is more data to collect, but I'm sure that if there was a meeting
deadline that the work would already be done :-)

    >> I would prefer that it be in-scope for SHMO!!
    >>
    >> I also wonder if "mtgvenue" shouldn't just be rechartered to do this
    >> work.  We are basically trying to establish a higher-order set of
    >> meeting "venue" criteria.

    > MTGVENUE has been closed, so at this point we are looking at a
    > chartering process rather than a re-chartering process either way.

So, there is always this adage that we can always re-charter a WG and re-open
it, that makes it easy for us to close it.

Do we really like making new TLAs so much?

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-