Re: [Tzdist] Next step

Eliot Lear <lear@cisco.com> Thu, 29 October 2015 08:53 UTC

Return-Path: <lear@cisco.com>
X-Original-To: tzdist@ietfa.amsl.com
Delivered-To: tzdist@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 785611B2B3E for <tzdist@ietfa.amsl.com>; Thu, 29 Oct 2015 01:53:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h5ohF3DUn8Nh for <tzdist@ietfa.amsl.com>; Thu, 29 Oct 2015 01:53:45 -0700 (PDT)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E71181B2B3D for <tzdist@ietf.org>; Thu, 29 Oct 2015 01:53:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2050; q=dns/txt; s=iport; t=1446108825; x=1447318425; h=subject:to:references:from:message-id:date:mime-version: in-reply-to; bh=CbHjsW6yu1OmrE3KIlcjLW0lGt2KOt5DurR6cV7gedM=; b=mosvxLDKXhP1JgzF4XCR3JfmTcbRu07J+gqM1YmsU+noK+mX5cC2EcFX T4Ie13YTM8kjsvIOhC5EM2EA3KgwRsJJXnlXU0HMY6PIg8d6+jyWe91yk NSplDKSal1y8b9WhQZKDqBtDV76nZ3DPBR9s01B8iSfm77CESrguUp9iO 4=;
X-Files: signature.asc : 481
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CoBACN3TFW/xbLJq1exXyGGwKBegEBAQEBAYELhDYBAQMBI1UGCwshFgsCAgkDAgECAUUGAQwIAQEQiBQIsy+SAAEBAQEBAQEDAQEBAQEBARMJi3WFF4JpgUUBBJZCglKBYYhyiRmTG2OEBjyGMQEBAQ
X-IronPort-AV: E=Sophos;i="5.20,213,1444694400"; d="asc'?scan'208";a="607847607"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP; 29 Oct 2015 08:53:41 +0000
Received: from [10.149.209.17] ([10.149.209.17]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id t9T8rff1007849; Thu, 29 Oct 2015 08:53:41 GMT
To: Cyrus Daboo <cyrus@daboo.name>, tzdist@ietf.org
References: <CADZyTkmO_PcfWTw-36U_6vo=EuDAnAmvUo6nvPZjkHjb_ALPSQ@mail.gmail.com> <40285_1445262970_t9JDu8BA043191_50DBD330DB51FDFC0C3E86D4@cyrus.local> <5624FAC4.5030008@andrew.cmu.edu> <B38549591D4FFBE5A83BF0BD@cyrus.local> <56253CCB.6010602@gmail.com> <316D3AAC6E4A5336C1784897@caldav.corp.apple.com> <5625EB92.4040808@cisco.com> <1D7932113B78B8547A9171D6@caldav.corp.apple.com>
From: Eliot Lear <lear@cisco.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <5631DE94.3070105@cisco.com>
Date: Thu, 29 Oct 2015 10:53:40 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <1D7932113B78B8547A9171D6@caldav.corp.apple.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="J3rFv1Td1hukjhfVtQ9I0b8fOS7PJw3E3"
Archived-At: <http://mailarchive.ietf.org/arch/msg/tzdist/RCRg5L3REX6KGuC_6usKglOlnd4>
Subject: Re: [Tzdist] Next step
X-BeenThere: tzdist@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <tzdist.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tzdist>, <mailto:tzdist-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tzdist/>
List-Post: <mailto:tzdist@ietf.org>
List-Help: <mailto:tzdist-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tzdist>, <mailto:tzdist-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Oct 2015 08:53:46 -0000

<chair hat on>

On 10/28/15 8:35 PM, Cyrus Daboo wrote:

> To be honest with you I don't have a serious use case to implement
> this right now.

ok.

>
> So if we drop that suggestion, that just leaves two possible things
> for the WG:
>
> 1) Registering a zoneinfo media type (which I think can be done
> without the need for a WG).

Do others agree or disagree?


> 2) Something new to think about: should we propose that IANA run a
> tzdist service as another facet of the time zone database support they
> do? That would certainly be a way to "bootstrap" interest in the
> protocol.

The same sorts of questions:

1.  Would the community make use of such a service?  I think when it
comes to a continuing operational cost, there would have to be very
strong and broad demand.
2.  Is it appropriate for IANA to perform this function?  This one would
require discussion once we get past (1).
3.  Is there a draft author?   Never too early to write a draft to
define the service requirements and how it would be managed.  It's not
all protocol.
4.  Are there reviewers?

Eliot