IETF Logo Mail Archive

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

Tim Chown <tjc@ecs.soton.ac.uk> Wed, 30 October 2013 14:09 UTC

Return-Path: <tjc@ecs.soton.ac.uk>
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 348BA11E8227 for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 07:09:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.342
X-Spam-Level:
X-Spam-Status: No, score=-2.342 tagged_above=-999 required=5 tests=[AWL=0.257, BAYES_00=-2.599]
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 SPjWHMLcDnlm for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 07:09:14 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id 6D5B011E822A for <ietf@ietf.org>; Wed, 30 Oct 2013 07:08:55 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r9UE8mcG021621; Wed, 30 Oct 2013 14:08:48 GMT
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk r9UE8mcG021621
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1383142128; bh=984Yb5utVkoic4hCI2daYBGrJhY=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=rqcYj/fxraBjTU4CIgj49t73JKfXvaIi4nAqhNhly2H5fgCDmguhJMEOHpN1eMUxn U+4u5oEy+W+MPCN8tD9vVxyYtNLPNQEGIJLyn6CD6YHdDJ+wHy0OMPVLvoJYqdVXna g/5zxYLAPI00xSRPrvnmwsxztsj6lAGgPV/m5En0=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id p9YE8m0959649989yw ret-id none; Wed, 30 Oct 2013 14:08:48 +0000
Received: from dhcp-202-90.wireless.soton.ac.uk (dhcp-202-90.wireless.soton.ac.uk [152.78.202.90]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r9UE8j30030928 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 30 Oct 2013 14:08:45 GMT
Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <7F135C08-A550-450F-82B4-1F239E115BC3@tzi.org>
Date: Wed, 30 Oct 2013 14:08:44 +0000
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|9e1becdb40bfbb97deb2f04c4b088de9p9YE8m03tjc|ecs.soton.ac.uk|3291AEDC-655D-4AD8-A60B-8D31A5C65DEA@ecs.soton.ac.uk>
References: <87879E7D-A55B-4A88-80B8-B503C89E52CB@iab.org> <20131030081355.GA23990@nic.fr> <7F135C08-A550-450F-82B4-1F239E115BC3@tzi.org> <3291AEDC-655D-4AD8-A60B-8D31A5C65DEA@ecs.soton.ac.uk>
To: Carsten Bormann <cabo@tzi.org>
X-Mailer: Apple Mail (2.1510)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=p9YE8m095964998900; tid=p9YE8m0959649989yw; client=relay,ipv6; mail=; rcpt=; nrcpt=3:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: r9UE8mcG021621
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
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 14:09:15 -0000

On 30 Oct 2013, at 08:25, Carsten Bormann <cabo@tzi.org> wrote:

> 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

This was something I suggested a couple of IETFs ago, and the tools team implemented it very quickly.

I think if you have constructive suggestions that can be implemented, the tools team is all ears :)

Tim

v2.23.0 | Report a Bug | By Email