RE: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
"Dearlove, Christopher (UK)" <Chris.Dearlove@baesystems.com> Wed, 30 October 2013 17:31 UTC
Return-Path: <Chris.Dearlove@baesystems.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 7859521E814F for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 10:31:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.445
X-Spam-Level:
X-Spam-Status: No, score=-10.445 tagged_above=-999 required=5 tests=[AWL=0.154, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 erGi83TA3dhH for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 10:31:27 -0700 (PDT)
Received: from ukmta3.baesystems.com (ukmta3.baesystems.com [20.133.40.55]) by ietfa.amsl.com (Postfix) with ESMTP id DC11121E8162 for <ietf@ietf.org>; Wed, 30 Oct 2013 10:30:35 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.93,602,1378854000"; d="scan'208";a="324438669"
Received: from unknown (HELO baemasodc005.greenlnk.net) ([10.108.52.29]) by Baemasodc001ir.sharelnk.net with ESMTP; 30 Oct 2013 17:30:34 +0000
From: "Dearlove, Christopher (UK)" <Chris.Dearlove@baesystems.com>
X-IronPort-AV: E=Sophos;i="4.93,602,1378854000"; d="scan'208";a="33849025"
Received: from glkxh0004v.greenlnk.net ([10.109.2.35]) by baemasodc005.greenlnk.net with ESMTP; 30 Oct 2013 17:30:34 +0000
Received: from GLKXM0002V.GREENLNK.net ([169.254.2.93]) by GLKXH0004V.GREENLNK.net ([10.109.2.35]) with mapi id 14.02.0328.009; Wed, 30 Oct 2013 17:30:34 +0000
To: joel jaeggli <joelja@bogus.com>, Scott Brim <scott.brim@gmail.com>
Subject: RE: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
Thread-Topic: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
Thread-Index: AQHO1XlyRnqNofJSSkeNqjj/8b6c/JoNTKIAgAApu4CAAAkdMA==
Date: Wed, 30 Oct 2013 17:30:33 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30D3DC043BD@GLKXM0002V.GREENLNK.net>
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> <CB860E86-F3A5-4292-ADA4-E7CBABC5660E@bogus.com>
In-Reply-To: <CB860E86-F3A5-4292-ADA4-E7CBABC5660E@bogus.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.109.62.6]
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
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 17:31:31 -0000
UK and GB is a bit redundant (GB is part of - most of - the UK). Basically we run GMT (UTC+0) in winter and BST (UTC+1) in summer. The S is summer. [We did once run an experiment to run BST - the S now standing for standard - all year, but a long time ago, and not for long.] [If - I don't know for sure either way - there's a subtle difference between GMT and UTC, for meeting start times, it's irrelevant.) -- Christopher Dearlove Senior Principal Engineer, Communications Group Communications, Networks and Image Analysis Capability BAE Systems Advanced Technology Centre West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK Tel: +44 1245 242194 | Fax: +44 1245 242124 chris.dearlove@baesystems.com | http://www.baesystems.com BAE Systems (Operations) Limited Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, Farnborough, Hants, GU14 6YU, UK Registered in England & Wales No: 1996687 -----Original Message----- From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of joel jaeggli Sent: 30 October 2013 16:54 To: Scott Brim Cc: ned+ietf; Carsten Bormann; IETF Discuss Subject: Re: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary 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. ******************************************************************** This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. ********************************************************************
- 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