Re: [111attendees] Agenda pains

Nigel Hickson <nigel.hickson@dcms.gov.uk> Fri, 30 July 2021 11:00 UTC

Return-Path: <nigel.hickson@dcms.gov.uk>
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 EB1F73A25E4 for <111attendees@ietfa.amsl.com>; Fri, 30 Jul 2021 04:00:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.161
X-Spam-Level:
X-Spam-Status: No, score=-3.161 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, FROM_GOV_DKIM_AU=-0.612, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, 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=dcms.gov.uk
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 giKKpmSw1LU5 for <111attendees@ietfa.amsl.com>; Fri, 30 Jul 2021 04:00:46 -0700 (PDT)
Received: from mail-lf1-x12a.google.com (mail-lf1-x12a.google.com [IPv6:2a00:1450:4864:20::12a]) (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 CDCED3A2676 for <111attendees@ietf.org>; Fri, 30 Jul 2021 04:00:42 -0700 (PDT)
Received: by mail-lf1-x12a.google.com with SMTP id h14so17087053lfv.7 for <111attendees@ietf.org>; Fri, 30 Jul 2021 04:00:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dcms.gov.uk; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=F1PminmBEhuZmfsLCnsiRcwv+fh7r50nD/HzlVj94GI=; b=cF6BaG85rLDI4gbfsp10HS/yGpbB9P25lpNPsyKMlBUjE3lH1iPVdBFVGZ4ad2kEzj GHFSaFaN61faGNhsSbIDSs1wXbxovODf437HHodVHLp2BoGq2MqFVej/li57CTzbNbbM LqteM8lHqGYoXlYV2LjXCVgRdn7B1M3GsolZBq6QRFBVNcwx8fqikIqdD5ADm4ynvhE8 QM1sIKrFOOT2cNYWBoT6VvQclXeEJnJwlkJr4bRJO7MODbHJWIU1l4oKlHhuROcaduMz Z9CdLo0CbO2CEsNhdixAzal13b3HUTnfmE0MnwYlbb/McwGkfebcIsZt7V7WyeawJ9H4 iFZg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=F1PminmBEhuZmfsLCnsiRcwv+fh7r50nD/HzlVj94GI=; b=LKXxnWYpZjSASCFUI8WqI9cQks4ctTejJI/B7AcF6cik/4tQUkDs86uPNUALRsI5mc RIUcttUGwZvVcurO7alKaTMHOhRDLCOBzpQN3RW06JEXfctGVdqbdiGSHOY4OCxP7ROd 2yT9CH6NxG/cuY8Zac4D82i8FnON2jSWxQOh4PajOp8UfhywKV4Vft/HtXq79VlrF3bV 5vzZTXH7mHXhc8gGMKImXCWycJHTaz5bvQEMz4SCWbPU3VQjOJFJUK04tTOm3ryu3fab vBibDMbrMrNz+c++TLH4cIBokw0ukP01tyv4PDvLAC0uogBN2XDxM46fun5d/nTcWaf3 F0OQ==
X-Gm-Message-State: AOAM530ytiADgJZk45W9AWOJJPqB2ytj634S8x+EiGYUialWyEDQGUR8 nHki82shzRvKQjDoiXNapgyI2JU/2DZZa4HrTnf96Q==
X-Google-Smtp-Source: ABdhPJzK4OILA+haX1yqsVojFxEXZK0nk7BXjFz5cW8UVL+a0bLRPjOt9u8r6/g589BiON+0w83wgpwGA6K9BqKXwfs=
X-Received: by 2002:ac2:46f5:: with SMTP id q21mr1454806lfo.624.1627642840261; Fri, 30 Jul 2021 04:00:40 -0700 (PDT)
MIME-Version: 1.0
References: <PAXPR07MB79998714008B89DC901FA1FD92E89@PAXPR07MB7999.eurprd07.prod.outlook.com> <E8C3A469-0A96-4083-A01E-24607AD8AD97@gmail.com> <PAXPR07MB79990EA6BB28C1E7BE606DA492E89@PAXPR07MB7999.eurprd07.prod.outlook.com> <PAXPR07MB7999154405364D450601936892EB9@PAXPR07MB7999.eurprd07.prod.outlook.com> <ED7AF66B-6776-44F4-AB3A-983E2505D494@gmail.com> <PAXPR07MB7999FA9BB147EA0334F1743392EB9@PAXPR07MB7999.eurprd07.prod.outlook.com> <F3496F18-9C89-40A3-BED5-EE3B6A9CFAA5@gmail.com> <026E0A2F-A081-4B1B-A83E-E7D0D552FF53@tzi.org>
In-Reply-To: <026E0A2F-A081-4B1B-A83E-E7D0D552FF53@tzi.org>
From: Nigel Hickson <nigel.hickson@dcms.gov.uk>
Date: Fri, 30 Jul 2021 12:00:14 +0100
Message-ID: <CAAm_rS+BYW1KqCENNZDpq_tJ4h2QsgfSVkuMZ3Z0vziYKP=HuA@mail.gmail.com>
To: Carsten Bormann <cabo@tzi.org>
Cc: Yoav Nir <ynir.ietf@gmail.com>, "111attendees@ietf.org" <111attendees@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000510e2005c85521f6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/111attendees/YKYTX1lWPdgKSyemR-h1Uvzs-Y4>
Subject: Re: [111attendees] Agenda pains
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: Fri, 30 Jul 2021 11:00:52 -0000

Good afternoon

Apologies; but why not UTC?

Nigel

On Fri, 30 Jul 2021 at 11:50, Carsten Bormann <cabo@tzi.org> wrote:

> On 2021-07-29, at 18:11, Yoav Nir <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
> https://www.ietf.org/mailman/listinfo/111attendees
>