Re: [Ietf-caldav] Last Call comment on Etag requirements in draft-dusseault-caldav-12
Wilfredo Sánchez Vega <wsanchez@wsanchez.net> Thu, 29 June 2006 12:20 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FvvVn-0006Sk-P5; Thu, 29 Jun 2006 08:20:47 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fsk0v-0006fo-QX for ietf@ietf.org; Tue, 20 Jun 2006 13:27:45 -0400
Received: from mail-out3.apple.com ([17.254.13.22]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fsk0t-0003jF-FG for ietf@ietf.org; Tue, 20 Jun 2006 13:27:45 -0400
Received: from relay6.apple.com (a17-128-113-36.apple.com [17.128.113.36]) by mail-out3.apple.com (8.12.11/8.12.11) with ESMTP id k5KHRerM007832; Tue, 20 Jun 2006 10:27:40 -0700 (PDT)
Received: from [17.221.42.43] (unknown [17.221.42.43]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by relay6.apple.com (Apple SCV relay) with ESMTP id 8B5B0BD; Tue, 20 Jun 2006 10:27:40 -0700 (PDT)
In-Reply-To: <80E35CD5-943D-4BE2-BA31-8987E6A4F634@osafoundation.org>
References: <D58B890CEBB86771C83E8401@Cyrus-Daboo.local> <443FAB85.8030503@gmx.de> <7246CAD3-9329-4B34-8D23-08B196E80EDE@osafoundation.org> <443FEF47.3050406@gmx.de> <5FD8AADA-F91A-4B1F-9453-01178901DB6F@osafoundation.org> <443FF7B9.3050801@gmx.de> <7D5DE367-5FD8-4398-849D-2158EF6BC256@osafoundation.org> <443FFE81.6010605@gmx.de> <CD95571B-E80E-4DA4-A522-23C0647CF6B6@osafoundation.org> <4440AC2D.2050802@gmx.de> <44509D3B.4050503@gmx.de> <DBB5A293-8F91-4E39-BE97-B6BD5236F5A3@osafoundation.org> <44512C9B.6090102@gmx.de> <44847841.8080902@gmx.de> <074E50A7C8A95FFDB5E8B5E6@Cyrus-Daboo.local> <44913E39.7040503@gmx.de> <A53A3668-1C4B-46B2-BE5C-02F3F8D7D45E@apple.com> <4136E0DE-F4F4-4A6E-9AC0-1C6297910ECA@osafoundation.org> <66682F0C-92F3-45E9-B59A-FB5D34561913@apple.com> <80E35CD5-943D-4BE2-BA31-8987E6A4F634@osafoundation.org>
Mime-Version: 1.0 (Apple Message framework v750)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <DF64CAE0-186D-4C8E-B822-A6826F71E533@wsanchez.net>
Content-Transfer-Encoding: 7bit
From: Wilfredo Sánchez Vega <wsanchez@wsanchez.net>
Date: Tue, 20 Jun 2006 10:27:39 -0700
To: Lisa Dusseault <lisa@osafoundation.org>
X-Mailer: Apple Mail (2.750)
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
X-Mailman-Approved-At: Thu, 29 Jun 2006 08:20:30 -0400
Cc: Julian Reschke <julian.reschke@gmx.de>, Ted Hardie <hardie@qualcomm.com>, HTTP Working Group <ietf-http-wg@w3.org>, ietf@ietf.org, CalDAV DevList <ietf-caldav@osafoundation.org>
Subject: Re: [Ietf-caldav] Last Call comment on Etag requirements in draft-dusseault-caldav-12
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Errors-To: ietf-bounces@ietf.org
Not really, no. HTTP defines ETag. An HTTP server should be able to use the same ETag logic on all HTTP resources, and not treat ETags for calendar resources differently than others. Not all users of ETags are going to be aware that calendar resources are special. My concern is that if there is *any* inconsistency between the general solution when it comes and CalDAV's, that an implementor may have to choose between being compliant with CalDAV or the more general ETag spec, or may have to continue to implement special semantics on calendar resources for purposes which are better served by the other spec. I realize that "the other spec" doesn't exist today, and that this is a total drag. Can't we take your one paragraph and put it into its own document? I don't know IETF process very well, so I don't know what the next steps should be, but as an implementor, I'm uncomfortable with the prospect of dealing with two independently written specifications for the same behavior. -wsv On Jun 20, 2006, at 8:13 AM, Lisa Dusseault wrote: > Wilfredo, does it make a difference that CalDAV specifies special > ETag behavior only on Calendar Component resource items (not for > all HTTP resources)? _______________________________________________ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf
- Last Call comment on Etag requirements in draft-d… Julian Reschke
- Re: [Ietf-caldav] Last Call comment on Etag requi… Lisa Dusseault
- Re: [Ietf-caldav] Last Call comment on Etag requi… Julian Reschke
- Re: [Ietf-caldav] Last Call comment on Etag requi… Julian Reschke
- Re: [Ietf-caldav] Last Call comment on Etag requi… Cyrus Daboo
- Re: [Ietf-caldav] Last Call comment on Etag requi… Julian Reschke
- Re: [Ietf-caldav] Last Call comment on Etag requi… Peter Dambier
- Re: [Ietf-caldav] Last Call comment on Etag requi… Lisa Dusseault
- Re: [Ietf-caldav] Last Call comment on Etag requi… Julian Reschke
- Re: [Ietf-caldav] Last Call comment on Etag requi… Lisa Dusseault
- Re: [Ietf-caldav] Last Call comment on Etag requi… Lisa Dusseault
- Re: [Ietf-caldav] Last Call comment on Etag requi… Julian Reschke
- Re: [Ietf-caldav] Last Call comment on Etag requi… Lisa Dusseault
- Re: [Ietf-caldav] Last Call comment on Etag requi… Lisa Dusseault
- Re: [Ietf-caldav] Last Call comment on Etag requi… Julian Reschke
- Re: [Ietf-caldav] Last Call comment on Etag requi… Julian Reschke
- Re: [Ietf-caldav] Last Call comment on Etag requi… Wilfredo Sánchez Vega
- Re: [Ietf-caldav] Last Call comment on Etag requi… Wilfredo Sánchez Vega
- Re: [Ietf-caldav] Last Call comment on Etag requi… Julian Reschke
- Re: [Ietf-caldav] Last Call comment on Etag requi… Robert Sayre
- Re: [Ietf-caldav] Last Call comment on Etag requi… Wilfredo Sánchez Vega
- Re: PMTUD Milestones past due Matt Mathis
- Re: [Ietf-caldav] Last Call comment on Etag requi… Wilfredo Sánchez Vega