Re: IETF 107 and Corona Virus? - timezone

Christian Huitema <huitema@huitema.net> Mon, 17 February 2020 05:49 UTC

Return-Path: <huitema@huitema.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 6A82512011C for <ietf@ietfa.amsl.com>; Sun, 16 Feb 2020 21:49:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-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 QhOwYiSn-hgu for <ietf@ietfa.amsl.com>; Sun, 16 Feb 2020 21:49:19 -0800 (PST)
Received: from mx36-out10.antispamcloud.com (mx36-out10.antispamcloud.com [209.126.121.30]) (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 F1DD2120114 for <ietf@ietf.org>; Sun, 16 Feb 2020 21:49:18 -0800 (PST)
Received: from xse223.mail2web.com ([66.113.196.223] helo=xse.mail2web.com) by mx63.antispamcloud.com with esmtp (Exim 4.92) (envelope-from <huitema@huitema.net>) id 1j3ZHO-000351-G4 for ietf@ietf.org; Mon, 17 Feb 2020 06:49:17 +0100
Received: from xsmtp21.mail2web.com (unknown [10.100.68.60]) by xse.mail2web.com (Postfix) with ESMTPS id 48LY2b4h4xz4jp for <ietf@ietf.org>; Sun, 16 Feb 2020 21:49:11 -0800 (PST)
Received: from [10.5.2.49] (helo=xmail11.myhosting.com) by xsmtp21.mail2web.com with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from <huitema@huitema.net>) id 1j3ZHL-0004Tb-HB for ietf@ietf.org; Sun, 16 Feb 2020 21:49:11 -0800
Received: (qmail 3313 invoked from network); 17 Feb 2020 05:49:11 -0000
Received: from unknown (HELO [192.168.1.102]) (Authenticated-user:_huitema@huitema.net@[172.58.46.153]) (envelope-sender <huitema@huitema.net>) by xmail11.myhosting.com (qmail-ldap-1.03) with ESMTPA for <ietf@ietf.org>; 17 Feb 2020 05:49:10 -0000
To: avri@acm.org, ietf@ietf.org
References: <6E58094ECC8D8344914996DAD28F1CCD27D91338@dggemm526-mbx.china.huawei.com> <19C010F0-B926-4A2E-87F9-CAFF1D3F5FDD@gmail.com> <7fbc2ccc-dcf9-0452-fe7b-494179a301e2@acm.org>
From: Christian Huitema <huitema@huitema.net>
Autocrypt: addr=huitema@huitema.net; prefer-encrypt=mutual; keydata= mQENBFIRX8gBCAC26usy/Ya38IqaLBSu33vKD6hP5Yw390XsWLaAZTeQR64OJEkoOdXpvcOS HWfMIlD5s5+oHfLe8jjmErFAXYJ8yytPj1fD2OdSKAe1TccUBiOXT8wdVxSr5d0alExVv/LO I/vA2aU1TwOkVHKSapD7j8/HZBrqIWRrXUSj2f5n9tY2nJzG9KRzSG0giaJWBfUFiGb4lvsy IaCaIU0YpfkDDk6PtK5YYzuCeF0B+O7N9LhDu/foUUc4MNq4K3EKDPb2FL1Hrv0XHpkXeMRZ olpH8SUFUJbmi+zYRuUgcXgMZRmZFL1tu6z9h6gY4/KPyF9aYot6zG28Qk/BFQRtj7V1ABEB AAG0J0NocmlzdGlhbiBIdWl0ZW1hIDxodWl0ZW1hQGh1aXRlbWEubmV0PokBOQQTAQIAIwUC UhFfyAIbLwcLCQgHAwIBBhUIAgkKCwQWAgMBAh4BAheAAAoJEJNDCbJVyA1yhbYH/1ud6x6m VqGIp0JcZUfSQO8w+TjugqxCyGNn+w/6Qb5O/xENxNQ4HaMQ5uSRK9n8WKKDDRSzwZ4syKKf wbkfj05vgFxrjCynVbm1zs2X2aGXh+PxPL/WHUaxzEP7KjYbLtCUZDRzOOrm+0LMktngT/k3 6+EZoLEM52hwwpIAzJoscyEz7QfqMOZtFm6xQnlvDQeIrHx0KUvwo/vgDLK3SuruG1CSHcR0 D24kEEUa044AIUKBS3b0b8AR7f6mP2NcnLpdsibtpabi9BzqAidcY/EjTaoea46HXALk/eJd 6OLkLE6UQe1PPzQC4jB7rErX2BxnSkHDw50xMgLRcl5/b1a5AQ0EUhFfyAEIAKp7Cp8lqKTV CC9QiAf6QTIjW+lie5J44Ad++0k8gRgANZVWubQuCQ71gxDWLtxYfFkEXjG4TXV/MUtnOliG 5rc2E+ih6Dg61Y5PQakm9OwPIsOx+2R+iSW325ngln2UQrVPgloO83QiUoi7mBJPbcHlxkhZ bd3+EjFxSLIQogt29sTcg2oSh4oljUpz5niTt69IOfZx21kf29NfDE+Iw56gfrxI2ywZbu5o G+d0ZSp0lsovygpk4jK04fDTq0vxjEU5HjPcsXC4CSZdq5E2DrF4nOh1UHkHzeaXdYR2Bn1Y wTePfaHBFlvQzI+Li/Q6AD/uxbTM0vIcsUxrv3MNHCUAEQEAAYkCPgQYAQIACQUCUhFfyAIb LgEpCRCTQwmyVcgNcsBdIAQZAQIABgUCUhFfyAAKCRC22tOSFDh1UOlBB/94RsCJepNvmi/c YiNmMnm0mKb6vjv43OsHkqrrCqJSfo95KHyl5Up4JEp8tiJMyYT2mp4IsirZHxz/5lqkw9Az tcGAF3GlFsj++xTyD07DXlNeddwTKlqPRi/b8sppjtWur6Pm+wnAHp0mQ7GidhxHccFCl65w uT7S/ocb1MjrTgnAMiz+x87d48n1UJ7yIdI41Wpg2XFZiA9xPBiDuuoPwFj14/nK0elV5Dvq 4/HVgfurb4+fd74PV/CC/dmd7hg0ZRlgnB5rFUcFO7ywb7/TvICIIaLWcI42OJDSZjZ/MAzz BeXm263lHh+kFxkh2LxEHnQGHCHGpTYyi4Z3dv03HtkH/1SI8joQMQq00Bv+RdEbJXfEExrT u4gtdZAihwvy97OPA2nCdTAHm/phkzryMeOaOztI4PS8u2Ce5lUB6P/HcGtK/038KdX5MYST Fn8KUDt4o29bkv0CUXwDzS3oTzPNtGdryBkRMc9b+yn9+AdwFEH4auhiTQXPMnl0+G3nhKr7 jvzVFJCRif3OAhEm4vmBNDE3uuaXFQnbK56GJrnqVN+KX5Z3M7X3fA8UcVCGOEHXRP/aubiw Ngawj0V9x+43kUapFp+nF69R53UI65YtJ95ec4PTO/Edvap8h1UbdEOc4+TiYwY1TBuIKltY 1cnrjgAWUh/Ucvr++/KbD9tD6C8=
Subject: Re: IETF 107 and Corona Virus? - timezone
Message-ID: <693230a0-064f-02d8-8a1e-ca1df86af79f@huitema.net>
Date: Sun, 16 Feb 2020 21:49:09 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.4.2
MIME-Version: 1.0
In-Reply-To: <7fbc2ccc-dcf9-0452-fe7b-494179a301e2@acm.org>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Language: en-US
X-Originating-IP: 66.113.196.223
X-Spampanel-Domain: xsmtpout.mail2web.com
X-Spampanel-Username: 66.113.196.223/32
Authentication-Results: antispamcloud.com; auth=pass smtp.auth=66.113.196.223/32@xsmtpout.mail2web.com
X-Spampanel-Outgoing-Class: unsure
X-Spampanel-Outgoing-Evidence: Combined (0.15)
X-Recommended-Action: accept
X-Filter-ID: Mvzo4OR0dZXEDF/gcnlw0QHHUXH8HYgJuwhvgiygxCWpSDasLI4SayDByyq9LIhVUZbR67CQ7/vm /hHDJU4RXkTNWdUk1Ol2OGx3IfrIJKywOmJyM1qr8uRnWBrbSAGDAzc5Jb/eaE0k3pqeq35lKbgN zB/4Jkrw1eDLcif59ftfFMyBcEqss9opQ/fVNWQBU7Tmz6iKnkQL9gqsxD347235Nhqq+/HvroPq 8GSPg+5aB4itzNZ07CdqP+KMfGjQPLhBThvdgyPN49yzDQzRHY6jSvfpO+1kZkomjtjB6X5Q5Q9f RUeIpTIC2ySfqvnqLwoxlgatmaBb0rBiK9xbkDrUqzcKIief90MVLZY9LbIZh9+IQ1oS9LBn3VIP 95Jz7ujRlJ9wSMlhvaudJXZ9EIBG/qaR+8r9SKFMmPJLf850OvZYsmoVQuOIhwKLK6IKBNB4LZ0v UHHKTzJX7b1JhLSQQ4vSj0QEim26t/Moy0UPX5E73H1QfrH/5kkrV/Cr0bm2vWdo8usP65i82q1C dZgGrpL44wdx9eXqjQjbvUopOMQJvQ/Ck3iiU+4DQAj3fuQgzT3K9JUHTNiGwfwAm/WxnoDhSIwu dyqaU1JgcKMOW4CkjtZBB9EE1lU6QPXuHg27/WGFtzgWA3bVlmvbqweYUOp7A73HI6oJg7w/VoeJ mZ6P40nPnvyoji6zg2JMTJD1rH7L4CCh2rwF43k4311677oPXF7r5zsW33ZNlioeEsGOJOKU/kLG nxJMOi7dkrv/Hi7R9+QPiwvVv0GyfzzAXPU1UvCyITFs2AML0PrWGVxNMVWkY4wbM+C9TW8aHHAS JNUmoOHSoqgqxfHmWRWcrRhLeB34s3hUb32GO+0K27+P2lXcinCIgayWlA4E08QV3No+S2msRDep v5w/kkG0v17AmegcpQ0tml/sN9lmMy/o83jVXTcfb9k0nLWblJy7uxV6dw8jzlsaNZe6hynMJcjx DydxsJEju76A7X1QIVydqXpZ6MHhiKws9Iiut28r9wo4SqUIg8Yh9hAM0n3LLzx/F2gT3wl8JQJv Bho=
X-Report-Abuse-To: spam@quarantine11.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/AY0OzB4YOBV-nOjshBtAIogqRyY>
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, 17 Feb 2020 05:49:22 -0000

