draft-ietf-vcarddav-webdav-mkcol-03.txt   draft-ietf-vcarddav-webdav-mkcol-04.txt 
Network Working Group C. Daboo Network Working Group C. Daboo
Internet-Draft Apple Inc. Internet-Draft Apple Inc.
Intended status: Standards Track February 10, 2009 Intended status: Standards Track March 9, 2009
Expires: August 14, 2009 Expires: September 10, 2009
Extended MKCOL for WebDAV Extended MKCOL for WebDAV
draft-ietf-vcarddav-webdav-mkcol-03 draft-ietf-vcarddav-webdav-mkcol-04
Status of This Memo Status of This Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. 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 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
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. 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 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 14, 2009. This Internet-Draft will expire on September 10, 2009.
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 Provisions Relating to IETF Documents in effect on the date of
(http://trustee.ietf.org/license-info) in effect on the date of publication of this document (http://trustee.ietf.org/license-info).
publication of this document. Please review these documents Please review these documents carefully, as they describe your rights
carefully, as they describe your rights and restrictions with respect and restrictions with respect to this document.
to this document.
Abstract Abstract
This specification extends the Web Distributed Authoring and This specification extends the Web Distributed Authoring and
Versioning (WebDAV) MKCOL method to allow collections of arbitrary Versioning (WebDAV) MKCOL method to allow collections of arbitrary
resourcetype to be created and to allow properties to be set at the resourcetype to be created and to allow properties to be set at the
same time. same time.
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 . . . . . . . . . . . . . . . . . . . . 3 3. WebDAV extended MKCOL . . . . . . . . . . . . . . . . . . . . 4
3.1. Extended MKCOL Support . . . . . . . . . . . . . . . . . . 4 3.1. Extended MKCOL Support . . . . . . . . . . . . . . . . . . 4
3.1.1. Example: Using OPTIONS for the Discovery of 3.1.1. Example: Using OPTIONS for the Discovery of
Support for Extended MKCOL . . . . . . . . . . . . . . 4 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 . . . . . . . . 5
4. Replacing Existing MKxxx Methods . . . . . . . . . . . . . . . 6 4. Replacing Existing MKxxx Methods . . . . . . . . . . . . . . . 6
4.1. MKCALENDAR Replacement . . . . . . . . . . . . . . . . . . 7 4.1. MKCALENDAR Replacement . . . . . . . . . . . . . . . . . . 7
4.1.1. Example: Replacing MKCALENDAR with MKCOL . . . . . . . 7 4.1.1. Example: Replacing MKCALENDAR with MKCOL . . . . . . . 7
5. XML Element Definitions . . . . . . . . . . . . . . . . . . . 9 5. XML Element Definitions . . . . . . . . . . . . . . . . . . . 9
5.1. mkcol XML Element . . . . . . . . . . . . . . . . . . . . 9 5.1. mkcol XML Element . . . . . . . . . . . . . . . . . . . . 9
5.2. mkcol-response XML Element . . . . . . . . . . . . . . . . 9 5.2. mkcol-response XML Element . . . . . . . . . . . . . . . . 9
6. Security Considerations . . . . . . . . . . . . . . . . . . . 10 6. Security Considerations . . . . . . . . . . . . . . . . . . . 10
skipping to change at page 3, line 18 skipping to change at page 3, line 18
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 which 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 through other means. These "special" collections are
created by new methods (e.g., MKCALENDAR). The addition of a new created by new methods (e.g., MKCALENDAR). The addition of a new
MKxxx method for each new "special" collection adds to server MKxxx method for each new "special" collection adds to server
complexity and is detrimental to overall reliability due to the need complexity and is detrimental to overall reliability due to the need
to make sure intermediaries are aware of these methods. to make sure intermediaries are aware of these methods.
This specification proposes an extension to the WebDAV MKCOL method This specification defined 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, or other properties used to create a "special"
resource. This avoids the need to invent new MKxxx methods. 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].
Definitions of XML elements in this document use XML element type This document uses XML DTD fragments ([W3C.REC-xml-20081126], Section
declarations (as found in XML Document Type Declarations), described 3.2) as a purely notational convention. WebDAV request and response
in Section 3.2 of [W3C.REC-xml-20060816]. bodies cannot be validated by a DTD due to the specific extensibility
rules defined in Section 17 of [RFC4918] and due to the fact that all
XML elements defined by this specification use the XML namespace name
"DAV:". In particular:
When XML element types in the namespace "DAV:" are referenced in this 1. element names use the "DAV:" namespace,
document outside of the context of an XML fragment, the string "DAV:"
will be prefixed to the element type names.
Processing of XML by clients and servers MUST follow the rules 2. element ordering is irrelevant unless explicitly stated,
described in Appendix A of [RFC4918].
3. extension elements (elements not already defined as valid child
elements) may be added anywhere, except when explicitly stated
otherwise,
4. extension attributes (attributes not already defined as valid for
this element) may be added anywhere, except when explicitly
stated otherwise.
When an XML element type in the "DAV:" namespace is referenced in
this document outside of the context of an XML fragment, the string
"DAV:" will be prefixed to the element type.
This document inherits, and sometimes extends, DTD productions from
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
request body. The request body is an XML document containing a request body. The request body is an XML document containing a
single DAV:mkcol XML element as the root element. The Content-Type single DAV:mkcol XML element as the root element. The Content-Type
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, that MUST include the DAV:collection element that needs
to be present for any WebDAV collection. to be present for any WebDAV collection.
As per the PROPPATCH method ([RFC4918], Section 9.2), servers MUST As per the PROPPATCH method ([RFC4918], Section 9.2), 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). Instructions MUST the normal rule that ordering is irrelevant). Instructions MUST
skipping to change at page 10, line 15 skipping to change at page 10, line 15
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+, ANY)> <!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 and WebDAV.
7. IANA Considerations 7. IANA Considerations
This document does not require any actions on the part of IANA. This document does not require any actions on the part of IANA.
8. Acknowledgments 8. Acknowledgments
Several people suggested this approach, including Julian Reschke and Thanks to Bernard Desruisseaux, Mike Douglass, Julian Reschke, and
Bernard Desruisseaux. Thanks also to Mike Douglass. Simon Vaillancourt.
9. Normative References 9. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to [RFC2119] Bradner, S., "Key words for use in RFCs to
Indicate Requirement Levels", BCP 14, Indicate Requirement Levels", BCP 14,
RFC 2119, March 1997. RFC 2119, March 1997.
[RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, [RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk,
H., Masinter, L., Leach, P., and T. Berners- H., Masinter, L., Leach, P., and T. Berners-
Lee, "Hypertext Transfer Protocol -- Lee, "Hypertext Transfer Protocol --
HTTP/1.1", RFC 2616, June 1999. HTTP/1.1", RFC 2616, June 1999.
[RFC4791] Daboo, C., Desruisseaux, B., and L. [RFC4791] Daboo, C., Desruisseaux, B., and L.
Dusseault, "Calendaring Extensions to WebDAV Dusseault, "Calendaring Extensions to WebDAV
(CalDAV)", RFC 4791, March 2007. (CalDAV)", RFC 4791, March 2007.
[RFC4918] Dusseault, L., "HTTP Extensions for Web [RFC4918] Dusseault, L., "HTTP Extensions for Web
Distributed Authoring and Versioning Distributed Authoring and Versioning
(WebDAV)", RFC 4918, June 2007. (WebDAV)", RFC 4918, June 2007.
[W3C.REC-xml-20060816] Yergeau, F., Paoli, J., Bray, T., Sperberg- [W3C.REC-xml-20081126] Paoli, J., Yergeau, F., Bray, T., Sperberg-
McQueen, C., and E. Maler, "Extensible Markup McQueen, C., and E. Maler, "Extensible Markup
Language (XML) 1.0 (Fourth Edition)", World Language (XML) 1.0 (Fifth Edition)", World
Wide Web Consortium FirstEdition REC-xml- Wide Web Consortium Recommendation REC-xml-
20060816, August 2006, 20081126, November 2008,
<http://www.w3.org/TR/2006/REC-xml-20060816>. <http://www.w3.org/TR/2008/REC-xml-20081126>.
Appendix A. Change History (to be removed prior to publication as an Appendix A. Change History (to be removed prior to publication as an
RFC) RFC)
Changes from -02: 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. 1. Boiler plate update.
Changes from -01: Changes in -02:
1. Minor formatting/wording changes proposed by Julian Reschke were 1. Minor formatting/wording changes proposed by Julian Reschke were
applied. applied.
2. Removed reference to DeltaV entirely as the spec no longer 2. Removed reference to DeltaV entirely as the spec no longer
replaces the MKxxx DeltaV defines. replaces the MKxxx DeltaV defines.
3. Added Namespace definition to precondition. 3. Added Namespace definition to precondition.
4. Added reference to 4918 XML extensibility rules. 4. Added reference to 4918 XML extensibility rules.
skipping to change at page 11, line 38 skipping to change at page 11, line 50
resourcetype in the request. resourcetype in the request.
6. Added statement on use of DTD fragments. 6. Added statement on use of DTD fragments.
7. Added statement about setting proper Content-Type for the MKCOL 7. Added statement about setting proper Content-Type for the MKCOL
body. body.
8. Added statement that MKCOL bodies using a different root element 8. Added statement that MKCOL bodies using a different root element
are reserved for future extensions. are reserved for future extensions.
Changes from -00: Changes in -01:
1. Fixed an example. 1. Fixed an example.
Changes from draft-daboo-webdav-mkcol-00: Changes in -00:
1. Removed MKACTIVITY and MKWORKSPACE replacement behavior. 1. Removed MKACTIVITY and MKWORKSPACE replacement behavior.
2. Added valid-resourcetype precondition. 2. Added valid-resourcetype precondition.
Author's Address Author's Address
Cyrus Daboo Cyrus Daboo
Apple Inc. Apple Inc.
1 Infinite Loop 1 Infinite Loop
 End of changes. 20 change blocks. 
34 lines changed or deleted 70 lines changed or added

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