draft-ietf-webdav-bind-13.txt   draft-ietf-webdav-bind-14.txt 
Network Working Group G. Clemm Network Working Group G. Clemm
Internet-Draft IBM Internet-Draft IBM
Updates: J. Crawford Updates: J. Crawford
draft-ietf-webdav-rfc2518bis (if IBM Research draft-ietf-webdav-rfc2518bis (if IBM Research
approved) J. Reschke approved) J. Reschke
Expires: August 12, 2006 greenbytes Expires: August 26, 2006 greenbytes
J. Whitehead J. Whitehead
U.C. Santa Cruz U.C. Santa Cruz
February 8, 2006 February 22, 2006
Binding Extensions to Web Distributed Authoring and Versioning (WebDAV) Binding Extensions to Web Distributed Authoring and Versioning (WebDAV)
draft-ietf-webdav-bind-13 draft-ietf-webdav-bind-14
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
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 Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 39 skipping to change at page 1, line 39
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 The list of current Internet-Drafts can be accessed at
http://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 August 12, 2006. This Internet-Draft will expire on August 26, 2006.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2006). Copyright (C) The Internet Society (2006).
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 2, line 24 skipping to change at page 2, line 24
working group are archived at working group are archived at
<http://lists.w3.org/Archives/Public/w3c-dist-auth/>. <http://lists.w3.org/Archives/Public/w3c-dist-auth/>.
<http://www.webdav.org/bind/draft-ietf-webdav-bind-issues.html> lists <http://www.webdav.org/bind/draft-ietf-webdav-bind-issues.html> lists
all registered issues since draft 02. 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. Method Preconditions and Postconditions . . . . . . . . . 6
1.3. Method Preconditions and Postconditions . . . . . . . . . 7 2. Overview of Bindings . . . . . . . . . . . . . . . . . . . . . 6
2. Overview of Bindings . . . . . . . . . . . . . . . . . . . . . 7 2.1. Bindings to Collections . . . . . . . . . . . . . . . . . 7
2.1. Bindings to Collections . . . . . . . . . . . . . . . . . 8
2.1.1. Bind loops . . . . . . . . . . . . . . . . . . . . . . 8 2.1.1. Bind loops . . . . . . . . . . . . . . . . . . . . . . 8
2.2. URI Mappings Created by a new Binding . . . . . . . . . . 9 2.2. URI Mappings Created by a new Binding . . . . . . . . . . 8
2.3. COPY and Bindings . . . . . . . . . . . . . . . . . . . . 9 2.3. COPY and Bindings . . . . . . . . . . . . . . . . . . . . 9
2.3.1. Example: COPY with 'Depth: infinity' in presence 2.3.1. Example: COPY with 'Depth: infinity' in presence
of bind loops . . . . . . . . . . . . . . . . . . . . 11 of bind loops . . . . . . . . . . . . . . . . . . . . 11
2.3.2. Example: COPY with 'Depth: infinity' with multiple 2.3.2. Example: COPY with 'Depth: infinity' with multiple
bindings to a leaf resource . . . . . . . . . . . . . 13 bindings to a leaf resource . . . . . . . . . . . . . 13
2.4. DELETE and Bindings . . . . . . . . . . . . . . . . . . . 14 2.4. DELETE and Bindings . . . . . . . . . . . . . . . . . . . 14
2.5. MOVE and Bindings . . . . . . . . . . . . . . . . . . . . 14 2.5. MOVE and Bindings . . . . . . . . . . . . . . . . . . . . 14
2.6. PROPFIND and Bindings . . . . . . . . . . . . . . . . . . 15 2.6. PROPFIND and Bindings . . . . . . . . . . . . . . . . . . 15
2.7. Determining Whether Two Bindings Are to the Same 2.7. Determining Whether Two Bindings Are to the Same
Resource . . . . . . . . . . . . . . . . . . . . . . . . . 15 Resource . . . . . . . . . . . . . . . . . . . . . . . . . 15
skipping to change at page 3, line 38 skipping to change at page 3, line 37
A.2. Since draft-ietf-webdav-bind-03 . . . . . . . . . . . . . 35 A.2. Since draft-ietf-webdav-bind-03 . . . . . . . . . . . . . 35
A.3. Since draft-ietf-webdav-bind-04 . . . . . . . . . . . . . 35 A.3. Since draft-ietf-webdav-bind-04 . . . . . . . . . . . . . 35
A.4. Since draft-ietf-webdav-bind-05 . . . . . . . . . . . . . 35 A.4. Since draft-ietf-webdav-bind-05 . . . . . . . . . . . . . 35
A.5. Since draft-ietf-webdav-bind-06 . . . . . . . . . . . . . 35 A.5. Since draft-ietf-webdav-bind-06 . . . . . . . . . . . . . 35
A.6. Since draft-ietf-webdav-bind-07 . . . . . . . . . . . . . 35 A.6. Since draft-ietf-webdav-bind-07 . . . . . . . . . . . . . 35
A.7. Since draft-ietf-webdav-bind-08 . . . . . . . . . . . . . 35 A.7. Since draft-ietf-webdav-bind-08 . . . . . . . . . . . . . 35
A.8. Since draft-ietf-webdav-bind-09 . . . . . . . . . . . . . 36 A.8. Since draft-ietf-webdav-bind-09 . . . . . . . . . . . . . 36
A.9. Since draft-ietf-webdav-bind-10 . . . . . . . . . . . . . 36 A.9. Since draft-ietf-webdav-bind-10 . . . . . . . . . . . . . 36
A.10. Since draft-ietf-webdav-bind-11 . . . . . . . . . . . . . 36 A.10. Since draft-ietf-webdav-bind-11 . . . . . . . . . . . . . 36
A.11. Since draft-ietf-webdav-bind-12 . . . . . . . . . . . . . 36 A.11. Since draft-ietf-webdav-bind-12 . . . . . . . . . . . . . 36
A.12. Since draft-ietf-webdav-bind-13 . . . . . . . . . . . . . 36
Appendix B. Resolved issues (to be removed by RFC Editor Appendix B. Resolved issues (to be removed by RFC Editor
before publication) . . . . . . . . . . . . . . . . . 36 before publication) . . . . . . . . . . . . . . . . . 37
B.1. ED_updates . . . . . . . . . . . . . . . . . . . . . . . . 37 B.1. webdav-rev . . . . . . . . . . . . . . . . . . . . . . . . 37
Appendix C. Open issues (to be removed by RFC Editor prior to Appendix C. Open issues (to be removed by RFC Editor prior to
publication) . . . . . . . . . . . . . . . . . . . . 37 publication) . . . . . . . . . . . . . . . . . . . . 37
C.1. edit . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 C.1. edit . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
C.2. webdav-rev . . . . . . . . . . . . . . . . . . . . . . . . 37 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 40
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 41 Intellectual Property and Copyright Statements . . . . . . . . . . 41
Intellectual Property and Copyright Statements . . . . . . . . . . 42
1. Introduction 1. Introduction
This specification extends the WebDAV Distributed Authoring Protocol This specification extends the WebDAV Distributed Authoring Protocol
([draft-ietf-webdav-rfc2518bis]) to enable clients to create new ([draft-ietf-webdav-rfc2518bis]) to enable clients to create new
access paths to existing resources. This capability is useful for access paths to existing resources. This capability is useful for
several reasons: 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
skipping to change at page 6, line 38 skipping to change at page 6, line 38
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. Method Preconditions and Postconditions
In [draft-ietf-webdav-rfc2518bis], the definition of collection state
has been partly updated so that it doesn't depend on the access URL
anymore. However, there are some more changes needed in the
subsequent paragraphs to complete this change. The authors of this
specification recommend updating paragraphs 2, 3 and 4 of Section 5.2
of [draft-ietf-webdav-rfc2518bis] to read:
A collection MUST contain at most one mapping for a given path
segment, i.e., it is illegal to have the same path segment mapped
to more than one resource. Properties defined on collections
behave exactly as do properties on non-collection resources.
For all WebDAV compliant resources A and B, identified by URLs "U"
and "V" respectively, such that "V" is equal to "U/SEGMENT", A
MUST be a collection that contains a mapping from "SEGMENT" to B.
So, if resource B with URL "http://example.com/bar/blah" is WebDAV
compliant and if resource A with URL "http://example.com/bar/" is
WebDAV compliant, then resource A must be a collection and must
contain a mapping from "blah" to B.
Collection resources MAY have mappings to non-WebDAV compliant
resources in the HTTP URL namespace hierarchy but are not required
to do so. For example, if the resource X with URL
"http://example.com/bar/blah" is not WebDAV compliant and the
resource A with "URL http://example.com/bar/" identifies a
collection, then A may or may not have a mapping from "blah" to X.
(See also
<http://ietf.cse.ucsc.edu:8080/bugzilla/show_bug.cgi?id=227#c5>).
1.3. Method Preconditions and Postconditions
See Section 16 of [draft-ietf-webdav-rfc2518bis] for the definitions See Section 16 of [draft-ietf-webdav-rfc2518bis] for the definitions
of "precondition" and "postcondition". of "precondition" and "postcondition".
2. Overview of Bindings 2. Overview of Bindings
Bindings are part of the state of a collection. They define the Bindings are part of the state of a collection. They define the
internal members of the collection, and the names of those internal internal members of the collection, and the names of those internal
members. members.
skipping to change at page 19, line 16 skipping to change at page 19, line 16
destroy the resource while A's binding exists. Otherwise server B destroy the resource while A's binding exists. Otherwise server B
may receive a DELETE request that it thinks removes the last binding may receive a DELETE request that it thinks removes the last binding
to the resource and destroy the resource while A's binding still to the resource and destroy the resource while A's binding still
exists. The precondition DAV:cross-server-binding is defined below exists. The precondition DAV:cross-server-binding is defined below
for cases where servers fail cross-server BIND requests because they for cases where servers fail cross-server BIND requests because they
cannot guarantee the integrity of cross-server bindings. cannot guarantee the integrity of cross-server bindings.
By default, if there already is a binding for the specified segment By default, if there already is a binding for the specified segment
in the collection, the new binding replaces the existing binding. in the collection, the new binding replaces the existing binding.
This default binding replacement behavior can be overridden using the This default binding replacement behavior can be overridden using the
Overwrite header defined in Section 9.6 of Overwrite header defined in Section 10.6 of
[draft-ietf-webdav-rfc2518bis]. [draft-ietf-webdav-rfc2518bis].
If a BIND request fails, the server state preceding the request MUST If a BIND request fails, the server state preceding the request MUST
be restored. This method is unsafe and idempotent (see [RFC2616], be restored. This method is unsafe and idempotent (see [RFC2616],
Section 9.1). Section 9.1).
Marshalling: Marshalling:
The request MAY include an Overwrite header. The request MAY include an Overwrite header.
skipping to change at page 21, line 11 skipping to change at page 21, line 11
the segment specified in the DAV:segment element in the request the segment specified in the DAV:segment element in the request
body, to the resource identified by the DAV:href element in the body, to the resource identified by the DAV:href element in the
request body. request body.
4.1. Example: BIND 4.1. Example: BIND
>> Request: >> Request:
BIND /CollY HTTP/1.1 BIND /CollY HTTP/1.1
Host: www.example.com Host: www.example.com
Content-Type: text/xml; charset="utf-8" Content-Type: application/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: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:
skipping to change at page 23, line 11 skipping to change at page 23, line 11
specified by the Request-URI and the DAV:segment element in the specified by the Request-URI and the DAV:segment element in the
request body was protected by a write-lock at the time of the request body was protected by a write-lock at the time of the
request, that write-lock must have been deleted by the request. request, that write-lock must have been deleted by the request.
5.1. Example: UNBIND 5.1. Example: UNBIND
>> Request: >> Request:
UNBIND /CollX HTTP/1.1 UNBIND /CollX HTTP/1.1
Host: www.example.com Host: www.example.com
Content-Type: text/xml; charset="utf-8" Content-Type: application/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:unbind xmlns:D="DAV:"> <D:unbind xmlns:D="DAV:">
<D:segment>foo.html</D:segment> <D:segment>foo.html</D:segment>
</D:unbind> </D:unbind>
>> Response: >> Response:
HTTP/1.1 200 OK HTTP/1.1 200 OK
skipping to change at page 25, line 30 skipping to change at page 25, line 30
in the request body was protected by a write-lock at the time of in the request body was protected by a write-lock at the time of
the request, that write-lock must have been deleted by the the request, that write-lock must have been deleted by the
request. request.
6.1. Example: REBIND 6.1. Example: REBIND
>> Request: >> Request:
REBIND /CollX HTTP/1.1 REBIND /CollX HTTP/1.1
Host: www.example.com Host: www.example.com
Content-Type: text/xml; charset="utf-8" Content-Type: application/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: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:
skipping to change at page 27, line 11 skipping to change at page 27, line 11
Note that the binding between CollZ and C1 creates a loop in the Note that the binding between CollZ and C1 creates a loop in the
containment hierarchy. Servers are not required to support such containment hierarchy. Servers are not required to support such
loops, though the server in this example does. loops, though the server in this example does.
The REBIND request below will remove the segment "CollZ" from C3 and The REBIND request below will remove the segment "CollZ" from C3 and
add a new binding from "CollA" to the collection C2. add a new binding from "CollA" to the collection C2.
REBIND /CollW/CollX HTTP/1.1 REBIND /CollW/CollX HTTP/1.1
Host: www.example.com Host: www.example.com
If: (<opaquelocktoken:f92d4fae-7012-11ab-a765-00c0ca1f6bf9>) If: (<opaquelocktoken:f92d4fae-7012-11ab-a765-00c0ca1f6bf9>)
Content-Type: text/xml; charset="utf-8" Content-Type: application/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:rebind xmlns:D="DAV:"> <D:rebind xmlns:D="DAV:">
<D:segment>CollA</D:segment> <D:segment>CollA</D:segment>
<D:href>/CollW/CollY/CollZ</D:href> <D:href>/CollW/CollY/CollZ</D:href>
</D:rebind> </D:rebind>
The outcome of the REBIND operation is: The outcome of the REBIND operation is:
+------------------+ +------------------+
skipping to change at page 29, line 36 skipping to change at page 29, line 36
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).
>> Request: >> Request:
PROPFIND /Coll/ HTTP/1.1 PROPFIND /Coll/ HTTP/1.1
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: application/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: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: application/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:resource-id>
skipping to change at page 31, line 17 skipping to change at page 31, line 17
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
request would cause a loop condition, the whole request is rejected request would cause a loop condition, the whole request is rejected
with a 506 status. with a 506 status.
>> Request: >> Request:
PROPFIND /Coll/ HTTP/1.1 PROPFIND /Coll/ HTTP/1.1
Host: www.example.com Host: www.example.com
Depth: infinity Depth: infinity
Content-Type: text/xml; charset="utf-8" Content-Type: application/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:displayname/> </D:prop> <D:prop> <D:displayname/> </D:prop>
</D:propfind> </D:propfind>
>> Response: >> Response:
HTTP/1.1 506 Loop Detected HTTP/1.1 506 Loop Detected
skipping to change at page 33, line 28 skipping to change at page 33, line 28
hostile attempts to make it devote resources to adding bindings to hostile attempts to make it devote resources to adding bindings to
the list. the list.
11. Internationalization Considerations 11. Internationalization Considerations
All internationalization considerations mentioned in All internationalization considerations mentioned in
[draft-ietf-webdav-rfc2518bis] also apply to this document. [draft-ietf-webdav-rfc2518bis] also apply to this document.
12. IANA Considerations 12. IANA Considerations
All IANA considerations mentioned in [draft-ietf-webdav-rfc2518bis] There are no IANA considerations related to this specification.
also apply to this document.
13. Acknowledgements 13. Acknowledgements
This document 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, Lisa Spencer Dawkins, Mark Day, Rajiv Dulepet, David Durand, Lisa
Dusseault, Stefan Eissing, Roy Fielding, Yaron Goland, Joe Dusseault, Stefan Eissing, Roy Fielding, Yaron Goland, Joe
Hildebrand, Fred Hitt, Alex Hopmann, James Hunt, Marcus Jager, Chris Hildebrand, Fred Hitt, Alex Hopmann, James Hunt, Marcus Jager, Chris
skipping to change at page 34, line 26 skipping to change at page 34, line 26
RFC 3986, January 2005. RFC 3986, January 2005.
[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, Edition)", W3C REC-xml-20040204, February 2004,
<http://www.w3.org/TR/2004/REC-xml-20040204>. <http://www.w3.org/TR/2004/REC-xml-20040204>.
[draft-ietf-webdav-rfc2518bis] [draft-ietf-webdav-rfc2518bis]
Dusseault, L., Ed., "HTTP Extensions for Distributed Dusseault, L., Ed., "HTTP Extensions for Distributed
Authoring - WebDAV RFC2518 bis", Authoring - WebDAV RFC2518 bis",
draft-ietf-webdav-rfc2518bis-12 (work in progress), draft-ietf-webdav-rfc2518bis-14 (work in progress),
February 2006, <http://greenbytes.de/tech/webdav/ February 2006, <http://greenbytes.de/tech/webdav/
draft-ietf-webdav-rfc2518bis-12.html>. draft-ietf-webdav-rfc2518bis-14.html>.
14.2. Informative References 14.2. Informative References
[RFC3253] Clemm, G., Amsden, J., Ellison, T., Kaler, C., and J. [RFC3253] Clemm, G., Amsden, J., Ellison, T., Kaler, C., and J.
Whitehead, "Versioning Extensions to WebDAV (Web Whitehead, "Versioning Extensions to WebDAV (Web
Distributed Authoring and Versioning)", RFC 3253, Distributed Authoring and Versioning)", RFC 3253,
March 2002. March 2002.
[RFC3744] Clemm, G., Reschke, J., Sedlar, E., and J. Whitehead, "Web [RFC3744] Clemm, G., Reschke, J., Sedlar, E., and J. Whitehead, "Web
Distributed Authoring and Versioning (WebDAV) Access Distributed Authoring and Versioning (WebDAV) Access
skipping to change at page 36, line 42 skipping to change at page 36, line 42
o Remove own explanation of DTD syntax. o Remove own explanation of DTD syntax.
o Remove own definition of precondition/postcondition. o Remove own definition of precondition/postcondition.
o Remove reference to broken RFC2518 language about DELETE and o Remove reference to broken RFC2518 language about DELETE and
UNLOCK. UNLOCK.
o Remove own definition of DAV: request header. o Remove own definition of DAV: request header.
o Updated Section 1.2 to reflect the changes in o Updated "Rationale for Distinguishing Bindings from URI Mappings"
[draft-ietf-webdav-rfc2518bis], making proposals for more changes to reflect the changes in [draft-ietf-webdav-rfc2518bis], making
so that the issue can be closed (see also proposals for more changes so that the issue can be closed (see
<http://ietf.cse.ucsc.edu:8080/bugzilla/show_bug.cgi?id=227> and < also <http://ietf.cse.ucsc.edu:8080/bugzilla/show_bug.cgi?id=227>
http://greenbytes.de/tech/webdav/ and <http://greenbytes.de/tech/webdav/
draft-ietf-webdav-rfc2518bis-12.html#rfc.section.5.2>). draft-ietf-webdav-rfc2518bis-12.html#rfc.section.5.2>).
A.12. Since draft-ietf-webdav-bind-13
Update [draft-ietf-webdav-rfc2518-bis] to draft 14. Update one
incorrect section reference. Remove Section "Rationale for
Distinguishing Bindings from URI Mappings" as
[draft-ietf-webdav-rfc2518-bis] now uses the proper definition of
collection state. Examples use application/xml instead of text/xml
MIME type.
Fix IANA section (there are no IANA considerations).
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. ED_updates B.1. webdav-rev
Type: edit Type: edit
<http://lists.w3.org/Archives/Public/w3c-dist-auth/2003OctDec/ julian.reschke@greenbytes.de (2006-01-30): Update from RFC2518 to
0306.html> RFC2518bis.
julian.reschke@greenbytes.de (2003-12-30): Shouldn't the BIND spec be
labelled as "updating" RFC2518 and/or RFC3253?
julian.reschke@greenbytes.de (2004-01-05): It seems that there was
consensus to say that BIND does update RFC2518, while there's no
consensus about the relationship to RFC3253. As this is a minor
editorial question, I propose to just say "updated 2518" and to close
the issue.
Resolution (2006-02-07): Previously: State "updates 2518". Changed Resolution (2006-02-21): Removed own explanation of DTD syntax,
to: "updated draft-ietf-webdav-rfc2518bis". removed own definition of precondition/postcondition, removed
reference to broken RFC2518 language about DELETE and UNLOCK, removed
own definition of DAV: request header, updated examples to use
application/xml instead of text/xml MIME type, removed "Rationale for
Distinguishing Bindings from URI Mappings" to reflect the changes in
draft-ietf-webdav-rfc2518bis-14.
Appendix C. Open issues (to be removed by RFC Editor prior to Appendix C. Open issues (to be removed by RFC Editor prior to
publication) publication)
C.1. edit C.1. edit
Type: edit Type: edit
julian.reschke@greenbytes.de (2004-05-30): Umbrella issue for julian.reschke@greenbytes.de (2004-05-30): Umbrella issue for
editorial fixes/enhancements. editorial fixes/enhancements.
C.2. webdav-rev
Type: edit
julian.reschke@greenbytes.de (2006-01-30): Update from RFC2518 to
RFC2518bis.
Resolution (2006-02-07): Partly resolved: removed own explanation of
DTD syntax, removed own definition of precondition/postcondition,
removed reference to broken RFC2518 language about DELETE and UNLOCK,
removed own definition of DAV: request header, updated "Rationale for
Distinguishing Bindings from URI Mappings" to reflect the changes in
draft-ietf-webdav-rfc2518bis-12, making proposals for more changes so
that the issue can be closed (see also
<http://ietf.cse.ucsc.edu:8080/bugzilla/show_bug.cgi?id=227> and <htt
p://greenbytes.de/tech/webdav/
draft-ietf-webdav-rfc2518bis-12.html#rfc.section.5.2">).
Index Index
2 2
208 Already Reported (status code) 28 208 Already Reported (status code) 28
5 5
506 Loop Detected (status code) 31 506 Loop Detected (status code) 31
B B
BIND method 18 BIND method 18
 End of changes. 28 change blocks. 
97 lines changed or deleted 53 lines changed or added

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