Re: [Ietf108planning] Reminder: Survey on planning for possible online IETF meetings

Alissa Cooper <alissa@cooperw.in> Mon, 04 May 2020 12:46 UTC

Return-Path: <alissa@cooperw.in>
X-Original-To: ietf108planning@ietfa.amsl.com
Delivered-To: ietf108planning@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 424313A084E; Mon, 4 May 2020 05:46:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 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, 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=cooperw.in header.b=UiHTlWig; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=dsO5u0RW
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 plyzs8wxZEJm; Mon, 4 May 2020 05:46:22 -0700 (PDT)
Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 831803A084B; Mon, 4 May 2020 05:46:22 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id 1AE374FE; Mon, 4 May 2020 08:40:00 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Mon, 04 May 2020 08:40:00 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm3; bh=G qqRW5CmMpGpldwoZgXhgUTOsc6sqgqHqICubcUN0PU=; b=UiHTlWigZp1ElpVg6 pIc7Dlq40Mjy/Lzeb/340CSJVQR9WUgT5IpyFImQQDnH5j4NaUCsPeG/sBzDTFbn D+vFTszcH3FHIp46laInBLlcUwI3Liymmay9mImjxQXhcJIPnrptCdgjqLx5r8sX 1jpssJtaIoKraH58zpfSY1Lrvm/LLnwz4kG9vjOyaPJsOgbMBKrVHX+68g84u+Ak c/6l+dXSMbzyAjCuTCM240GnuuUZN/y1X8C1Y8FUBvFPzH3OwvOW1pfNOex29n// 45N6aVeLBfOKYmUhJrARt9cAL4xbcCh+HAHZReTVu0X/lJmDrmrqdDjA/XO/FAkC ALGNw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=GqqRW5CmMpGpldwoZgXhgUTOsc6sqgqHqICubcUN0 PU=; b=dsO5u0RWnG329QZhoE5OgGKu4LkQMaK5TVsC6MrDV9lpYMlr3zbUsKpmm iE1B5kJpRFUDwXfzb+tnlF8iAE050iqF8p7EOEQJNEXe13oWL/c2js4rkqQka6aT MbOvzXYO6E895DmOrUK+sfNjGzKFsGXmBeMwjIrQ4pnNd4a/wfR1HptzgfoLLn4n CIwDL56cp1d01t93lklFiMTjzdriVWNCU7ZIUE22vSv/3NSSR1PkzxdgOfo9DjXQ zMAA0htiXgSxz46jHvAohTsmCGdXvykhwG/FxywM0gL4kOXtM528qjPD/0RyFMBe Bo/UkgcoZ4Y2C7al/Fw+9lsEgXWrg==
X-ME-Sender: <xms:Hw2wXr7kkfAqoPBMrGlkwL78FUsrVsbJ9WrGV_S0mCS6DQLlPR4nYA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedrjeeggdegkecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurheptggguffhjgffgffkfhfvofesthhqmh dthhdtvdenucfhrhhomheptehlihhsshgrucevohhophgvrhcuoegrlhhishhsrgestgho ohhpvghrfidrihhnqeenucggtffrrghtthgvrhhnpedvvdehhfduteevveehjeetjefhtd egtdekfeevuddvvddtueffhfdvheehleduteenucffohhmrghinhepshhurhhvvgihmhho nhhkvgihrdgtohhmpdhivghtfhdrohhrghenucfkphepudejfedrfeekrdduudejrdekie enucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegrlhhi shhsrgestghoohhpvghrfidrihhn
X-ME-Proxy: <xmx:Hw2wXpDJFeHHOHVAC3SQPMunSWmOyFJM2yZq3CuiD3U6VK5GJAczmQ> <xmx:Hw2wXlXmck4I5MBb4ZDfHzCFyLFrm6TnfOvicBzrohe-Fibb5WkNGg> <xmx:Hw2wXiZwyqkNDl_w6pgzHVDAU7GzL5h1CBvsgrEdkIcxb3D2IoBMtw> <xmx:Hw2wXouwS3_zIHr9OdLUealA3wwk58xMPJ5y6vnXCVAVxrttPIV7uw>
Received: from rtp-alcoop-nitro2.cisco.com (unknown [173.38.117.86]) by mail.messagingengine.com (Postfix) with ESMTPA id 3D11E306601C; Mon, 4 May 2020 08:39:59 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.5\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <DB6PR0701MB2118BC06B5CE7BE2BCD37804CEA60@DB6PR0701MB2118.eurprd07.prod.outlook.com>
Date: Mon, 04 May 2020 08:40:02 -0400
Cc: "ietf108planning@ietf.org" <ietf108planning@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <AA807DD7-7DC6-4EC8-876C-2B313A3D2F5D@cooperw.in>
References: <158857581528.28405.17372040856513106617@ietfa.amsl.com> <DB6PR0701MB2118BC06B5CE7BE2BCD37804CEA60@DB6PR0701MB2118.eurprd07.prod.outlook.com>
To: tom petch <ietfid@btconnect.com>
X-Mailer: Apple Mail (2.3445.9.5)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf108planning/IGWZ9nkoOcpaIc5FBQrmk1KZGYE>
Subject: Re: [Ietf108planning] Reminder: Survey on planning for possible online IETF meetings
X-BeenThere: ietf108planning@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <ietf108planning.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf108planning>, <mailto:ietf108planning-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf108planning/>
List-Post: <mailto:ietf108planning@ietf.org>
List-Help: <mailto:ietf108planning-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf108planning>, <mailto:ietf108planning-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 May 2020 12:46:24 -0000

Thanks Tom. The IESG has this question on its radar. We will consider it further after we see understand from the survey whether the community wants a replacement online meeting at all should the in-person meeting need to be cancelled.

Alissa


> On May 4, 2020, at 7:15 AM, tom petch <ietfid@btconnect.com> wrote:
> 
> One issue that I did not see addressed in this, which spells out a number of possible arrangements, is whether or not the submission window for I-D would remain and if so when would submission be inhibited.  With one fixed week for an IETF meeting then the time to close the window is clear even when it causes problems with systems being overloaded with hundreds of I-D being announced i.e.. removing the window has much to be said for it.
> 
> With an online meeting, I am unclear what happens to the window.
> 
> Tom Petch
> 
> ________________________________________
> From: IETF-Announce <ietf-announce-bounces@ietf.org> on behalf of IETF Executive Director <exec-director@ietf.org>
> Sent: 04 May 2020 08:03
> To: IETF Announcement List
> Subject: Reminder: Survey on planning for possible online IETF meetings
> 
> This is a reminder that we need the IETF community to help us plan for the possibility that one or more upcoming IETF meetings in 2020 and possibly 2021 may not be able to go ahead in person.  You can help us with this by filling out the following survey:
> 
>        https://www.surveymonkey.com/r/5328FFJ
> 
> So far we have 114 responses and we would ideally like 500 or more.
> 
> The survey contains the following pages and will take 15-20 minutes to complete:
> 
> 1. Welcome
> 2. Online IETF 107 and the subsequent virtual interims
> 3. Replacing a cancelled in-person meeting
> 4. Online meeting format and timezone
> 5. Replicating humming
> 6. Replicating the hallway environment
> 7. Fees
> 8. Thanks and anything else
> 
> We run the survey in anonymous mode which means that we only see data that you explicitly provide.
> 
> Thank you in advance for your help.
> 
> --
> Alissa Cooper, IETF Chair
> Jay Daley, IETF Executive Director
> Colin Perkins, IRTF Chair
> 
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce
> 
> -- 
> Ietf108planning mailing list
> Ietf108planning@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf108planning