I recently attended several Quic interim meetings remotely --2 days of
interop and 2 days of meeting. Couple of other meetings as well. Yes, it
can be hard, and Yes it does feel like jet lag without the jet, and Yes
it has some impact on family life. But as John Klensin said "different
people react in different ways." Overall, I find that less hard than
traveling to another continent for a short meeting. I don't have to
spend a day traveling each way, so "without the jet" is actually nice. I
have way fewer chances of catching an unexpected germ in the plane or in
transit. I am probably more awake for the meeting than if I was
recovering from jet lag.

Of course it is not ideal. When you do that, you are a tiny spoke to a
big hub. This is asymmetric, and it has effects. Inserting yourself in
the conversation requires some practice. The remote audio is a best
effort service provided by volunteers, so you cannot really blame them
for the glitches. But then you have to compensate for by relying on chat
rooms and other tools. And you do miss the most of the little breakaway
sessions and discussions around lunch and dinner.

On the other hand, the Quic WG also organized "Virtual Interop"
sessions, and I found that those worked really well. Pick a calendar
date, and have people join progressively through the day or two as their
time zone permits. Every team was putting a version of their software
online for others to tests, doing frequent updates as issues were found
and fixed. There is always enough overlap between the time zones to give
each pair of teams to test against each other, discuss potential issues
with the spec, etc. This is not a "hub and spoke" model, the
configuration is symmetric for all participants.

It may be that the Virtual Interop scenario worked well because we were
doing a lot of software development and Interop testing -- good old
fashioned rough consensus and running code. But dedicating a day for
"rolling sessions" and discussions of specifications could also work.
Putting decks or videos on line, dedicating rolling time slots to
discussing drafts and issues, etc. That might be worth trying.

-- Christian Huitema

On 2/16/2020 12:04 PM, avri doria wrote:
> Hi,
>
> When I remote attend meetings in another timezone, I think of it as jet
> lag without the jet.
>
> avri
>
>
> 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) <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.
>>>
>>> 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 [mailto:ietf-bounces@ietf.org] On Behalf Of Andrew Alston
>>>> Sent: Thursday, February 13, 2020 8:48 AM
>>>> To: ietf@ietf.org
>>>> 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