IETF Logo Mail Archive

Re: IETF in July

Michael StJohns <mstjohns@comcast.net> Mon, 23 March 2020 17:03 UTC

Return-Path: <mstjohns@comcast.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4761F3A07C0 for <ietf@ietfa.amsl.com>; Mon, 23 Mar 2020 10:03:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.net
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 AC0oQ3lPokkb for <ietf@ietfa.amsl.com>; Mon, 23 Mar 2020 10:03:49 -0700 (PDT)
Received: from resqmta-ch2-12v.sys.comcast.net (resqmta-ch2-12v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:44]) (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 37B623A07AC for <ietf@ietf.org>; Mon, 23 Mar 2020 10:03:48 -0700 (PDT)
Received: from resomta-ch2-10v.sys.comcast.net ([69.252.207.106]) by resqmta-ch2-12v.sys.comcast.net with ESMTP id GQE7jpAVPtdfMGQUNjnkIa; Mon, 23 Mar 2020 17:03:47 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=20190202a; t=1584983027; bh=Y2cspWn/q3HFuVERKcwAQ4yFuOV9lQnpng6lI4P7VRw=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=TzB9m0FOgzJQ1u4n0QOpK8h/LF0JIVZaiV3Ae5hVhuK/Ib+grC5BQsBS/ptp5rop+ DppFAa9PCSgzFBu+L09Vz8gtB5sjOjjWYsr/0fVV6vA8tIjGTmLzlURXM8cX+PK6q9 aEH7omSgOYoL2vQeNZXkfidx3HH/dbtvQP1u84q6Y7Ecqijh5lixFZ5pNywh5oKMLX bYpjAWl1/5WT3CbR95WbUcsHB+dhIgjEVV+APGrEBJeKwHbDIWqlNYHEnFlaYV3aCm qupZPtWBRf5r66OoP4Bf29U1XEdglDOVEKpCPs81lP1fPIOX1YHWxFKnLFMLAIbtGF cnEMV1LvTtu0A==
Received: from [192.168.1.115] ([71.163.188.115]) by resomta-ch2-10v.sys.comcast.net with ESMTPSA id GQUGjfG5Fg6zoGQUHjSLQm; Mon, 23 Mar 2020 17:03:45 +0000
X-Xfinity-VAAS: gggruggvucftvghtrhhoucdtuddrgedugedrudegkedgleehucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuvehomhgtrghsthdqtfgvshhipdfqfgfvpdfpqffurfetoffkrfenuceurghilhhouhhtmecufedttdenucenucfjughrpefuvfhfhffkffgfgggjtgfgsehtkeertddtfeejnecuhfhrohhmpefoihgthhgrvghlucfuthflohhhnhhsuceomhhsthhjohhhnhhssegtohhmtggrshhtrdhnvghtqeenucfkphepjedurdduieefrddukeekrdduudehnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehhvghloheplgduledvrdduieekrddurdduudehngdpihhnvghtpeejuddrudeifedrudekkedrudduhedpmhgrihhlfhhrohhmpehmshhtjhhohhhnshestghomhgtrghsthdrnhgvthdprhgtphhtthhopehivghtfhesihgvthhfrdhorhhg
X-Xfinity-VMeta: sc=0.00;st=legit
Subject: Re: IETF in July
To: ietf@ietf.org
References: <DM6PR05MB63488A5D5D14D11CBF145CEBAEF50@DM6PR05MB6348.namprd05.prod.outlook.com> <2E3DFE67-85D0-4259-85D5-09FF9A262B48@tzi.org> <B28C7981-1AF4-4299-AAA0-4ABA667D81B4@consulintel.es> <CAOj+MMHROy2UA7YUdRrTM240nQY4ykbYHtFME87FPznNDMdcUQ@mail.gmail.com> <0B0BBC48-1504-4847-85B1-36700873D78E@consulintel.es> <5134FD38-F675-4E81-8C57-1EBCBE475705@tzi.org> <37205051-dab1-d59e-5fb2-fbcef327302b@nostrum.com> <CAJc3aaMFdyYxeX_6bZCmOJ8q8KBaHYmV79N70O85dHZ3AWUcaA@mail.gmail.com> <50BB2CE9-DEFC-4269-8FDC-ACA708FC5BE5@gmail.com> <0E824A81-B9ED-485C-9183-84C17CECFD88@consulintel.es> <CA5E598A-4A07-4DDD-9D23-B1E85018B17D@gmail.com>
From: Michael StJohns <mstjohns@comcast.net>
Message-ID: <8e16f641-08b0-8234-d9c5-f18637198369@comcast.net>
Date: Mon, 23 Mar 2020 13:03:39 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Thunderbird/68.6.0
MIME-Version: 1.0
In-Reply-To: <CA5E598A-4A07-4DDD-9D23-B1E85018B17D@gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ggqdolUReYhLiUI6hIyhkAksJ2o>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Mar 2020 17:03:52 -0000

On 3/23/2020 12:31 PM, Bob Hinden wrote:
> I have no idea what the state of the world will be regarding the July IETF meeting, but given the current state and lack of a vaccine, I really hope that the IESG and LLC are working hard to plan an all virtual IETF July meeting.   Perhaps extensions to Meetecho that could make that possible.  Lots of challenges for sure, but I think there is time to prepare.
>
> Hopefully it won’t be necessary, but good to have a workable plan in place.
>
> Bob
>
>
I've been thinking about buying VR gear, with an eye to being able to 
recreate some of the informal parts of the IETF meetings, but I haven't 
been able to find any software that would allow for 100+ people in the 
same virtual space using VR.

I would be surprised (e.g. I wouldn't use *your* money to  bet on it) if 
we had an in-person July meeting and I'm not sanguine about the Bangkok 
meeting happening either.  One of the side effects of "flattening the 
curve" is the extension of time for which we have to be vigilant and I 
think that is going to bring us out to the end of the year and possibly 
later.  I haven't actually seen any math on this, but given that the 
area under the curve is constant in either case, it ought to be possible 
to estimate where the drop off is rather than making guesses.

Mike

v2.23.0 | Report a Bug | By Email