Re: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
joel jaeggli <joelja@bogus.com> Wed, 30 October 2013 16:54 UTC
Return-Path: <joelja@bogus.com>
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 15FE511E8164 for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 09:54:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.521
X-Spam-Level:
X-Spam-Status: No, score=-102.521 tagged_above=-999 required=5 tests=[AWL=0.078, 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 lTmE19ByYasV for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 09:54:34 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id C538111E8169 for <ietf@ietf.org>; Wed, 30 Oct 2013 09:54:18 -0700 (PDT)
Received: from mb-aye.corp.zynga.com ([199.48.105.4]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r9UGsG5s016566 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 30 Oct 2013 16:54:17 GMT (envelope-from joelja@bogus.com)
Content-Type: multipart/signed; boundary="Apple-Mail=_19FC02DC-1016-459B-B28D-22EF63E1B84E"; protocol="application/pgp-signature"; micalg="pgp-sha1"
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1816\))
Subject: Re: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
From: joel jaeggli <joelja@bogus.com>
In-Reply-To: <CAPv4CP_X7M0GQr4O4DfSZE=wXGfsuxtCED6JfH+MX34J2j_h=Q@mail.gmail.com>
Date: Wed, 30 Oct 2013 09:54:11 -0700
Message-Id: <CB860E86-F3A5-4292-ADA4-E7CBABC5660E@bogus.com>
References: <87879E7D-A55B-4A88-80B8-B503C89E52CB@iab.org> <20131030081355.GA23990@nic.fr> <7F135C08-A550-450F-82B4-1F239E115BC3@tzi.org> <20131030083611.GA27804@nic.fr> <01P06PWP9XG4004X76@mauve.mrochek.com> <CAPv4CP_X7M0GQr4O4DfSZE=wXGfsuxtCED6JfH+MX34J2j_h=Q@mail.gmail.com>
To: Scott Brim <scott.brim@gmail.com>
X-Mailer: Apple Mail (2.1816)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Wed, 30 Oct 2013 16:54:18 +0000 (UTC)
Cc: ned+ietf <ned+ietf@mauve.mrochek.com>, 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 16:54:39 -0000
On Oct 30, 2013, at 7:24 AM, Scott Brim <scott.brim@gmail.com> wrote: > One aspect of the problem is calendar apps. Some rather popular ones don't have a way to enter UTC, only UK time eg. BST, so you need some local time somewhere to enter the event in your calendar. And the United Kingdom and Great Britian are not on BST all year. Ghana on the other hand is.
- 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