IETF Logo Mail Archive

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

Loa Andersson <loa@pi.nu> Wed, 30 October 2013 08:42 UTC

Return-Path: <loa@pi.nu>
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 1495711E8265 for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 01:42:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.617
X-Spam-Level:
X-Spam-Status: No, score=-102.617 tagged_above=-999 required=5 tests=[AWL=-0.018, BAYES_00=-2.599, 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 bRaIeCP1TlyH for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 01:42:23 -0700 (PDT)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) by ietfa.amsl.com (Postfix) with ESMTP id B858C11E8211 for <ietf@ietf.org>; Wed, 30 Oct 2013 01:42:23 -0700 (PDT)
Received: from [192.168.1.6] (unknown [112.208.65.178]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id ACC8018014F6 for <ietf@ietf.org>; Wed, 30 Oct 2013 09:42:21 +0100 (CET)
Message-ID: <5270C66C.9070109@pi.nu>
Date: Wed, 30 Oct 2013 16:42:20 +0800
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
References: <87879E7D-A55B-4A88-80B8-B503C89E52CB@iab.org> <20131030081355.GA23990@nic.fr> <ADB30B3C-6A91-416D-AF72-4C22A29D6C87@live555.com> <20131030083751.GB27804@nic.fr>
In-Reply-To: <20131030083751.GB27804@nic.fr>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
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 08:42:30 -0000

hmmm - I thought the "Technical Plenary" which you used as an example
actually is (partly) a physical meeting. We should have the local AND
UTC time announced.

/Loa

On 2013-10-30 16:37, Stephane Bortzmeyer wrote:
> On Wed, Oct 30, 2013 at 01:28:35AM -0700,
>   Ross Finlayson <finlayson@live555.com> wrote
>   a message of 16 lines which said:
>
>> I would prefer SHOULD rather than MUST (or must) :-)
>
> What could be a good reason to use the local time, when it is an event
> broadcasted on the Internet? For a physical meeting, I can imagine
> such good reasons but for a network one?
>

-- 


Loa Andersson                        email: loa@mail01.huawei.com
Senior MPLS Expert                          loa@pi.nu
Huawei Technologies (consultant)     phone: +46 739 81 21 64

v2.23.0 | Report a Bug | By Email