Re: [Ietf-caldav] I-D ACTION:draft-dusseault-caldav-11.txt (fwd)

Lisa Dusseault <lisa@osafoundation.org> Fri, 14 April 2006 19:20 UTC

Return-Path: <lisa@osafoundation.org>
X-Original-To: ietf-caldav@osafoundation.org
Delivered-To: ietf-caldav@osafoundation.org
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 3E07B7F8D4 for <ietf-caldav@osafoundation.org>; Fri, 14 Apr 2006 12:20:10 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 2EDEC14227B for <ietf-caldav@osafoundation.org>; Fri, 14 Apr 2006 12:20:10 -0700 (PDT)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 18117-06; Fri, 14 Apr 2006 12:20:09 -0700 (PDT)
Received: from [192.168.1.100] (c-67-161-46-163.hsd1.ca.comcast.net [67.161.46.163]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 7DB2E142258; Fri, 14 Apr 2006 12:20:09 -0700 (PDT)
In-Reply-To: <443FEF47.3050406@gmx.de>
References: <D58B890CEBB86771C83E8401@Cyrus-Daboo.local> <443FAB85.8030503@gmx.de> <7246CAD3-9329-4B34-8D23-08B196E80EDE@osafoundation.org> <443FEF47.3050406@gmx.de>
Mime-Version: 1.0 (Apple Message framework v746.2)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <5FD8AADA-F91A-4B1F-9453-01178901DB6F@osafoundation.org>
Content-Transfer-Encoding: 7bit
From: Lisa Dusseault <lisa@osafoundation.org>
Subject: Re: [Ietf-caldav] I-D ACTION:draft-dusseault-caldav-11.txt (fwd)
Date: Fri, 14 Apr 2006 12:20:05 -0700
To: Julian Reschke <julian.reschke@gmx.de>
X-Mailer: Apple Mail (2.746.2)
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=-0.6 tagged_above=-50.0 required=4.0 tests=AWL, BAYES_00, RCVD_IN_NJABL_DUL, RCVD_IN_SORBS_DUL
X-Spam-Level:
Cc: CalDAV DevList <ietf-caldav@osafoundation.org>
X-BeenThere: ietf-caldav@osafoundation.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions on Calendar Access protocol based on WebDAV <ietf-caldav.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-caldav>, <mailto:ietf-caldav-request@osafoundation.org?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-caldav>
List-Post: <mailto:ietf-caldav@osafoundation.org>
List-Help: <mailto:ietf-caldav-request@osafoundation.org?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-caldav>, <mailto:ietf-caldav-request@osafoundation.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Apr 2006 19:20:10 -0000

On Apr 14, 2006, at 11:51 AM, Julian Reschke wrote:

> Lisa Dusseault wrote:
>> Should we simply remove the claim about what RFC2616 says and  
>> continue to make these requirements?  (If not, do you have a  
>> proposal for solving the problem?)
>
> I think neither CalDAV nor RFC2518bis should make any statements  
> about this issue, but draft-whitehead-http-etag. This who care  
> about this issue should join the discussion on the HTTP mailing list.
>

Unfortunately, that just does not solve the problem for CalDAV, which  
is likely to have interoperability problems if we don't make firm  
requirements about modifying resources on PUT.  Relying on  
RFC2518bis, which has been through WG last call, is one thing;  
relying on the etag draft is another.

Lisa