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

Vinayak Hegde <> Wed, 30 October 2013 19:30 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 19B6711E8220; Wed, 30 Oct 2013 12:30:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.351
X-Spam-Status: No, score=-2.351 tagged_above=-999 required=5 tests=[AWL=0.248, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id bZe+pUvb7-Vg; Wed, 30 Oct 2013 12:30:12 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:400e:c01::22a]) by (Postfix) with ESMTP id E856411E818E; Wed, 30 Oct 2013 12:30:11 -0700 (PDT)
Received: by with SMTP id jt11so1838077pbb.15 for <multiple recipients>; Wed, 30 Oct 2013 12:30:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=0CsC63aSYj53+siI2L9UQwkcHT/LsiJfV1NPriqAKN0=; b=JV4Tgug4LOd33Em0qnBjwH0Eaa3CAUZnIxB/LCQOd79EUGqyHacrJmuEkdoZ5iDy7U QuLW9GYZ5TgzvlmvPI9Wao3QnVsKjOAJPsSaeYlRAY3Ix0LkD9Q2hbaK4kIN2wqxufai g8Iy/jtYqf1NekptX+O2PbVOH5uMqjOje+o+l/UTLF7EJJLb/8k3OwgmqiXprGUoCAOA auBvT/EurleMbi//SKwEqx0srhvR7nzEN5k4gqF6sebbDJvnHFTtqqn24pXJnoIDFdHL etUTrkwfbaUSHrFumAg+/3kL6H2lmw9qHMrpr+Gu/oZJjEcB+/yrhrhHyBCec4jm2SBu xmew==
MIME-Version: 1.0
X-Received: by with SMTP id wg7mr4190pab.81.1383161411657; Wed, 30 Oct 2013 12:30:11 -0700 (PDT)
Received: by with HTTP; Wed, 30 Oct 2013 12:30:11 -0700 (PDT)
In-Reply-To: <>
References: <> <> <>
Date: Thu, 31 Oct 2013 01:00:11 +0530
Message-ID: <>
Subject: Re: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
From: Vinayak Hegde <>
To: IAB Chair <>, "" <>
Content-Type: multipart/alternative; boundary="047d7b86c7489bf97704e9fa5c2e"
Cc: IETF Discussion Mailing List <>
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 30 Oct 2013 19:30:13 -0000

On Wed, Oct 30, 2013 at 7:49 PM, IAB Chair <> wrote:

> Stephane:
> I think that the use of the local timezone make it easy for people to look
> it up on the agenda.  I do agree that inclusion of UTC as well would have
> been very helpful.  I'll try to remember to do that in the future.
> Russ

Why is it so hard to even mention the offset of the local time from UTC if
not anything else on the Agenda itself ? Everyone is aware of the offset
from the timezone they are in but may not be aware of the local timezone
offsets during the time of the year (think day-light savings) and the place
(several countries have different timezones so different cities within same
country can have different times).

I think the problem here is of the mindset within the IETF which looks at
IETF meetings as local physical meetings rather than a place of
congregation of people (whether physical or remote) at certain point in
time. If IETF really means to encourage wider participation (both in number
and diversity), then they need to make small changes such as these to
accommodate remote participants more. The change should start right from
the very top if this were to work.

-- Vinayak