draft-ietf-vcarddav-webdav-mkcol-06.txt   rfc5689.txt 
Network Working Group C. Daboo Network Working Group C. Daboo
Internet-Draft Apple Inc. Request for Comments: 5689 Apple Inc.
Updates: 4791, 4918 August 18, 2009 Updates: 4791, 4918 September 2009
(if approved) Category: Standards Track
Intended status: Standards Track
Expires: February 19, 2010
Extended MKCOL for WebDAV
draft-ietf-vcarddav-webdav-mkcol-06
Status of This Memo
This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. This document may contain material
from IETF Documents or IETF Contributions published or made publicly
available before November 10, 2008. The person(s) controlling the
copyright in some of this material may not have granted the IETF
Trust the right to allow modifications of such material outside the
IETF Standards Process. Without obtaining an adequate license from
the person(s) controlling the copyright in such materials, this
document may not be modified outside the IETF Standards Process, and
derivative works of it may not be created outside the IETF Standards
Process, except to format it for publication as an RFC or to
translate it into languages other than English.
Internet-Drafts are working documents of the Internet Engineering Extended MKCOL for Web Distributed Authoring and Versioning (WebDAV)
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Abstract
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at This specification extends the Web Distributed Authoring and
http://www.ietf.org/ietf/1id-abstracts.txt. Versioning (WebDAV) MKCOL (Make Collection) method to allow
collections of arbitrary resourcetype to be created and to allow
properties to be set at the same time.
The list of Internet-Draft Shadow Directories can be accessed at Status of This Memo
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on February 19, 2010. This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of Provisions Relating to IETF Documents
publication of this document (http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info) in effect on the date of
Please review these documents carefully, as they describe your rights publication of this document. Please review these documents
and restrictions with respect to this document. carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the BSD License.
Abstract This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
This specification extends the Web Distributed Authoring and RFC 5689 Extended MKCOL for WebDAV September 2009
Versioning (WebDAV) MKCOL ("Make Collection") method to allow
collections of arbitrary resourcetype to be created and to allow not be created outside the IETF Standards Process, except to format
properties to be set at the same time. it for publication as an RFC or to translate it into languages other
than English.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Conventions Used in This Document . . . . . . . . . . . . . . 3 2. Conventions Used in This Document . . . . . . . . . . . . . . 3
3. WebDAV Extended MKCOL . . . . . . . . . . . . . . . . . . . . 4 3. WebDAV Extended MKCOL . . . . . . . . . . . . . . . . . . . . 4
3.1. Extended MKCOL Support . . . . . . . . . . . . . . . . . . 4 3.1. Extended MKCOL Support . . . . . . . . . . . . . . . . . . 5
3.1.1. Example: Using OPTIONS for the Discovery of 3.1.1. Example: Using OPTIONS for the Discovery of
Support for Extended MKCOL . . . . . . . . . . . . . . 5 Support for Extended MKCOL . . . . . . . . . . . . . . 5
3.2. Status Codes . . . . . . . . . . . . . . . . . . . . . . . 5 3.2. Status Codes . . . . . . . . . . . . . . . . . . . . . . . 5
3.3. Additional Precondition for Extended MKCOL . . . . . . . . 5 3.3. Additional Precondition for Extended MKCOL . . . . . . . . 5
3.4. Example: Successful Extended MKCOL Request . . . . . . . . 5 3.4. Example: Successful Extended MKCOL Request . . . . . . . . 6
3.5. Example: Unsuccessful Extended MKCOL Request . . . . . . . 6 3.5. Example: Unsuccessful Extended MKCOL Request . . . . . . . 6
4. Using Extended MKCOL as an Alternative for MKxxx Methods . . . 8 4. Using Extended MKCOL as an Alternative for MKxxx Methods . . . 8
4.1. MKCALENDAR alternative . . . . . . . . . . . . . . . . . . 8 4.1. MKCALENDAR Alternative . . . . . . . . . . . . . . . . . . 8
4.1.1. Example: Using MKCOL instead of MKCALENDAR . . . . . . 8 4.1.1. Example: Using MKCOL Instead of MKCALENDAR . . . . . . 8
5. XML Element Definitions . . . . . . . . . . . . . . . . . . . 10 5. XML Element Definitions . . . . . . . . . . . . . . . . . . . 10
5.1. mkcol XML Element . . . . . . . . . . . . . . . . . . . . 10 5.1. mkcol XML Element . . . . . . . . . . . . . . . . . . . . 10
5.2. mkcol-response XML Element . . . . . . . . . . . . . . . . 10 5.2. mkcol-response XML Element . . . . . . . . . . . . . . . . 10
6. Security Considerations . . . . . . . . . . . . . . . . . . . 11 6. Security Considerations . . . . . . . . . . . . . . . . . . . 11
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 11
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 11 8. Normative References . . . . . . . . . . . . . . . . . . . . . 11
9. Normative References . . . . . . . . . . . . . . . . . . . . . 11
Appendix A. Change History (to be removed prior to RFC 5689 Extended MKCOL for WebDAV September 2009
publication as an RFC) . . . . . . . . . . . . . . . 12
1. Introduction 1. Introduction
WebDAV [RFC4918] defines the HTTP [RFC2616] method MKCOL. This WebDAV [RFC4918] defines the HTTP [RFC2616] method MKCOL. This
method is used to create WebDAV collections on the server. However, method is used to create WebDAV collections on the server. However,
several WebDAV-based specifications (e.g., CalDAV [RFC4791]) define several WebDAV-based specifications (e.g., CalDAV [RFC4791]) define
"special" collections - ones which are identified by additional "special" collections -- ones that are identified by additional
values in the DAV:resourcetype property assigned to the collection values in the DAV:resourcetype property assigned to the collection
resource, or through other means. These "special" collections are resource or by other means. These "special" collections are created
created by new methods (e.g., MKCALENDAR). The addition of a new by new methods (e.g., MKCALENDAR). The addition of a new MKxxx
MKxxx method for each new "special" collection adds to server method for each new "special" collection adds to server complexity
complexity and is detrimental to overall reliability due to the need and is detrimental to overall reliability due to the need to make
to make sure intermediaries are aware of these methods. sure intermediaries are aware of these methods.
This specification defines an extension to the WebDAV MKCOL method This specification defines an extension to the WebDAV MKCOL method
that adds a request body allowing a client to specify WebDAV that adds a request body allowing a client to specify WebDAV
properties to be set on the newly created collection or resource. In properties to be set on the newly created collection or resource. In
particular, the DAV:resourcetype property can be used to create a particular, the DAV:resourcetype property can be used to create a
"special" collection, or other properties used to create a "special" "special" collection; alternatively, other properties can be used to
resource. This avoids the need to invent new MKxxx methods. create a "special" resource. This avoids the need to invent new
MKxxx methods.
2. Conventions Used in This Document 2. Conventions Used in This Document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
This document uses XML DTD fragments ([W3C.REC-xml-20081126], Section This document uses XML DTD fragments (Section 3.2 of
3.2) as a purely notational convention. WebDAV request and response [W3C.REC-xml-20081126]) as a purely notational convention. WebDAV
bodies cannot be validated by a DTD due to the specific extensibility request and response bodies cannot be validated by a DTD due to the
rules defined in Section 17 of [RFC4918] and due to the fact that all specific extensibility rules defined in Section 17 of [RFC4918] and
XML elements defined by this specification use the XML namespace name due to the fact that all XML elements defined by this specification
"DAV:". In particular: use the XML namespace name "DAV:". In particular:
1. element names use the "DAV:" namespace, 1. Element names use the "DAV:" namespace.
2. element ordering is irrelevant unless explicitly stated, 2. Element ordering is irrelevant unless explicitly stated.
3. extension elements (elements not already defined as valid child 3. Extension elements (elements not already defined as valid child
elements) may be added anywhere, except when explicitly stated elements) may be added anywhere, except when explicitly stated
otherwise, otherwise.
4. extension attributes (attributes not already defined as valid for 4. Extension attributes (attributes not already defined as valid for
this element) may be added anywhere, except when explicitly this element) may be added anywhere, except when explicitly
stated otherwise. stated otherwise.
RFC 5689 Extended MKCOL for WebDAV September 2009
When an XML element type in the "DAV:" namespace is referenced in When an XML element type in the "DAV:" namespace is referenced in
this document outside of the context of an XML fragment, the string this document outside of the context of an XML fragment, the string
"DAV:" will be prefixed to the element type. "DAV:" will be prefixed to the element type.
This document inherits, and sometimes extends, DTD productions from This document inherits, and sometimes extends, DTD productions from
Section 14 of [RFC4918]. Section 14 of [RFC4918].
3. WebDAV Extended MKCOL 3. WebDAV Extended MKCOL
The WebDAV MKCOL request is extended to allow the inclusion of a The WebDAV MKCOL request is extended to allow the inclusion of a
skipping to change at page 4, line 23 skipping to change at page 4, line 29
request header MUST be set appropriately for an XML body (e.g., set request header MUST be set appropriately for an XML body (e.g., set
to "text/xml" or "application/xml"). XML-typed bodies for an MKCOL to "text/xml" or "application/xml"). XML-typed bodies for an MKCOL
request that do not have DAV:mkcol as the root element are reserved request that do not have DAV:mkcol as the root element are reserved
for future usage. for future usage.
One or more DAV:set XML elements may be included in the DAV:mkcol XML One or more DAV:set XML elements may be included in the DAV:mkcol XML
element to allow setting properties on the collection as it is element to allow setting properties on the collection as it is
created. In particular, to create a collection of a particular type, created. In particular, to create a collection of a particular type,
the DAV:resourcetype XML element MUST be included in a DAV:set XML the DAV:resourcetype XML element MUST be included in a DAV:set XML
element and MUST specify the expected resource type elements for the element and MUST specify the expected resource type elements for the
new resource, that MUST include the DAV:collection element that needs new resource, which MUST include the DAV:collection element that
to be present for any WebDAV collection. needs to be present for any WebDAV collection.
As per the PROPPATCH method ([RFC4918], Section 9.2), servers MUST As per the PROPPATCH method (Section 9.2 of [RFC4918]), servers MUST
process any DAV:set instructions in document order (an exception to process any DAV:set instructions in document order (an exception to
the normal rule that ordering is irrelevant). If any one instruction the normal rule that ordering is irrelevant). If any one instruction
fails to execute successfully, all instructions MUST fail (i.e., fails to execute successfully, all instructions MUST fail (i.e.,
either all succeed or all fail). Thus, if any error occurs during either all succeed or all fail). Thus, if any error occurs during
processing, all executed instructions MUST be undone and a proper processing, all executed instructions MUST be undone and a proper
error result returned. Failure to set a property value on the error result returned. Failure to set a property value on the
collection MUST result in a failure of the overall MKCOL request - collection MUST result in a failure of the overall MKCOL request --
i.e. the collection is not created. i.e., the collection is not created.
The response to an extended MKCOL request MUST be an XML document The response to an extended MKCOL request MUST be an XML document
containing a single DAV:mkcol-response XML element, which MUST containing a single DAV:mkcol-response XML element, which MUST
contain DAV:propstat XML elements with the status of each property contain DAV:propstat XML elements with the status of each property
when the request fails due to a failure to set one or more of the when the request fails due to a failure to set one or more of the
properties specified in the request body. The server MAY return a properties specified in the request body. The server MAY return a
response body in the case where the request is successful, indicating response body in the case where the request is successful, indicating
success for setting each property specified in the request body. success for setting each property specified in the request body.
When an empty response body is returned with a success request status When an empty response body is returned with a success request status
code, the client can assume that all properties were set. code, the client can assume that all properties were set.
In all other respects the behavior of the extended MKCOL request In all other respects, the behavior of the extended MKCOL request
follows that of the standard MKCOL request. follows that of the standard MKCOL request.
RFC 5689 Extended MKCOL for WebDAV September 2009
3.1. Extended MKCOL Support 3.1. Extended MKCOL Support
A server supporting the features described in this document, MUST A server supporting the features described in this document MUST
include "extended-mkcol" as a field in the DAV response header from include "extended-mkcol" as a field in the DAV response header from
an OPTIONS request on any URI that supports use of the extended MKCOL an OPTIONS request on any URI that supports use of the extended MKCOL
method. method.
3.1.1. Example: Using OPTIONS for the Discovery of Support for Extended 3.1.1. Example: Using OPTIONS for the Discovery of Support for Extended
MKCOL MKCOL
>> Request << >> Request <<
OPTIONS /addressbooks/users/ HTTP/1.1 OPTIONS /addressbooks/users/ HTTP/1.1
skipping to change at page 5, line 43 skipping to change at page 6, line 5
Name: valid-resourcetype Name: valid-resourcetype
Namespace: DAV: Namespace: DAV:
Use with: Typically 403 (Forbidden) Use with: Typically 403 (Forbidden)
Purpose: (precondition) -- The server MUST support the specified Purpose: (precondition) -- The server MUST support the specified
resourcetype value for the specified collection. resourcetype value for the specified collection.
RFC 5689 Extended MKCOL for WebDAV September 2009
3.4. Example: Successful Extended MKCOL Request 3.4. Example: Successful Extended MKCOL Request
This example shows how the extended MKCOL request is used to create a This example shows how the extended MKCOL request is used to create a
collection of a fictitious type "special-resource". The response collection of a fictitious type "special-resource". The response
body is empty as the request completed successfully. body is empty as the request completed successfully.
>> Request << >> Request <<
MKCOL /home/special/ HTTP/1.1 MKCOL /home/special/ HTTP/1.1
Host: special.example.com Host: special.example.com
skipping to change at page 7, line 5 skipping to change at page 7, line 5
Cache-Control: no-cache Cache-Control: no-cache
Date: Sat, 11 Nov 2006 09:32:12 GMT Date: Sat, 11 Nov 2006 09:32:12 GMT
3.5. Example: Unsuccessful Extended MKCOL Request 3.5. Example: Unsuccessful Extended MKCOL Request
This example shows an attempt to use the extended MKCOL request to This example shows an attempt to use the extended MKCOL request to
create a collection of a fictitious type "special-resource", which is create a collection of a fictitious type "special-resource", which is
not actually supported by the server. The response body shows that not actually supported by the server. The response body shows that
an error occurred specifically with the DAV:resourcetype property. an error occurred specifically with the DAV:resourcetype property.
RFC 5689 Extended MKCOL for WebDAV September 2009
>> Request << >> Request <<
MKCOL /home/special/ HTTP/1.1 MKCOL /home/special/ HTTP/1.1
Host: special.example.com Host: special.example.com
Content-Type: application/xml; charset="utf-8" Content-Type: application/xml; charset="utf-8"
Content-Length: xxxx Content-Length: xxxx
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
<D:mkcol xmlns:D="DAV:" <D:mkcol xmlns:D="DAV:"
xmlns:E="http://example.com/ns/"> xmlns:E="http://example.com/ns/">
skipping to change at page 8, line 5 skipping to change at page 8, line 5
supported by this server</D:responsedescription> supported by this server</D:responsedescription>
</D:propstat> </D:propstat>
<D:propstat> <D:propstat>
<D:prop> <D:prop>
<D:displayname/> <D:displayname/>
</D:prop> </D:prop>
<D:status>HTTP/1.1 424 Failed Dependency</D:status> <D:status>HTTP/1.1 424 Failed Dependency</D:status>
</D:propstat> </D:propstat>
</D:mkcol-response> </D:mkcol-response>
RFC 5689 Extended MKCOL for WebDAV September 2009
4. Using Extended MKCOL as an Alternative for MKxxx Methods 4. Using Extended MKCOL as an Alternative for MKxxx Methods
One of the goals of this extension is to eliminate the need for other One of the goals of this extension is to eliminate the need for other
extensions to define their own variant of MKCOL to create the special extensions to define their own variant of MKCOL to create the special
collections they need. This extension can be used as an alternative collections they need. This extension can be used as an alternative
to existing MKxxx methods in other extensions as detailed below. If to existing MKxxx methods in other extensions as detailed below. If
a server supports this extension and the other extension listed, then a server supports this extension and the other extension listed, then
the server MUST support use of the extended MKCOL method to achieve the server MUST support use of the extended MKCOL method to achieve
the same result as the MKxxx method of the other extension. the same result as the MKxxx method of the other extension.
4.1. MKCALENDAR alternative 4.1. MKCALENDAR Alternative
CalDAV defines the MKCALENDAR method to create a calendar collection CalDAV defines the MKCALENDAR method to create a calendar collection
as well as set properties during creation ([RFC4791], Section 5.3.1). as well as to set properties during creation (Section 5.3.1 of
[RFC4791]).
The extended MKCOL method can be used instead by specifying both DAV: The extended MKCOL method can be used instead by specifying both DAV:
collection and CALDAV:calendar-collection XML elements in the DAV: collection and CALDAV:calendar-collection XML elements in the DAV:
resourcetype property, set during the extended MKCOL request. resourcetype property, set during the extended MKCOL request.
4.1.1. Example: Using MKCOL instead of MKCALENDAR 4.1.1. Example: Using MKCOL Instead of MKCALENDAR
The first example below shows an MKCALENDAR request containing a The first example below shows an MKCALENDAR request containing a
CALDAV:mkcalendar XML element in the request body, and returning a CALDAV:mkcalendar XML element in the request body and returning a
CALDAV:mkcalendar-response XML element in the response body. CALDAV:mkcalendar-response XML element in the response body.
>> MKCALENDAR Request << >> MKCALENDAR Request <<
MKCALENDAR /home/lisa/calendars/events/ HTTP/1.1 MKCALENDAR /home/lisa/calendars/events/ HTTP/1.1
Host: calendar.example.com Host: calendar.example.com
Content-Type: application/xml; charset="utf-8" Content-Type: application/xml; charset="utf-8"
Content-Length: xxxx Content-Length: xxxx
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
<C:mkcalendar xmlns:D="DAV:" <C:mkcalendar xmlns:D="DAV:"
xmlns:C="urn:ietf:params:xml:ns:caldav"> xmlns:C="urn:ietf:params:xml:ns:caldav">
<D:set> <D:set>
<D:prop> <D:prop>
<D:displayname>Lisa's Events</D:displayname> <D:displayname>Lisa's Events</D:displayname>
</D:prop> </D:prop>
</D:set> </D:set>
</C:mkcalendar> </C:mkcalendar>
RFC 5689 Extended MKCOL for WebDAV September 2009
>> MKCALENDAR Response << >> MKCALENDAR Response <<
HTTP/1.1 201 Created HTTP/1.1 201 Created
Cache-Control: no-cache Cache-Control: no-cache
Date: Sat, 11 Nov 2006 09:32:12 GMT Date: Sat, 11 Nov 2006 09:32:12 GMT
Content-Type: application/xml; charset="utf-8" Content-Type: application/xml; charset="utf-8"
Content-Length: xxxx Content-Length: xxxx
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
<C:mkcalendar-response xmlns:D="DAV:" <C:mkcalendar-response xmlns:D="DAV:"
skipping to change at page 10, line 4 skipping to change at page 10, line 4
<D:set> <D:set>
<D:prop> <D:prop>
<D:resourcetype> <D:resourcetype>
<D:collection/> <D:collection/>
<C:calendar/> <C:calendar/>
</D:resourcetype> </D:resourcetype>
<D:displayname>Lisa's Events</D:displayname> <D:displayname>Lisa's Events</D:displayname>
</D:prop> </D:prop>
</D:set> </D:set>
</D:mkcol> </D:mkcol>
RFC 5689 Extended MKCOL for WebDAV September 2009
>> MKCOL Response << >> MKCOL Response <<
HTTP/1.1 201 Created HTTP/1.1 201 Created
Cache-Control: no-cache Cache-Control: no-cache
Date: Sat, 11 Nov 2006 09:32:12 GMT Date: Sat, 11 Nov 2006 09:32:12 GMT
Content-Type: application/xml; charset="utf-8" Content-Type: application/xml; charset="utf-8"
Content-Length: xxxx Content-Length: xxxx
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
<D:mkcol-response xmlns:D="DAV:" <D:mkcol-response xmlns:D="DAV:"
skipping to change at page 11, line 5 skipping to change at page 11, line 5
Definition: Definition:
<!ELEMENT mkcol (set+)> <!ELEMENT mkcol (set+)>
5.2. mkcol-response XML Element 5.2. mkcol-response XML Element
Name: mkcol-response Name: mkcol-response
Namespace: DAV: Namespace: DAV:
RFC 5689 Extended MKCOL for WebDAV September 2009
Purpose: Used in a response to indicate the status of properties Purpose: Used in a response to indicate the status of properties
that were set or failed to be set during an extended MKCOL that were set or failed to be set during an extended MKCOL
request. request.
Description: This XML element is a container for the information Description: This XML element is a container for the information
returned about a resource that has been created in an extended returned about a resource that has been created in an extended
MKCOL request. MKCOL request.
Definition: Definition:
<!ELEMENT mkcol-response (propstat+)> <!ELEMENT mkcol-response (propstat+)>
6. Security Considerations 6. Security Considerations
This extension does not introduce any new security concerns beyond This extension does not introduce any new security concerns beyond
those already described in HTTP and WebDAV. those already described in HTTP [RFC2616] and WebDAV [RFC4918].
7. IANA Considerations
This document does not require any actions on the part of IANA.
8. Acknowledgments 7. Acknowledgments
Thanks to Bernard Desruisseaux, Mike Douglass, Alexey Melnikov, Thanks to Bernard Desruisseaux, Mike Douglass, Alexey Melnikov,
Julian Reschke, and Simon Vaillancourt. Julian Reschke, and Simon Vaillancourt.
9. Normative References 8. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to
Indicate Requirement Levels", BCP 14,
RFC 2119, March 1997.
[RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk,
H., Masinter, L., Leach, P., and T. Berners-
Lee, "Hypertext Transfer Protocol --
HTTP/1.1", RFC 2616, June 1999.
[RFC4791] Daboo, C., Desruisseaux, B., and L.
Dusseault, "Calendaring Extensions to WebDAV
(CalDAV)", RFC 4791, March 2007.
[RFC4918] Dusseault, L., "HTTP Extensions for Web
Distributed Authoring and Versioning
(WebDAV)", RFC 4918, June 2007.
[W3C.REC-xml-20081126] Paoli, J., Yergeau, F., Bray, T., Sperberg-
McQueen, C., and E. Maler, "Extensible Markup
Language (XML) 1.0 (Fifth Edition)", World
Wide Web Consortium Recommendation REC-xml-
20081126, November 2008,
<http://www.w3.org/TR/2008/REC-xml-20081126>.
Appendix A. Change History (to be removed prior to publication as an
RFC)
Changes in -06:
1. Fixed section title.
2. Gen-ART review comments addressed.
3. Added "Updates 4791, 4918".
4. Tweaked examples.
Changes in -05:
1. Make response body optional in case of complete success.
2. Added an example of an error with extended MKCOL.
Changes in -04:
1. WGLC: minor wording tweaks.
2. WGLC: switch to using XML conventions text from RFC5323.
3. WGLC: MAY -> may in section 3/paragraph 2.
4. WGLC: mkcol-response DTD - removed ANY.
5. WGLC: updated to W3C.REC-xml-20081126 reference.
Changes in -03:
1. Boiler plate update.
Changes in -02:
1. Minor formatting/wording changes proposed by Julian Reschke were
applied.
2. Removed reference to DeltaV entirely as the spec no longer
replaces the MKxxx DeltaV defines.
3. Added Namespace definition to precondition.
4. Added reference to 4918 XML extensibility rules.
5. Added statement that DAV:collection must be present in DAV:
resourcetype in the request.
6. Added statement on use of DTD fragments.
7. Added statement about setting proper Content-Type for the MKCOL
body.
8. Added statement that MKCOL bodies using a different root element [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
are reserved for future extensions. Requirement Levels", BCP 14, RFC 2119, March 1997.
Changes in -01: [RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H.,
Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext
Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999.
1. Fixed an example. [RFC4791] Daboo, C., Desruisseaux, B., and L. Dusseault,
"Calendaring Extensions to WebDAV (CalDAV)", RFC 4791,
March 2007.
Changes in -00: [RFC4918] Dusseault, L., "HTTP Extensions for Web Distributed
Authoring and Versioning (WebDAV)", RFC 4918, June 2007.
1. Removed MKACTIVITY and MKWORKSPACE replacement behavior. [W3C.REC-xml-20081126]
Maler, E., Yergeau, F., Paoli, J., Bray, T., and C.
Sperberg-McQueen, "Extensible Markup Language (XML) 1.0
(Fifth Edition)", World Wide Web Consortium
Recommendation REC-xml-20081126, November 2008,
<http://www.w3.org/TR/2008/REC-xml-20081126>.
2. Added valid-resourcetype precondition. RFC 5689 Extended MKCOL for WebDAV September 2009
Author's Address Author's Address
Cyrus Daboo Cyrus Daboo
Apple Inc. Apple Inc.
1 Infinite Loop 1 Infinite Loop
Cupertino, CA 95014 Cupertino, CA 95014
USA USA
EMail: cyrus@daboo.name EMail: cyrus@daboo.name
 End of changes. 48 change blocks. 
177 lines changed or deleted 114 lines changed or added

This html diff was produced by rfcdiff 1.37a. The latest version is available from http://tools.ietf.org/tools/rfcdiff/