[Tzdist] Create and distribution process of events with TZ data.
Doug Royer <douglasroyer@gmail.com> Thu, 11 December 2014 17:33 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 35AFF1A0673 for <tzdist@ietfa.amsl.com>; Thu, 11 Dec 2014 09:33:47 -0800 (PST)
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 edBNN6ZCZiHE for <tzdist@ietfa.amsl.com>; Thu, 11 Dec 2014 09:33:45 -0800 (PST)
Received: from mail-pd0-x230.google.com (mail-pd0-x230.google.com [IPv6:2607:f8b0:400e:c02::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D59261A01F2 for <tzdist@ietf.org>; Thu, 11 Dec 2014 09:33:40 -0800 (PST)
Received: by mail-pd0-f176.google.com with SMTP id r10so3395144pdi.7 for <tzdist@ietf.org>; Thu, 11 Dec 2014 09:33:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to :subject:references:in-reply-to:content-type; bh=ViKUKuHmt7FBCTu4s15q2unKX6EIcCwnOxBw88EfyDs=; b=omWlnbc2UYvQsrb+CLdnglKLJR/sx+YUsO/bLyyMAvDEDA4luPUWRp589UB2dGbFUZ y7gdi8qteRZJUwy1r/HhZYtE022tv93TMjrDSihUqHRtvi0mNX5/ePfZ9Me/ipWxkAGr SfZNhQqKc3H6zRB6j7ll4AnMJOfWXTE++axo0HgBRjrxOyM94l5RVcU6IeeQyQJ71dvG iX4Sk8LkpY3KTBZGxxJURcMqGfi25Avh2X0cX26UVnZIRfpsQ+z/qEB0ilpcbIpHiPOJ eO2Yd2n6Ic4HCKTtsTewKMTBz5ndcIZzglCsJ1OiRvvf4aRM5p/TZT8Vpa7rW/xfOS3s ahLA==
X-Received: by 10.68.91.4 with SMTP id ca4mr19002706pbb.97.1418319219848; Thu, 11 Dec 2014 09:33:39 -0800 (PST)
Received: from [192.168.1.4] (184-76-96-188.war.clearwire-wmx.net. [184.76.96.188]) by mx.google.com with ESMTPSA id is2sm1954015pbb.4.2014.12.11.09.33.38 for <tzdist@ietf.org> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 11 Dec 2014 09:33:38 -0800 (PST)
Message-ID: <5489D56D.5010206@gmail.com>
Date: Thu, 11 Dec 2014 10:33:33 -0700
From: Doug Royer <douglasroyer@gmail.com>
Organization: http://SoftwareAndServices.NET
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: tzdist@ietf.org
References: <54888642.1030108@lsces.co.uk> <F2F4FB8F282334E543F462B5@caldav.corp.apple.com> <54889270.7040801@lsces.co.uk> <CADC+-gQTgF8HYKoO=vLrgC=5jWDQuOn9ZTrtLH4e7ABAgJqtEw@mail.gmail.com> <54889940.9000900@lsces.co.uk> <54889EC9.90500@gmail.com>
In-Reply-To: <54889EC9.90500@gmail.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha1"; boundary="------------ms090707010704000202010206"
Archived-At: http://mailarchive.ietf.org/arch/msg/tzdist/wP9qFzaq0mUTMs6K6YPMdGhlkoA
Subject: [Tzdist] Create and distribution process of events with TZ data.
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: <http://www.ietf.org/mail-archive/web/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, 11 Dec 2014 17:33:47 -0000
There seem to be two separate issues in the latest discussions. (1) Distribution of TZ data. (2) Create/Update event change notifications that may include TZ changes. As to Distribution (#1) of updated TZ data: That is one of the points to this mailing list and I am still getting up to date. I still do not see the need for version information - still reading old posts. As to the Create/Update (#2) it already has a mechanism - iTIP and my comments on that are: I would think the achievable process would be to first have at event creation time the organizers user agent make an attempt to get the latest up to date version of time zone and distribute all or part of that TZ data with the event (or group of events). Its not going to be possible for many small devices to track TZ versions or compute differences and update the user to a schedule change resulting from TZ data changes. Explaining how to do that, doing that correctly, is going to be a pain. If too many fail at this, inaccurately computed TZ change computations is just as useless as not sharing any TZ data. I don't think anyone wants every CUA when powered up to contact a TZ authority and look for updates, then do all those recalculations on every event to determine if there are any changes the user needs to see. This would be DNS level connections with larger data packets. Which is why I think it is the event creators responsibility to get the up to date information and if it happens to not be up to date at least everyone will be late or early :-) When the organizer/CUA notices a significant TZ change has occurred, then then it iTIP handles the redistribution of scheduled events. No need for a new mechanism. When the organizer, or organizers CUA notices a TZ change, a person or automated process can re-PUBLISH or schedule the new updates with the new TZ data just as they do now. Any iTIP compliant CUA can already handle this. -- Doug Royer - (http://K7DMR.us / http://DougRoyer.US) DouglasRoyer@gmail.com 714-989-6135
- [Tzdist] Existing and new data ... Lester Caine
- Re: [Tzdist] Existing and new data ... Cyrus Daboo
- Re: [Tzdist] Existing and new data ... Lester Caine
- Re: [Tzdist] Existing and new data ... Paul Eggert
- Re: [Tzdist] Existing and new data ... Doug Royer
- Re: [Tzdist] Existing and new data ... Lester Caine
- Re: [Tzdist] Existing and new data ... Cyrus Daboo
- Re: [Tzdist] Existing and new data ... Cyrus Daboo
- Re: [Tzdist] Existing and new data ... Mike Douglass
- Re: [Tzdist] Existing and new data ... Lester Caine
- Re: [Tzdist] Existing and new data ... Paul Eggert
- Re: [Tzdist] Existing and new data ... Matthew Bobowski
- Re: [Tzdist] Existing and new data ... Cyrus Daboo
- Re: [Tzdist] Existing and new data ... Paul Eggert
- Re: [Tzdist] Existing and new data ... Matthew Bobowski
- Re: [Tzdist] Existing and new data ... Lester Caine
- Re: [Tzdist] Existing and new data ... Cyrus Daboo
- Re: [Tzdist] Existing and new data ... Lester Caine
- Re: [Tzdist] Existing and new data ... Cyrus Daboo
- [Tzdist] Create and distribution process of event… Doug Royer
- Re: [Tzdist] Create and distribution process of e… Lester Caine
- Re: [Tzdist] Create and distribution process of e… Doug Royer
- Re: [Tzdist] Create and distribution process of e… Tim Parenti
- Re: [Tzdist] Existing and new data ... Eliot Lear
- Re: [Tzdist] Existing and new data ... Paul Eggert
- Re: [Tzdist] Existing and new data ... Lester Caine
- Re: [Tzdist] Create and distribution process of e… Eliot Lear
- Re: [Tzdist] Create and distribution process of e… Lester Caine
- Re: [Tzdist] Create and distribution process of e… Tim Parenti
- Re: [Tzdist] Create and distribution process of e… Lester Caine
- Re: [Tzdist] Create and distribution process of e… Doug Royer