IETF Logo Mail Archive

Re: [Tzdist] Next step (IANA as server)

Doug Royer <douglasroyer@gmail.com> Thu, 29 October 2015 16:22 UTC

Return-Path: <douglasroyer@gmail.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 685B81B2F41 for <tzdist@ietfa.amsl.com>; Thu, 29 Oct 2015 09:22:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 3tz7bl9LNL16 for <tzdist@ietfa.amsl.com>; Thu, 29 Oct 2015 09:22:26 -0700 (PDT)
Received: from mail-pa0-x232.google.com (mail-pa0-x232.google.com [IPv6:2607:f8b0:400e:c03::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7E37C1B2F3B for <tzdist@ietf.org>; Thu, 29 Oct 2015 09:22:26 -0700 (PDT)
Received: by padhk11 with SMTP id hk11so45124883pad.1 for <tzdist@ietf.org>; Thu, 29 Oct 2015 09:22:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-type; bh=kFue9/cIhOhM/ssZzTEpKRKpWG24ui7JUNGbCEpCW4Y=; b=HeCm5R91vw5/hhqjRPvNAzKsehUihGSNdVbNyCGNp/V1r//9jRITzayhujK47WrvDC Ig/ZNKmV2wZ4PL6ZGGHjJ//GqURdAVNh+7pwv937e/WjplJ4KJaTiGb5Ckc+QGMXK1n8 maSUB8d8bEu49iJx3/5pDTLuLbMHHVyK94idUQ8M6H9hTDA51PeP+3NfJkVxBuot51g1 RmvRx3z9y/IgVVqjYVYNOTVJ426eKB2KVte7dFyFNXS6onlpxq6M8ug28VItt8FANq3u bXU3eRqofeKvaTxbwrW/wSnSMle1N0BkzafCkg/gfXoPEbyC9btbFgyXQA+tpB1IWf5l XTcg==
X-Received: by 10.66.123.9 with SMTP id lw9mr2749644pab.119.1446135746139; Thu, 29 Oct 2015 09:22:26 -0700 (PDT)
Received: from [192.168.1.4] ([71.209.58.192]) by smtp.googlemail.com with ESMTPSA id dd4sm3193587pbb.52.2015.10.29.09.22.24 for <tzdist@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Thu, 29 Oct 2015 09:22:25 -0700 (PDT)
To: 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> <5631DE94.3070105@cisco.com>
From: Doug Royer <douglasroyer@gmail.com>
Organization: http://SoftwareAndServices.NET
Message-ID: <563247BF.7020906@gmail.com>
Date: Thu, 29 Oct 2015 10:22:23 -0600
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <5631DE94.3070105@cisco.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="------------ms010209060700080402070103"
Archived-At: <http://mailarchive.ietf.org/arch/msg/tzdist/UUJzuAb76BQdV9g19we7dkOYILM>
Subject: Re: [Tzdist] Next step (IANA as server)
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 16:22:31 -0000

On 10/29/2015 02:53 AM, Eliot Lear wrote:

> 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.

Most users would not have a clue it happened and would still complain if
they did not get their TZ updates.

There are already some systems in place for this kind of thing.

Has anyone contacted NTP.org or NIST?
(http://www.nist.gov/pml/div688/grp40/its.cfm)

> 2.  Is it appropriate for IANA to perform this function?  This one would
> require discussion once we get past (1).

They are fantastic as a registration service. Do they run any other kind
of data servers? I can't think of anything like this now.

For the most part IANA does not review changes to content, they depend
on the IETF process to inform them of changes.

I think this would be a large change in mission for them.






-- 

Doug Royer - (http://K7DMR.us / http://DougRoyer.US)
DouglasRoyer@gmail.com
714-989-6135

v2.23.0 | Report a Bug | By Email