Re: [Tzdist] draft-ietf-tzdist-caldav-ref-02

Cyrus Daboo <cyrus@daboo.name> Wed, 27 May 2015 15:14 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 3E9A91B2D27 for <tzdist@ietfa.amsl.com>; Wed, 27 May 2015 08:14:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.013
X-Spam-Level:
X-Spam-Status: No, score=-0.013 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, 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 GTK8EV-6NL2K for <tzdist@ietfa.amsl.com>; Wed, 27 May 2015 08:14:36 -0700 (PDT)
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 EAAD31B2CE7 for <tzdist@ietf.org>; Wed, 27 May 2015 08:14:26 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id 4CFC114E0AAC; Wed, 27 May 2015 11:14:26 -0400 (EDT)
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 tGVnNRPMbIkE; Wed, 27 May 2015 11:14:25 -0400 (EDT)
Received: from caldav.corp.apple.com (unknown [17.45.162.46]) by daboo.name (Postfix) with ESMTPSA id 6B4FA14E0AA1; Wed, 27 May 2015 11:14:24 -0400 (EDT)
Date: Wed, 27 May 2015 11:14:21 -0400
From: Cyrus Daboo <cyrus@daboo.name>
To: Ken Murchison <murch@andrew.cmu.edu>, Time Zone Data Distribution Service <tzdist@ietf.org>
Message-ID: <4214D3605334C216B4B0C6F2@caldav.corp.apple.com>
In-Reply-To: <55479ABA.1050701@andrew.cmu.edu>
References: <55479ABA.1050701@andrew.cmu.edu>
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="1418"
Archived-At: <http://mailarchive.ietf.org/arch/msg/tzdist/I-G1i9r5BdgIg9e8P6Eyf5vXL_0>
Subject: Re: [Tzdist] draft-ietf-tzdist-caldav-ref-02
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: Wed, 27 May 2015 15:14:41 -0000

Hi Ken,
Following up on this now that WG last call is over.

--On May 4, 2015 at 12:13:46 PM -0400 Ken Murchison <murch@andrew.cmu.edu> 
wrote:

> My only comment/concern on this document is the new text in Section 3.1.3
> regarding use of the Prefer header field for clients to require a
> 'calendar-no-timezone' capable server to include VTIMEZONE components in
> the iCalendar data.  My reading of RFC 7240 (Section 2, para 1) leads me
> to believe that a server is free to ignore any/all preferences in the
> Prefer header, therefore a client would have no guaranteed way to opt-out
> of the tz-by-ref behavior.
>
> I could be reading RFC 7240 incorrectly, or maybe we can force
> 'calendar-no-timezone' capable servers to implement and obey the
> 'vtimezone' preference as this document leans towards doing.  Either way,
> we may want to reach out to the HTTPbis folks to get some input.
>
> Other alternatives OTH (perhaps not good ones) might be to use the Expect
> header field, or doing something with the Accept header field.

I do think what we are doing is OK, particularly given that we use the DAV 
header field to advertise the fact that the server will obey the Prefer 
option behaviors the spec defines. In any case, the Prefer header item will 
need to be registered and go through the designated expert review process - 
so let's get that done and see if they object to this usage.

-- 
Cyrus Daboo