Re: [111attendees] IETFers chokes on time zones

Michael StJohns <> Sat, 24 July 2021 18:31 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 876763A458D for <>; Sat, 24 Jul 2021 11:31:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id cJyfm0X8RlIH for <>; Sat, 24 Jul 2021 11:31:25 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::836]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id BA61A3A458C for <>; Sat, 24 Jul 2021 11:31:25 -0700 (PDT)
Received: by with SMTP id t18so4006804qta.8 for <>; Sat, 24 Jul 2021 11:31:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20150623; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=ldobi2dcQ3seX3Gylym2OMPw7fziM8Alhw2Gpc0qaTc=; b=ml+LmH/rCDj8Rgxp+kQExltB1E0jY7M/J9GaGp5MpkdgTAfAs3n/9pGfpd7CJAV2Kg T/YDHkZcbZ5wofqXIM8/XHsREwdJNTFD/ysmzLA2DyJrOeti8KPtb4es17bDaoiUk8S+ anr+o2ttU01vXsZtJXgp/bxeMwBP2L11rsjjPWZs/NhL+/o5VkE6Ikw6EkICRYPKz2Dx k+IhSUMbrsNxWSXIQVBmYB01KiFFNQoS9vzyyRdfG5O+Xf+lvMnGig36qW0OYH6T2MWV LLe6xHpguNQRovEaqoV32AiWNWG2SUTaYCtLclFcj+aKybjbInsngimNgq1noWdYoUxI 3ajQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=ldobi2dcQ3seX3Gylym2OMPw7fziM8Alhw2Gpc0qaTc=; b=YM+zio92CASaBN0yJc4tMFfUBRkACqNYXoNzuujLKmOxhQqxMYSybnM/TxwWtgI0eN V6uhOrm1UPCBSV14bRYnyael2BIpiL8fPN/0F85g/jm6h1+hHief1Ff9HQreJrlIf1B4 0lWAZ9RPtyfXjuDBd55PrquYiBoOH1NdwOSH5kd8QBHwBSM4pTwF4yw2ysAFutkyzNbu rlGYJ2ZVvaCC5iCvm0AG0wA+651eu501867reGzpAann7JfqTPaKsqiBpk3He5iVsg2O 2ezl9K0QcojkjmIv+RpBrrMpdVRgITiggmgPkQTcDtSCqvNQ8nUyOVfG4ZCXU0sf2G6w qOpw==
X-Gm-Message-State: AOAM5305uuSomylbQdkLGfr/rBmlnTssImvmIQpyyIs51VuqMSUpT0kh ueu/EbnTHp4jZCd/u9vp6qiFYmCM17otu187
X-Google-Smtp-Source: ABdhPJwpwdsM0/xPYJGjfI/vhNkt6JmZEXv7w0xFecqucuQek86Z0mQgr7vmI4cDcYzaTRYMI6s6rw==
X-Received: by 2002:ac8:43c1:: with SMTP id w1mr8822379qtn.358.1627151482571; Sat, 24 Jul 2021 11:31:22 -0700 (PDT)
Received: from [] ( []) by with ESMTPSA id d20sm5392367qkg.34.2021. (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 24 Jul 2021 11:31:22 -0700 (PDT)
To: Carsten Bormann <>
References: <> <> <> <>
From: Michael StJohns <>
Message-ID: <>
Date: Sat, 24 Jul 2021 14:31:20 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.12.0
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <>
Subject: Re: [111attendees] IETFers chokes on time zones
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mailing list for IETF 111 attendees <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sat, 24 Jul 2021 18:31:31 -0000

On 7/24/2021 1:02 PM, Carsten Bormann wrote:
> On 2021-07-24, at 18:57, Michael StJohns <> wrote:
>> Report the bug from the App store - Tom is pretty responsive. There was a similar bug that was fixed in version 2.9.   You may want to check and see if you have Version 2.9.  (I can't do any verification because I'm in EDT timezone so none of the sessions would bridge two days).
> I already used the bug reporting address offered by the tool.
> (I have 2.9.2, as indicated in the original message.)
> I don’t expect that this can be fixed 48 hours before the meeting, so I was interested if anyone has a better coping strategy than switching the tool to PDT (which works, but does increase the cognitive load, which can be bad when working at 25:00).
> Grüße, Carsten
I just sent Tom a note and he replied that he's now looking into the 
problem.  Last time it took about 48 hours to get the fix uploaded to 
the APP store - its possible you could have a fix soon after the 
beginning of the meeting.

Later, Mike