idnits 2.17.1 draft-reschke-webdav-mount-05.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 15. -- Found old boilerplate from RFC 3978, Section 5.5 on line 720. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 731. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 738. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 744. ** 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 issues found here. 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 (July 21, 2006) is 6460 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 (~~), 1 warning (==), 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 Intended status: Standards Track July 21, 2006 5 Expires: January 22, 2007 7 Mounting Web Distributed Authoring and Versioning (WebDAV) servers 8 draft-reschke-webdav-mount-05 10 Status of this Memo 12 By submitting this Internet-Draft, each author represents that any 13 applicable patent or other IPR claims of which he or she is aware 14 have been or will be disclosed, and any of which he or she becomes 15 aware will be disclosed, in accordance with Section 6 of BCP 79. 17 Internet-Drafts are working documents of the Internet Engineering 18 Task Force (IETF), its areas, and its working groups. Note that 19 other groups may also distribute working documents as Internet- 20 Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six months 23 and may be updated, replaced, or obsoleted by other documents at any 24 time. It is inappropriate to use Internet-Drafts as reference 25 material or to cite them other than as "work in progress." 27 The list of current Internet-Drafts can be accessed at 28 http://www.ietf.org/ietf/1id-abstracts.txt. 30 The list of Internet-Draft Shadow Directories can be accessed at 31 http://www.ietf.org/shadow.html. 33 This Internet-Draft will expire on January 22, 2007. 35 Copyright Notice 37 Copyright (C) The Internet Society (2006). 39 Abstract 41 In current Web browsers, there is no uniform way to specify that a 42 user clicking on a link will be presented with an editable view of a 43 WebDAV server. For example, it is frequently desirable to be able to 44 click on a link, and have this link open a window that can handle 45 drag and drop interaction with the resources of a WebDAV server. 47 This document specifies a mechanism and a document format that 48 enables Web Distributed Authoring and Versioning (WebDAV) servers to 49 send "mounting" information to a WebDAV client. The mechanism is 50 designed to work on any platform and with any combination of browser 51 and WebDAV client, relying solely on the well-understood dispatch of 52 documents through their MIME type. 54 Editorial Note (To be removed by RFC Editor before publication) 56 Please send comments to the Distributed Authoring and Versioning 57 (WebDAV) working group at , which may be 58 joined by sending a message with subject "subscribe" to 59 . Discussions of the WEBDAV 60 working group are archived at 61 . 63 Note that although discussion takes place on the WebDAV working 64 group's mailing list, this is not a working group document. 66 XML versions, latest edits and the issues list for this document are 67 available from 68 . 70 Table of Contents 72 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 73 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 74 3. Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 75 3.1. dm:mount . . . . . . . . . . . . . . . . . . . . . . . . . 5 76 3.2. dm:url . . . . . . . . . . . . . . . . . . . . . . . . . . 5 77 3.3. dm:open . . . . . . . . . . . . . . . . . . . . . . . . . 5 78 3.4. dm:username . . . . . . . . . . . . . . . . . . . . . . . 5 79 4. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 80 5. Internationalization Considerations . . . . . . . . . . . . . 7 81 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 82 6.1. MIME type registration . . . . . . . . . . . . . . . . . . 7 83 7. Security Considerations . . . . . . . . . . . . . . . . . . . 9 84 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 9 85 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9 86 9.1. Normative References . . . . . . . . . . . . . . . . . . . 9 87 9.2. Informative References . . . . . . . . . . . . . . . . . . 10 88 Appendix A. Alternative approaches . . . . . . . . . . . . . . . 10 89 A.1. ...through HTML/CSS extensions . . . . . . . . . . . . . . 10 90 A.2. ...through custom URI schemes . . . . . . . . . . . . . . 10 91 Appendix B. Implementations . . . . . . . . . . . . . . . . . . . 11 92 B.1. Example implementation for Webfolder client . . . . . . . 11 93 B.2. Xythos . . . . . . . . . . . . . . . . . . . . . . . . . . 14 94 Appendix C. Change Log (to be removed by RFC Editor before 95 publication) . . . . . . . . . . . . . . . . . . . . 14 96 C.1. Since draft-reschke-webdav-mount-00 . . . . . . . . . . . 14 97 C.2. Since draft-reschke-webdav-mount-01 . . . . . . . . . . . 15 98 C.3. Since draft-reschke-webdav-mount-02 . . . . . . . . . . . 15 99 C.4. Since draft-reschke-webdav-mount-03 . . . . . . . . . . . 15 100 C.5. Since draft-reschke-webdav-mount-04 . . . . . . . . . . . 15 101 Appendix D. Resolved issues (to be removed by RFC Editor 102 before publication) . . . . . . . . . . . . . . . . . 15 103 D.1. warn-username-visibility . . . . . . . . . . . . . . . . . 15 104 D.2. ms-impl-fn . . . . . . . . . . . . . . . . . . . . . . . . 15 105 Appendix E. Open issues (to be removed by RFC Editor prior to 106 publication) . . . . . . . . . . . . . . . . . . . . 16 107 E.1. edit . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 108 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 109 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 16 110 Intellectual Property and Copyright Statements . . . . . . . . . . 17 112 1. Introduction 114 By definition, a WebDAV server ([RFC2518]) is an HTTP server as well 115 ([RFC2616]). Most WebDAV servers can be (at least partly) operated 116 from an HTML-based user interface in a web browser. However, it is 117 frequently desirable to be able to switch from an HTML-based view to 118 a presentation provided by a native WebDAV client, directly 119 supporting the authoring features defined in WebDAV and related 120 specifications. 122 This document specifies a platform neutral mechanism based on the 123 dispatch of documents through their MIME type. For completeness, 124 Appendix A lists other approaches that have been implemented in 125 existing clients. 127 For example, many educational institutions use WebDAV servers as a 128 mechanism for sharing documents among students. Each student owns a 129 separate collection structure on a WebDAV server, often called his/ 130 her "locker". Ideally, when users click on a link in an HTML page 131 provided by the university (perhaps by their university Web portal), 132 an editable view of their locker will appear. 134 2. Terminology 136 The terminology used here follows that in the WebDAV Distributed 137 Authoring Protocol specification [RFC2518]. 139 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 140 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 141 document are to be interpreted as described in [RFC2119]. 143 This document uses XML DTD fragments ([XML]) as a purely notational 144 convention. In particular: 146 o Element names use the namespace 147 "http://purl.org/NET/webdav/mount". When an XML element type in 148 this namespace is referenced in this document outside of the 149 context of an XML fragment, the string "dm:" will be prefixed to 150 the element name. 152 o Element ordering is irrelevant. 154 o Extension elements/attributes (elements/attributes not already 155 defined as valid child elements) may be added anywhere, except 156 when explicitly stated otherwise. 158 3. Format 160 A WebDAV mount request is encoded in a specific XML format ([XML]) 161 with a well-defined MIME type (see Section 6.1). The MIME type 162 allows user agents to dispatch the content to a handler specific to 163 the system's WebDAV client. 165 The elements defined below use the namespace 166 "http://purl.org/NET/webdav/mount". 168 170 171 174 175 178 180 3.1. dm:mount 182 The element acts as container for all the remaining 183 elements defined by this protocol. 185 3.2. dm:url 187 The mandatory element provides the HTTP URL of the WebDAV 188 collection that should be mounted by the client. 190 3.3. dm:open 192 The optional element instructs the client to display the 193 specified child collection; its URL is computed by concatenating this 194 element's value with the URL obtained from the (Section 3.2) 195 element (see Section 7 for a discussion about why this element only 196 supports displaying collections rather than opening arbitrary 197 documents). 199 3.4. dm:username 201 The server can use the optional element to specify the 202 name of the currently authenticated principal. A client can use this 203 value to select a matching mount point (different users may have 204 mounted the URL with different credentials under different local 205 mount points) or to provide a meaningful default for authentication 206 against the server. It is common that browser and WebDAV client do 207 not share HTTP connections, so including this information in the 208 mount document increases usability. 210 Implementation Note: If a element is present, public 211 caching of the document should be disallowed. Thus, appropriate 212 'Vary' or 'Cache-Control' headers are needed in the server response. 214 4. Example 216 In the example below, the client first retrieves a representation of 217 a WebDAV collection using a generic Web browser (1). The returned 218 HTML content contains a hyperlink that identifies the "davmount" 219 document in the format defined in Section 3 (2). The user follows 220 this link (3), which causes the server to return the "davmount" 221 document to the user's browser (4). The browser in turn passes the 222 content to the application that was registered to handle the 223 "application/davmount+xml" MIME type, usually the default WebDAV 224 client on the client's system. 226 (1) Client retrieves representation of WebDAV collection "/user42/ 227 inbox/". 229 GET /user42/inbox/ HTTP/1.1 230 Host: www.example.com 232 (2) Server returns representation. 234 HTTP/1.1 200 OK 235 Content-Type: text/html 236 Content-Length: xxx 238 .. 239 View this collection in your 240 WebDAV client 241 .. 242 (note that the example shows only that part of the HTML page that 243 contains the relevant link) 245 (3) Client follows link to "davmount" document 247 GET /user42/inbox/?action=davmount HTTP/1.1 248 Host: www.example.com 249 (4) Server returns "davmount" document 251 HTTP/1.1 200 OK 252 Content-Type: application/davmount+xml 253 Content-Length: xxx 254 Cache-Control: private 256 257 http://www.example.com/user42/ 258 inbox/ 259 261 5. Internationalization Considerations 263 This document does not introduce any new internationalization 264 considerations beyond those discussed in [RFC2518], Section 16. 266 6. IANA Considerations 268 6.1. MIME type registration 270 Type name: 272 application 274 Subtype name: 276 davmount+xml 278 Required parameters: 280 none 282 Optional parameters: 284 "charset": This parameter has identical semantics to the charset 285 parameter of the "application/xml" media type as specified in 286 [RFC3023]. 288 Encoding considerations: 290 Identical to those of "application/xml" as described in [RFC3023], 291 Section 3.2. 293 Security considerations: 295 As defined in this specification. In addition, as this media type 296 uses the "+xml" convention, it shares the same security 297 considerations as described in [RFC3023], Section 10. 299 Interoperability considerations: 301 There are no known interoperability issues. 303 Published specification: 305 This specification. 307 Applications that use this media type: 309 SAP Netweaver Knowledge Management, Xythos Drive. 311 Additional information: 313 Magic number(s): 315 As specified for "application/xml" in [RFC3023], Section 3.2. 317 File extension(s): 319 .davmount 321 Fragment identifiers: 323 As specified for "application/xml" in [RFC3023], Section 5. 325 Base URI: 327 As specified in [RFC3023], Section 6. 329 Macintosh file type code(s): 331 TEXT 333 Person & email address to contact for further information: 335 Julian Reschke 337 Intended usage: 339 COMMON 341 Restrictions on usage: 343 None. 345 Author: 347 Julian Reschke 349 Change controller: 351 IESG 353 7. Security Considerations 355 All security considerations connected to HTTP/WebDAV and XML apply 356 for this specification as well, namely [RFC2518] (Section 17) and 357 [RFC3470] (Section 7). 359 In addition, client implementers must be careful when implementing 360 the element (see Section 3.3). It MUST NOT be used to 361 initiate any action beyond displaying the contents of a WebDAV 362 collection (supporting "opening" documents could be abused to trick a 363 user into letting the operating system's shell execute arbitrary 364 content, possibly running it as an executable program). 366 When mount documents contain user names (using the 367 element defined in Section 3.4), servers hosting such documents (or 368 clients creating them) should pay attention to the public readability 369 of the document and related privacy concerns. 371 8. Acknowledgements 373 This draft has benefited from thoughtful discussion by Emile Baizel, 374 Spencer Dawkins, Lisa Dusseault, Stefan Eissing, Joe Gregorio, Michal 375 Gregr, Jim Luther, Jaroslav Mazanec, and Jim Whitehead. 377 9. References 379 9.1. Normative References 381 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 382 Requirement Levels", BCP 14, RFC 2119, March 1997. 384 [RFC2518] Goland, Y., Whitehead, E., Faizi, A., Carter, S., and D. 385 Jensen, "HTTP Extensions for Distributed Authoring -- 386 WEBDAV", RFC 2518, February 1999. 388 [RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., 389 Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext 390 Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999. 392 [RFC3023] Murata, M., St.Laurent, S., and D. Kohn, "XML Media 393 Types", RFC 3023, January 2001. 395 [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform 396 Resource Identifier (URI): Generic Syntax", STD 66, 397 RFC 3986, January 2005. 399 [XML] Bray, T., Paoli, J., Sperberg-McQueen, C., Maler, E., and 400 F. Yergeau, "Extensible Markup Language (XML) 1.0 (Third 401 Edition)", W3C REC-xml-20040204, February 2004, 402 . 404 9.2. Informative References 406 [RFC3470] Hollenbeck, S., Rose, M., and L. Masinter, "Guidelines for 407 the Use of Extensible Markup Language (XML) within IETF 408 Protocols", RFC 3470, BCP 70, January 2003. 410 [WEBARCH] Walsh, N. and I. Jacobs, "Architecture of the World Wide 411 Web, Volume One", W3C REC-webarch-20041215, December 2004, 412 . 414 Appendix A. Alternative approaches 416 A.1. ...through HTML/CSS extensions 418 Microsoft Internet Explorer implements a CSS extension that allows 419 switching to its own WebDAV client ("Webfolder", see ). However, at the time of this writing this extension 422 was not implemented by any other user agent. 424 A.2. ...through custom URI schemes 426 The "kio" library of the "K Desktop Enviroment" 427 () uses the URI scheme "webdav" to dispatch to 428 the system's WebDAV client. This URI scheme is not registered, nor 429 supported on other platforms. Furthermore, W3C's "Architecture of 430 the World Wide Web, Volume One" explicitly advises against defining 431 new schemes when existing schemes can be used: 433 A specification SHOULD reuse an existing URI scheme (rather than 434 create a new one) when it provides the desired properties of 435 identifiers and their relation to resources. 437 (see [WEBARCH], Section 2.4) 439 Appendix B. Implementations 441 B.1. Example implementation for Webfolder client 443 The figure below shows a sample implementation of a dispatcher for 444 the application/davmount+xml datatype, suited for Win32 systems and 445 the Microsoft "Webfolder" client. 447 // sample implementation of application/davmount+xml 448 // dispatcher for Windows Webfolder client 449 // 450 // to install/uninstall: 451 // wscript davmount.js 452 // 453 // to open the webfolder: 454 // wscript davmount.js filename 455 // (where filename refers to an XML document with MIME type 456 // application/davmount+xml) 458 var EXTENSION = ".davmount"; 459 var MIMETYPE = "application/davmount+xml"; 460 var REGKW = "WebDAV.mount"; 461 var NS = "xmlns:m='http://purl.org/NET/webdav/mount"; 463 // remove keys/entries from the registry 465 function regdel(shell, key) { 466 try { 467 var x = shell.RegRead(key); 468 try { 469 shell.RegDelete(key); 470 } 471 catch(e) { 472 WScript.Echo("Error removing key " + key + ": " + e); 473 } 474 } 475 catch(e) { 476 // entry not present 477 } 478 } 479 // methods for registering/unregistering the handler 481 function install() { 483 var WshShell = new ActiveXObject("WScript.Shell"); 484 if (WshShell == null) { 485 WScript.Echo("Couldn't instantiate WScript.Shell object"); 486 return 2; 487 } 489 var fso = new ActiveXObject("Scripting.FileSystemObject"); 491 var RegExt = "HKCR\\" + EXTENSION + "\\"; 492 var RegMimeType = "HKCR\\MIME\\DataBase\\Content Type\\" 493 + MIMETYPE + "\\"; 494 var RegKw = "HKCR\\" + REGKW + "\\"; 496 var extension = null; 497 try { 498 extension = WshShell.RegRead(RegMimeType + "Extension"); 499 } 500 catch (e) { 501 } 503 if (extension == null) { 504 var but = WshShell.popup("Install the dispatcher for mime type " 505 + MIMETYPE + "?", 0, MIMETYPE + " installation", 4); 507 if (but == 6) { 508 try { 509 WshShell.RegWrite(RegExt, REGKW); 510 WshShell.RegWrite(RegExt + "Content Type", MIMETYPE); 511 WshShell.RegWrite(RegMimeType + "Extension", EXTENSION); 512 WshShell.RegWrite(RegKw, "WebDAV Mount Request"); 513 WshShell.RegWrite(RegKw + "DefaultIcon\\", 514 "shell32.dll,103"); 515 var path = fso.getAbsolutePathName("davmount.js"); 516 WshShell.RegWrite(RegKw + "shell\\open\\command\\", 517 "%SystemRoot%\\system32\\wscript.exe /nologo \"" 518 + path + "\" \"%1\"", "REG_EXPAND_SZ"); 519 } 520 catch (e) { 521 WScript.Echo("Error writing to registry"); 522 return 1; 523 } 525 return 0; 526 } 527 else { 528 return 1; 529 } 530 } 531 else { 532 var but = WshShell.popup("Remove the dispatcher for mime type " 533 + MIMETYPE + "?", 0, MIMETYPE + " installation", 4); 535 if (but == 6) { 536 regdel(WshShell, RegExt + "Content Type"); 537 regdel(WshShell, RegExt); 538 regdel(WshShell, RegKw + "shell\\open\\command\\"); 539 regdel(WshShell, RegKw + "DefaultIcon\\"); 540 regdel(WshShell, RegKw); 541 regdel(WshShell, RegMimeType + "Extension"); 542 regdel(WshShell, RegMimeType); 543 return 0; 544 } 545 else { 546 return 1; 547 } 548 } 549 } 551 if (WScript.Arguments.length == 0) { 552 // install/uninstall 553 WScript.Quit(install()); 554 } 555 else { 556 // try to invoke Webfolder 558 var inp = new ActiveXObject("MSXML2.DOMDocument"); 559 var furi = encodeURI(WScript.Arguments(0)); 560 if (! inp.load(furi)) { 561 WScript.Echo("Can't read from '" 562 + WScript.Arguments(0) + "'!"); 563 WScript.Quit(2); 564 } 566 inp.setProperty("SelectionLanguage", "XPath"); 567 inp.setProperty("SelectionNamespaces", 568 "xmlns:m='http://purl.org/NET/webdav/mount'"); 570 var n1 = inp.selectSingleNode("/m:mount/m:url"); 571 var n2 = inp.selectSingleNode("/m:mount/m:open"); 573 if (n1 == null) { 574 WScript.Echo(" element missing."); 575 WScript.Quit(2); 576 } 578 var ie = new ActiveXObject("InternetExplorer.Application"); 580 ie.Navigate("about:blank"); 581 var doc = ie.Document; 583 var folder = doc.createElement("span"); 584 folder.addBehavior("#default#httpFolder"); 586 var result = folder.navigate(n1.text + 587 (n2 == null ? "" : n2.text)); 589 // close the window again when there was no element 590 if (n2 == null) ie.Quit(); 592 if (result != "OK") { 593 if (result == "PROTOCOL_NOT_SUPPORTED") { 594 WScript.Echo("This site doesn't seem to support WebDAV."); 595 WScript.Quit(1); 596 } 597 else { 598 WScript.Echo("Unexpected status: " + result); 599 WScript.Quit(2); 600 } 601 } 602 } 604 B.2. Xythos 606 The "Xythos Drive" WebDAV client for WebDAV supports this 607 specification starting with version 4.4. 609 Appendix C. Change Log (to be removed by RFC Editor before publication) 611 C.1. Since draft-reschke-webdav-mount-00 613 Add implementations section; add sample implementation for Microsoft 614 Webfolder client. Add acknowledgments section. 616 C.2. Since draft-reschke-webdav-mount-01 618 Be consistent in using trailing slashes on collection URLs in 619 examples. Fix webfolder reference impl not to require 620 element. Update acknowledgments. Incorporate some of JimW's 621 suggestions in abstract and introduction. Expand security 622 considerations regarding and fwd-reference it from the spec. 624 C.3. Since draft-reschke-webdav-mount-02 626 Author's address updated. Mainly editorial fixes after review by 627 Spencer Dawkins. Enhance rational for dm:username based of feedback 628 by Stefan Eissing. 630 C.4. Since draft-reschke-webdav-mount-03 632 Minor editorial tweaks to WEBARCH reference. Fix title. Update MIME 633 registration template (based on RFC4288). 635 C.5. Since draft-reschke-webdav-mount-04 637 Add and resolve issue "ms-impl-fn" (filenames needs to be URI escaped 638 for usage in MSXML's load() method). Add and resolve issue "warn- 639 username-visibility" (add security consideration regarding user names 640 in content). 642 Appendix D. Resolved issues (to be removed by RFC Editor before 643 publication) 645 Issues that were either rejected or resolved in this version of this 646 document. 648 D.1. warn-username-visibility 650 Type: edit 652 julian.reschke@greenbytes.de (2006-07-21): Mention the potential 653 issues with having user names appear in public content. 655 Resolution (2006-07-21): Done. 657 D.2. ms-impl-fn 659 Type: change 661 julian.reschke@greenbytes.de (2006-07-11): Escape the filename passed 662 as a parameter before handing it to MSXML's load() method (which 663 expects a URI (reference), not a filename). 665 Resolution (2006-07-11): Done. 667 Appendix E. Open issues (to be removed by RFC Editor prior to 668 publication) 670 E.1. edit 672 Type: edit 674 julian.reschke@greenbytes.de (2005-09-17): Umbrella issue for 675 editorial fixes/enhancements. 677 Index 679 A 680 application/mount 681 xml MIME type 7 683 D 684 dm:mount 5 685 dm:opent 5 686 dm:url 5 687 dm:username 5 689 M 690 MIME type 691 application/mount 7 693 Author's Address 695 Julian F. Reschke 696 greenbytes GmbH 697 Hafenweg 16 698 Muenster, NW 48155 699 Germany 701 Phone: +49 251 2807760 702 Fax: +49 251 2807761 703 Email: julian.reschke@greenbytes.de 704 URI: http://greenbytes.de/tech/webdav/ 706 Full Copyright Statement 708 Copyright (C) The Internet Society (2006). 710 This document is subject to the rights, licenses and restrictions 711 contained in BCP 78, and except as set forth therein, the authors 712 retain all their rights. 714 This document and the information contained herein are provided on an 715 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 716 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 717 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 718 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 719 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 720 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 722 Intellectual Property 724 The IETF takes no position regarding the validity or scope of any 725 Intellectual Property Rights or other rights that might be claimed to 726 pertain to the implementation or use of the technology described in 727 this document or the extent to which any license under such rights 728 might or might not be available; nor does it represent that it has 729 made any independent effort to identify any such rights. Information 730 on the procedures with respect to rights in RFC documents can be 731 found in BCP 78 and BCP 79. 733 Copies of IPR disclosures made to the IETF Secretariat and any 734 assurances of licenses to be made available, or the result of an 735 attempt made to obtain a general license or permission for the use of 736 such proprietary rights by implementers or users of this 737 specification can be obtained from the IETF on-line IPR repository at 738 http://www.ietf.org/ipr. 740 The IETF invites any interested party to bring to its attention any 741 copyrights, patents or patent applications, or other proprietary 742 rights that may cover technology that may be required to implement 743 this standard. Please address the information to the IETF at 744 ietf-ipr@ietf.org. 746 Acknowledgment 748 Funding for the RFC Editor function is provided by the IETF 749 Administrative Support Activity (IASA).