Re: [Manycouches] Summary of discussions on meeting cadence

Alexandre Petrescu <alexandre.petrescu@gmail.com> Tue, 13 October 2020 12:28 UTC

Return-Path: <alexandre.petrescu@gmail.com>
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 1B6923A0F38 for <manycouches@ietfa.amsl.com>; Tue, 13 Oct 2020 05:28:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.458
X-Spam-Level:
X-Spam-Status: No, score=0.458 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FORGED_GMAIL_RCVD=1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.213, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no 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 Alc8l84_PZho for <manycouches@ietfa.amsl.com>; Tue, 13 Oct 2020 05:27:59 -0700 (PDT)
Received: from oxalide-smtp-out.extra.cea.fr (oxalide-smtp-out.extra.cea.fr [132.168.224.13]) (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 3254B3A0F94 for <manycouches@ietf.org>; Tue, 13 Oct 2020 05:27:59 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 09DCRuNW009666 for <manycouches@ietf.org>; Tue, 13 Oct 2020 14:27:56 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id A6EB5205A6D for <manycouches@ietf.org>; Tue, 13 Oct 2020 14:27:56 +0200 (CEST)
Received: from muguet1-smtp-out.intra.cea.fr (muguet1-smtp-out.intra.cea.fr [132.166.192.12]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 9C00C2014E9 for <manycouches@ietf.org>; Tue, 13 Oct 2020 14:27:56 +0200 (CEST)
Received: from [10.8.35.150] (is154594.intra.cea.fr [10.8.35.150]) by muguet1-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 09DCRume015716 for <manycouches@ietf.org>; Tue, 13 Oct 2020 14:27:56 +0200
To: manycouches@ietf.org
References: <f0c7e848-66ab-f08f-4cb2-24462c227dcf@andersdotter.cc> <12027.1602263977@localhost>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <74055ff2-d85f-c579-4fcf-8fed3422ea44@gmail.com>
Date: Tue, 13 Oct 2020 14:27:56 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.3.2
MIME-Version: 1.0
In-Reply-To: <12027.1602263977@localhost>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/manycouches/7NXurz4sVSun8E4HlkN1zCwTUXk>
Subject: Re: [Manycouches] Summary of discussions on meeting cadence
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: Tue, 13 Oct 2020 12:28:01 -0000


Le 09/10/2020 à 19:19, Michael Richardson a écrit :
> 
> Amelia Andersdotter <amelia.ietf@andersdotter.cc> wrote:
>      > These two different goals of meetings are somehow conflicting. If many
>      > WG participants are from the same geographical area or time zone, and
>      > their focus is on completing standards and specifications, it is more
>      > reasonable for these participants to organise interim meetings in their
>      > time-zone of convenience. But if participants feel that they want to do
>      > tourism in areas that they don't normally work on to get a more complete
>      > view of the internet, it makes more sense to have a condensed set of
>      > meetings in a week with rotating time-schedule as per already existing
>      > regional rotation as per RFC8719.
> 
> Your summary of the conflict is accurate, but the word "tourism" is rather
> loaded for me.
> 
> While many see the word and may understand "impromptu cross-area review", the
> term is loaded with negative attachments.
> For instance, the location of physical meetings has at times been criticised
> as being picked for touristic reasons.

Tourism:
- has negative co-notation to mean that the room was packed with people
   raising their hands to vote because told to do so.  They will not be
   seen again at the next meeting, as they already visited that City.
- is positive: productive meeting during the day, free of occupation in
   evening, see new things, cross-polinate the spirits, admit the
   differences in the world... 'get a more complete view of the
   Internet.'
- is something to not do during times of virus.

Alex

> 
> There is some significant negative experience with mic comments like,
>     "I haven't read the document, but..."
> 
> yet, often these comments *do* lead to significant issues.

> 
> Sometimes, though, they lead to an understanding that two WGs are facing the same
> issues, and that they should work together.  And getting this understanding
> is really quite valuable.
> 
> This is *PARTICULARLY* the case for new work (BOFs), and for the first few
> meetings of a newly formed WG.
> 
> This is also why heavily conflicted (physical) meeting schedules have been a
> growing issue.
> 
>      > Is the /purpose/ of IETF meetings something we should address directly
>      > before producing guidelines? The IETF Mission Statement currently is
>      > fairly outcome-oriented (i.e. could be construed as prioritizing
>      > focussed work over cross-pollination).'
> 
> I think that you raise an important question.
> let me try to answer it.
> 
> I think that we have a healthy growth of virtual interim meetings which are:
>    a) heavily focused.
>    b) frequent participant-time-zone optimized
>    c) typically occur at twice-monthly to monthly intervals appropriate for
>       getting work done.
> 
> While the mission statement is very outcome focused, that doesn't mean that
> every activity needs to be only outcome focused.  :-)
> 
> I think that the IETF "plenary" meeting times should be arranged to not just
> permit, but encourage cross-working-group participation.
> 
> I want the IETF meeting weeks focused on:
>    1) meta-activites like IESG, IAB, NOMCOM
>    2) *DISPATCH activities
>    3) BOFs
>    4) new WG meetings,
>    5) maybe WGs who have gone through some major milestone, and are rechartering
> 
> I would like there to be time to arrange 1:1 or rather-small-group meetings
> with ADs and document authors to talk through some lingering DISCUSSes.
> The gather.town was exceptionally useful for this.
> The RIOT Summit used it as well, and used it for side-meetings as well, and I
> think it well very well.  I don't how big a group it can handle on it's own,
> but it seemed that perhaps the RIOT Summit didn't need webex as well.
> But, RIOT is O(10^2), while IETF is O(10^3).
> 
> 
> So, I would like to have fewer tracks.
> Less like IETF108 and more like IETF107.  But, slightly longer days.
> In particular, I don't mind having some gaps where I can reasonably expect to
> find someone.
> 
> I don't think that spreading 107 across the month of April was great,
> although many WGs that had never had virtual interims sure learnt how.
> I would like the meeting restricted to a 5 or 7 day period, because "jet lag"
> 
> --
> Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
>             Sandelman Software Works Inc, Ottawa and Worldwide
> 
> 
> _______________________________________________
> Manycouches mailing list
> Manycouches@ietf.org
> https://www.ietf.org/mailman/listinfo/manycouches
>