IETF Logo Mail Archive

Re: [Ietf-caldav] Comments on draft-dusseault-caldav-05

Cyrus Daboo <daboo@isamet.com> Sun, 06 March 2005 20:41 UTC

X-Envelope-From: daboo@isamet.com
X-Envelope-To: <ietf-caldav@osafoundation.org>
Received: from darius.cyrusoft.com (darius.cyrusoft.com [63.163.82.2]) by kahuna.osafoundation.org (8.12.8/8.12.8) with ESMTP id j26Kfuaa001072 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf-caldav@osafoundation.org>; Sun, 6 Mar 2005 12:41:57 -0800
Received: from [10.0.1.5] (pool-68-162-179-106.pitt.east.verizon.net [68.162.179.106]) (authenticated bits=0) by darius.cyrusoft.com (8.12.9/8.12.9) with ESMTP id j26KTe6g032440 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 6 Mar 2005 15:29:42 -0500
Date: Sun, 06 Mar 2005 15:41:43 -0500
From: Cyrus Daboo <daboo@isamet.com>
To: Julian Reschke <julian.reschke@gmx.de>, Helge Hess <helge.hess@opengroupware.org>
Subject: Re: [Ietf-caldav] Comments on draft-dusseault-caldav-05
Message-ID: <15E3D38DD5378F06A173F0A6@ninevah.cyrusoft.com>
In-Reply-To: <422B669E.4080202@gmx.de>
References: <422B5D86.9060409@gmx.de> <343bfb41e0d14b38c845978b3710a566@opengroupware.org> <422B629E.7010807@gmx.de> <3a5d87b842358a29b0f537d3cf227881@opengroupware.org> <422B669E.4080202@gmx.de>
X-Mailer: Mulberry/3.2.0a1 (Linux/PPC)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Status: No, hits=0.0 tests=none
X-Spam-Score: 0 ()
X-Scanned-By: MIMEDefang 2.48 on 127.0.0.1
Cc: CalDAV DevList <ietf-caldav@osafoundation.org>
X-BeenThere: ietf-caldav@osafoundation.org
X-Mailman-Version: 2.1.4
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: Sun, 06 Mar 2005 20:41:59 -0000

Hi Julian,

--On Sunday, March 06, 2005 09:22:54 PM +0100 Julian Reschke 
<julian.reschke@gmx.de> wrote:

> Helge Hess wrote:
>> On 6. Mrz 2005, at 21:05 Uhr, Julian Reschke wrote:
>>
>>> Anyway, we heard from Roy Fielding (author of RFC2616 and RFC3986)
>>> that this is a protocol violation; see
>>> <http://lists.w3.org/Archives/Public/ietf-http-wg/2005JanMar/
>>> 0066.html>).
>>
>>
>> I don't find a simple
>> ---snip---
>> That is not allowed in HTTP.
>> ---snap---
>> particulary convincing (the rest of the text is about using POST).
>
> ...in which case you should follow up to Roy's posting over at the IETF
> HTTP WG.
>
> I think I've done my part in documenting the issue and proposing
> alternatives :-)
>
>> ...

OK - just to put this one to bed, at least in regards to CalDAV - it is our 
(the authors') intention to remove this 'redirect on PUT' behaviour from 
the CalDAV draft. Instead, if a server has this type of behaviour, then it 
can use whatever generic http solution is finally settled on (ADDMEMBER, 
POST, PUT + status code etc).

-- 
Cyrus Daboo

v2.23.0 | Report a Bug | By Email