draft-ietf-webdav-bind-05.txt   draft-ietf-webdav-bind-06.txt 
Network Working Group G. Clemm Network Working Group G. Clemm
Internet-Draft IBM Internet-Draft IBM
Updates: 2518 (if approved) J. Crawford Updates: 2518 (if approved) J. Crawford
Expires: September 21, 2004 IBM Research Expires: December 31, 2004 IBM Research
J. Reschke J. Reschke
greenbytes greenbytes
J. Whitehead J. Whitehead
U.C. Santa Cruz U.C. Santa Cruz
March 23, 2004 July 2, 2004
Binding Extensions to Web Distributed Authoring and Versioning Binding Extensions to Web Distributed Authoring and Versioning
(WebDAV) (WebDAV)
draft-ietf-webdav-bind-05 draft-ietf-webdav-bind-latest-06
Status of this Memo Status of this Memo
By submitting this Internet-Draft, I certify that any applicable By submitting this Internet-Draft, I certify that any applicable
patent or other IPR claims of which I am aware have been disclosed, patent or other IPR claims of which I am aware have been disclosed,
and any of which I become aware will be disclosed, in accordance with and any of which I become aware will be disclosed, in accordance with
RFC 3667. RFC 3668.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that other Task Force (IETF), its areas, and its working groups. Note that
groups may also distribute working documents as Internet-Drafts. other groups may also distribute working documents as
Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at http:// The list of current Internet-Drafts can be accessed at
www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on September 21, 2004. This Internet-Draft will expire on December 31, 2004.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2004). All Rights Reserved. Copyright (C) The Internet Society (2004). All Rights Reserved.
Abstract Abstract
This specification defines bindings, and the BIND method for creating This specification defines bindings, and the BIND method for creating
multiple bindings to the same resource. Creating a new binding to a multiple bindings to the same resource. Creating a new binding to a
resource causes at least one new URI to be mapped to that resource. resource causes at least one new URI to be mapped to that resource.
skipping to change at page 1, line 49 skipping to change at page 2, line 4
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2004). All Rights Reserved. Copyright (C) The Internet Society (2004). All Rights Reserved.
Abstract Abstract
This specification defines bindings, and the BIND method for creating This specification defines bindings, and the BIND method for creating
multiple bindings to the same resource. Creating a new binding to a multiple bindings to the same resource. Creating a new binding to a
resource causes at least one new URI to be mapped to that resource. resource causes at least one new URI to be mapped to that resource.
Servers are required to insure the integrity of any bindings that Servers are required to insure the integrity of any bindings that
they allow to be created. they allow to be created.
Please send comments to the Distributed Authoring and Versioning Editorial Note
(WebDAV) working group at <mailto:w3c-dist-auth@w3.org>, which may be
joined by sending a message with subject "subscribe" to
<mailto:w3c-dist-auth-request@w3.org?subject=subscribe>. Discussions
of the WEBDAV working group are archived at <http://lists.w3.org/
Archives/Public/w3c-dist-auth/>.
*(To be removed before publication as RFC): * *(To be removed before publication as RFC): *
<http://greenbytes.de/tech/webdav/draft-ietf-webdav-bind-issues.html> Please send comments to the Distributed Authoring and Versioning
(WebDAV) working group at w3c-dist-auth@w3.org [1], which may be
joined by sending a message with subject "subscribe" to
w3c-dist-auth-request@w3.org [2]. Discussions of the WEBDAV working
group are archived at .
lists all registered issues since draft 02. lists all registered issues since draft 02.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1 Terminology . . . . . . . . . . . . . . . . . . . . . . . . 5 1.1 Terminology . . . . . . . . . . . . . . . . . . . . . . . 5
1.2 Rationale for Distinguishing Bindings from URI Mappings . . 6 1.2 Rationale for Distinguishing Bindings from URI Mappings . 6
1.3 Method Preconditions and Postconditions . . . . . . . . . . 7 1.3 Method Preconditions and Postconditions . . . . . . . . . 7
2. Overview of Bindings . . . . . . . . . . . . . . . . . . . . 7 2. Overview of Bindings . . . . . . . . . . . . . . . . . . . . . 7
2.1 Bindings to Collections . . . . . . . . . . . . . . . . . . 8 2.1 Bindings to Collections . . . . . . . . . . . . . . . . . 8
2.2 URI Mappings Created by a new Binding . . . . . . . . . . . 9 2.2 URI Mappings Created by a new Binding . . . . . . . . . . 9
2.3 COPY and Bindings . . . . . . . . . . . . . . . . . . . . . 10 2.3 COPY and Bindings . . . . . . . . . . . . . . . . . . . . 10
2.4 DELETE and Bindings . . . . . . . . . . . . . . . . . . . . 11 2.4 DELETE and Bindings . . . . . . . . . . . . . . . . . . . 11
2.5 MOVE and Bindings . . . . . . . . . . . . . . . . . . . . . 12 2.5 MOVE and Bindings . . . . . . . . . . . . . . . . . . . . 12
2.6 Determining Whether Two Bindings Are to the Same Resource . 13 2.6 Determining Whether Two Bindings Are to the Same
2.7 Discovering the Bindings to a Resource . . . . . . . . . . . 14 Resource . . . . . . . . . . . . . . . . . . . . . . . . . 13
3. Properties . . . . . . . . . . . . . . . . . . . . . . . . . 14 2.7 Discovering the Bindings to a Resource . . . . . . . . . . 13
3.1 DAV:resource-id Property . . . . . . . . . . . . . . . . . . 14 3. Properties . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.2 DAV:parent-set Property . . . . . . . . . . . . . . . . . . 14 3.1 DAV:resource-id Property . . . . . . . . . . . . . . . . . 14
4. BIND Method . . . . . . . . . . . . . . . . . . . . . . . . 15 3.2 DAV:parent-set Property . . . . . . . . . . . . . . . . . 14
4.1 Example: BIND . . . . . . . . . . . . . . . . . . . . . . . 17 4. BIND Method . . . . . . . . . . . . . . . . . . . . . . . . . 15
5. UNBIND Method . . . . . . . . . . . . . . . . . . . . . . . 17 4.1 Example: BIND . . . . . . . . . . . . . . . . . . . . . . 17
5.1 Example: UNBIND . . . . . . . . . . . . . . . . . . . . . . 19 5. UNBIND Method . . . . . . . . . . . . . . . . . . . . . . . . 17
6. REBIND Method . . . . . . . . . . . . . . . . . . . . . . . 19 5.1 Example: UNBIND . . . . . . . . . . . . . . . . . . . . . 19
6.1 Example: REBIND . . . . . . . . . . . . . . . . . . . . . . 21 6. REBIND Method . . . . . . . . . . . . . . . . . . . . . . . . 19
7. Additional Status Codes . . . . . . . . . . . . . . . . . . 21 6.1 Example: REBIND . . . . . . . . . . . . . . . . . . . . . 21
7.1 208 Already Reported . . . . . . . . . . . . . . . . . . . . 21 7. Additional Status Codes . . . . . . . . . . . . . . . . . . . 21
7.1.1 Example: PROPFIND by bind-aware client . . . . . . . . . . . 22 7.1 208 Already Reported . . . . . . . . . . . . . . . . . . . 21
7.1.2 Example: PROPFIND by non-bind-aware client . . . . . . . . . 23 7.1.1 Example: PROPFIND by bind-aware client . . . . . . . . 22
7.2 506 Loop Detected . . . . . . . . . . . . . . . . . . . . . 24 7.1.2 Example: PROPFIND by non-bind-aware client . . . . . . 24
8. Capability discovery . . . . . . . . . . . . . . . . . . . . 24 7.2 506 Loop Detected . . . . . . . . . . . . . . . . . . . . 24
8.1 OPTIONS method . . . . . . . . . . . . . . . . . . . . . . . 24 8. Capability discovery . . . . . . . . . . . . . . . . . . . . . 24
8.2 'DAV' request header . . . . . . . . . . . . . . . . . . . . 24 8.1 OPTIONS method . . . . . . . . . . . . . . . . . . . . . . 24
8.2.1 Generic syntax . . . . . . . . . . . . . . . . . . . . . . . 24 8.2 'DAV' request header . . . . . . . . . . . . . . . . . . . 24
8.2.2 Client compliance class 'bind' . . . . . . . . . . . . . . . 25 8.2.1 Generic syntax . . . . . . . . . . . . . . . . . . . . 24
9. Security Considerations . . . . . . . . . . . . . . . . . . 25 8.2.2 Client compliance class 'bind' . . . . . . . . . . . . 25
9.1 Privacy Concerns . . . . . . . . . . . . . . . . . . . . . . 25 9. Security Considerations . . . . . . . . . . . . . . . . . . . 25
9.2 Bind Loops . . . . . . . . . . . . . . . . . . . . . . . . . 25 9.1 Privacy Concerns . . . . . . . . . . . . . . . . . . . . . 25
9.3 Bindings, and Denial of Service . . . . . . . . . . . . . . 25 9.2 Bind Loops . . . . . . . . . . . . . . . . . . . . . . . . 25
9.4 Private Locations May Be Revealed . . . . . . . . . . . . . 26 9.3 Bindings, and Denial of Service . . . . . . . . . . . . . 26
9.5 DAV:parent-set and Denial of Service . . . . . . . . . . . . 26 9.4 Private Locations May Be Revealed . . . . . . . . . . . . 26
9.5 DAV:parent-set and Denial of Service . . . . . . . . . . . 26
10. Internationalization Considerations . . . . . . . . . . . . 26 10. Internationalization Considerations . . . . . . . . . . . . 26
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . 26 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . 26
12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 26 12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 26
Normative References . . . . . . . . . . . . . . . . . . . . 26 13. Normative References . . . . . . . . . . . . . . . . . . . . 27
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 27 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 27
A. Change Log (to be removed by RFC Editor before A. Change Log (to be removed by RFC Editor before publication) . 28
publication) . . . . . . . . . . . . . . . . . . . . . . . . 28 A.1 Since draft-ietf-webdav-bind-02 . . . . . . . . . . . . . 28
A.1 Since draft-ietf-webdav-bind-02 . . . . . . . . . . . . . . 28 A.2 Since draft-ietf-webdav-bind-03 . . . . . . . . . . . . . 28
A.2 Since draft-ietf-webdav-bind-03 . . . . . . . . . . . . . . 28 A.3 Since draft-ietf-webdav-bind-04 . . . . . . . . . . . . . 28
A.3 Since draft-ietf-webdav-bind-04 . . . . . . . . . . . . . . 28 A.4 Since draft-ietf-webdav-bind-05 . . . . . . . . . . . . . 28
B. Resolved issues (to be removed by RFC Editor before B. Resolved issues (to be removed by RFC Editor before
publication) . . . . . . . . . . . . . . . . . . . . . . . . 28 publication) . . . . . . . . . . . . . . . . . . . . . . . . . 29
B.1 6_precondition_binding_allowed . . . . . . . . . . . . . . . 28 B.1 4_LOCK_BEHAVIOR . . . . . . . . . . . . . . . . . . . . . 29
B.2 6_lock_behaviour . . . . . . . . . . . . . . . . . . . . . . 29 B.2 1.3_error_negotiation . . . . . . . . . . . . . . . . . . 29
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 B.3 2.5_language . . . . . . . . . . . . . . . . . . . . . . . 30
Intellectual Property and Copyright Statements . . . . . . . 32 B.4 7.1.1_add_resource_id . . . . . . . . . . . . . . . . . . 30
C. Open issues (to be removed by RFC Editor prior to
publication) . . . . . . . . . . . . . . . . . . . . . . . . . 30
C.1 edit . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Intellectual Property and Copyright Statements . . . . . . . . 33
1. Introduction 1. Introduction
This specification extends the WebDAV Distributed Authoring Protocol This specification extends the WebDAV Distributed Authoring Protocol
to enable clients to create new access paths to existing resources. to enable clients to create new access paths to existing resources.
This capability is useful for several reasons: This capability is useful for several reasons:
URIs of WebDAV-compliant resources are hierarchical and correspond to URIs of WebDAV-compliant resources are hierarchical and correspond to
a hierarchy of collections in resource space. The WebDAV Distributed a hierarchy of collections in resource space. The WebDAV Distributed
Authoring Protocol makes it possible to organize these resources into Authoring Protocol makes it possible to organize these resources into
hierarchies, placing them into groupings, known as collections, which hierarchies, placing them into groupings, known as collections, which
are more easily browsed and manipulated than a single flat are more easily browsed and manipulated than a single flat
collection. However, hierarchies require categorization decisions collection. However, hierarchies require categorization decisions
that locate resources at a single location in the hierarchy, a that locate resources at a single location in the hierarchy, a
drawback when a resource has multiple valid categories. For example, drawback when a resource has multiple valid categories. For example,
in a hierarchy of vehicle descriptions containing collections for in a hierarchy of vehicle descriptions containing collections for
cars and boats, a description of a combination car/boat vehicle could cars and boats, a description of a combination car/boat vehicle could
belong in either collection. Ideally, the description should be belong in either collection. Ideally, the description should be
accessible from both. Allowing clients to create new URIs that access accessible from both. Allowing clients to create new URIs that
the existing resource lets them put that resource into multiple access the existing resource lets them put that resource into
collections. multiple collections.
Hierarchies also make resource sharing more difficult, since Hierarchies also make resource sharing more difficult, since
resources that have utility across many collections are still forced resources that have utility across many collections are still forced
into a single collection. For example, the mathematics department at into a single collection. For example, the mathematics department at
one university might create a collection of information on fractals one university might create a collection of information on fractals
that contains bindings to some local resources, but also provides that contains bindings to some local resources, but also provides
access to some resources at other universities. For many reasons, it access to some resources at other universities. For many reasons, it
may be undesirable to make physical copies of the shared resources on may be undesirable to make physical copies of the shared resources on
the local server: to conserve disk space, to respect copyright the local server: to conserve disk space, to respect copyright
constraints, or to make any changes in the shared resources visible constraints, or to make any changes in the shared resources visible
skipping to change at page 6, line 27 skipping to change at page 6, line 27
Binding Binding
A relation between a single path segment (in a collection) and a A relation between a single path segment (in a collection) and a
resource. A binding is part of the state of a collection. If two resource. A binding is part of the state of a collection. If two
different collections contain a binding between the same path different collections contain a binding between the same path
segment and the same resource, these are two distinct bindings. segment and the same resource, these are two distinct bindings.
So for a collection C, a path segment S, and a resource R, the So for a collection C, a path segment S, and a resource R, the
binding can be thought of as C:(S -> R). Bindings create URI binding can be thought of as C:(S -> R). Bindings create URI
mappings, and hence allow requests to be sent to a single resource mappings, and hence allow requests to be sent to a single resource
from multiple locations in a URI namespace. For example, given a from multiple locations in a URI namespace. For example, given a
collection C (accessible through the URI http://www.example.com/ collection C (accessible through the URI
CollX), a path segment S (equal to "foo.html"), and a resource R, http://www.example.com/CollX), a path segment S (equal to
then creating the binding C: (S -> R) makes it possible to use the "foo.html"), and a resource R, then creating the binding C: (S ->
URI http://www.example.com/CollX/foo.html to access R. R) makes it possible to use the URI
http://www.example.com/CollX/foo.html to access R.
Collection Collection
A resource that contains, as part of its state, a set of bindings A resource that contains, as part of its state, a set of bindings
that identify internal member resources. that identify internal member resources.
Internal Member URI Internal Member URI
The URI that identifies an internal member of a collection, and The URI that identifies an internal member of a collection, and
that consists of the URI for the collection, followed by a slash that consists of the URI for the collection, followed by a slash
character ('/'), followed by the path segment of the binding for character ('/'), followed by the path segment of the binding for
that internal member. that internal member.
1.2 Rationale for Distinguishing Bindings from URI Mappings 1.2 Rationale for Distinguishing Bindings from URI Mappings
In [RFC2518], the state of a collection is defined as containing a In [RFC2518], the state of a collection is defined as containing a
list of internal member URIs. If there are multiple mappings to a list of internal member URIs. If there are multiple mappings to a
collection, then the state of the collection is different when you collection, then the state of the collection is different when you
refer to it via a different URI. This is undesirable, since ideally a refer to it via a different URI. This is undesirable, since ideally
collection's membership should remain the same, independent of which a collection's membership should remain the same, independent of
URI was used to reference it. which URI was used to reference it.
The notion of binding is introduced to separate the final segment of The notion of binding is introduced to separate the final segment of
a URI from its parent collection's contribution. This done, a a URI from its parent collection's contribution. This done, a
collection can be defined as containing a set of bindings, thus collection can be defined as containing a set of bindings, thus
permitting new mappings to a collection without modifying its permitting new mappings to a collection without modifying its
membership. The authors of this specification anticipate and membership. The authors of this specification anticipate and
recommend that future revisions of [RFC2518] will update the recommend that future revisions of [RFC2518] will update the
definition of the state of a collection to correspond to the definition of the state of a collection to correspond to the
definition in this document. definition in this document.
skipping to change at page 9, line 27 skipping to change at page 9, line 27
+------------------+ +------------------+
| \ | \
| \ | \
| \ | \
+-------------+ +-------------+ +-------------+ +-------------+
| Resource R1 | | Resource R2 | | Resource R1 | | Resource R2 |
+-------------+ +-------------+ +-------------+ +-------------+
2.2 URI Mappings Created by a new Binding 2.2 URI Mappings Created by a new Binding
Suppose a binding from "Binding-Name" to resource R to be added to a Suppose a binding from "Binding-Name" to resource R is to be added to
collection, C. Then if C-MAP is the set of URIs that were mapped to a collection, C. Then if C-MAP is the set of URIs that were mapped
C before the BIND request, then for each URI "C-URI" in C-MAP, the to C before the BIND request, then for each URI "C-URI" in C-MAP, the
URI "C-URI/Binding-Name" is mapped to resource R following the BIND URI "C-URI/Binding-Name" is mapped to resource R following the BIND
request. request.
For example, if a binding from "foo.html" to R is added to a For example, if a binding from "foo.html" to R is added to a
collection C, and if the following URIs are mapped to C: collection C, and if the following URIs are mapped to C:
http://www.example.com/A/1/ http://www.example.com/A/1/
http://example.com/A/one/ http://example.com/A/one/
then the following new mappings to R are introduced: then the following new mappings to R are introduced:
skipping to change at page 12, line 25 skipping to change at page 12, line 25
unaffected. Also, if MOVE is used with Overwrite:T to delete an unaffected. Also, if MOVE is used with Overwrite:T to delete an
existing resource, the constraints specified for DELETE apply. existing resource, the constraints specified for DELETE apply.
If the destination collection of a MOVE request supports the REBIND If the destination collection of a MOVE request supports the REBIND
method (see Section 6), a MOVE of a resource into that collection MAY method (see Section 6), a MOVE of a resource into that collection MAY
be implemented as a REBIND request. Although [RFC2518] allows a MOVE be implemented as a REBIND request. Although [RFC2518] allows a MOVE
to be a non-atomic operation, when the MOVE operation is implemented to be a non-atomic operation, when the MOVE operation is implemented
as a REBIND, the operation is atomic. In particular, applying a MOVE as a REBIND, the operation is atomic. In particular, applying a MOVE
to a Request-URI and a Destination URI has the effect of removing a to a Request-URI and a Destination URI has the effect of removing a
binding to a resource (at the Request-URI), and creating a new binding to a resource (at the Request-URI), and creating a new
binding to that resource (at the Destination URI). binding to that resource (at the Destination URI). Even when the
Request-URI identifies a collection, the MOVE operation involves only
removing one binding to that collection and adding another.
As an example, suppose that a MOVE is issued to URI-3 for resource R As an example, suppose that a MOVE is issued to URI-3 for resource R
below (which is also mapped to URI-1 and URI-2), with the Destination below (which is also mapped to URI-1 and URI-2), with the Destination
header set to URI-X. After successful completion of the MOVE header set to URI-X. After successful completion of the MOVE
operation, a new binding has been created which creates the URI operation, a new binding has been created which creates the URI
mapping between URI-X and resource R. The binding corresponding to mapping between URI-X and resource R. The binding corresponding to
the final segment of URI-3 has been removed, which also causes the the final segment of URI-3 has been removed, which also causes the
URI mapping between URI-3 and R to be removed. If resource R were a URI mapping between URI-3 and R to be removed. If resource R were a
collection, old URI-3 based mappings to members of R would have been collection, old URI-3 based mappings to members of R would have been
removed, and new URI-X based mappings to members of R would have been removed, and new URI-X based mappings to members of R would have been
skipping to change at page 13, line 14 skipping to change at page 13, line 14
>> After Request: >> After Request:
URI-1 URI-2 URI-X URI-1 URI-2 URI-X
| | | | | |
| | | <---- URI Mappings | | | <---- URI Mappings
| | | | | |
+---------------------+ +---------------------+
| Resource R | | Resource R |
+---------------------+ +---------------------+
Although [RFC2518] allows a MOVE on a collection to be a non-atomic
operation, a MOVE implemented as a REBIND MUST be atomic. Even when
the Request-URI identifies a collection, the MOVE operation involves
only removing one binding to that collection and adding another.
There are no operations on bindings to any of its children, so the
case of MOVE on a collection is the same as the case of MOVE on a
non-collection resource. Both are atomic.
2.6 Determining Whether Two Bindings Are to the Same Resource 2.6 Determining Whether Two Bindings Are to the Same Resource
It is useful to have some way of determining whether two bindings are It is useful to have some way of determining whether two bindings are
to the same resource. Two resources might have identical contents to the same resource. Two resources might have identical contents
and properties, but not be the same resource (e.g. an update to one and properties, but not be the same resource (e.g. an update to one
resource does not affect the other resource). resource does not affect the other resource).
The REQUIRED DAV:resource-id property defined in Section 3.1 is a The REQUIRED DAV:resource-id property defined in Section 3.1 is a
resource identifier, which MUST be unique across all resources for resource identifier, which MUST be unique across all resources for
all time. If the values of DAV:resource-id returned by PROPFIND all time. If the values of DAV:resource-id returned by PROPFIND
skipping to change at page 17, line 32 skipping to change at page 17, line 25
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
<D:bind xmlns:D="DAV:"> <D:bind xmlns:D="DAV:">
<D:segment>bar.html</D:segment> <D:segment>bar.html</D:segment>
<D:href>http://www.example.com/CollX/foo.html</D:href> <D:href>http://www.example.com/CollX/foo.html</D:href>
</D:bind> </D:bind>
>> Response: >> Response:
HTTP/1.1 201 Created HTTP/1.1 201 Created
The server added a new binding to the collection, "http:// The server added a new binding to the collection,
www.example.com/CollY", associating "bar.html" with the resource "http://www.example.com/CollY", associating "bar.html" with the
identified by the URI "http://www.example.com/CollX/foo.html". resource identified by the URI
Clients can now use the URI "http://www.example.com/CollY/bar.html", "http://www.example.com/CollX/foo.html". Clients can now use the URI
to submit requests to that resource. "http://www.example.com/CollY/bar.html", to submit requests to that
resource.
5. UNBIND Method 5. UNBIND Method
The UNBIND method modifies the collection identified by the The UNBIND method modifies the collection identified by the
Request-URI, by removing the binding identified by the segment Request-URI, by removing the binding identified by the segment
specified in the UNBIND body. specified in the UNBIND body.
Once a resource is unreachable by any URI mapping, the server MAY Once a resource is unreachable by any URI mapping, the server MAY
reclaim system resources associated with that resource. If UNBIND reclaim system resources associated with that resource. If UNBIND
removes a binding to a resource, but there remain URI mappings to removes a binding to a resource, but there remain URI mappings to
skipping to change at page 21, line 37 skipping to change at page 21, line 37
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
<D:rebind xmlns:D="DAV:"> <D:rebind xmlns:D="DAV:">
<D:segment>foo.html</D:segment> <D:segment>foo.html</D:segment>
<D:href>http://www.example.com/CollY/bar.html</D:href> <D:href>http://www.example.com/CollY/bar.html</D:href>
</D:rebind> </D:rebind>
>> Response: >> Response:
HTTP/1.1 200 OK HTTP/1.1 200 OK
The server added a new binding to the collection, "http:// The server added a new binding to the collection,
www.example.com/CollX", associating "foo.html" with the resource "http://www.example.com/CollX", associating "foo.html" with the
identified by the URI "http://www.example.com/CollY/bar.html", and resource identified by the URI
removes the binding named "bar.html" from the collection identified "http://www.example.com/CollY/bar.html", and removes the binding
by the URI "http://www.example.com/CollY". Clients can now use the named "bar.html" from the collection identified by the URI
URI "http://www.example.com/CollX/foo.html" to submit requests to "http://www.example.com/CollY". Clients can now use the URI "http://
that resource, and requests on the URI "http://www.example.com/CollY/ www.example.com/CollX/foo.html" to submit requests to that resource,
bar.html" will fail with a 404 (Not Found) response. and requests on the URI "http://www.example.com/CollY/bar.html" will
fail with a 404 (Not Found) response.
7. Additional Status Codes 7. Additional Status Codes
7.1 208 Already Reported 7.1 208 Already Reported
The 208 (Already Reported) status code can be used inside a The 208 (Already Reported) status code can be used inside a
DAV:propstat response element to avoid enumerating the internal DAV:propstat response element to avoid enumerating the internal
members of multiple bindings to the same collection repeatedly. For members of multiple bindings to the same collection repeatedly. For
each binding to a collection inside the request's scope, only one each binding to a collection inside the request's scope, only one
will be reported with a 200 status, while subsequent DAV:response will be reported with a 200 status, while subsequent DAV:response
skipping to change at page 22, line 23 skipping to change at page 22, line 24
A client can request the DAV:resourceid property in a PROPFIND A client can request the DAV:resourceid property in a PROPFIND
request to guarantee that they can accurately reconstruct the binding request to guarantee that they can accurately reconstruct the binding
structure of a collection with multiple bindings to a single structure of a collection with multiple bindings to a single
resource. resource.
For backward compatibility with clients not aware of the 208 status For backward compatibility with clients not aware of the 208 status
code appearing in multistatus response bodies, it SHOULD NOT be used code appearing in multistatus response bodies, it SHOULD NOT be used
unless the client has signalled support for this specification using unless the client has signalled support for this specification using
the "DAV" request header (see Section 8.2). Instead, a 506 status the "DAV" request header (see Section 8.2). Instead, a 506 status
should be returned when a binding loop is discovered. This allows the should be returned when a binding loop is discovered. This allows
server to return the 506 as the top level return status, if it the server to return the 506 as the top level return status, if it
discovers it before it started the response, or in the middle of a discovers it before it started the response, or in the middle of a
multistatus, if it discovers it in the middle of streaming out a multistatus, if it discovers it in the middle of streaming out a
multistatus response. multistatus response.
7.1.1 Example: PROPFIND by bind-aware client 7.1.1 Example: PROPFIND by bind-aware client
For example, consider a PROPFIND request on /Coll (bound to For example, consider a PROPFIND request on /Coll (bound to
collection C), where the members of /Coll are /Coll/Foo (bound to collection C), where the members of /Coll are /Coll/Foo (bound to
resource R) and /Coll/Bar (bound to collection C). resource R) and /Coll/Bar (bound to collection C).
skipping to change at page 22, line 48 skipping to change at page 22, line 49
Host: www.example.com Host: www.example.com
Depth: infinity Depth: infinity
DAV: bind DAV: bind
Content-Type: text/xml; charset="utf-8" Content-Type: text/xml; charset="utf-8"
Content-Length: xxx Content-Length: xxx
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
<D:propfind xmlns:D="DAV:"> <D:propfind xmlns:D="DAV:">
<D:prop> <D:prop>
<D:displayname/> <D:displayname/>
<D:resource-id/>
</D:prop> </D:prop>
</D:propfind> </D:propfind>
>> Response: >> Response:
HTTP/1.1 207 Multi-Status HTTP/1.1 207 Multi-Status
Content-Type: text/xml; charset="utf-8" Content-Type: text/xml; charset="utf-8"
Content-Length: xxx Content-Length: xxx
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
<D:multistatus xmlns:D="DAV:"> <D:multistatus xmlns:D="DAV:">
<D:response> <D:response>
<D:href>http://www.example.com/Coll/</D:href> <D:href>http://www.example.com/Coll/</D:href>
<D:propstat> <D:propstat>
<D:prop> <D:prop>
<D:displayname>Loop Demo</D:displayname> <D:displayname>Loop Demo</D:displayname>
<D:resource-id>
<D:href
>opaquelocktoken:f81d4fae-7dec-11d0-a765-00a0c91e6bf8</D:href>
</D:resource-id>
</D:prop> </D:prop>
<D:status>HTTP/1.1 200 OK</D:status> <D:status>HTTP/1.1 200 OK</D:status>
</D:propstat> </D:propstat>
</D:response> </D:response>
<D:response> <D:response>
<D:href>http://www.example.com/Coll/Foo</D:href> <D:href>http://www.example.com/Coll/Foo</D:href>
<D:propstat> <D:propstat>
<D:prop> <D:prop>
<D:displayname>Bird Inventory</D:displayname> <D:displayname>Bird Inventory</D:displayname>
<D:resource-id>
<D:href
>opaquelocktoken:f81d4fae-7dec-11d0-a765-00a0c91e6bf9</D:href>
</D:resource-id>
</D:prop> </D:prop>
<D:status>HTTP/1.1 200 OK</D:status> <D:status>HTTP/1.1 200 OK</D:status>
</D:propstat> </D:propstat>
</D:response> </D:response>
<D:response> <D:response>
<D:href>http://www.example.com/Coll/Bar</D:href> <D:href>http://www.example.com/Coll/Bar</D:href>
<D:propstat> <D:propstat>
<D:prop> <D:prop>
<D:displayname>Loop Demo</D:displayname> <D:displayname>Loop Demo</D:displayname>
<D:resource-id>
<D:href
>opaquelocktoken:f81d4fae-7dec-11d0-a765-00a0c91e6bf8</D:href>
</D:resource-id>
</D:prop> </D:prop>
<D:status>HTTP/1.1 208 Already Reported</D:status> <D:status>HTTP/1.1 208 Already Reported</D:status>
</D:propstat> </D:propstat>
</D:response> </D:response>
</D:multistatus> </D:multistatus>
7.1.2 Example: PROPFIND by non-bind-aware client 7.1.2 Example: PROPFIND by non-bind-aware client
In this example, the client isn't aware of the 208 status code In this example, the client isn't aware of the 208 status code
introduced by this specification. As the "Depth: infinity" PROPFIND introduced by this specification. As the "Depth: infinity" PROPFIND
skipping to change at page 24, line 36 skipping to change at page 24, line 43
processing a request with "Depth: infinity". This status indicates processing a request with "Depth: infinity". This status indicates
that the entire operation failed. that the entire operation failed.
8. Capability discovery 8. Capability discovery
8.1 OPTIONS method 8.1 OPTIONS method
If the server supports bindings, it MUST return the compliance class If the server supports bindings, it MUST return the compliance class
name "bind" as a field in the "DAV" response header (see [RFC2518], name "bind" as a field in the "DAV" response header (see [RFC2518],
section 9.1) from an OPTIONS request on any resource implemented by section 9.1) from an OPTIONS request on any resource implemented by
that server. A value of "bind" in the "DAV" header MUST indicate that that server. A value of "bind" in the "DAV" header MUST indicate
the server supports all MUST level requirements and REQUIRED features that the server supports all MUST level requirements and REQUIRED
specified in this document. features specified in this document.
8.2 'DAV' request header 8.2 'DAV' request header
8.2.1 Generic syntax 8.2.1 Generic syntax
This specification introduces the 'DAV' request header that allows This specification introduces the 'DAV' request header that allows
clients to signal compliance to specific WebDAV features. It has the clients to signal compliance to specific WebDAV features. It has the
same syntax as the response header defined in [RFC2518], section 9.1, same syntax as the response header defined in [RFC2518], section 9.1,
but MAY be used with any method. but MAY be used with any method.
Note that clients MUST NOT submit a specific compliance class name in Note that clients MUST NOT submit a specific compliance class name in
the request header unless the specification defining this compliance the request header unless the specification defining this compliance
class specifically defines it's semantics for clients. class specifically defines its semantics for clients.
Note that if a server chooses to vary the result of a request based Note that if a server chooses to vary the result of a request based
on values in the "DAV" header, the response either MUST NOT be on values in the "DAV" header, the response either MUST NOT be
cacheable or the server MUST mark the response accordingly using the cacheable or the server MUST mark the response accordingly using the
"Vary" header (see [RFC2616], section 14.44). "Vary" header (see [RFC2616], section 14.44).
8.2.2 Client compliance class 'bind' 8.2.2 Client compliance class 'bind'
Clients SHOULD signal support for all MUST level requirements and Clients SHOULD signal support for all MUST level requirements and
REQUIRED features by submitting a "DAV" request header containing the REQUIRED features by submitting a "DAV" request header containing the
skipping to change at page 26, line 33 skipping to change at page 26, line 42
All internationalization considerations mentioned in [RFC2518] also All internationalization considerations mentioned in [RFC2518] also
apply to this document. apply to this document.
11. IANA Considerations 11. IANA Considerations
All IANA considerations mentioned in [RFC2518] also apply to this All IANA considerations mentioned in [RFC2518] also apply to this
document. document.
12. Acknowledgements 12. Acknowledgements
This draft is the collaborative product of the authors and Tyson This document is the collaborative product of the authors and Tyson
Chihaya, Jim Davis, Chuck Fay and Judith Slein. This draft has Chihaya, Jim Davis, Chuck Fay and Judith Slein. This draft has
benefited from thoughtful discussion by Jim Amsden, Peter Carlson, benefited from thoughtful discussion by Jim Amsden, Peter Carlson,
Steve Carter, Ken Coar, Ellis Cohen, Dan Connolly, Bruce Cragun, Steve Carter, Ken Coar, Ellis Cohen, Dan Connolly, Bruce Cragun,
Spencer Dawkins, Mark Day, Rajiv Dulepet, David Durand, Stefan Spencer Dawkins, Mark Day, Rajiv Dulepet, David Durand, Stefan
Eissing, Roy Fielding, Yaron Goland, Fred Hitt, Alex Hopmann, James Eissing, Roy Fielding, Yaron Goland, Joe Hildebrand, Fred Hitt, Alex
Hunt, Marcus Jager, Chris Kaler, Manoj Kasichainula, Rohit Khare, Hopmann, James Hunt, Marcus Jager, Chris Kaler, Manoj Kasichainula,
Daniel LaLiberte, Steve Martin, Larry Masinter, Jeff McAffer, Rohit Khare, Brian Korver, Daniel LaLiberte Steve Martin, Larry
Surendra Koduru Reddy, Max Rible, Sam Ruby, Bradley Sergeant, Nick Masinter, Jeff McAffer, Surendra Koduru Reddy, Max Rible, Sam Ruby,
Shelness, John Stracke, John Tigue, John Turner, Kevin Wiggen, and Bradley Sergeant, Nick Shelness, John Stracke, John Tigue, John
other members of the WebDAV working group. Turner, Kevin Wiggen, and other members of the WebDAV working group.
Normative References 13 Normative References
[RFC2026] Bradner, S., "The Internet Standards Process -- Revision [RFC2026] Bradner, S., "The Internet Standards Process -- Revision
3", BCP 9, RFC 2026, October 1996. 3", BCP 9, RFC 2026, October 1996.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2396] Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform [RFC2396] Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform
Resource Identifiers (URI): Generic Syntax", RFC 2396, Resource Identifiers (URI): Generic Syntax", RFC 2396,
August 1998. August 1998.
skipping to change at page 27, line 19 skipping to change at page 27, line 27
[RFC2518] Goland, Y., Whitehead, E., Faizi, A., Carter, S. and D. [RFC2518] Goland, Y., Whitehead, E., Faizi, A., Carter, S. and D.
Jensen, "HTTP Extensions for Distributed Authoring -- Jensen, "HTTP Extensions for Distributed Authoring --
WEBDAV", RFC 2518, February 1999. WEBDAV", RFC 2518, February 1999.
[RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., [RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H.,
Masinter, L., Leach, P. and T. Berners-Lee, "Hypertext Masinter, L., Leach, P. and T. Berners-Lee, "Hypertext
Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999. Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999.
[XML] Bray, T., Paoli, J., Sperberg-McQueen, C., Maler, E. and [XML] Bray, T., Paoli, J., Sperberg-McQueen, C., Maler, E. and
F. Yergeau, "Extensible Markup Language (XML) 1.0 (Third F. Yergeau, "Extensible Markup Language (XML) 1.0 (Third
Edition)", W3C REC-xml-20040204, February 2004, <http:// Edition)", W3C REC-xml-20040204, February 2004,
www.w3.org/TR/2004/REC-xml-20040204>. <http://www.w3.org/TR/2004/REC-xml-20040204>.
[1] <mailto:w3c-dist-auth@w3.org>
[2] <mailto:w3c-dist-auth-request@w3.org?subject=subscribe>
Authors' Addresses Authors' Addresses
Geoffrey Clemm Geoffrey Clemm
IBM IBM
20 Maguire Road 20 Maguire Road
Lexington, MA 02421 Lexington, MA 02421
EMail: geoffrey.clemm@us.ibm.com EMail: geoffrey.clemm@us.ibm.com
skipping to change at page 28, line 21 skipping to change at page 28, line 29
Appendix A. Change Log (to be removed by RFC Editor before publication) Appendix A. Change Log (to be removed by RFC Editor before publication)
A.1 Since draft-ietf-webdav-bind-02 A.1 Since draft-ietf-webdav-bind-02
Add and resolve issues "2.3_COPY_SHARED_BINDINGS" and Add and resolve issues "2.3_COPY_SHARED_BINDINGS" and
"2.3_MULTIPLE_COPY". Add issue "5.1_LOOP_STATUS" and proposed "2.3_MULTIPLE_COPY". Add issue "5.1_LOOP_STATUS" and proposed
resolution, but keep it open. Add issues "ED_references" and resolution, but keep it open. Add issues "ED_references" and
"4_507_status". Started work on index. Rename document to "Binding "4_507_status". Started work on index. Rename document to "Binding
Extensions to Web Distributed Authoring and Versioning (WebDAV)". Extensions to Web Distributed Authoring and Versioning (WebDAV)".
Rename "References" to "Normative References". Close issue Rename "References" to "Normative References". Close issue
"ED_references". CLose issue "4_507_status". "ED_references". Close issue "4_507_status".
A.2 Since draft-ietf-webdav-bind-03 A.2 Since draft-ietf-webdav-bind-03
Add and close issues "9.2_redirect_loops", "ED_authors" and Add and close issues "9.2_redirect_loops", "ED_authors" and
"ED_updates". Add section about capability discovery (DAV header). "ED_updates". Add section about capability discovery (DAV header).
Close issues "5.1_LOOP_STATUS". Add and resolve new issue Close issues "5.1_LOOP_STATUS". Add and resolve new issue
"5.1_506_STATUS_STREAMING". Update XML spec reference. Add issue "5.1_506_STATUS_STREAMING". Update XML spec reference. Add issue
"locking" and resolve as invalid. "locking" and resolve as invalid.
A.3 Since draft-ietf-webdav-bind-04 A.3 Since draft-ietf-webdav-bind-04
Add and close issues "6_precondition_binding_allowed" and Add and close issues "6_precondition_binding_allowed" and
"6_lock_behaviour". Add mailing list and issues list pointers to "6_lock_behaviour". Add mailing list and issues list pointers to
front. front.
A.4 Since draft-ietf-webdav-bind-05
Editorial fixes. Add and resolve issues "1.3_error_negotiation",
"2.5_language" and "7.1.1_add_resource_id". Add historical issue
"4_LOCK_BEHAVIOR" and it's resolution for better tracking.
Appendix B. Resolved issues (to be removed by RFC Editor before Appendix B. Resolved issues (to be removed by RFC Editor before
publication) publication)
Issues that were either rejected or resolved in this version of this Issues that were either rejected or resolved in this version of this
document. document.
B.1 6_precondition_binding_allowed B.1 4_LOCK_BEHAVIOR
Type: change Type: change
<http://lists.w3.org/Archives/Public/w3c-dist-auth/2004JanMar/ <http://lists.w3.org/Archives/Public/w3c-dist-auth/2003JanMar/0200.html>
0093.html>
lisa@osafoundation.org (2004-03-17): One precondition is " briank@xythos.com (2003-02-28): Define "Resource": The term
(DAV:binding-allowed): The resource identified by the DAV:href "resource" should be defined in the draft. I imagine the definition
supports multiple bindings to it." How can this error possibly is something along the lines of "all content and all properties
occur? associated with that content (including live and dead properties),
but which does not include properties associated with URIs." Bindings
and Locks: The relationship between bindings and locks is missing
from the draft. I think the behavior of locks and the lock methods
should be fully specified in this draft. URL Properties: The
behavior of other URL properties (in addition to locks) should be
fully specified, for instance the display-name property. Move and
Delete: The spec states that move and delete are merely operations on
bindings. At the very least, this is inconsistent with 2518, but I
also think that the draft doesn't adequately address any of the
issues that come up when the server goes to "reclaim system
resources." I would expect most servers to reclaim said resources
during move and delete. Operations not Atomic: None of the
operations specified should be required to be atomic. I'd prefer
SHOULD NOT myself. This is especially true for any operation that
involves deleting collections.
Resolution (2004-03-19): Cut & Paste error (copied from BIND method). Resolution: This was closed in draft 02. Some comments: (1) It's up
Remove it. to RFC2396 and RFC2616 to define what a "resource" is. We don't
change that here. (2) There is no such thing as URL properties.
WebDAV properties are part of the state of a WebDAV/HTTP resource;
and a URI by itself is not a resource. (3) Bindings vs Locks: see
other issues. (4) MOVE and DELETE are allowed to work the same way
as in RFC2518 (except for Delete not removing all bindings). (5) The
new methods are all atomic on purpose. If a server can't implement
UNBIND on collections; that is fine. It can still implement DELETE
with the classic non-atomic behaviour.
B.2 6_lock_behaviour B.2 1.3_error_negotiation
Type: change Type: change
<http://lists.w3.org/Archives/Public/w3c-dist-auth/2004AprJun/0205.html>
<http://lists.w3.org/Archives/Public/w3c-dist-auth/2004JanMar/ joe@cursive.net (2004-06-22): Second paragraph: how might I otherwise
0093.html> negotiate? The DAV:bind header?
lisa@osafoundation.org (2004-03-17): Does REBIND destroy locks, as Resolution: No change. Summary: this is to allow future extensions
MOVE does? It shouldn't, unless there's a compelling reason for where different error marsahlling mechanisms would be used. See also
backward compatibility. http://lists.w3.org/Archives/Public/w3c-dist-auth/2004AprJun/0210.html.
Resolution (2004-03-20): REBIND behaves like MOVE (and any other B.3 2.5_language
namespace operation), thus locks are destroyed. Add postcondition
DAV:lock-deleted. Type: change
<http://lists.w3.org/Archives/Public/w3c-dist-auth/2004AprJun/0205.html>
joe@cursive.net (2004-06-22): Last paragraph is a repeat of text two
paragraphs before.
Resolution (2004-06-24): Just move the second sentence of the last
paragraph to the end of the second paragraph, and then delete the
rest of the last paragraph.
B.4 7.1.1_add_resource_id
Type: change
<http://lists.w3.org/Archives/Public/w3c-dist-auth/2004AprJun/0205.html>
joe@cursive.net (2004-06-22): I think this would be clearer if it
included D:resource-id in the request and response, so you could tell
where the loop happened. Are resource-id's likely to be costly to
return?
Resolution (2004-06-23): No, they should be cheap. Update example.
Appendix C. Open issues (to be removed by RFC Editor prior to
publication)
C.1 edit
Type: edit
julian.reschke@greenbytes.de (2004-05-30): Umbrella issue for
editorial fixes/enhancements.
Index Index
2 2
208 Already Reported (status code) 21 208 Already Reported (status code) 21
5 5
506 Loop Detected (status code) 24 506 Loop Detected (status code) 24
B B
skipping to change at page 30, line 30 skipping to change at page 31, line 30
DAV:binding-allowed (pre) 16 DAV:binding-allowed (pre) 16
DAV:binding-deleted (post) 18, 21 DAV:binding-deleted (post) 18, 21
DAV:can-overwrite (pre) 16, 20 DAV:can-overwrite (pre) 16, 20
DAV:cross-server-binding (pre) 16, 20 DAV:cross-server-binding (pre) 16, 20
DAV:cycle-allowed (pre) 16, 20 DAV:cycle-allowed (pre) 16, 20
DAV:lock-deleted (post) 18, 21 DAV:lock-deleted (post) 18, 21
DAV:locked-overwrite-allowed (pre) 16 DAV:locked-overwrite-allowed (pre) 16
DAV:locked-source-collection-update-allowed (pre) 20 DAV:locked-source-collection-update-allowed (pre) 20
DAV:locked-update-allowed (pre) 16, 18, 20 DAV:locked-update-allowed (pre) 16, 18, 20
DAV:name-allowed (pre) 16, 20 DAV:name-allowed (pre) 16, 20
DAV:new-binding (post) 17, 21 DAV:new-binding (post) 16, 21
DAV:protected-source-url-deletion-allowed (pre) 20 DAV:protected-source-url-deletion-allowed (pre) 20
DAV:protected-url-deletion-allowed (pre) 18 DAV:protected-url-deletion-allowed (pre) 18
DAV:protected-url-modification-allowed (pre) 20 DAV:protected-url-modification-allowed (pre) 20
DAV:rebind-into-collection (pre) 20 DAV:rebind-into-collection (pre) 20
DAV:rebind-source-exists (pre) 20 DAV:rebind-source-exists (pre) 20
DAV:unbind-from-collection (pre) 18 DAV:unbind-from-collection (pre) 18
DAV:unbind-source-exists (pre) 18 DAV:unbind-source-exists (pre) 18
D D
DAV header DAV header
skipping to change at page 31, line 5 skipping to change at page 32, line 5
DAV:binding-allowed precondition 16 DAV:binding-allowed precondition 16
DAV:binding-deleted postcondition 18, 21 DAV:binding-deleted postcondition 18, 21
DAV:can-overwrite precondition 16, 20 DAV:can-overwrite precondition 16, 20
DAV:cross-server-binding precondition 16, 20 DAV:cross-server-binding precondition 16, 20
DAV:cycle-allowed precondition 16, 20 DAV:cycle-allowed precondition 16, 20
DAV:lock-deleted postcondition 18, 21 DAV:lock-deleted postcondition 18, 21
DAV:locked-overwrite-allowed precondition 16 DAV:locked-overwrite-allowed precondition 16
DAV:locked-source-collection-update-allowed precondition 20 DAV:locked-source-collection-update-allowed precondition 20
DAV:locked-update-allowed precondition 16, 18, 20 DAV:locked-update-allowed precondition 16, 18, 20
DAV:name-allowed precondition 16, 20 DAV:name-allowed precondition 16, 20
DAV:new-binding postcondition 17, 21 DAV:new-binding postcondition 16, 21
DAV:parent-set property 14 DAV:parent-set property 14
DAV:protected-source-url-deletion-allowed precondition 20 DAV:protected-source-url-deletion-allowed precondition 20
DAV:protected-url-deletion-allowed precondition 18 DAV:protected-url-deletion-allowed precondition 18
DAV:protected-url-modification-allowed precondition 20 DAV:protected-url-modification-allowed precondition 20
DAV:rebind-into-collection precondition 20 DAV:rebind-into-collection precondition 20
DAV:rebind-source-exists precondition 20 DAV:rebind-source-exists precondition 20
DAV:resource-id property 14 DAV:resource-id property 14
DAV:unbind-from-collection precondition 18 DAV:unbind-from-collection precondition 18
DAV:unbind-source-exists precondition 18 DAV:unbind-source-exists precondition 18
skipping to change at page 32, line 13 skipping to change at page 33, line 13
UNBIND method 17 UNBIND method 17
Intellectual Property Statement Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the IETF's procedures with respect to rights in IETF Documents can on the procedures with respect to rights in RFC documents can be
be found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/