Re: IETF 107 and Corona Virus? - timezone

Brian E Carpenter <brian.e.carpenter@gmail.com> Sun, 16 February 2020 19:28 UTC

Return-Path: <brian.e.carpenter@gmail.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 B9F88120033 for <ietf@ietfa.amsl.com>; Sun, 16 Feb 2020 11:28:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, 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=gmail.com
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 S48OeDA4FsDR for <ietf@ietfa.amsl.com>; Sun, 16 Feb 2020 11:28:47 -0800 (PST)
Received: from mail-pg1-x533.google.com (mail-pg1-x533.google.com [IPv6:2607:f8b0:4864:20::533]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ACA2812001B for <ietf@ietf.org>; Sun, 16 Feb 2020 11:28:47 -0800 (PST)
Received: by mail-pg1-x533.google.com with SMTP id v23so4488523pgk.2 for <ietf@ietf.org>; Sun, 16 Feb 2020 11:28:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=jIzZ8F3Fv0bjy/a4lFizctE0zUFL+v1Pnl39Y2PWmY4=; b=EvIxHEneIB12yQLrWv6RMWSd+c7JZZ49IuIHskStI33pbcBc3iwY5AKdTaLwnfA7kM 9ODbqv7n7saH1Ij69Bp6yLfIWPbZtV7zvaSb9DW3JVAwb/iJdqVI0+qS/yVRt0c9GOdN aIA0HRki1qOMI3PMNzdudWYDBD7Cc9QiE4H6wGVt0xnmFuU7EURMYXjrFUblTqwxVQOZ FfPwIZC3KMiswWKz9AvXq1INBjb0ZFhbNBsqdiobGq53qw5Xky44lGE3W/FbDeDzu0c6 KB8j+VURVq8yIA2E48gjJkKXd1paX1iHDnvZUVSEd4dnQPWmBYapqp6uIXR0PyVo9OCD lnGA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=jIzZ8F3Fv0bjy/a4lFizctE0zUFL+v1Pnl39Y2PWmY4=; b=CPWqPmRQgcqMxYrVStceUehhugIqmUiqQHkPK2atXMcENJC79FC8WgssskwmWywJ1j KfBu/zdrmRmKM2b6esQZaWfhkbcsfSOJGREmhJvOBiyNMasbqW4DfUzsxlOxcZ2UeFIK +F2PytYRAIjNN3ah4TV+qNuQY1f0+G39f/P4h7bSbcZqne8YycuUubDDikAEOtqsQqJc yUCfwevJT0zJ2PMs27EFqMkWayVnvgxFUhTIT5tXzHhibkVwppX3f27C9LZzGY6DMI65 Q7CdtVPlYAQGU32McEopSuONMXlePStc4E289uaozea+wKGhplXnNoQBwgWII/2xURe3 mcnQ==
X-Gm-Message-State: APjAAAXbsci67f+hrEGwmdZn+Z6PHP2I5lAjSyqorKV7j9LUhib/KFN0 Xs3xg7qU4kYRGgEq5FVP2+RPqC4G
X-Google-Smtp-Source: APXvYqzZXAI04hx9kn9E9yvEfpLnLOoavefpThtN4RaCleK308EZQotVge8i6sQSta1LXz2hUs8agw==
X-Received: by 2002:aa7:98c6:: with SMTP id e6mr13338934pfm.251.1581881326819; Sun, 16 Feb 2020 11:28:46 -0800 (PST)
Received: from [192.168.178.30] ([165.84.25.143]) by smtp.gmail.com with ESMTPSA id d3sm13601397pjx.10.2020.02.16.11.28.44 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 16 Feb 2020 11:28:46 -0800 (PST)
Subject: Re: IETF 107 and Corona Virus? - timezone
To: John C Klensin <john-ietf@jck.com>, "Roni Even (A)" <roni.even@huawei.com>
Cc: ietf@ietf.org
References: <6E58094ECC8D8344914996DAD28F1CCD27D91338@dggemm526-mbx.china.huawei.com> <34D2DDC68D63FC374FE43A9C@JcK-HP5.jck.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <20a86161-3a77-9c30-1d39-06ef9e47398f@gmail.com>
Date: Mon, 17 Feb 2020 08:28:43 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <34D2DDC68D63FC374FE43A9C@JcK-HP5.jck.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/i6LNBrqBeScPTfOc7ZO2wxeWVbw>
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 19:28:50 -0000

On 17-Feb-20 07:25, John C Klensin wrote:
> 
> 
> --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.

Depending on one's family situation,  shifting onto a different
time zone at home may be even more disruptive and painful than travel.
And in fact, virtually impossible to explain to the rest of the
household.

Yes, I realise that shift workers have to deal with this, but shift
work is a terrible thing anyway.

Let's not kid ourselves that there is an easy answer here.

    Brian