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:24 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 BD0D111E8126 for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 10:24:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.166
X-Spam-Level:
X-Spam-Status: No, score=-10.166 tagged_above=-999 required=5 tests=[AWL=-0.168, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_34=0.6, 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 Lu7L-dOD+64t for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 10:24:43 -0700 (PDT)
Received: from ukmta1.baesystems.com (ukmta1.baesystems.com [20.133.0.55]) by ietfa.amsl.com (Postfix) with ESMTP id 9D38811E81F0 for <ietf@ietf.org>; Wed, 30 Oct 2013 10:24:39 -0700 (PDT)
X-IronPort-AV: E=Sophos; i="4.93,602,1378854000"; d="scan'208,217"; a="385227585"
Received: from unknown (HELO baemasmds017.greenlnk.net) ([10.15.207.104]) by baemasmds003ir.sharelnk.net with ESMTP; 30 Oct 2013 17:24:38 +0000
X-IronPort-AV: E=Sophos; i="4.93,602,1378854000"; d="scan'208,217"; a="31416738"
Received: from glkxh0005v.greenlnk.net ([10.109.2.36]) by baemasmds017.greenlnk.net with ESMTP; 30 Oct 2013 17:24:38 +0000
Received: from GLKXM0002V.GREENLNK.net ([169.254.2.93]) by GLKXH0005V.GREENLNK.net ([10.109.2.36]) with mapi id 14.02.0328.009; Wed, 30 Oct 2013 17:24:38 +0000
From: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
To: Scott Brim <scott.brim@gmail.com>, ned+ietf <ned+ietf@mauve.mrochek.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/JoNTKIAgAAxyeA=
Date: Wed, 30 Oct 2013 17:24:38 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30D3DC0438E@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>
In-Reply-To: <CAPv4CP_X7M0GQr4O4DfSZE=wXGfsuxtCED6JfH+MX34J2j_h=Q@mail.gmail.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: multipart/alternative; boundary="_000_B31EEDDDB8ED7E4A93FDF12A4EECD30D3DC0438EGLKXM0002VGREEN_"
MIME-Version: 1.0
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 17:24:47 -0000
GMT would be better than BST if you want UTC. (BST is GMT+1, used in summer.) -- 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<mailto: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 From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Scott Brim Sent: 30 October 2013 14:25 To: ned+ietf Cc: Carsten Bormann; IETF Discuss Subject: Re: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary *** WARNING *** This message originates from outside our organisation, either from an external partner or the internet. Keep this in mind if you answer this message. For information regarding Red Flags that you can look out for in emails you receive, click here<http://intranet.ent.baesystems.com/howwework/security/spotlights/Documents/Red%20Flags.pdf>. If you feel the email is suspicious, please follow this process<http://intranet.ent.baesystems.com/howwework/security/spotlights/Documents/Dealing%20With%20Suspicious%20Emails.pdf>. 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. ******************************************************************** 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