Re: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary

Eliot Lear <> Wed, 30 October 2013 14:38 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id D5BB321E80F1 for <>; Wed, 30 Oct 2013 07:38:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -110.464
X-Spam-Status: No, score=-110.464 tagged_above=-999 required=5 tests=[AWL=0.135, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id DlQwajD2XiZr for <>; Wed, 30 Oct 2013 07:38:51 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 8A83D11E8253 for <>; Wed, 30 Oct 2013 07:38:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=1593; q=dns/txt; s=iport; t=1383143930; x=1384353530; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=RQ2WQCcMXSuCtxE6nw2/MO9mRasSV0pbUGRU8zm0RBA=; b=jBZONd5Ad1tnAlyQ/axw37MXF2twkxbtOBzGUA/rj4pqxWin4ac+PS+r qShG+4EUhmJQGfdRGhmzrg2BpxJgZQ1lQYibyqbBZW6QgA6dCeqtR16mS y2IId+jSs7qj/0/JoKVhAau1Hh/xk86VQLDVDaHeH7SqRgxrWPVRplutt M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="4.93,601,1378857600"; d="scan'208";a="161202065"
Received: from ([]) by with ESMTP; 30 Oct 2013 14:38:40 +0000
Received: from mctiny.local ([]) by (8.14.5/8.14.5) with ESMTP id r9UEcXcw017934 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 30 Oct 2013 14:38:36 GMT
Message-ID: <>
Date: Wed, 30 Oct 2013 15:38:33 +0100
From: Eliot Lear <>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To:, Stephane Bortzmeyer <>
Subject: Re: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
References: <> <> <> <> <>
In-Reply-To: <>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
Cc: Carsten Bormann <>, IETF Discuss <>
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 30 Oct 2013 14:38:57 -0000

On 10/30/13 3:08 PM, wrote:
>> On Wed, Oct 30, 2013 at 09:25:59AM +0100,
>>  Carsten Bormann <> wrote
>>  a message of 16 lines which said:
>>> I don’t know about “only UTC" for events that are also visited
>>> locally, but giving the UTC time as well would be a good idea.
>> My experience with international organizations is that, when you
>> indicate the time in two zones, there is often a discrepancy. With
>> only one zone, there is no doubt about the real value.
> And my experience is that regardless of what sort of organization you're
> dealing with, if you ask them to convert a time for a future event that is
> being held in a particular physical location to some other time zone, they
> won't apply time zone rules correctly and the only announced time will be
> wrong.
> Which argues for including the local time when the event will take place. If
> you want to mandate that the time also appear in UTC, great, but it's quite
> important that the local time also be there.

And local time should be normative to deal with such unforeseen
circumstances as a papal visit.  From the southamerica file in the TZ

# From Daniel C. Sobral (1998-02-12):
# In 1997, the DS began on October 6. The stated reason was that
# because international television networks ignored Brazil's policy on DS,
# they bought the wrong times on satellite for coverage of Pope's visit.
# This year, the ending date of DS was postponed to March 1
# to help dealing with the shortages of electric power.