IETF Logo Mail Archive

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

Randy Bush <randy@psg.com> Wed, 30 October 2013 14:26 UTC

Return-Path: <randy@psg.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 11BDD11E8221 for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 07:26:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.216
X-Spam-Level:
X-Spam-Status: No, score=-3.216 tagged_above=-999 required=5 tests=[AWL=-0.617, 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 FDPRswWu2+kj for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 07:26:39 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) by ietfa.amsl.com (Postfix) with ESMTP id 98B5811E8222 for <ietf@ietf.org>; Wed, 30 Oct 2013 07:26:15 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.76) (envelope-from <randy@psg.com>) id 1VbWir-0002h4-U8; Wed, 30 Oct 2013 14:26:14 +0000
Date: Wed, 30 Oct 2013 07:26:13 -0700
Message-ID: <m2habyq1h6.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Jari Arkko <jari.arkko@piuha.net>
Subject: Re: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
In-Reply-To: <0800C77D-7CA2-43DA-AE7E-E6AF7C70310B@piuha.net>
References: <87879E7D-A55B-4A88-80B8-B503C89E52CB@iab.org> <20131030081355.GA23990@nic.fr> <ADB30B3C-6A91-416D-AF72-4C22A29D6C87@live555.com> <20131030083751.GB27804@nic.fr> <5270C66C.9070109@pi.nu> <0800C77D-7CA2-43DA-AE7E-E6AF7C70310B@piuha.net>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset="US-ASCII"
Cc: IETF Disgust <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:26:40 -0000

since we were looking for a rat-hole, i can crawl in this one.

from the ops pov, uct/gmt (and let's skip that rathole) makes sense.
most of us think that way.  but it is amusing to note that i worked for
one global isp which runs on the new jersey timezone and another global
isp that runs on japanese standard time <blush>.  and i am sure there
are more.

but i suspect we all know how to convert.

randy

v2.23.0 | Report a Bug | By Email