Re: [111attendees] timing

Pedro Martinez-Julia <pedro@nict.go.jp> Wed, 28 July 2021 22:17 UTC

Return-Path: <pedro@nict.go.jp>
X-Original-To: 111attendees@ietfa.amsl.com
Delivered-To: 111attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A44B3A23EE for <111attendees@ietfa.amsl.com>; Wed, 28 Jul 2021 15:17:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.549
X-Spam-Level:
X-Spam-Status: No, score=-2.549 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.452, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=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=nict.go.jp
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 kRWv9YloBnLl for <111attendees@ietfa.amsl.com>; Wed, 28 Jul 2021 15:17:41 -0700 (PDT)
Received: from mo-csw.securemx.jp (mo-csw1516.securemx.jp [210.130.202.155]) (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 8848B3A23F3 for <111attendees@ietf.org>; Wed, 28 Jul 2021 15:17:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nict.go.jp; h=Date:From:To: Cc:Subject:Message-ID:References:MIME-Version:Content-Type: Content-Transfer-Encoding:In-Reply-To;i=pedro@nict.go.jp;s=20200225.smx;t= 1627510636; x=1628720236; bh=s6cPHD5BbFkPma5qXnpka/xJ3yBwUciD6tLmLrG8jyA=; b=jyA hSMmWFH6H5wFZPXe3ImPxkP8E2OxMKko7FlItcSBWU0GHi4U1O34hDce/JMMW0v2qwtJlX/AOH15/ tahHVGmqc+aTYv1QJOzAEEiGVlrSdzxoz1Nn7ZiRL8W3W3RZF59ierkhwePYC0t64EUiNEDLav15/ N4qTzxSofw12JR4vQ/TGvq5e45ZgOiEkAYvC7LDRY142b6hhld5mAITK7AE3qNErqiwGhdrhf0QOv FBIMkKxZZuVi3H8ElK5+lITjA0q4z9HeMdt7dn00vsmXn+ewDH/QjLoZsSeF9XyXLMInP8brM7Uit eUOojubfIqfWNXI5uA3qCPfbaJBDFYw==;
Received: by mo-csw.securemx.jp (mx-mo-csw1516) id 16SMHEO4006841; Thu, 29 Jul 2021 07:17:15 +0900
X-Iguazu-Qid: 34tr8rsmpaBIvPh7Fk
X-Iguazu-QSIG: v=2; s=0; t=1627510634; q=34tr8rsmpaBIvPh7Fk; m=9unVPJ3kjY8CeXBJF4lgrS5VmVFPshgSDU/jJUfWLrA=
Received: from mail2.nict.go.jp (ipv6.mail2.nict.go.jp [IPv6:2001:df0:232:1200::f]) by relay.securemx.jp (mx-mr1513) id 16SMHChS024560 (version=TLSv1.2 cipher=AES128-GCM-SHA256 bits=128 verify=NOT); Thu, 29 Jul 2021 07:17:13 +0900
Received: from spectre (ssh1.nict.go.jp [133.243.3.49]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail2.nict.go.jp (NICT Mail Spool Server2) with ESMTPSA id 83E7382CAB; Thu, 29 Jul 2021 07:17:12 +0900 (JST)
Date: Thu, 29 Jul 2021 07:17:08 +0900
From: Pedro Martinez-Julia <pedro@nict.go.jp>
To: Mark Andrews <marka@isc.org>
Cc: Luigi IANNONE <luigi.iannone@huawei.com>, "111attendees@ietf.org" <111attendees@ietf.org>, Carsten Bormann <cabo@tzi.org>, Toerless Eckert <tte@cs.fau.de>
Message-ID: <YQHXZJ4phH6rubJd@spectre>
References: <20210728211403.C21B7254289F@ary.qy> <AA76737E-C2D4-4C00-8347-33D15611E1D2@tzi.org> <20210728212535.GP57091@faui48e.informatik.uni-erlangen.de> <f4ffb279cd1041538733e4cfe70a88cd@huawei.com> <20210728214639.GR57091@faui48e.informatik.uni-erlangen.de> <09e8068f93284fd3a00d5769f39cf2b2@huawei.com> <BBF96CC3-69D3-4A55-ACE6-B9A26CE9A184@isc.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <BBF96CC3-69D3-4A55-ACE6-B9A26CE9A184@isc.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/111attendees/XoX4O0EAJocQRP95GS_NVvkJONo>
Subject: Re: [111attendees] timing
X-BeenThere: 111attendees@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mailing list for IETF 111 attendees <111attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/111attendees>, <mailto:111attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/111attendees/>
List-Post: <mailto:111attendees@ietf.org>
List-Help: <mailto:111attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/111attendees>, <mailto:111attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Jul 2021 22:17:48 -0000

Dear Mark and others,

This is a good point for the good organization of global meetings. For
me, living in Japan, the current timing is good. It is very early on the
morning. In contrast, in Europe, some colleagues have complained (yes,
everybody has the right to complain) about having the meeting late at
night. However, it is not "in the middle of the night" for neither of
us, which is perfect for such a global event.

Regarding the time. I had many mistakes by the date being specified in
some TZ and then it being translated by nonsense application, browser,
or whatever, so I missed the correct time. All times must be in UTC and
they must be explicitly told (adding UTC to the time). In addition, as
Mark points, the day used as label is another problem, although using
the relative day is still a problem. Days must be derived from the UTC
time, so a "date and time" must be used and organizers must be aware of
both the UTC *time* and *date* of a meeting. Applications can understand
this and replace it by the correct name of the day and/or a label such
as proposed by Mark.

Regards,
Pedro

On Thu, Jul 29, 2021 at 08:07:03AM +1000, Mark Andrews wrote:
> One hard part is actually having the days listed as Monday, Tuesday, Wednesday instead of Day 1, Day 2, Day 3.  It is Thursday here but we are on Wednesday’s program. Off by 24 hours errors are easy to make.  Even setting the calendar to the local time zone doesn’t change the titles in the schedule.  You have to look for the (+1) on the times.
> 
> > On 29 Jul 2021, at 07:50, Luigi IANNONE <luigi.iannone@huawei.com> wrote:
> > 
> > You are right 
> > 
> > https://en.wikipedia.org/wiki/Time_in_Portugal#:~:text=Daylight%20saving%20time%20(locally%20known,use%20UTC%2B00%3A00.
> > 
> > Says Azores' UTC+00:00 is actually Azores' DST.... useless...
> > 
> > Ciao
> > 
> > L.
> > 
> > 
> >> -----Original Message-----
> >> From: Toerless Eckert [mailto:tte@cs.fau.de]
> >> Sent: Wednesday, July 28, 2021 23:47
> >> To: Luigi IANNONE <luigi.iannone@huawei.com>
> >> Cc: Carsten Bormann <cabo@tzi.org>; 111attendees@ietf.org
> >> Subject: Re: [111attendees] timing
> >> 
> >> Right. Thats i think what i did some time ago, but when i look up Azores, it is
> >> part of portugal and the wiki page does not explain whether or not it has DST.
> >> 
> >> Do you want to bet whether or not that webex Azores TZ comes with or
> >> without DST ? If it comes with DST its useless.
> >> 
> >> Cheers
> >>    toerless
> >> 
> >> On Wed, Jul 28, 2021 at 09:29:20PM +0000, Luigi IANNONE wrote:
> >>> You can select the "UTC+00:00 Azores" time zone (kind of a workaround
> >>> though..)
> >>> 
> >>> Ciao
> >>> 
> >>> L.
> >>> 
> >>> 
> >>>> -----Original Message-----
> >>>> From: 111attendees [mailto:111attendees-bounces@ietf.org] On Behalf
> >>>> Of Toerless Eckert
> >>>> Sent: Wednesday, July 28, 2021 23:26
> >>>> To: Carsten Bormann <cabo@tzi.org>
> >>>> Cc: 111attendees@ietf.org
> >>>> Subject: Re: [111attendees] timing
> >>>> 
> >>>> Does Webex by now allow you to enter UTC ?
> >>>> 
> >>>> I don't think it does explicitly, and if it stil doesn't that is
> >>>> still a very annoying issue for recurring meetings.
> >>>> 
> >>>> For example for our weekly NomCom meetings i can already see how
> >>>> folks will be confused when DST ends differently in different parts
> >>>> of the planet and you have to figure out which the original TZ was
> >>>> in which the recurring meeting was done during those weeks.
> >>>> 
> >>>> Cheers
> >>>>    Toerless
> >>>> 
> >>>> 
> >>>> On Wed, Jul 28, 2021 at 11:19:00PM +0200, Carsten Bormann wrote:
> >>>>>> 
> >>>>>>> Using UTC is a big source of errors: ...
> >>>>>> 
> >>>>>> I have to completely disagree.
> >>>>> 
> >>>>> +1
> >>>>> 
> >>>>> NOT using UTC is a big source of errors. (FTFY)
> >>>>> 
> >>>>> But this is totally unrelated to the issue at hand.
> >>>>> 
> >>>>> Grüße, Carsten
> >>>>> 
> >>>>> --
> >>>>> 111attendees mailing list
> >>>>> 111attendees@ietf.org
> >>>>> https://www.ietf.org/mailman/listinfo/111attendees
> >>>> 
> >>>> --
> >>>> ---
> >>>> tte@cs.fau.de
> >>>> 
> >>>> --
> >>>> 111attendees mailing list
> >>>> 111attendees@ietf.org
> >>>> https://www.ietf.org/mailman/listinfo/111attendees
> >> 
> >> --
> >> ---
> >> tte@cs.fau.de
> > 
> > -- 
> > 111attendees mailing list
> > 111attendees@ietf.org
> > https://www.ietf.org/mailman/listinfo/111attendees
> 
> -- 
> Mark Andrews, ISC
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742              INTERNET: marka@isc.org
> 
> -- 
> 111attendees mailing list
> 111attendees@ietf.org
> https://www.ietf.org/mailman/listinfo/111attendees

-- 
Pedro Martinez-Julia
Network Architecture Laboratory, Network Research Institute
National Institute of Information and Communications Technology (NICT)
4-2-1, Nukui-Kitamachi, Koganei, Tokyo 184-8795, Japan
Email: pedro@nict.go.jp
---------------------------------------------------------
*** Entia non sunt multiplicanda praeter necessitatem ***