Re: [111attendees] Agenda pains

Le 30/07/2021 à 13:00, Nigel Hickson a écrit :
> Good afternoon
> 
> Apologies; but why not UTC?

Because it is a third step in the conversion process.

Two steps are sufficient.

Alex

> 
> Nigel
> 
> On Fri, 30 Jul 2021 at 11:50, Carsten Bormann <cabo@tzi.org 
> <mailto:cabo@tzi.org>> wrote:
> 
>     On 2021-07-29, at 18:11, Yoav Nir <ynir.ietf@gmail.com
>     <mailto:ynir.ietf@gmail.com>> wrote:
>      >
>      > I think UTC is best because it’s predictable and sort-of universal.
> 
>     It also happens to be the standard.
> 
>     (The waters are muddied because corporations trying to dumb down
>     their communication, including the press, tend to call it GMT, which
>     is close.  Hence people on the street are more likely to know “GMT”
>     than “UTC”.)
> 
>     Call it “world time” and it is unambiguous (“1500Z” == “1500 world”)
>     and has the lowest number of syllables.
> 
>     Being able to operate in world time is a skill that is becoming ever
>     more important to many of us, so we might want to get with the program.
> 
>      > Meeting local timezone is at least predictable when you know
>     where the meeting “is”
> 
>     "Meeting local” timezone is meaningless for anyone except at the
>     meeting location.  Nobody is actually at the virtual meeting
>     location, so why waste time with this?  (Once we go hybrid and use
>     printed schedules again, the “browser time” of the printed schedule
>     is the “meeting local” time, though.  But that is only relevant for
>     printed matter; it MUST never be used for online information.)
> 
>      > Local is most convenient, but only if it is set correctly.
> 
>     “Browser local” is probably a more accurate term.  If the timezone
>     on your computer (which is what the browser uses) is not set to your
>     local time, you might have a problem, but not just with IETF
>     meetings :-)
> 
>     Re the +1 notation:  There is a simpler way, used on my eclectic
>     schedule:
> 
>     1900-2100  Session I
>     2130-2230  Session II
>     2300-2500  Session III
> 
>     If you can count, this should work for you.
>     (Not too great with negative, so once we meet on Tonga = UTC+13,
>     we’ll need to get used to some modulo arithmetic:
> 
>     9900-0100  Session 1
>     0130-0230  Session 2
>     0300-0500  Session 3
> 
>     I’m not sure Tonga is on the shortlist; Auckland in Winter [Northern
>     Summer] might be, though.)
> 
>     Grüße, Carsten
> 
>     -- 
>     111attendees mailing list
>     111attendees@ietf.org <mailto:111attendees@ietf.org>
>     https://www.ietf.org/mailman/listinfo/111attendees
>     <https://www.ietf.org/mailman/listinfo/111attendees>
> 
> 