Re: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
IAB Chair <iab-chair@iab.org> Wed, 30 October 2013 14:19 UTC
Return-Path: <iab-chair@iab.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 C4C1721F9EBE for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 07:19:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 KRyTIY5Ni4js for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 07:19:23 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:126c::1:15]) by ietfa.amsl.com (Postfix) with ESMTP id 64B0221F9F7F for <ietf@ietf.org>; Wed, 30 Oct 2013 07:19:12 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c9a.amsl.com (Postfix) with ESMTP id 8BC8AA6099; Wed, 30 Oct 2013 07:17:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c9a.amsl.com ([127.0.0.1]) by localhost (c9a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GO7ArxhS7ycA; Wed, 30 Oct 2013 07:17:08 -0700 (PDT)
Received: from [192.168.2.103] (pool-96-241-225-66.washdc.fios.verizon.net [96.241.225.66]) by c9a.amsl.com (Postfix) with ESMTPSA id 335FDA6087; Wed, 30 Oct 2013 07:17:08 -0700 (PDT)
Subject: Re: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset="us-ascii"
From: IAB Chair <iab-chair@iab.org>
In-Reply-To: <20131030081355.GA23990@nic.fr>
Date: Wed, 30 Oct 2013 10:19:10 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <33E29264-2B13-40F0-BE86-7A840CEEF5AA@iab.org>
References: <87879E7D-A55B-4A88-80B8-B503C89E52CB@iab.org> <20131030081355.GA23990@nic.fr>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
X-Mailer: Apple Mail (2.1085)
Cc: 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:23 -0000
Stephane: I think that the use of the local timezone make it easy for people to look it up on the agenda. I do agree that inclusion of UTC as well would have been very helpful. I'll try to remember to do that in the future. Russ On Oct 30, 2013, at 4:13 AM, Stephane Bortzmeyer wrote: > On Tue, Oct 29, 2013 at 09:10:08AM -0400, > IAB Chair <iab-chair@iab.org> wrote > a message of 54 lines which said: > >> The Technical Plenary session is expected to be popular. It will be >> held on Wednesday, 6 Nov 2013 at 0900 PST, > > Why why why using a local timezone when announcing a live broadcast, > which will be seen by many people anywhere in the world? > > Do note also that there are three different timezones in the world > which are named PST. Not everyone lives in North America! > > IETF must use only UTC when announcing a worldwide event. >
- 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