Re: [Anima] Hold for IoT Onboarding Virtual Meeting

Carsten Bormann <cabo@tzi.org> Thu, 08 August 2019 18:38 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 99755120220; Thu, 8 Aug 2019 11:38:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.197
X-Spam-Level:
X-Spam-Status: No, score=-4.197 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 lJ7z2oO_szYB; Thu, 8 Aug 2019 11:38:50 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1A1CC12023C; Thu, 8 Aug 2019 11:38:38 -0700 (PDT)
Received: from [192.168.217.120] (p548DCCB9.dip0.t-ipconnect.de [84.141.204.185]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 464HFS4HvmzyxN; Thu, 8 Aug 2019 20:38:36 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <20190808182152.csrqbf4tv77kwl3g@faui48f.informatik.uni-erlangen.de>
Date: Thu, 08 Aug 2019 20:38:35 +0200
Cc: "Eliot Lear (elear)" <elear@cisco.com>, "iot-onboarding@ietf.org" <iot-onboarding@ietf.org>, "anima@ietf.org" <anima@ietf.org>
X-Mao-Original-Outgoing-Id: 586982314.400864-2fff8729ac4ad2749d1f1f1416f7c6b2
Content-Transfer-Encoding: quoted-printable
Message-Id: <832011CC-F194-49D8-B78D-672C82B42006@tzi.org>
References: <BYAPR11MB38142E3CA85751BFD7CB8A53BFD70@BYAPR11MB3814.namprd11.prod.outlook.com> <20190808182152.csrqbf4tv77kwl3g@faui48f.informatik.uni-erlangen.de>
To: Toerless Eckert <tte@cs.fau.de>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/IYEUPYVmPpwcq3KAoVDzvV2IHA4>
Subject: Re: [Anima] Hold for IoT Onboarding Virtual Meeting
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Aug 2019 18:38:53 -0000

On Aug 8, 2019, at 20:21, Toerless Eckert <tte@cs.fau.de> wrote:
> 
>> 5:00 pm - 6:00 pm Thursday, Aug 29 2019 (UTC+01:00) Amsterdam, Berlin,
>> Bern, Rome, Stockholm, Vienna
> 
> And webex continues to confuse me,

Webex is just following the great tradition of certain other widely used calendaring tools: foist the confusion of the people that designed it on all of its users.

> because UTC+1 is NOT the local time
> on Aug 29 in Amsterdam/Berlin because of DST,

The “UTC+1” is just a lame way of saying what the time in Amsterdam/Berlin normally is, for people who don’t know where those weird settlements might be.

> so is the meeting at
> 5 PM UTC+1 or at 5 PM local time in Amsterdam/Berlin (UTC+2) ?

Webex is trying to tell you the meeting is at 17:00 (5 pm for people who get their time from sundials) at Amsterdam/Berlin local time, which happens to be UTC+0200 on that date.  You can always look up whether DST applies on timeanddate.com; this is none of Webex’s business.  Webex only tells you where Amsterdam/Berlin approximately are, because you are not expected to know that.

> Best to wait for EU to get rid of DST to fix this webex bug *sigh*.

Actually, that is probably true.  But if some countries go for permanent DST, Webex will then always show the wrong time and not just half the year.

The real fix is to announce all meetings in Reykjavik time (UTC+0000 the whole year).  Log in at ietf.webex.com, use the menu to go to preferences, and set the time zone to Monrovia/Reykjavik.

Grüße, Carsten