IETF Logo Mail Archive

Re: [Tzdist] Fwd: [tzdist] #32 (service): managing historical data

Cyrus Daboo <cyrus@daboo.name> Thu, 11 December 2014 17:00 UTC

Return-Path: <cyrus@daboo.name>
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 6FACA1A1AE8 for <tzdist@ietfa.amsl.com>; Thu, 11 Dec 2014 09:00:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, T_RP_MATCHES_RCVD=-0.01] 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 4EZo1ZlWM-NF for <tzdist@ietfa.amsl.com>; Thu, 11 Dec 2014 09:00:34 -0800 (PST)
Received: from daboo.name (daboo.name [173.13.55.49]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 31ACA1A1A95 for <tzdist@ietf.org>; Thu, 11 Dec 2014 09:00:34 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id 5B47C5CDBB3; Thu, 11 Dec 2014 12:00:33 -0500 (EST)
X-Virus-Scanned: amavisd-new at example.com
Received: from daboo.name ([127.0.0.1]) by localhost (daboo.name [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AfE-95fw4H_a; Thu, 11 Dec 2014 12:00:33 -0500 (EST)
Received: from caldav.corp.apple.com (unknown [17.45.162.46]) by daboo.name (Postfix) with ESMTPSA id 348905CDBA3; Thu, 11 Dec 2014 12:00:31 -0500 (EST)
Date: Thu, 11 Dec 2014 12:00:28 -0500
From: Cyrus Daboo <cyrus@daboo.name>
To: Doug Royer <douglasroyer@gmail.com>, tzdist@ietf.org
Message-ID: <35BC5886C9A58F866E8A46A8@caldav.corp.apple.com>
In-Reply-To: <5489CA90.1070307@gmail.com>
References: <059.5da79d7c9d394e20e3c22513cfe04c33@tools.ietf.org> <CADZyTk=aVNFmoR1GA+w_xU7+-28Rnb-TJY4uT-jVOU4jdC1yKg@mail.gmail.com> <CACzrW9D=wZi1VvCiGa-4kwbKAyHMs6rduF6+cKA0Nn0gshm+sQ@mail.gmail.com> <54877E06.5020409@lsces.co.uk> <39981BA759F3923868CCFBD3@caldav.corp.apple.com> <54888249.9080607@lsces.co.uk> <CAFpi07z8NauUZ5aBqqg9sXDsmSA+hG4HuZNDkLe7fnk=mg4wgA@mail.gmail.com> <676B23282D9F7F1DCE6A54C7@caldav.corp.apple.com> <CAFpi07x79gJLEBWmpxWv7V13CiwmeKGy7bwS1=+ukp-sKmwFxA@mail.gmail.com> <5488921B.8020900@lsces.co.uk> <5488973F.7050400@andrew.cmu.edu> <54889C39.1080103@lsces.co.uk> <D2BE5C3BFE11019ECF4BEF62@caldav.corp.apple.com> <5488A6E6.8050903@lsces.co.uk> <CADC+-gTiyJ4QHZT6m3je9M9-ifSELnSWgmgy7iXSWNS+p8pthg@mail.gmail.com> <5488C0EA.8090505@lsces.co.uk> <CADC+-gTgckSe1ca6Sai6RguQid=ReM7bH6K8+dVVFm-YfbpFbA@mail.gmail.com> <5488DA56.2090306@lsces.co.uk> <CADC+-gQN=Qb2y8M-bHnPzMcK8r=xUG-seQ7XzvZwwcWsHpHnBQ@mail.gmail.com> <54895986.6060806@lsces.co.uk> <5489CA90.1070307@gmail.com>
X-Mailer: Mulberry/4.1.0b1 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; size="1007"
Archived-At: http://mailarchive.ietf.org/arch/msg/tzdist/zMYTTPp5jHzqKjNkywkoekDSusA
Subject: Re: [Tzdist] Fwd: [tzdist] #32 (service): managing historical 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:00:35 -0000

Hi Doug,

--On December 11, 2014 at 9:47:12 AM -0700 Doug Royer 
<douglasroyer@gmail.com> wrote:

>> Which is EXACTLY the problem that tzdist SHOULD be addressing. Just
>> perpetuating the current mess is simply not acceptable, and any draft
>> which does that should not be allowed forward.
>
> Its not a problem unless you ignore what the organizer sends. Its more
> relevant that
> everyone agree with the organizer, than with some other source.

Except that many clients DO ignore what the organizer sends - they just 
assume that if the TZID in the iCalendar data matches one they have 
locally, then the local definition is used in place of any sent in a 
VTIMEZONE. i.e., they throw away the organizer's copy of the VTIMEZONE in 
favor of there own.

One of the goals for tzdist is to ensure that when clients do that, they 
have a reasonable chance that their local time zone data matches what the 
organizer had (i.e., organizer and attendees are in sync wrt the VTIMEZONE 
data).

-- 
Cyrus Daboo

v2.23.0 | Report a Bug | By Email