Re: IETF 107 and Corona Virus? - timezone
John C Klensin <john-ietf@jck.com> Sun, 16 February 2020 19:44 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 7906E120033 for <ietf@ietfa.amsl.com>; Sun, 16 Feb 2020 11:44:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=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 ZRHneiOU0cWP for <ietf@ietfa.amsl.com>; Sun, 16 Feb 2020 11:44:13 -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 1A0A112001B for <ietf@ietf.org>; Sun, 16 Feb 2020 11:44:13 -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 1j3Ppn-0001hT-5D; Sun, 16 Feb 2020 14:44:07 -0500
Date: Sun, 16 Feb 2020 14:44:02 -0500
From: John C Klensin <john-ietf@jck.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, "Roni Even (A)" <roni.even@huawei.com>
cc: ietf@ietf.org
Subject: Re: IETF 107 and Corona Virus? - timezone
Message-ID: <E01CF12F305C843866553DDA@JcK-HP5.jck.com>
In-Reply-To: <20a86161-3a77-9c30-1d39-06ef9e47398f@gmail.com>
References: <6E58094ECC8D8344914996DAD28F1CCD27D91338@dggemm526-mbx.china.huawei.com> <34D2DDC68D63FC374FE43A9C@JcK-HP5.jck.com> <20a86161-3a77-9c30-1d39-06ef9e47398f@gmail.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/2-wbOJC09P5Y7HrAOEkribfBoeU>
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:44:15 -0000
--On Monday, 17 February, 2020 08:28 +1300 Brian E Carpenter <brian.e.carpenter@gmail.com> wrote: > 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, In case it wasn't clear from what I wrote, I agree completely. Even without a complicating family situation, it is hard to resist the meetings or other commitments in the middle of the (local time) day when the IETF (or other remote) schedule is locally in the middle of the night. And, as soon as one need to be in both time zones at the same time, remote participation gets tough, maybe even tougher than travel to the meeting. The only real solution is finding means of communication that are insensitive to precise timing and we have, and have tested, one of those -- I believe it is called "email". It does impose a different requirement to which, as Keith has indirectly pointed out, some of us have become resistant in recent years. That is the ability and willingness to write, and read, email messages that actually contain careful analyses of issues rather than adopting "TL;DR" attitudes. best, 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