Another strategic discussion (Re: IETF 107 and Corona Virus?)

Eliot Lear <> Mon, 17 February 2020 21:18 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 5C6BB120871 for <>; Mon, 17 Feb 2020 13:18:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -14.502
X-Spam-Status: No, score=-14.502 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id dRnlEqmrZQRP for <>; Mon, 17 Feb 2020 13:18:31 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id EA3A6120052 for <>; Mon, 17 Feb 2020 13:18:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=1164; q=dns/txt; s=iport; t=1581974311; x=1583183911; h=from:content-transfer-encoding:mime-version:subject:date: references:to:in-reply-to:message-id; bh=dc7aEgH4Eo8yHaYG0xfyNBB8WhS0PGw56cQr/DlT5tY=; b=Ox4u/QOpsTuvbLN8+ZvqHRuFgQzMwGJiaZ4J8Z5osVS4fvOOdjpY1UFb twpt+VNcY2R0HctGuUCf05+5dWfuCXuxnjBp2IbyHn8VtzcQ44ylBV7NI tNnpz6N9/ylXT2Gw3D2WqbDvWvg8B2T5jVtOmW6B6BZP+pooqgYU5Lxuu s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AfCAA0Akte/4sNJK1mHQEBAQkBEQU?= =?us-ascii?q?FAYF7gimBQTKEPo8QlW+HXAkBAQEMAQEvBAEBhEACggQkOBMCAw0BAQUBAQE?= =?us-ascii?q?CAQUEbYVDhWcGI0ocJQImAgJXBoM5gnysB3WBMopsgQ4qjCQaggCBOCCDCoE?= =?us-ascii?q?EhlcygiwElwCIdZAJgkQEgkuUBByPAowYpmmDMQIEBgUCFYFpIoFYMxoIGxV?= =?us-ascii?q?lAYJCPRIYDVaNX44tAkADjw8BAQ?=
X-IronPort-AV: E=Sophos;i="5.70,454,1574121600"; d="scan'208";a="718540867"
Received: from ([]) by with ESMTP/TLS/DHE-RSA-SEED-SHA; 17 Feb 2020 21:18:28 +0000
Received: from [] ([]) by (8.15.2/8.15.2) with ESMTPS id 01HLIPPX019966 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <>; Mon, 17 Feb 2020 21:18:27 GMT
From: Eliot Lear <>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.\))
Subject: Another strategic discussion (Re: IETF 107 and Corona Virus?)
Date: Mon, 17 Feb 2020 22:18:25 +0100
References: <> <> <> <> <>
To: IETF Discussion <>
In-Reply-To: <>
Message-Id: <>
X-Mailer: Apple Mail (2.3608.
X-Outbound-SMTP-Client:, []
Archived-At: <>
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 17 Feb 2020 21:18:33 -0000

I think one of the issues with discussions about creating remote meetings in these sorts of circumstances seems to necessitate someone being at a disadvantage from a timezone perspective.  It seems to me that one area to explore is analogous to our “share the pain” process for meeting locales, and seeing that WG virtual meetings in particular not unfairly disadvantage groups of participants.  I note that the RFC editor virtual meetings have occurred at different times precisely to follow this principle.  That idea might require refining: for instance, some WGs may be heavily Euro- or Ameri- or Asia-centric, allowing some weighting.

Also, Christian’s point about learning how and when to interject oneself as a remote participant is in play when there is an in-person meeting.  Pure virtual meetings do put everyone at that same disadvantage.

All of this to point out that as we eventually cycle back to the meeting modalities discussion some time from now with some data from the LLC, we should be thinking broadly about how we all get together… in person or virtually.