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

Richard Barnes <rlb@ipv.sx> Wed, 30 October 2013 14:34 UTC

MIME-Version: 1.0
In-Reply-To: <XyRGzVN6jOwk6F_vwEhe8OdueiPR8DgdnsPcWPmoKmbQ39LtU@smtp.gmail.com>
References: <3291AEDC-655D-4AD8-A60B-8D31A5C65DEA@ecs.soton.ac.uk> <7F135C08-A550-450F-82B4-1F239E115BC3@tzi.org> <87879E7D-A55B-4A88-80B8-B503C89E52CB@iab.org> <EMEW3|9e1becdb40bfbb97deb2f04c4b088de9p9YE8m03tjc|ecs.soton.ac.uk|3291AEDC-655D-4AD8-A60B-8D31A5C65DEA@ecs.soton.ac.uk> <20131030081355.GA23990@nic.fr> <CAL02cgRyC=DdwCHgmnz1oEL+5CbUehi3jbcfGfjgqO_Nkx4j1A@mail.gmail.com> <XyRGzVN6jOwk6F_vwEhe8OdueiPR8DgdnsPcWPmoKmbQ39LtU@smtp.gmail.com>
Date: Wed, 30 Oct 2013 10:34:15 -0400
Message-ID: <CAL02cgRXBWom+0VGvqqEmw2NnBzu_wLcym1rLbAN7kLbg8tpSA@mail.gmail.com>
Subject: Re: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
From: Richard Barnes <rlb@ipv.sx>
To: Dave Cridland <dave@cridland.net>
Content-Type: multipart/alternative; boundary="e89a8ff1ce9e49adb804e9f63ae4"
Cc: Carsten Bormann <cabo@tzi.org>, Tim Chown <tjc@ecs.soton.ac.uk>, IETF Discuss <ietf@ietf.org>
Precedence: list

This is why these tools have an option to set the date when computing
future times.

--Richard


On Wed, Oct 30, 2013 at 10:30 AM, Dave Cridland <dave@cridland.net> wrote:

> Richard Barnes wrote:
>   I hope everyone in the IETF is familiar with sites such as:
> <http://www.timeanddate.com/>
> <http://www.worldtimebuddy.com/>
>
>
>
>
>
> Yes, but given we're in the throes of timezone mutilation for the purposes
> of playing a longer game of golf, I'm not sure what the offset is, nor what
> it will be by then.
>
>
>
> If you pick the translation into local now, for most folk in Europe, it'll
> give you 1700. By Wednesday 6th November, it'll be 1800. I think.
>
>
>
> For UK folk, it'll be 1700. (Which I get by entering Vancouver as the
> timezone in Google calendar).
>
>
>
> Did I mention I hate daylight savings time?
>
>
>
> Dave.
>
> —
>
> Dave Cridland -- Sent with Inky -- http://inky.com/
>
>
>

IETF must use only UTC in its announcements (Was:… Stephane Bortzmeyer
Re: IETF must use only UTC in its announcements (… Carsten Bormann
Re: IETF must use only UTC in its announcements (… Ross Finlayson
Re: IETF must use only UTC in its announcements (… Stephane Bortzmeyer
Re: IETF must use only UTC in its announcements (… Stephane Bortzmeyer
Re: IETF must use only UTC in its announcements (… Loa Andersson
Re: IETF must use only UTC in its announcements (… Jari Arkko
Re: IETF must use only UTC in its announcements (… Tim Chown
Re: IETF must use only UTC in its announcements (… ned+ietf
Re: IETF must use only UTC in its announcements (… Richard Barnes
Re: IETF must use only UTC in its announcements (… IAB Chair
Re: IETF must use only UTC in its announcements (… Scott Brim
Re: IETF must use only UTC in its announcements (… Randy Bush
Re: IETF must use only UTC in its announcements (… Dave Cridland
Re: IETF must use only UTC in its announcements (… Ole Jacobsen
Re: IETF must use only UTC in its announcements (… Richard Barnes
Re: IETF must use only UTC in its announcements (… Eliot Lear
Re: IETF must use only UTC in its announcements (… ned+ietf
Re: IETF must use only UTC in its announcements (… Tony Finch
Re: IETF must use only UTC in its announcements (… Cyrus Daboo
Re: IETF must use only UTC in its announcements (… Bjoern Hoehrmann
Re: IETF must use only UTC in its announcements (… joel jaeggli
Re: IETF must use only UTC in its announcements (… Andrew Feren
RE: IETF must use only UTC in its announcements (… Dearlove, Christopher (UK)
Re: [IETF] Re: IETF must use only UTC in its anno… Warren Kumari
RE: IETF must use only UTC in its announcements (… Dearlove, Christopher (UK)
Re: IETF must use only UTC in its announcements (… John Levine
Re: IETF must use only UTC in its announcements (… Vinayak Hegde
Re: IETF must use only UTC in its announcements (… Vinayak Hegde
RE: IETF must use only UTC in its announcements (… l.wood