Re: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
"John Levine" <johnl@taugh.com> Wed, 30 October 2013 17:50 UTC
Return-Path: <prvs=0008e0cf97=johnl@iecc.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 748F021E80F3 for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 10:50:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.475
X-Spam-Level:
X-Spam-Status: No, score=-2.475 tagged_above=-999 required=5 tests=[AWL=0.124, BAYES_00=-2.599]
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 0NpmA5fX4jqO for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 10:50:35 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 3B68D11E8126 for <ietf@ietf.org>; Wed, 30 Oct 2013 10:50:28 -0700 (PDT)
Received: (qmail 94747 invoked from network); 30 Oct 2013 17:50:26 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 30 Oct 2013 17:50:26 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=527146e2.xn--30v786c.k1310; i=johnl@user.iecc.com; bh=H7moMek05VpwKFZGUa0ANPmi93Gt5vBgAnuRp+CUCDk=; b=LoLeSn9vD3S9ktIx9toTbq+JWFWq/DrtgChiGsR4ltfrLKux24BtvINEaLZz4oSeNQIaktlLTRc1ElYnLxdHu/JrZ06lbtdVzE5W62zmuT8udJ1SE9mpJwvIMEQFTON88oBRa747sIrZ3tWBtebMsFdLvFU3phcacCEdh2lVtxlzLAkEs3gaG5qGZZBmhU/rFFvxeY6I08T75nI9jtlEegCiyke5NYoj+8TwjqbPsQQ3n/0yZDC1g9rZpATQDBmg
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=527146e2.xn--30v786c.k1310; olt=johnl@user.iecc.com; bh=H7moMek05VpwKFZGUa0ANPmi93Gt5vBgAnuRp+CUCDk=; b=wsXgEZ8lDg2xl5KMxN/NXDRdXHGcGp51A9tfe930n91hGqUeK74d26YNoBhysGP6SRE+jThnDXEnFzOrs3M3rbvkJujMKWcdLKXmu2QVHWeR5GPP8C/psdNeKPuqR7HLQxmSC2BnQbVVVbdcQRmiQprHlE+ifc73mpTRHsNN5U3bQ8ZHgHVObR21ojBBayV86+mol9cQwa5zCiINpqeXs+B7B/k/Ymyd1mVNqdhvsvdCbckmDctE16RFLewmiR/m
Date: Wed, 30 Oct 2013 17:50:04 -0000
Message-ID: <20131030175004.44640.qmail@joyce.lan>
From: John Levine <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
In-Reply-To: <20131030083611.GA27804@nic.fr>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
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:50:39 -0000
>My experience with international organizations is that, when you >indicate the time in two zones, there is often a discrepancy. With >only one zone, there is no doubt about the real value. I've basically given up asking people what time zone their schedule is in, because most people have no idea, and don't understand that time offsets vary from place to place and from one time of the year to another, so the correct zone matters. In San Francisco in July, they'll say PST. Do you mean PDT? Yes, PST. Or this call will be at 10:00 in New York, 11:00 in San Juan. where the time is an hour ahead. Uh, it's May and there's no daylight time in Puerto Rico so the times are the same. What? Huh? This problem is not helped by a widely used alleged calendar application sold by a vendor located about 220 km south of Vancouver that doesn't even try to get the time zones right. The least broken approach I've found is to ask what place the time is. If they say Vancouver, I can figure it out. R's, John
- 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