Re: [111attendees] Agenda pains

Yoav Nir <ynir.ietf@gmail.com> Thu, 29 July 2021 16:11 UTC

Return-Path: <ynir.ietf@gmail.com>
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 D35413A09D3 for <111attendees@ietfa.amsl.com>; Thu, 29 Jul 2021 09:11:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=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=gmail.com
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 pMTX-Ktdxprr for <111attendees@ietfa.amsl.com>; Thu, 29 Jul 2021 09:11:54 -0700 (PDT)
Received: from mail-wr1-x42c.google.com (mail-wr1-x42c.google.com [IPv6:2a00:1450:4864:20::42c]) (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 1B2C43A09CD for <111attendees@ietf.org>; Thu, 29 Jul 2021 09:11:54 -0700 (PDT)
Received: by mail-wr1-x42c.google.com with SMTP id g15so7618464wrd.3 for <111attendees@ietf.org>; Thu, 29 Jul 2021 09:11:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=/IT5yrlNY2OvpkLKhWRVz4xehL0xQZv5F5ZL09D8gPc=; b=rlFeSobpIoDtJyeBuxN/uNK3zX+o1aTF4EMBxDkw+3tpsMj//P8Zf1OYGAH2X+4Mvc Ad1OGdEuFEcA6uTzKHMEiK6qhAT+FZR3i/EjtLHyZgj1C/hAfVJRoQdg1gkn0/LXQLcM IhlMvl/L/KZAZlbCl5WINmLeX0sFRd51Etd8QeHELcb9U4Yn0lsIOo/FZhWIJBLkUTU0 9TmkzBlKu7dMB1flVxlG08D7YBcbf7s0x1KoCOlwXflrP16WPiagiMDwECtnNdoQfzqa df6FmiXY+JjiibAJQdA9o0RNO4UPxX3vYrAAbtcgjZHBHR4lF/M2Lz9+YWTrmbhs+4/q 7S9g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=/IT5yrlNY2OvpkLKhWRVz4xehL0xQZv5F5ZL09D8gPc=; b=kgSSMhlssPAJ2vcO9k6RhJCRXjpzlK0Nt5LqLxEV48V0rPV7PsvCn1y1VrjgmlQ529 hcTUlxzcTXXf/WJlNS7Qgq5yN6AcD7Awk148hdwlQRH2aRPdw742kY1bcXtlNc6cshG9 RYN2l/8GXvqdCdLunWzFP0VHmDrBOl95PaI3Fob0ivq7+0ZQbch8+o8ay+i0II1NsLxg EyX4f4bTYP0WFyuVgZAwCjbmYJYwbnZ9WnYXOhwebAWCFxZiaHhK3KW9VCWq9LwF1ve8 yRF+bkP3jAog7uM6VLli8rm1jbFGYkEn1l2n4IUDqLivm6jk0cb2+1VN4cWMK+5Z0QwA /gWA==
X-Gm-Message-State: AOAM532LaHnCzTU14Be175+3R33ZEAfF2GzWZVtI9W9MeuPhss2WBhRf fv6kmd/yA0tUx9YZb+/ckgA=
X-Google-Smtp-Source: ABdhPJzvvZWYiEy+d4W+vXuIG73cXxFR4TRWMr66NeMkyvMjtPz1yAcdLY1ZS4sk6cJQQB+lFUeb6g==
X-Received: by 2002:a5d:6184:: with SMTP id j4mr5792419wru.340.1627575111061; Thu, 29 Jul 2021 09:11:51 -0700 (PDT)
Received: from smtpclient.apple ([46.120.57.183]) by smtp.gmail.com with ESMTPSA id p5sm3553611wme.2.2021.07.29.09.11.49 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 29 Jul 2021 09:11:50 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
From: Yoav Nir <ynir.ietf@gmail.com>
In-Reply-To: <PAXPR07MB7999FA9BB147EA0334F1743392EB9@PAXPR07MB7999.eurprd07.prod.outlook.com>
Date: Thu, 29 Jul 2021 19:11:48 +0300
Cc: Jonathan Morton <chromatix99@gmail.com>, "111attendees@ietf.org" <111attendees@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <F3496F18-9C89-40A3-BED5-EE3B6A9CFAA5@gmail.com>
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>
To: "Maisonneuve, Julien (Nokia - FR/Paris-Saclay)" <julien.maisonneuve@nokia.com>
X-Mailer: Apple Mail (2.3654.120.0.1.13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/111attendees/6Xo3w90fG1OL784Bb_s5JAP3m3I>
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: Thu, 29 Jul 2021 16:12:00 -0000

I think UTC is best because it’s predictable and sort-of universal.

Meeting local timezone is at least predictable when you know where the meeting “is”

Local is most convenient, but only if it is set correctly.  Cork is just two timezones away from me, making the times there just plausible enough to fool me.

> On 29 Jul 2021, at 18:03, Maisonneuve, Julien (Nokia - FR/Paris-Saclay) <julien.maisonneuve@nokia.com> wrote:
> 
> Well, the alternative of being back to the meeting's local timezone is almost certainly worse.
> J.
> 
> -----Original Message-----
> From: Yoav Nir <ynir.ietf@gmail.com> 
> Sent: Thursday, July 29, 2021 4:45 PM
> 
>> On 29 Jul 2021, at 16:23, Maisonneuve, Julien (Nokia - FR/Paris-Saclay) <julien.maisonneuve@nokia.com> wrote:
>> Thinking out loud : why not make the "local" agenda option the default ?
> 
> Because when you change to local time manually, you see the box where it says your time zone and make sure it’s right.
> When I browse the web at work, I keep getting ads for car dealerships in Cork, because that’s the way the VPNs at my company are set up.  I don’t know where the IETF agenda picks up the local time, but I wouldn’t blindly trust it to be correct.
>