Re: IETF 107 and Corona Virus? - timezone

avri doria <> Sun, 16 February 2020 20:04 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 4068E120033 for <>; Sun, 16 Feb 2020 12:04:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.253
X-Spam-Status: No, score=-1.253 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id NksVAkDGc61W for <>; Sun, 16 Feb 2020 12:04:26 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 5A3ED12001B for <>; Sun, 16 Feb 2020 12:04:26 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 240AD181D341A for <>; Sun, 16 Feb 2020 20:04:25 +0000 (UTC)
X-Session-Marker: 6176726940646F7269612E6F7267
X-Spam-Summary: 20, 1.5, 0, , d41d8cd98f00b204,, :, RULES_HIT:41:152:355:379:599:800:854:960:973:988:989:1260:1261:1277:1311:1313:1314:1345:1359:1381:1437:1515:1516:1518:1534:1542:1593:1594:1605:1711:1730:1747:1777:1792:2194:2199:2393:2551:2553:2559:2562:2693:2900:2917:2987:3138:3139:3140:3141:3142:3865:3866:3867:3868:3870:3871:3872:3873:3874:4184:4250:4641:4648:5007:6119:7576:7652:7903:9036:9545:10009:10400:10450:10455:10848:11232:11658:11914:12043:12050:12305:12663:12740:12760:12895:13071:13095:13137:13150:13230:13231:13846:14039:14180:14181:14721:19904:19999:21060:21063:21080:21324:21433:21451:21627:21740:21772:30028:30046:30054:30063:30090:30091, 0, RBL:none, CacheIP:none, Bayesian:0.5, 0.5, 0.5, Netcheck:none, DomainCache:0, MSF:not bulk, SPF:, MSBL:0, DNSBL:none, Custom_rules:0:1:0, LFtime:2, LUA_SUMMARY:none
X-HE-Tag: can89_43a0f159d8630
X-Filterd-Recvd-Size: 3737
Received: from [] ( []) (Authenticated sender: by (Postfix) with ESMTPA for <>; Sun, 16 Feb 2020 20:04:24 +0000 (UTC)
Subject: Re: IETF 107 and Corona Virus? - timezone
References: <> <>
From: avri doria <>
Message-ID: <>
Date: Sun, 16 Feb 2020 15:04:23 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.5.0
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Content-Language: en-US
X-Antivirus: Avast (VPS 200215-0, 02/15/2020), Outbound message
X-Antivirus-Status: Clean
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: Sun, 16 Feb 2020 20:04:28 -0000


When I remote attend meetings in another timezone, I think of it as jet
lag without the jet.


On 16-Feb-20 03:29, Stewart Bryant wrote:
> We all suffer from and recover from jet lag in different ways, and the same with adapting to antisocial work shifts, but I find the TZ argument strange.
> If you want to attend the whole meeting, then shifting your day is no worse than what first responders such as the police service do every week here in UK. 
> At least with doing a time shift rather than a trip you do not need to worry about the dehydration and stress of a long flight.
> Stewart
>> On 16 Feb 2020, at 07:37, Roni Even (A) <> 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.
>> 1. The meeting time for me was from 2:00AM till 10:00 AM. (9:00-17:00 in Japan) for three days.
>> 2. I used the lunch break to try to catch some sleep, due to lack of enough time to sleep
>> 3. Starting at 2:00 AM did not provide enough time to have a healthy night sleep before starting my daily attendance.
>> 4. The recovery from the "jetlag" was much slower than when attending the meeting in person.
>> My conclusion was that I will try to avoid as much as I can this mode of participating from remote in a meeting that takes a couple of days in which I have to attend multiple sessions.
>> It is not healthy.
>> One other advantage of a f2f meeting is the "official" and non-official off line sessions/meetings that I find very productive while attending the IETF meeting
>> If a full virtual meeting will happen and use Vancouver time zone than daily meeting from 9-18 will be 19-4AM for me
>> Roni Even
>>> -----Original Message-----
>>> From: ietf [] On Behalf Of Andrew Alston
>>> Sent: Thursday, February 13, 2020 8:48 AM
>>> To:
>>> Subject: IETF 107 and Corona Virus?
>>> Hi All,
>>> I am just wondering if there are any thoughts on the status of the IETF 107
>>> meeting in light of the corona virus.
>>> Particularly in light of the fact that for safety reasons mobile world congress
>>> has been cancelled and we're seeing other events being cancelled in light of
>>> this as well.  Should it be considered a safe and responsible move to go
>>> ahead with this meeting or should we be looking at an entirely virtual
>>> meeting in light of the situation?
>>> Andrew