Re: Relationship between BIND and RFC 3253

Julian Reschke <julian.reschke@gmx.de> Sat, 16 August 2008 10:46 UTC

Return-Path: <w3c-dist-auth-request@listhub.w3.org>
X-Original-To: ietfarch-webdav-archive@core3.amsl.com
Delivered-To: ietfarch-webdav-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 53DDF3A6AEB for <ietfarch-webdav-archive@core3.amsl.com>; Sat, 16 Aug 2008 03:46:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.725
X-Spam-Level:
X-Spam-Status: No, score=-9.725 tagged_above=-999 required=5 tests=[AWL=0.874, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ymEZD0wMN2fa for <ietfarch-webdav-archive@core3.amsl.com>; Sat, 16 Aug 2008 03:46:17 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by core3.amsl.com (Postfix) with ESMTP id 3393B3A6A29 for <webdav-archive@lists.ietf.org>; Sat, 16 Aug 2008 03:46:16 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.63) (envelope-from <w3c-dist-auth-request@listhub.w3.org>) id 1KUJHK-0005wQ-J5 for w3c-dist-auth-dist@listhub.w3.org; Sat, 16 Aug 2008 10:45:02 +0000
Received: from [128.30.52.63] (helo=bart.w3.org) by frink.w3.org with esmtp (Exim 4.63) (envelope-from <julian.reschke@gmx.de>) id 1KUJHI-00057a-Ns for w3c-dist-auth@listhub.w3.org; Sat, 16 Aug 2008 10:45:00 +0000
Received: from mail.gmx.net ([213.165.64.20]) by bart.w3.org with smtp (Exim 4.63) (envelope-from <julian.reschke@gmx.de>) id 1KUJ54-0006de-Dn for w3c-dist-auth@w3.org; Sat, 16 Aug 2008 06:32:33 -0400
Received: (qmail invoked by alias); 16 Aug 2008 10:31:50 -0000
Received: from p508FCA64.dip.t-dialin.net (EHLO [192.168.178.22]) [80.143.202.100] by mail.gmx.net (mp051) with SMTP; 16 Aug 2008 12:31:50 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1/Y3BsZ7VXYsEnBPPOuACZ3XN5qwKXhBMHo+AwqOE x2O88h8NSPFbBm
Message-ID: <48A6AC91.4010309@gmx.de>
Date: Sat, 16 Aug 2008 12:31:45 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.0.4) Gecko/20060516 Thunderbird/1.5.0.4 Mnenhy/0.7.4.666
MIME-Version: 1.0
To: Geoffrey M Clemm <geoffrey.clemm@us.ibm.com>
CC: Werner Donné <werner.donne@re.be>, w3c-dist-auth@w3.org
References: <OF2B3F6AA5.34557DA6-ON852574A3.001C254A-852574A3.001C8E5C@us.ibm.com> <48A69DFC.3060200@gmx.de>
In-Reply-To: <48A69DFC.3060200@gmx.de>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
X-FuHaFi: 0.6
Received-SPF: pass
X-SPF-Guess: pass
X-W3C-Hub-Spam-Status: No, score=-0.7
X-W3C-Hub-Spam-Report: BAYES_20=-0.74, SPF_PASS=-0.001
X-W3C-Scan-Sig: bart.w3.org 1KUJ54-0006de-Dn 116b41c23f34d60a7e8f58fb05f23b18
X-Original-To: w3c-dist-auth@w3.org
Subject: Re: Relationship between BIND and RFC 3253
Archived-At: <http://www.w3.org/mid/48A6AC91.4010309@gmx.de>
Resent-From: w3c-dist-auth@w3.org
X-Mailing-List: <w3c-dist-auth@w3.org> archive/latest/12989
X-Loop: w3c-dist-auth@w3.org
Sender: w3c-dist-auth-request@w3.org
Resent-Sender: w3c-dist-auth-request@w3.org
Precedence: list
List-Id: <w3c-dist-auth.w3.org>
List-Help: <http://www.w3.org/Mail/>
List-Unsubscribe: <mailto:w3c-dist-auth-request@w3.org?subject=unsubscribe>
Resent-Message-Id: <E1KUJHK-0005wQ-J5@frink.w3.org>
Resent-Date: Sat, 16 Aug 2008 10:45:02 +0000

Julian Reschke wrote:
> 
> Geoffrey M Clemm wrote:
>>
>> Point 1 is correct.  
> 
> Indeed.
> 
> I think Werner is right in that many do not understand the relation 
> between BIND and DeltaV, and thus it would be useful to state it.
> 
> We already have a "Relationship to WebDAV Access Control Protocol" 
> (<http://greenbytes.de/tech/webdav/draft-ietf-webdav-bind-latest.html#rfc.section.9>), 
> so my proposal would be to make that a generic "Relationship to other 
> WebDAV Specifications", and having one subsection for ACL and DeltaV each.
> 
> The DeltaV part could read (this is mainly Werner's text):
> 
> "When supporting version controlled collections, bindings may be 
> introduced in a server without actually issuing the BIND method. For 
> instance, when a MOVE is performed of a resource from one 
> version-controlled collection to another, both collections should be 
> checked out. An additional binding would be the result if the target 
> collection would be subsequently checked in, while the check-out of the 
> source collection is undone. The resulting situation is meaningless if 
> the binding model is not supported."
> ...

Hm.

It just occurred to me that a server that implements MOVE as a sequence 
of COPY and DELETE would expose a different behavior -- checking in the 
destination collection but reverting the source collection would turn 
the operation into the equivalent of a COPY, not a BIND...

BR, Julian