idnits 2.17.1 draft-reschke-webdav-mount-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 14. -- Found old boilerplate from RFC 3978, Section 5.5 on line 409. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 386. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 393. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 399. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- 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 7, 2005) is 6837 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) ** Obsolete normative reference: RFC 2518 (Obsoleted by RFC 4918) ** Obsolete normative reference: RFC 2616 (Obsoleted by RFC 7230, RFC 7231, RFC 7232, RFC 7233, RFC 7234, RFC 7235) ** Obsolete normative reference: RFC 3023 (Obsoleted by RFC 7303) -- Possible downref: Non-RFC (?) normative reference: ref. 'XML' Summary: 6 errors (**), 0 flaws (~~), 2 warnings (==), 8 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group J. Reschke 3 Internet-Draft greenbytes 4 Expires: February 8, 2006 August 7, 2005 6 Mounting WebDAV (Web Distributed Authoring and Versioning) servers 7 draft-reschke-webdav-mount-00 9 Status of this Memo 11 By submitting this Internet-Draft, each author represents that any 12 applicable patent or other IPR claims of which he or she is aware 13 have been or will be disclosed, and any of which he or she becomes 14 aware will be disclosed, in accordance with Section 6 of BCP 79. 16 Internet-Drafts are working documents of the Internet Engineering 17 Task Force (IETF), its areas, and its working groups. Note that 18 other groups may also distribute working documents as Internet- 19 Drafts. 21 Internet-Drafts are draft documents valid for a maximum of six months 22 and may be updated, replaced, or obsoleted by other documents at any 23 time. It is inappropriate to use Internet-Drafts as reference 24 material or to cite them other than as "work in progress." 26 The list of current Internet-Drafts can be accessed at 27 http://www.ietf.org/ietf/1id-abstracts.txt. 29 The list of Internet-Draft Shadow Directories can be accessed at 30 http://www.ietf.org/shadow.html. 32 This Internet-Draft will expire on February 8, 2006. 34 Copyright Notice 36 Copyright (C) The Internet Society (2005). 38 Abstract 40 This document specifies a mechanism and a document format that 41 enables Web Distributed Authoring and Versioning (WebDAV) servers to 42 send "mounting" information to a WebDAV client. The protocol is 43 designed to work on any platform and with any combination of browser 44 and WebDAV client, relying solely on the well-understood dispatch of 45 documents through their MIME type. 47 Editorial Note (To be removed by RFC Editor before publication) 48 Please send comments to the Distributed Authoring and Versioning 49 (WebDAV) working group at , which may be 50 joined by sending a message with subject "subscribe" to 51 . Discussions of the WEBDAV 52 working group are archived at 53 . 55 Note that although discussion takes place on the WebDAV working 56 group's mailing list, this is not a working group document. 58 XML versions, latest edits and the issues list for this document are 59 available from 60 . 62 Table of Contents 64 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 65 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 66 3. Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 67 3.1 dm:mount . . . . . . . . . . . . . . . . . . . . . . . . . 4 68 3.2 dm:url . . . . . . . . . . . . . . . . . . . . . . . . . . 4 69 3.3 dm:open . . . . . . . . . . . . . . . . . . . . . . . . . 4 70 3.4 dm:username . . . . . . . . . . . . . . . . . . . . . . . 4 71 4. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 72 5. Internationalization Considerations . . . . . . . . . . . . . 5 73 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 74 6.1 MIME type registration . . . . . . . . . . . . . . . . . . 5 75 7. Security Considerations . . . . . . . . . . . . . . . . . . . 7 76 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 7 77 8.1 Normative References . . . . . . . . . . . . . . . . . . . 7 78 8.2 Informative References . . . . . . . . . . . . . . . . . . 7 79 Author's Address . . . . . . . . . . . . . . . . . . . . . . . 8 80 A. Alternative approaches . . . . . . . . . . . . . . . . . . . . 8 81 A.1 ...through HTML/CSS extensions . . . . . . . . . . . . . . 8 82 A.2 ...through custom URI schemes . . . . . . . . . . . . . . 8 83 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 84 Intellectual Property and Copyright Statements . . . . . . . . 10 86 1. Introduction 88 By definition, a WebDAV server ([RFC2518]) is an HTTP server as well 89 ([RFC2616]). Most WebDAV servers can be (at least partly) operated 90 from an HTML-based user interface in a web browser. However, it is 91 frequently desirable to be able to switch from an HTML-based view to 92 a presentation provided by a native WebDAV client, directly 93 supporting the authoring features defined in WebDAV and related 94 specifications. 96 For completeness, Appendix A lists other approaches that have been 97 implemented in existing clients. 99 2. Terminology 101 The terminology used here follows and extends that in the WebDAV 102 Distributed Authoring Protocol specification [RFC2518]. 104 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 105 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 106 document are to be interpreted as described in [RFC2119]. 108 This document uses XML DTD fragments ([XML]) as a purely notational 109 convention. In particular: 111 o Element names use the namespace 112 "http://purl.org/NET/webdav/mount". When an XML element type in 113 this namespace is referenced in this document outside of the 114 context of an XML fragment, the string "dm:" will be prefixed to 115 the element name. 117 o Element ordering is irrelevant. 119 o Extension elements/attributes (elements/attributes not already 120 defined as valid child elements) may be added anywhere, except 121 when explicitly stated otherwise. 123 3. Format 125 A WebDAV mount request is encoded in a specific XML format ([XML]) 126 with a well-defined MIME type (see Section 6.1). The MIME type 127 allows user agents to dispatch the content to a handler specific to 128 the system's WebDAV client. 130 The elements defined below use the namespace 131 "http://purl.org/NET/webdav/mount". 133 135 136 139 140 143 145 3.1 dm:mount 147 The element acts as container for all the remaining 148 elements defined by this protocol. 150 3.2 dm:url 152 The mandatory element provides the HTTP URL of the WebDAV 153 collection that should be mounted by the client. 155 3.3 dm:open 157 The optional element instructs the client to display the 158 specified child collection; it's URL is computed by concatenating 159 this element's value with the URL obtained from the 160 (Section 3.2) element. 162 3.4 dm:username 164 The server can use the optional element to specify the 165 name of the authenticated principal. A client can use this value to 166 select a matching mount point (different users may have mounted the 167 URL with different credentials under different local mount points) or 168 to provide a meaningful default for a authentication dialogue. 170 4. Example 172 In the example below, the server instructs the user agent to mount 173 the WebDAV URL "http://www.example.com/documents" in it's WebDAV 174 client, and then to display the contents the child collection 175 "/user42/inbox", identified by the URL 176 ""http://www.example.com/documents/user42/inbox". 178 >> Request: 180 GET /Coll/&mount-me HTTP/1.1 181 Host: www.example.com 183 >> Response: 185 HTTP/1.1 200 OK 186 Content-Type: application/davmount+xml 187 Content-Length: xxx 189 190 http://www.example.com/documents 191 /user42/inbox 192 194 5. Internationalization Considerations 196 This document does not introduce any new internationalization 197 considerations beyond those discussed in [RFC2518], Section 16. 199 6. IANA Considerations 201 6.1 MIME type registration 203 MIME media type name: 205 application 207 MIME subtype name: 209 davmount+xml 211 Mandatory parameters: 213 none 215 Optional parameters: 217 "charset": This parameter has identical semantics to the charset 218 parameter of the "application/xml" media type as specified in 219 [RFC3023]. 221 Encoding considerations: 223 Identical to those of "application/xml" as described in [RFC3023], 224 section 3.2. 226 Security considerations: 228 As defined in this specification. In addition, as this media type 229 uses the "+xml" convention, it shares the same security 230 considerations as described in [RFC3023], section 10. 232 Interoperability considerations: 234 There are no known interoperability issues. 236 Published specification: 238 This specification. 240 Additional information: 242 Magic number(s): 244 As specified for "application/xml" in [RFC3023], section 3.2. 246 File extension: 248 .davmount 250 Fragment identifiers: 252 As specified for "application/xml" in [RFC3023], section 5. 254 Base URI: 256 As specified in [RFC3023], section 6. 258 Macintosh File Type code: 260 TEXT 262 Person and email address to contact for further information: 264 Julian Reschke 266 Intended usage: 268 COMMON 270 Author/Change controller: 272 IESG 274 7. Security Considerations 276 All security considerations connected to HTTP/WebDAV and XML apply 277 for this specification as well, namely [RFC2518] (Section 17) and 278 [RFC3470] (Section 7). 280 In addition, client implementors must be careful when implementing 281 the element (see Section 3.3). It MUST NOT be used to 282 initiate any action beyond displaying the contents of a WebDAV 283 collection. 285 8. References 287 8.1 Normative References 289 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 290 Requirement Levels", BCP 14, RFC 2119, March 1997. 292 [RFC2518] Goland, Y., Whitehead, E., Faizi, A., Carter, S., and D. 293 Jensen, "HTTP Extensions for Distributed Authoring -- 294 WEBDAV", RFC 2518, February 1999. 296 [RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., 297 Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext 298 Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999. 300 [RFC3023] Murata, M., St.Laurent, S., and D. Kohn, "XML Media 301 Types", RFC 3023, January 2001. 303 [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform 304 Resource Identifier (URI): Generic Syntax", STD 66, 305 RFC 3986, January 2005. 307 [XML] Bray, T., Paoli, J., Sperberg-McQueen, C., Maler, E., and 308 F. Yergeau, "Extensible Markup Language (XML) 1.0 (Third 309 Edition)", W3C REC-xml-20040204, February 2004, 310 . 312 8.2 Informative References 314 [RFC3470] Hollenbeck, S., Rose, M., and L. Masinter, "Guidelines for 315 the Use of Extensible Markup Language (XML) within IETF 316 Protocols", RFC 3470, BCP 70, January 2003. 318 [WEBARCH] Walsh, N. and I. Jacobs, "Architecture of the World Wide 319 Web, Volume One", W3C REC REC-webarch-20041215, 320 December 2004, 321 . 323 Author's Address 325 Julian F. Reschke 326 greenbytes GmbH 327 Salzmannstrasse 152 328 Muenster, NW 48159 329 Germany 331 Phone: +49 251 2807760 332 Fax: +49 251 2807761 333 Email: julian.reschke@greenbytes.de 334 URI: http://greenbytes.de/tech/webdav/ 336 Appendix A. Alternative approaches 338 A.1 ...through HTML/CSS extensions 340 Microsoft Internet Explorer implements a CSS extension that allows 341 switching to it's own WebDAV client ("Webfolder", see ). However, at the time of this writing this extension 344 was not implemented by any other user agent. 346 A.2 ...through custom URI schemes 348 The "kio" library of the "K Desktop Enviroment" 349 () uses the URI scheme "webdav" to dispatch to 350 the system's WebDAV client. This URI scheme is not registered, nor 351 supported on other platforms. Furthermore, W3C's "Architecture of 352 the World Wide Web, Volume One" explicitly advises against defining 353 new schemes when existing schemes can be used: 355 "A specification SHOULD reuse an existing URI scheme (rather than 356 create a new one) when it provides the desired properties of 357 identifiers and their relation to resources." 359 (see [WEBARCH], Section 2.4) 361 Index 363 A 364 application/mount 365 xml MIME type 5 367 D 368 dm:mount 4 369 dm:opent 4 370 dm:url 4 371 dm:username 4 373 M 374 MIME type 375 application/mount 5 377 Intellectual Property Statement 379 The IETF takes no position regarding the validity or scope of any 380 Intellectual Property Rights or other rights that might be claimed to 381 pertain to the implementation or use of the technology described in 382 this document or the extent to which any license under such rights 383 might or might not be available; nor does it represent that it has 384 made any independent effort to identify any such rights. Information 385 on the procedures with respect to rights in RFC documents can be 386 found in BCP 78 and BCP 79. 388 Copies of IPR disclosures made to the IETF Secretariat and any 389 assurances of licenses to be made available, or the result of an 390 attempt made to obtain a general license or permission for the use of 391 such proprietary rights by implementers or users of this 392 specification can be obtained from the IETF on-line IPR repository at 393 http://www.ietf.org/ipr. 395 The IETF invites any interested party to bring to its attention any 396 copyrights, patents or patent applications, or other proprietary 397 rights that may cover technology that may be required to implement 398 this standard. Please address the information to the IETF at 399 ietf-ipr@ietf.org. 401 Disclaimer of Validity 403 This document and the information contained herein are provided on an 404 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 405 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 406 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 407 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 408 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 409 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 411 Copyright Statement 413 Copyright (C) The Internet Society (2005). This document is subject 414 to the rights, licenses and restrictions contained in BCP 78, and 415 except as set forth therein, the authors retain all their rights. 417 Acknowledgment 419 Funding for the RFC Editor function is currently provided by the 420 Internet Society.