IETF Logo Mail Archive

Re: [Tzdist-bis] [calsify] tzdist and IANA

David Thewlis <dave.thewlis@calconnect.org> Wed, 17 July 2019 22:20 UTC

Return-Path: <dave.thewlis@calconnect.org>
X-Original-To: tzdist-bis@ietfa.amsl.com
Delivered-To: tzdist-bis@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44C9D120203; Wed, 17 Jul 2019 15:20:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=calconnect.org
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 wQC0VKR7_ryn; Wed, 17 Jul 2019 15:20:40 -0700 (PDT)
Received: from bumble.birch.relay.mailchannels.net (bumble.birch.relay.mailchannels.net [23.83.209.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C9E59120170; Wed, 17 Jul 2019 15:20:39 -0700 (PDT)
X-Sender-Id: dreamhost|x-authsender|dave.thewlis@calconnect.org
Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id E77D75018AD; Wed, 17 Jul 2019 22:20:38 +0000 (UTC)
Received: from pdx1-sub0-mail-a68.g.dreamhost.com (100-96-11-126.trex.outbound.svc.cluster.local [100.96.11.126]) (Authenticated sender: dreamhost) by relay.mailchannels.net (Postfix) with ESMTPA id 33910501B82; Wed, 17 Jul 2019 22:20:38 +0000 (UTC)
X-Sender-Id: dreamhost|x-authsender|dave.thewlis@calconnect.org
Received: from pdx1-sub0-mail-a68.g.dreamhost.com ([TEMPUNAVAIL]. [64.90.62.162]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:2500 (trex/5.17.3); Wed, 17 Jul 2019 22:20:38 +0000
X-MC-Relay: Neutral
X-MailChannels-SenderId: dreamhost|x-authsender|dave.thewlis@calconnect.org
X-MailChannels-Auth-Id: dreamhost
X-Cold-Desert: 0993eae81de4afcb_1563402038738_1988730191
X-MC-Loop-Signature: 1563402038738:1867493010
X-MC-Ingress-Time: 1563402038738
Received: from pdx1-sub0-mail-a68.g.dreamhost.com (localhost [127.0.0.1]) by pdx1-sub0-mail-a68.g.dreamhost.com (Postfix) with ESMTP id 740CE82B61; Wed, 17 Jul 2019 15:20:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=calconnect.org; h= content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; s=calconnect.org; bh=9IxuGdF4hYF2MnzR R4s/1Ap3I+Q=; b=OSbiQV1ulWGST9Ujk3fkBfd6Rz9nWhbh2okqcNyQBUkMfz47 Q4ji+qWwOwk+mfatMDC186r1TsAeahz3t4h47/68db7N/g+t0lI4nXTOTobiSDm9 Yq4btb/5PhoC+GZ5A8yr9qwN2db8NnDj0JBNDrvJHOnijJ9WY6kxCq+B+wY=
Received: from [192.168.0.108] (47-208-67-174.erkacmtk02.res.dyn.suddenlink.net [47.208.67.174]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: dave.thewlis@calconnect.org) by pdx1-sub0-mail-a68.g.dreamhost.com (Postfix) with ESMTPSA id 5A65382B60; Wed, 17 Jul 2019 15:20:32 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_12395A41-AF5B-4F12-AD66-317C15028CD9"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
X-DH-BACKEND: pdx1-sub0-mail-a68
From: David Thewlis <dave.thewlis@calconnect.org>
In-Reply-To: <9bf84b35-1918-e282-0c7c-bab8aee45f43@fastmail.com>
Date: Wed, 17 Jul 2019 15:20:31 -0700
Cc: Daniel Migault <daniel.migault@ericsson.com>, IETF-Calsify <calsify@ietf.org>, tzdist-bis@ietf.org
Message-Id: <71F326FF-1B26-4280-B496-DC8687A268D3@calconnect.org>
References: <CADZyTkkNuenOTx77cB8vFzWaSjp_fqtEgaYd00t5e2+Kk6MtRA@mail.gmail.com> <9bf84b35-1918-e282-0c7c-bab8aee45f43@fastmail.com>
To: Ken Murchison <murch@fastmail.com>
X-Mailer: Apple Mail (2.3445.104.11)
X-VR-OUT-STATUS: OK
X-VR-OUT-SCORE: -100
X-VR-OUT-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgeduvddrieeggddtjecutefuodetggdotefrodftvfcurfhrohhfihhlvgemucggtfgfnhhsuhgsshgtrhhisggvpdfftffgtefojffquffvnecuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjughrpegtggfuhfgjfffkfhfvofesrgdtmherhhdtjeenucfhrhhomhepffgrvhhiugcuvfhhvgiflhhishcuoegurghvvgdrthhhvgiflhhishestggrlhgtohhnnhgvtghtrdhorhhgqeenucffohhmrghinhepihgvthhfrdhorhhgnecukfhppeegjedrvddtkedrieejrddujeegnecurfgrrhgrmhepmhhouggvpehsmhhtphdphhgvlhhopegludelvddrudeikedrtddruddtkegnpdhinhgvthepgeejrddvtdekrdeijedrudejgedprhgvthhurhhnqdhprghthhepffgrvhhiugcuvfhhvgiflhhishcuoegurghvvgdrthhhvgiflhhishestggrlhgtohhnnhgvtghtrdhorhhgqedpmhgrihhlfhhrohhmpegurghvvgdrthhhvgiflhhishestggrlhgtohhnnhgvtghtrdhorhhgpdhnrhgtphhtthhopegurghvvgdrthhhvgiflhhishestggrlhgtohhnnhgvtghtrdhorhhgnecuvehluhhsthgvrhfuihiivgeptd
Archived-At: <https://mailarchive.ietf.org/arch/msg/tzdist-bis/qc6gajIZMz4VkI75YMqjMsDyteU>
Subject: Re: [Tzdist-bis] [calsify] tzdist and IANA
X-BeenThere: tzdist-bis@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Extensions to Time Zone Data Distribution Service <tzdist-bis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tzdist-bis>, <mailto:tzdist-bis-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tzdist-bis/>
List-Post: <mailto:tzdist-bis@ietf.org>
List-Help: <mailto:tzdist-bis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tzdist-bis>, <mailto:tzdist-bis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Jul 2019 22:20:42 -0000

I agree.  



> On Jul 17, 2019, at 13:46, Ken Murchison <murch@fastmail.com> wrote:
> 
> I completely agree that we should approach IANA about hosting a root/primary TZDIST server, whether it be for iCalendar data (RFC5545) or TZif data (RFC 8536) or both.
> 
> 
> 
> On 7/17/19 4:35 PM, Daniel Migault wrote:
>> Hi, 
>> 
>> IANA is budgeting its next 4 year plan, they are taking comments until
>> end of July. In short inputs need to be provided before next IETF.
>> 
>> This has already been suggested in the past that IANA could operate a tzdist server and I would like to get the opinion of the WGs on that. Please provide your feed backs if possible by the end of the week, as we expect to meet IANA people during the IETF in Montreal.
>> 
>> I am in favour of having a global system to distribute the time zones, however, it seems maybe difficult to request IANA to operate the service alone. I believe we need a more scalable system. I would rather suggest that we work with IANA to build a scalable system within these four years. This may in turn require a revision of the tzdist protocol. 
>> 
>> I see the tzdist situation a bit similar as the one with the DNS root zone, where IANA provides the data and the root zone being served by multiple operators. In the case of tzdist I believe it would be helpful that IANA may be one of the operators. 
>> 
>> Yours, 
>> Daniel
>> 
>> 
>> 
>> _______________________________________________
>> calsify mailing list
>> calsify@ietf.org <mailto:calsify@ietf.org>
>> https://www.ietf.org/mailman/listinfo/calsify <https://www.ietf.org/mailman/listinfo/calsify>
> -- 
> Ken Murchison
> Cyrus Development Team
> Fastmail US LLC
> <murch.vcf>_______________________________________________
> calsify mailing list
> calsify@ietf.org
> https://www.ietf.org/mailman/listinfo/calsify

v2.23.0 | Report a Bug | By Email