Re: [Ietf-caldav] Last Call comment on Etag requirements in draft-dusseault-caldav-12

Cyrus Daboo <cyrus@daboo.name> Mon, 05 June 2006 21:20 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FnMUY-0000aV-5i; Mon, 05 Jun 2006 17:20:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FnJuF-0006ws-FW for ietf@ietf.org; Mon, 05 Jun 2006 14:34:28 -0400
Received: from out3.smtp.messagingengine.com ([66.111.4.27]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FnJuE-0006XG-7m for ietf@ietf.org; Mon, 05 Jun 2006 14:34:27 -0400
Received: from frontend3.internal (frontend3.internal [10.202.2.152]) by frontend1.messagingengine.com (Postfix) with ESMTP id EBA13D68FA7; Mon, 5 Jun 2006 14:34:24 -0400 (EDT)
Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by frontend3.internal (MEProxy); Mon, 05 Jun 2006 14:34:27 -0400
X-Sasl-enc: em1oVeABaaSx3nPftLSAzsz5NZUUgwPGQdyqLpuWEi00 1149532466
Received: from [17.101.35.126] (unknown [17.101.35.126]) by www.fastmail.fm (Postfix) with ESMTP id 2921E88E7; Mon, 5 Jun 2006 14:34:23 -0400 (EDT)
Date: Mon, 05 Jun 2006 14:34:17 -0400
From: Cyrus Daboo <cyrus@daboo.name>
To: Julian Reschke <julian.reschke@gmx.de>, ietf@ietf.org
Message-ID: <074E50A7C8A95FFDB5E8B5E6@Cyrus-Daboo.local>
In-Reply-To: <44847841.8080902@gmx.de>
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>
X-Mailer: Mulberry/4.0.5 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
X-Mailman-Approved-At: Mon, 05 Jun 2006 17:20:04 -0400
Cc: Ted Hardie <hardie@qualcomm.com>, 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

Hi Julian,

--On June 5, 2006 8:30:25 PM +0200 Julian Reschke <julian.reschke@gmx.de> 
wrote:

> I notice that draft-dusseault-caldav-12 now is in IESG Evaluation
> (<https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag
> =11253>).
>
> For the record: as far as I can tell, the issue that I raised below is
> critical (given the fact that we have a separate activity to clarify this
> in HTTP), and has not been addressed. It's not clear to me whether the
> client issue it attempts to solve really is important. If it is, there is
> a simpler way to accomplish this ([1]) that doesn't risk making CalDAV
> incompatible with other specs extending HTTP (or HTTP itself, for that
> matter).

We are planning on addressing this ETag issue in a revision now that 
last-call is over. Authors are discussing right now.

-- 
Cyrus Daboo


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf