IETF Logo Mail Archive

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

Carsten Bormann <cabo@tzi.org> Wed, 30 October 2013 08:26 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D6FC011E820D for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 01:26:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.213
X-Spam-Level:
X-Spam-Status: No, score=-106.213 tagged_above=-999 required=5 tests=[AWL=0.036, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RDbSAsHbj+rr for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 01:26:13 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id F071F11E8118 for <ietf@ietf.org>; Wed, 30 Oct 2013 01:26:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.4/8.14.4) with ESMTP id r9U8Q12W008169; Wed, 30 Oct 2013 09:26:01 +0100 (CET)
Received: from [192.168.217.105] (p548911BB.dip0.t-ipconnect.de [84.137.17.187]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 04458EEB; Wed, 30 Oct 2013 09:26:00 +0100 (CET)
Subject: Re: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1816\))
Content-Type: text/plain; charset="windows-1252"
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <20131030081355.GA23990@nic.fr>
Date: Wed, 30 Oct 2013 09:25:59 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <7F135C08-A550-450F-82B4-1F239E115BC3@tzi.org>
References: <87879E7D-A55B-4A88-80B8-B503C89E52CB@iab.org> <20131030081355.GA23990@nic.fr>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
X-Mailer: Apple Mail (2.1816)
Cc: IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Oct 2013 08:26:19 -0000

On 30 Oct 2013, at 09:13, Stephane Bortzmeyer <bortzmeyer@nic.fr> wrote:

> IETF must use only UTC when announcing a worldwide event.

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.  Even more so for a event that is days from a local time zone change.

Beyond UTC, I would normally point to

	http://datatracker.ietf.org/meeting/agenda-utc

and its “display in browser time” feature here as well, but the latter seems to be broken by a missing file right now.

Grüße, Carsten

v2.23.0 | Report a Bug | By Email