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:19 UTC
Return-Path: <rlb@ipv.sx>
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 E3E1321F9FBE for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 07:19:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.89
X-Spam-Level:
X-Spam-Status: No, score=-2.89 tagged_above=-999 required=5 tests=[AWL=0.086, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 S4GAMnyhj3EO for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 07:19:02 -0700 (PDT)
Received: from mail-ob0-f173.google.com (mail-ob0-f173.google.com [209.85.214.173]) by ietfa.amsl.com (Postfix) with ESMTP id 7B27B21E80F9 for <ietf@ietf.org>; Wed, 30 Oct 2013 07:18:41 -0700 (PDT)
Received: by mail-ob0-f173.google.com with SMTP id gq1so1489501obb.32 for <ietf@ietf.org>; Wed, 30 Oct 2013 07:18:41 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=42joi7AFDgXOLP0HbDV64qN6jNsXdUCZLOOVeaK4Jgg=; b=ilC1AhToefv5iVDyh023+3gB19z8/Ey2AYJ4BFqT9iEe2zoRQsco15Ycj3UCR0j3Rx JjPW4xsKctfqdMXOEi72g3vbUnYTRgidf6plN7nxZsIdyfyZkaUDWT/4adF9C1Krtozy UVcDg8tmsDgRbaQBo8H8XDOzXcBVej4ElbKTzf74s3GrtysEpjhAnTWOlm85pnUXS4WX g2X1BSZi6cdpvRhjCCy1XrB7QH7CQNkKby+YYACTJbfbYKVLgBban2XdGgCIrdI/snza TDQOu14KfOMetRklW/8vvHWgh/AzDULdcj3qNk7GStbbLRgfT4nzni9/TO7bqCdexxkC +bDA==
X-Gm-Message-State: ALoCoQklCpfYnsFzZkFeFgkQBkVF8f2QXufqMP46m/BgGOz87JuUXQ6AXxW9Nl1kp87A7sUHVdjk
MIME-Version: 1.0
X-Received: by 10.182.106.4 with SMTP id gq4mr4479843obb.4.1383142720935; Wed, 30 Oct 2013 07:18:40 -0700 (PDT)
Received: by 10.76.101.10 with HTTP; Wed, 30 Oct 2013 07:18:40 -0700 (PDT)
In-Reply-To: <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> <3291AEDC-655D-4AD8-A60B-8D31A5C65DEA@ecs.soton.ac.uk> <7F135C08-A550-450F-82B4-1F239E115BC3@tzi.org> <EMEW3|9e1becdb40bfbb97deb2f04c4b088de9p9YE8m03tjc|ecs.soton.ac.uk|3291AEDC-655D-4AD8-A60B-8D31A5C65DEA@ecs.soton.ac.uk>
Date: Wed, 30 Oct 2013 10:18:40 -0400
Message-ID: <CAL02cgRyC=DdwCHgmnz1oEL+5CbUehi3jbcfGfjgqO_Nkx4j1A@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: Tim Chown <tjc@ecs.soton.ac.uk>
Content-Type: multipart/alternative; boundary="e89a8fb1fa628e2dbf04e9f60249"
Cc: Carsten Bormann <cabo@tzi.org>, 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:19:06 -0000
I hope everyone in the IETF is familiar with sites such as: <http://www.timeanddate.com/> <http://www.worldtimebuddy.com/> On Wed, Oct 30, 2013 at 10:08 AM, Tim Chown <tjc@ecs.soton.ac.uk> wrote: > 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 > >
- 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