Re: [Manycouches] many-fine-dinners --- a view on how to organize virtual meetings

Martin Duke <martin.h.duke@gmail.com> Fri, 20 November 2020 06:20 UTC

Return-Path: <martin.h.duke@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 9902E3A190E for <manycouches@ietfa.amsl.com>; Thu, 19 Nov 2020 22:20:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=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=gmail.com
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 A05Xnn6hN8_3 for <manycouches@ietfa.amsl.com>; Thu, 19 Nov 2020 22:20:32 -0800 (PST)
Received: from mail-io1-xd2e.google.com (mail-io1-xd2e.google.com [IPv6:2607:f8b0:4864:20::d2e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2233A3A139C for <manycouches@ietf.org>; Thu, 19 Nov 2020 22:20:32 -0800 (PST)
Received: by mail-io1-xd2e.google.com with SMTP id j23so8802915iog.6 for <manycouches@ietf.org>; Thu, 19 Nov 2020 22:20:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=OvOXgSxfAxSTtOekRTHREz82ngYvLDgeMiz7cyPppEs=; b=uC5wMpyUqUUIAj2/FW1I+eT3Br5wk1GZ5lGlLKK9zuQZUaEmFOBH5ZDPJlwoV/LQ6j +XThS8z5g3QpVsaC4CmNlq58wH6tsB3G2r5IOFkVdIz6eRInFDhx+QvEGNosQlBiVojc 92ouAb8oLN3VxFR/Cvo4aoa4do5qg5T2ClZUzTN3hLl5gmFA0ue9686pp1oORatSF8OF gro5+KgUqmizM8pq95Rgc4uTOn+vnVql4COO3NC7qvy6R3i8xhQxBdPAEN8X/HvPNF3m 4GBEYWkm8WzRvX5rD42SoIUF1uUaPLJQaa8E+ERfmux6SL+CzDhFMmJX1KmLRetCnLv8 b0Mg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=OvOXgSxfAxSTtOekRTHREz82ngYvLDgeMiz7cyPppEs=; b=LK94oo+vJvYAUZ4l1UMu42mC3V179fdtEJIjb6Ze91QGHa7USiD+VCRrbNTEgv7rg8 4rNZtCruCoEIaOmZK1gBUiUV7PdI5yr9iVtBJDj7srg8784CYiDujU+eb15hiDm2/O6T RkFRQlHkzgNg0PsmlFSWvu+0AGeJah6NP78wQHkskoqjWC8TWizgaICYmy0leIV81CdO s9yTff2eXQIS389u4rK7ADaVDJirtFJPCHhfUkxf6h+4XAFVTaBEwcOq/ioDobOzo0l7 9tV4FMriyAhQP5LFqGHivUT81aSceSTRFQidRA8Z8X+Fy0q/rbNCZ4lcDfR1MOy4bZ5P ukxg==
X-Gm-Message-State: AOAM530qqJfwFUFYosnYO+EpJI1G7HutbHyF8Tk/ahPcGgO+LO4K+yO0 FOdsfaBdpDIYkwJSp5EUA/RQTKUYQFpIZvxgxoALOIxLCTQ=
X-Google-Smtp-Source: ABdhPJwoyoc0LOF84H8boWPW1HOapkrK+7lfRg0A+Y7mywLHSzPQBmbfnIC+Up2e6UyJBa4flfL9unrS9VEb8LDiP2Q=
X-Received: by 2002:a5d:9a03:: with SMTP id s3mr10863947iol.20.1605853231336; Thu, 19 Nov 2020 22:20:31 -0800 (PST)
MIME-Version: 1.0
References: <160288855079.14008.13967692974159638979@ietfa.amsl.com> <30344.1602894208@localhost> <FD995870-E9C6-4099-93AF-253F0A11F56B@tzi.org> <CADaq8jcKK5kUvU3v7+6gEaeqjqxtw-Bii5is_hoq1ugogCoWPg@mail.gmail.com> <20201017193610.GA39170@kduck.mit.edu> <12526.1602980594@localhost> <2f99a293-b2b1-498f-36af-36fd201e9e8d@joelhalpern.com> <15451.1603056956@localhost> <2a305ee7-7511-f74d-fd7b-93ff8641c451@joelhalpern.com> <17295.1603123341@localhost> <228dbe14-2362-7374-bf1c-768c6ada7a3f@joelhalpern.com> <5926.1603128427@localhost> <a11e38fd-7d21-112c-fbe9-dc4b699ca5fe@joelhalpern.com> <13688.1604619321@localhost> <E441A975-F3E0-4011-86E5-AAC7494EBE31@cisco.com> <CAM4esxQdW2N=NAwgGpJKc3Q9xdyDRG1K-R=75vK7wi2tUO9btQ@mail.gmail.com> <32537.1605850657@localhost>
In-Reply-To: <32537.1605850657@localhost>
From: Martin Duke <martin.h.duke@gmail.com>
Date: Thu, 19 Nov 2020 22:20:32 -0800
Message-ID: <CAM4esxTN7KYM8q0deRaa4MaEJyGAymM1g7Tj+Ggmt=+D3t7JhQ@mail.gmail.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: "manycouches@ietf.org" <manycouches@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000006a4f1c05b483d715"
Archived-At: <https://mailarchive.ietf.org/arch/msg/manycouches/wDIQVnlWnTzUMZ03nldcb0MFwhM>
Subject: Re: [Manycouches] many-fine-dinners --- a view on how to organize virtual meetings
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: Fri, 20 Nov 2020 06:20:34 -0000

On Thu, Nov 19, 2020 at 9:37 PM Michael Richardson <mcr+ietf@sandelman.ca>
wrote:

>
>     > 5. *More interim meetings*: the near-universal interim start time of
> ~1500
>     > UTC makes a lot of inherently discriminatory assumptions about what
> time
>     > zones have the most important contributors and what hours are
> optimal for
>     > any particular time zone. If we were to have regular virtual IETFs
> without
>     > a canceled location as a timebase, using a random start time would be
>     > better than optimizing for the Atlantic. That said, sometimes WGs
> enter a
>     > phase where they're in the weeds, tourists are not that helpful, and
> indeed
>     > entirely theoretical anyway. For these groups, interims are currently
>     > available but I don't think we should be in the business of actively
>     > encouraging interims for the reasons above.
>
> I don't really understand this paragraph at all.
>

Alright, I'll try again.

I think you're arguing for fewer meetings in IETF week and more interims.

Interims tend to be scheduled at a time most convenient for the key
participants, which discourages tourism and marginalizes non-key
participants.

There's a time when that's OK, and the interim procedures exist for this
reason.

However, I think the balance today between interim and non-interim is about
right.