RE: IETF 107 and Corona Virus? - timezone
John C Klensin <john-ietf@jck.com> Sun, 16 February 2020 18:25 UTC
Return-Path: <john-ietf@jck.com>
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 EF27312001B for <ietf@ietfa.amsl.com>; Sun, 16 Feb 2020 10:25:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 enWUoFIVU4pH for <ietf@ietfa.amsl.com>; Sun, 16 Feb 2020 10:25:38 -0800 (PST)
Received: from bsa3.jck.com (bsa3.jck.com [65.175.133.137]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E9680120024 for <ietf@ietf.org>; Sun, 16 Feb 2020 10:25:37 -0800 (PST)
Received: from hp5.int.jck.com ([198.252.137.153] helo=JcK-HP5.jck.com) by bsa3.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1j3Obm-0001bu-9S; Sun, 16 Feb 2020 13:25:34 -0500
Date: Sun, 16 Feb 2020 13:25:29 -0500
From: John C Klensin <john-ietf@jck.com>
To: "Roni Even (A)" <roni.even@huawei.com>
cc: ietf@ietf.org
Subject: RE: IETF 107 and Corona Virus? - timezone
Message-ID: <34D2DDC68D63FC374FE43A9C@JcK-HP5.jck.com>
In-Reply-To: <6E58094ECC8D8344914996DAD28F1CCD27D91338@dggemm526-mbx.china.huawei.com>
References: <6E58094ECC8D8344914996DAD28F1CCD27D91338@dggemm526-mbx.china.huawei.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Nr9tdKtmOcoH2caP3Z2CLuXxvGk>
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: Sun, 16 Feb 2020 18:25:40 -0000
--On Sunday, 16 February, 2020 07:37 +0000 "Roni Even (A)" <roni.even@huawei.com> wrote: > One issue to consider about having an entirely virtual > meeting is what are the implication on participants in > different time zone. Attending few scattered session may not > be a big issue but if one wants to attend many sessions it > becomes a problem. > > My personal experience when trying to attend a QUIC WG Interim > meeting in Japan was very bad. >... Roni, As Stewart points out, different people react in different ways. However, at least in principle, attending a full-week meeting remotely should be no worse from a time zone standpoint than going in person if one just shifts onto the meeting time zone for the week. Same time zone shift as f2f, none of the physical and aggravation costs of dealing with airports, airport transit, long and often cramped plane flights, etc. The only way in which remote attendance of that type becomes more difficult from a body rhythm standpoint is if one tries to stay on one's normal schedule and activities at home and the remote schedule at the same time. I am just guessing from your explanation, but that 2AM QUIC meeting may have been a problem because you tried to say on your normal sleep (and probably eating) schedule rather that going to sleep at 5PM or earlier your time. That is, of course, another type of shift that some people find easier than others. And I've often suspected that, despite all the complaints about jet lag, at least some people find that being stuck in a large can with wings, with few external stimuli, for many hours may actually help make the shift and make it back after the meeting. But... Of course, part of the reason the IETF originally developed its rules about decisions being made on mailing lists was that, back then, a very significant fraction of the participants did not have corporate (or equivalent) support for attending week-long meetings in expensive and far-away places. What I was told when I started attending and participating at f2f meetings (after several years on mailing lists only) was that the purpose of f2f WG discussions included catching people up a bit but that they are primarily to bring out, identify, and understand a broader range of issues. Patterns have shifted -- in some cases for very good reasons such as more participation from more parts of the world. But maybe, if organizational or government policies keep a significant number of contributors from f2f attendance, we should consider learning from our own history and consider an entirely different remote participation option. That would be to shut Meetecho down entirely except to live-stream various meetings (really good scaling properties even if we don't need to return to multicast) and get really serious about the mailing list rule - not for ratification, but for accurately summarizing and following up the f2f discussions, making sure that all perspectives are aired and discussed. That would not work unless WG Chairs and ADs understood the importance of that approach and were willing to put effort into being sure that it succeeded and that both those who got to the meeting and those who, for whatever reason, did not, were treated fairly, but that might still be easier than trying to manage both in-room and long remote speaker queues in a careful and fair way. Agree with him or not, Keith Moore's recent note about interim meetings may reflect a different view of the same underlying issues. john
- RE: IETF 107 and Corona Virus? - timezone Roni Even (A)
- Re: IETF 107 and Corona Virus? - timezone Stewart Bryant
- Excessive use of interim meetings Keith Moore
- Re: Excessive use of interim meetings Phillip Hallam-Baker
- RE: IETF 107 and Corona Virus? - timezone John C Klensin
- Re: IETF 107 and Corona Virus? - timezone Brian E Carpenter
- Re: IETF 107 and Corona Virus? - timezone John C Klensin
- Re: IETF 107 and Corona Virus? - timezone avri doria
- Re: Excessive use of interim meetings Mark Andrews
- Re: Excessive use of interim meetings Benjamin Kaduk
- Re: Excessive use of interim meetings Keith Moore
- RE: IETF 107 and Corona Virus? - timezone Ron Bonica
- Re: Excessive use of interim meetings John C Klensin
- Re: Excessive use of interim meetings Rob Sayre
- Re: IETF 107 and Corona Virus? - timezone Christian Huitema
- RE: IETF 107 and Corona Virus? - timezone Roni Even (A)
- Re: Excessive use of interim meetings Phillip Hallam-Baker
- Re: Excessive use of interim meetings Keith Moore
- Re: Excessive use of interim meetings Nico Williams
- Scaling the IETF (Re: Excessive use of interim me… Nico Williams
- Re: Excessive use of interim meetings John C Klensin
- Re: Excessive use of interim meetings Phillip Hallam-Baker
- Re: Excessive use of interim meetings John C Klensin