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

Scott Brim <scott.brim@gmail.com> Wed, 30 October 2013 14:25 UTC

Return-Path: <scott.brim@gmail.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 8BE9311E8222 for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 07:25:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.593
X-Spam-Level:
X-Spam-Status: No, score=-102.593 tagged_above=-999 required=5 tests=[AWL=0.006, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, 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 aaThpbLtk+bk for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 07:25:17 -0700 (PDT)
Received: from mail-ob0-x232.google.com (mail-ob0-x232.google.com [IPv6:2607:f8b0:4003:c01::232]) by ietfa.amsl.com (Postfix) with ESMTP id CF9F721E80F3 for <ietf@ietf.org>; Wed, 30 Oct 2013 07:25:10 -0700 (PDT)
Received: by mail-ob0-f178.google.com with SMTP id wm4so1483560obc.37 for <ietf@ietf.org>; Wed, 30 Oct 2013 07:25:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=JLKMb7ydzHzF/E1hWbEQGFQULYj61U8lBSdRUQO86VY=; b=xHvTotYkliNjoBl8cOC6PeeEnfeN46gbz/fN5P0guUw3rxds9jtaIPVi68C3cUG/1F W3BF92pQo/M1ohUPqgqdExGIp0isW5FCVsrwLBBDEGnB6UjS6rnDa8/pCYijM49qKcl8 91n7/SrS8UWsgTnxMmjc2tA9j6krlK5ej6pTdLNmtjLlh/a6mrwwNcd2RNpbjbI2O8e/ YryLis0M5N/ejYJJJcxHs3iTQI3/7KFANeo7g81Qai/M1lQz/YtawirLOf2MPYZ4w71y ljswqn21+CY8ZEWihPGKPp+EI9BnfhYkvJ5nYupJ1rrB+hNO0+0ylJQ+S1qC5Dp77lLm +YFQ==
X-Received: by 10.60.142.137 with SMTP id rw9mr64757oeb.94.1383143110268; Wed, 30 Oct 2013 07:25:10 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.2.134 with HTTP; Wed, 30 Oct 2013 07:24:50 -0700 (PDT)
In-Reply-To: <01P06PWP9XG4004X76@mauve.mrochek.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>
From: Scott Brim <scott.brim@gmail.com>
Date: Wed, 30 Oct 2013 10:24:50 -0400
Message-ID: <CAPv4CP_X7M0GQr4O4DfSZE=wXGfsuxtCED6JfH+MX34J2j_h=Q@mail.gmail.com>
Subject: Re: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
To: ned+ietf <ned+ietf@mauve.mrochek.com>
Content-Type: multipart/alternative; boundary="047d7b2e463cc2dc1004e9f619fb"
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:25:17 -0000

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.