idnits 2.17.1 draft-ietf-webdav-propfind-space-00.txt: ** The Abstract section seems to be numbered Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories -- however, there's a paragraph with a matching beginning. Boilerplate error? == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** The abstract seems to contain references ([WEBDAV]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (August 10, 1999) is 9025 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'Bradner' is mentioned on line 252, but not defined -- Looks like a reference, but probably isn't: '1996' on line 252 ** Obsolete normative reference: RFC 2518 (ref. 'WEBDAV') (Obsoleted by RFC 4918) Summary: 8 errors (**), 0 flaws (~~), 2 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group J. Stracke, eCal Corp. 2 INTERNET DRAFT 3 4 Expires April, 2000 August 10, 1999 6 WebDAV PROPFIND Extension To List Specified Namespaces 8 1 Status of this Document 10 This document is an Internet-Draft and is in full conformance with 11 all provisions of Section 10 of RFC2026. 13 Internet-Drafts are working documents of the Internet Engineering 14 Task Force (IETF), its areas, and its working groups. Note that other 15 groups may also distribute working documents as Internet-Drafts. 17 Internet-Drafts are draft documents valid for a maximum of six months 18 and may be updated, replaced, or obsoleted by other documents at any 19 time. It is inappropriate to use Internet-Drafts as reference 20 material or to cite them other than as ``work in progress.'' 22 The list of current Internet-Drafts can be accessed at 23 25 The list of Internet-Draft Shadow Directories can be accessed at 26 28 Distribution of this document is unlimited. Please send comments to 29 francis@ecal.com or to the w3c-dist-auth@w3.org discussion list. 31 2 Abstract 33 This document specifies an extension to the [WEBDAV] PROPFIND method 34 to permit a WebDAV client to request all properties which belong to a 35 specified namespace or namespaces. 37 3 Introduction 39 This document specifies an extension to the [WEBDAV] PROPFIND method 40 to permit a WebDAV client to request all properties which belong to a 41 specified namespace or namespaces. 43 A WebDAV application using a custom namespace for 44 application-specific data may occasionally need to use PROPFIND to 45 list all a resource's properties from that namespace. (Similarly, a 46 WebDAV client might need to know all DAV: properties, but not care 47 about non-standard properties.) In such a case, the client must 48 choose between the element, which will retrieve all 49 properties on the resource, and the element, which will 50 retrieve specified properties only. The problem with is 51 that the resource may have many properties from other namespaces, in 52 which the application is not interested. The problem with is 53 that the client may not know all the property names which may be 54 present (for example, if the client is too general-purpose to permit 55 it to be configured with the list of property names, or if property 56 name munging is being used). A third choice would be to use 57 to list all the resource's properties without their 58 contents, then use with just the properties in the desired 59 namespace; the problem with this approach is that it requires an 60 extra HTTP request. 62 This document proposes a middle ground, an extension to and 63 which provides a list of namespaces to search. 65 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 66 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 67 document are to be interpreted as described in [MUSTS] . 69 4 Extension definition 71 Two new XML elements are proposed, and . In 72 the idiom of [WEBDAV]: 74 4.1 namespaces XML Element 76 Name: namespaces 78 Namespace: DAV: 80 Purpose: The namespaces XML element specifies that the enclosing 81 allprop or propname element applies only to properties belonging to 82 the namespaces listed in the enclosed namespace elements. 84 4.2 namespace XML Element 86 Name: namespace 88 Namespace: DAV: 90 Purpose: The namespace XML element specifies a namespace in the 91 namespaces list. appears inside , and has a 92 single attribute, uri, the URI of the namespace. 94 5 Examples 96 5.1 Fetching all DAV: properties 98 Request: 99 PROPFIND /index.html HTTP/1.1 100 Host: www.example.com 101 Content-Length: xxxx 102 Content-Type: text/xml 104 105 106 107 108 109 110 112 Response: 113 HTTP/1.1 200 OK 114 Content-Type: text/xml 115 Content-Length: xxxx 117 118 119 120 121 123 124 125 126 128 1999-08-11T12:12:12Z 129 Example.com, The Fictious Site! 130 17 131 text/html 132 xyzzy 133 1999-08-11T12:12:14Z 134 136 138 140 5.2 Listing names of properties in two namespaces 142 Request: 143 PROPFIND /index.html HTTP/1.1 144 Host: www.example.com 145 Content-Length: xxxx 146 Content-Type: text/xml 148 149 150 151 152 153 154 155 157 Response: 158 161 162 163 165 6 Compatibility Considerations 167 Section 14 of [WEBDAV] specifies: 169 "All DAV compliant resources MUST ignore any unknown XML 170 element and all its children encountered while processing a DAV 171 method that uses XML as its command language." 173 As a result, a client which uses on a server which 174 does not support it will get the base-level DAV behavior (listing all 175 properties), exactly as if it had issued a base-level DAV request. 176 Therefore, a client which sends PROPFIND requests using 177 MUST accept responses which include properties not in 178 the listed namespace(s). 180 Of course, it is always risky assuming that all implementations of a 181 young standard adhere to all points of the standard. In this case, 182 the risk is mitigated by the fact that section 23.3.2.2 of [WEBDAV] 183 presents a (hypothetical) similar extension, , and 184 states: 186 "If the previous example were submitted to a server unfamiliar 187 with leave-out, the only result would be that the leave-out 188 element would be ignored and a propname would be executed." 190 Nevertheless, since there may be some servers which, for whatever 191 reason, violate this prescription (say, if they attempt to validate 192 the XML request against the DTD in section 23.2 of [WEBDAV] ), a 193 client which uses SHOULD be aware that it may receive 194 a 400 Bad Request from such a server, and SHOULD be able to retry the 195 request without using . 197 7 Internationalization Considerations 199 This proposal builds on [WEBDAV], and inherits its 200 internationalizability. 202 8 IANA Considerations 204 This proposal does not introduce any new IANA considerations, since 205 it does not specify any new namespaces (in the general sense), but 206 merely uses existing ones. 208 9 Security Considerations 210 For a server, this proposal does not introduce any new security 211 considerations over those of [WEBDAV], since the information which is 212 exposed is already available. There might be privacy considerations 213 for a client, since telling the server which namespaces one wishes to 214 search does reveal some information. Implementors must balance this 215 concern against the efficiency gains this proposal offers. 217 10 Copyright 219 The following copyright notice is copied from RFC 2026 [Bradner, 220 1996], section 10.4, and describes the applicable copyright for this 221 document. 223 Copyright (C) The Internet Society April 5, 1998. All Rights 224 Reserved. 226 This document and translations of it may be copied and furnished to 227 others, and derivative works that comment on or otherwise explain it 228 or assist in its implementation may be prepared, copied, published 229 and distributed, in whole or in part, without restriction of any 230 kind, provided that the above copyright notice and this paragraph are 231 included on all such copies and derivative works. However, this 232 document itself may not be modified in any way, such as by removing 233 the copyright notice or references to the Internet Society or other 234 Internet organizations, except as needed for the purpose of 235 developing Internet standards in which case the procedures for 236 copyrights defined in the Internet Standards process must be 237 followed, or as required to translate it into languages other than 238 English. 240 The limited permissions granted above are perpetual and will not be 241 revoked by the Internet Society or its successors or assignees. 243 This document and the information contained herein is provided on an 244 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 245 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 246 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 247 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 248 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 250 11 Intellectual Property 252 The following notice is copied from RFC 2026 [Bradner, 1996], section 253 10.4, and describes the position of the IETF concerning intellectual 254 property claims made against this document. 256 The IETF takes no position regarding the validity or scope of any 257 intellectual property or other rights that might be claimed to 258 pertain to the implementation or use other technology described in 259 this document or the extent to which any license under such rights 260 might or might not be available; neither does it represent that it 261 has made any effort to identify any such rights. Information on the 262 IETF's procedures with respect to rights in standards-track and 263 standards-related documentation can be found in BCP-11. Copies of 264 claims of rights made available for publication and any assurances of 265 licenses to be made available, or the result of an attempt made to 266 obtain a general license or permission for the use of such 267 proprietary rights by implementors or users of this specification can 268 be obtained from the IETF Secretariat. 270 The IETF invites any interested party to bring to its attention any 271 copyrights, patents or patent applications, or other proprietary 272 rights which may cover technology that may be required to practice 273 this standard. Please address the information to the IETF Executive 274 Director. 276 12 Acknowledgements 278 Some of the PROPFIND syntax in the examples was copied from examples 279 in [WEBDAV]. 281 13 References 283 [WEBDAV] Y. Y. Goland, E. J. Whitehead, Jr., A. Faizi, S. R. Carter, 284 D. Jensen, "Extensions for Distributed Authoring on the World Wide 285 Web - WebDAV." RFC 2518. Microsoft, U.C. Irvine, Netscape, Novell. 286 April, 1998. 288 [MUSTS] Bradner, S., "Key words for use in RFCs to Indicate 289 Requirement Levels," BCP 14, RFC 2119, Harvard University, March 290 1997. 292 14 Author's Address 294 J. Stracke 295 eCal Corp. 296 234 N. Columbus Blvd., 2nd Floor 297 francis@ecal.com