idnits 2.17.1 draft-reschke-webdav-mount-03.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 676. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 653. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 660. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 666. ** 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 (November 28, 2005) is 6695 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: June 1, 2006 November 28, 2005 6 Mounting WebDAV (Web Distributed Authoring and Versioning) servers 7 draft-reschke-webdav-mount-03 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 June 1, 2006. 34 Copyright Notice 36 Copyright (C) The Internet Society (2005). 38 Abstract 40 In current Web browsers, there is no uniform way to specify that a 41 user clicking on a link will be presented with an editable view of a 42 WebDAV server. For example, it is frequently desirable to be able to 43 click on a link, and have this link open a window that can handle 44 drag and drop interaction with the resources of a WebDAV server. 46 This document specifies a mechanism and a document format that 47 enables Web Distributed Authoring and Versioning (WebDAV) servers to 48 send "mounting" information to a WebDAV client. The mechanism is 49 designed to work on any platform and with any combination of browser 50 and WebDAV client, relying solely on the well-understood dispatch of 51 documents through their MIME type. 53 Editorial Note (To be removed by RFC Editor before publication) 55 Please send comments to the Distributed Authoring and Versioning 56 (WebDAV) working group at , which may be 57 joined by sending a message with subject "subscribe" to 58 . Discussions of the WEBDAV 59 working group are archived at 60 . 62 Note that although discussion takes place on the WebDAV working 63 group's mailing list, this is not a working group document. 65 XML versions, latest edits and the issues list for this document are 66 available from 67 . 69 Table of Contents 71 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 72 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 73 3. Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 74 3.1 dm:mount . . . . . . . . . . . . . . . . . . . . . . . . . 5 75 3.2 dm:url . . . . . . . . . . . . . . . . . . . . . . . . . . 5 76 3.3 dm:open . . . . . . . . . . . . . . . . . . . . . . . . . 5 77 3.4 dm:username . . . . . . . . . . . . . . . . . . . . . . . 5 78 4. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 79 5. Internationalization Considerations . . . . . . . . . . . . . 7 80 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 81 6.1 MIME type registration . . . . . . . . . . . . . . . . . . 7 82 7. Security Considerations . . . . . . . . . . . . . . . . . . . 8 83 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 9 84 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9 85 9.1 Normative References . . . . . . . . . . . . . . . . . . . 9 86 9.2 Informative References . . . . . . . . . . . . . . . . . . 9 87 Author's Address . . . . . . . . . . . . . . . . . . . . . . . 10 88 A. Alternative approaches . . . . . . . . . . . . . . . . . . . . 10 89 A.1 ...through HTML/CSS extensions . . . . . . . . . . . . . . 10 90 A.2 ...through custom URI schemes . . . . . . . . . . . . . . 10 91 B. Implementations . . . . . . . . . . . . . . . . . . . . . . . 10 92 B.1 Example implementation for Webfolder client . . . . . . . 11 93 B.2 Xythos . . . . . . . . . . . . . . . . . . . . . . . . . . 14 94 C. Change Log (to be removed by RFC Editor before publication) . 14 95 C.1 Since draft-reschke-webdav-mount-00 . . . . . . . . . . . 14 96 C.2 Since draft-reschke-webdav-mount-01 . . . . . . . . . . . 14 97 C.3 Since draft-reschke-webdav-mount-02 . . . . . . . . . . . 14 98 D. Open issues (to be removed by RFC Editor prior to 99 publication) . . . . . . . . . . . . . . . . . . . . . . . . . 15 100 D.1 edit . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 101 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 102 Intellectual Property and Copyright Statements . . . . . . . . 17 104 1. Introduction 106 By definition, a WebDAV server ([RFC2518]) is an HTTP server as well 107 ([RFC2616]). Most WebDAV servers can be (at least partly) operated 108 from an HTML-based user interface in a web browser. However, it is 109 frequently desirable to be able to switch from an HTML-based view to 110 a presentation provided by a native WebDAV client, directly 111 supporting the authoring features defined in WebDAV and related 112 specifications. 114 This document specifies a platform neutral mechanism based on the 115 dispatch of documents through their MIME type. For completeness, 116 Appendix A lists other approaches that have been implemented in 117 existing clients. 119 For example, many educational institutions use WebDAV servers as a 120 mechanism for sharing documents among students. Each student owns a 121 separate collection structure on a WebDAV server, often called his/ 122 her "locker". Ideally, when users click on a link in an HTML page 123 provided by the university (perhaps by their university Web portal), 124 an editable view of their locker will appear. 126 2. Terminology 128 The terminology used here follows that in the WebDAV Distributed 129 Authoring Protocol specification [RFC2518]. 131 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 132 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 133 document are to be interpreted as described in [RFC2119]. 135 This document uses XML DTD fragments ([XML]) as a purely notational 136 convention. In particular: 138 o Element names use the namespace 139 "http://purl.org/NET/webdav/mount". When an XML element type in 140 this namespace is referenced in this document outside of the 141 context of an XML fragment, the string "dm:" will be prefixed to 142 the element name. 144 o Element ordering is irrelevant. 146 o Extension elements/attributes (elements/attributes not already 147 defined as valid child elements) may be added anywhere, except 148 when explicitly stated otherwise. 150 3. Format 152 A WebDAV mount request is encoded in a specific XML format ([XML]) 153 with a well-defined MIME type (see Section 6.1). The MIME type 154 allows user agents to dispatch the content to a handler specific to 155 the system's WebDAV client. 157 The elements defined below use the namespace 158 "http://purl.org/NET/webdav/mount". 160 162 163 166 167 170 172 3.1 dm:mount 174 The element acts as container for all the remaining 175 elements defined by this protocol. 177 3.2 dm:url 179 The mandatory element provides the HTTP URL of the WebDAV 180 collection that should be mounted by the client. 182 3.3 dm:open 184 The optional element instructs the client to display the 185 specified child collection; its URL is computed by concatenating this 186 element's value with the URL obtained from the (Section 3.2) 187 element (see Section 7 for a discussion about why this element only 188 supports displaying collections rather than opening arbitrary 189 documents). 191 3.4 dm:username 193 The server can use the optional element to specify the 194 name of the currently authenticated principal. A client can use this 195 value to select a matching mount point (different users may have 196 mounted the URL with different credentials under different local 197 mount points) or to provide a meaningful default for authentication 198 against the server. It is common that browser and WebDAV client do 199 not share HTTP connections, so including this information in the 200 mount document increases usability. 202 Implementation Note: If a element is present, public 203 caching of the document should be disallowed. Thus, appropriate 204 'Vary' or 'Cache-Control' headers are needed in the server response. 206 4. Example 208 In the example below, the client first retrieves a representation of 209 a WebDAV collection using a generic Web browser (1). The returned 210 HTML content contains a hyperlink that identifies the "davmount" 211 document in the format defined in Section 3 (2). The user follows 212 this link (3), which causes the server to return the "davmount" 213 document to the user's browser (4). The browser in turn passes the 214 content to the application that was registered to handle the 215 "application/davmount+xml" MIME type, usually the default WebDAV 216 client on the client's system. 218 (1) Client retrieves representation of WebDAV collection "/user42/ 219 inbox/". 221 GET /user42/inbox/ HTTP/1.1 222 Host: www.example.com 224 (2) Server returns representation. 226 HTTP/1.1 200 OK 227 Content-Type: text/html 228 Content-Length: xxx 230 .. 231 View this collection in your 232 WebDAV client 233 .. 234 (note that the example shows only that part of the HTML page that 235 contains the relevant link) 237 (3) Client follows link to "davmount" document 239 GET /user42/inbox/?action=davmount HTTP/1.1 240 Host: www.example.com 241 (4) Server returns "davmount" document 243 HTTP/1.1 200 OK 244 Content-Type: application/davmount+xml 245 Content-Length: xxx 246 Cache-Control: private 248 249 http://www.example.com/user42/ 250 inbox/ 251 253 5. Internationalization Considerations 255 This document does not introduce any new internationalization 256 considerations beyond those discussed in [RFC2518], Section 16. 258 6. IANA Considerations 260 6.1 MIME type registration 262 MIME media type name: 264 application 266 MIME subtype name: 268 davmount+xml 270 Mandatory parameters: 272 none 274 Optional parameters: 276 "charset": This parameter has identical semantics to the charset 277 parameter of the "application/xml" media type as specified in 278 [RFC3023]. 280 Encoding considerations: 282 Identical to those of "application/xml" as described in [RFC3023], 283 section 3.2. 285 Security considerations: 287 As defined in this specification. In addition, as this media type 288 uses the "+xml" convention, it shares the same security 289 considerations as described in [RFC3023], section 10. 291 Interoperability considerations: 293 There are no known interoperability issues. 295 Published specification: 297 This specification. 299 Additional information: 301 Magic number(s): 303 As specified for "application/xml" in [RFC3023], section 3.2. 305 File extension: 307 .davmount 309 Fragment identifiers: 311 As specified for "application/xml" in [RFC3023], section 5. 313 Base URI: 315 As specified in [RFC3023], section 6. 317 Macintosh File Type code: 319 TEXT 321 Person and email address to contact for further information: 323 Julian Reschke 325 Intended usage: 327 COMMON 329 Author/Change controller: 331 IESG 333 7. Security Considerations 335 All security considerations connected to HTTP/WebDAV and XML apply 336 for this specification as well, namely [RFC2518] (Section 17) and 337 [RFC3470] (Section 7). 339 In addition, client implementers must be careful when implementing 340 the element (see Section 3.3). It MUST NOT be used to 341 initiate any action beyond displaying the contents of a WebDAV 342 collection (supporting "opening" documents could be abused to trick a 343 user into letting the operating system's shell execute arbitrary 344 content, possibly running it as an executable program). 346 8. Acknowledgements 348 This draft has benefited from thoughtful discussion by Emile Baizel, 349 Spencer Dawkins, Stefan Eissing, Joe Gregorio, Michal Gregr, Jim 350 Luther, Jaroslav Mazanec, and Jim Whitehead. 352 9. References 354 9.1 Normative References 356 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 357 Requirement Levels", BCP 14, RFC 2119, March 1997. 359 [RFC2518] Goland, Y., Whitehead, E., Faizi, A., Carter, S., and D. 360 Jensen, "HTTP Extensions for Distributed Authoring -- 361 WEBDAV", RFC 2518, February 1999. 363 [RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., 364 Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext 365 Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999. 367 [RFC3023] Murata, M., St.Laurent, S., and D. Kohn, "XML Media 368 Types", RFC 3023, January 2001. 370 [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform 371 Resource Identifier (URI): Generic Syntax", STD 66, 372 RFC 3986, January 2005. 374 [XML] Bray, T., Paoli, J., Sperberg-McQueen, C., Maler, E., and 375 F. Yergeau, "Extensible Markup Language (XML) 1.0 (Third 376 Edition)", W3C REC-xml-20040204, February 2004, 377 . 379 9.2 Informative References 381 [RFC3470] Hollenbeck, S., Rose, M., and L. Masinter, "Guidelines for 382 the Use of Extensible Markup Language (XML) within IETF 383 Protocols", RFC 3470, BCP 70, January 2003. 385 [WEBARCH] Walsh, N. and I. Jacobs, "Architecture of the World Wide 386 Web, Volume One", W3C REC REC-webarch-20041215, 387 December 2004, 388 . 390 Author's Address 392 Julian F. Reschke 393 greenbytes GmbH 394 Hafenweg 16 395 Muenster, NW 48155 396 Germany 398 Phone: +49 251 2807760 399 Fax: +49 251 2807761 400 Email: julian.reschke@greenbytes.de 401 URI: http://greenbytes.de/tech/webdav/ 403 Appendix A. Alternative approaches 405 A.1 ...through HTML/CSS extensions 407 Microsoft Internet Explorer implements a CSS extension that allows 408 switching to its own WebDAV client ("Webfolder", see ). However, at the time of this writing this extension 411 was not implemented by any other user agent. 413 A.2 ...through custom URI schemes 415 The "kio" library of the "K Desktop Enviroment" 416 () uses the URI scheme "webdav" to dispatch to 417 the system's WebDAV client. This URI scheme is not registered, nor 418 supported on other platforms. Furthermore, W3C's "Architecture of 419 the World Wide Web, Volume One" explicitly advises against defining 420 new schemes when existing schemes can be used: 422 "A specification SHOULD reuse an existing URI scheme (rather than 423 create a new one) when it provides the desired properties of 424 identifiers and their relation to resources." 426 (see [WEBARCH], Section 2.4) 428 Appendix B. Implementations 429 B.1 Example implementation for Webfolder client 431 The figure below shows a sample implementation of a dispatcher for 432 the application/davmount+xml datatype, suited for Win32 systems and 433 the Microsoft "Webfolder" client. 435 // sample implementation of application/davmount+xml 436 // dispatcher for Windows Webfolder client 437 // 438 // to install/uninstall: 439 // wscript davmount.js 440 // 441 // to open the webfolder: 442 // wscript davmount.js filename 443 // (where filename refers to an XML document with MIME type 444 // application/davmount+xml) 446 var EXTENSION = ".davmount"; 447 var MIMETYPE = "application/davmount+xml"; 448 var REGKW = "WebDAV.mount"; 449 var NS = "xmlns:m='http://purl.org/NET/webdav/mount"; 451 // remove keys/entries from the registry 453 function regdel(shell, key) { 454 try { 455 var x = shell.RegRead(key); 456 try { 457 shell.RegDelete(key); 458 } 459 catch(e) { 460 WScript.Echo("Error removing key " + key + ": " + e); 461 } 462 } 463 catch(e) { 464 // entry not present 465 } 466 } 468 // methods for registering/unregistering the handler 470 function install() { 472 var WshShell = new ActiveXObject("WScript.Shell"); 473 if (WshShell == null) { 474 WScript.Echo("Couldn't instantiate WScript.Shell object"); 475 return 2; 477 } 479 var fso = new ActiveXObject("Scripting.FileSystemObject"); 481 var RegExt = "HKCR\\" + EXTENSION + "\\"; 482 var RegMimeType = "HKCR\\MIME\\DataBase\\Content Type\\" 483 + MIMETYPE + "\\"; 484 var RegKw = "HKCR\\" + REGKW + "\\"; 486 var extension = null; 487 try { 488 extension = WshShell.RegRead(RegMimeType + "Extension"); 489 } 490 catch (e) { 491 } 493 if (extension == null) { 494 var but = WshShell.popup("Install the dispatcher for mime type " 495 + MIMETYPE + "?", 0, MIMETYPE + " installation", 4); 497 if (but == 6) { 498 try { 499 WshShell.RegWrite(RegExt, REGKW); 500 WshShell.RegWrite(RegExt + "Content Type", MIMETYPE); 501 WshShell.RegWrite(RegMimeType + "Extension", EXTENSION); 502 WshShell.RegWrite(RegKw, "WebDAV Mount Request"); 503 WshShell.RegWrite(RegKw + "DefaultIcon\\", 504 "shell32.dll,103"); 505 var path = fso.getAbsolutePathName("davmount.js"); 506 WshShell.RegWrite(RegKw + "shell\\open\\command\\", 507 "%SystemRoot%\\system32\\wscript.exe /nologo \"" 508 + path + "\" \"%1\"", "REG_EXPAND_SZ"); 509 } 510 catch (e) { 511 WScript.Echo("Error writing to registry"); 512 return 1; 513 } 515 return 0; 516 } 517 else { 518 return 1; 519 } 520 } 521 else { 522 var but = WshShell.popup("Remove the dispatcher for mime type " 523 + MIMETYPE + "?", 0, MIMETYPE + " installation", 4); 525 if (but == 6) { 526 regdel(WshShell, RegExt + "Content Type"); 527 regdel(WshShell, RegExt); 528 regdel(WshShell, RegKw + "shell\\open\\command\\"); 529 regdel(WshShell, RegKw + "DefaultIcon\\"); 530 regdel(WshShell, RegKw); 531 regdel(WshShell, RegMimeType + "Extension"); 532 regdel(WshShell, RegMimeType); 533 return 0; 534 } 535 else { 536 return 1; 537 } 538 } 539 } 541 if (WScript.Arguments.length == 0) { 542 // install/uninstall 543 WScript.Quit(install()); 544 } 545 else { 546 // try to invoke Webfolder 548 var inp = new ActiveXObject("MSXML2.DOMDocument"); 549 if (! inp.load(WScript.Arguments(0))) { 550 WScript.Echo("Can't read from '" 551 + WScript.Arguments(0) + "'!"); 552 WScript.Quit(2); 553 } 555 inp.setProperty("SelectionLanguage", "XPath"); 556 inp.setProperty("SelectionNamespaces", 557 "xmlns:m='http://purl.org/NET/webdav/mount'"); 559 var n1 = inp.selectSingleNode("/m:mount/m:url"); 560 var n2 = inp.selectSingleNode("/m:mount/m:open"); 562 if (n1 == null) { 563 WScript.Echo(" element missing."); 564 WScript.Quit(2); 565 } 567 var ie = new ActiveXObject("InternetExplorer.Application"); 569 ie.Navigate("about:blank"); 570 var doc = ie.Document; 571 var folder = doc.createElement("span"); 572 folder.addBehavior("#default#httpFolder"); 574 var result = folder.navigate(n1.text + 575 (n2 == null ? "" : n2.text)); 577 // close the window again when there was no element 578 if (n2 == null) ie.Quit(); 580 if (result != "OK") { 581 if (result == "PROTOCOL_NOT_SUPPORTED") { 582 WScript.Echo("This site doesn't seem to support WebDAV."); 583 WScript.Quit(1); 584 } 585 else { 586 WScript.Echo("Unexpected status: " + result); 587 WScript.Quit(2); 588 } 589 } 590 } 592 B.2 Xythos 594 The "Xythos Drive" WebDAV client for WebDAV supports this 595 specification starting with version 4.4. 597 Appendix C. Change Log (to be removed by RFC Editor before publication) 599 C.1 Since draft-reschke-webdav-mount-00 601 Add implementations section; add sample implementation for Microsoft 602 Webfolder client. Add acknowledgments section. 604 C.2 Since draft-reschke-webdav-mount-01 606 Be consistent in using trailing slashes on collection URLs in 607 examples. Fix webfolder reference impl not to require 608 element. Update acknowledgments. Incorporate some of JimW's 609 suggestions in abstract and introduction. Expand security 610 considerations regarding and fwd-reference it from the spec. 612 C.3 Since draft-reschke-webdav-mount-02 614 Author's address updated. Mainly editorial fixes after review by 615 Spencer Dawkins. Enhance rational for dm:username based of feedback 616 by Stefan Eissing. 618 Appendix D. Open issues (to be removed by RFC Editor prior to 619 publication) 621 D.1 edit 623 Type: edit 625 julian.reschke@greenbytes.de (2005-09-17): Umbrella issue for 626 editorial fixes/enhancements. 628 Index 630 A 631 application/mount 632 xml MIME type 7 634 D 635 dm:mount 5 636 dm:opent 5 637 dm:url 5 638 dm:username 5 640 M 641 MIME type 642 application/mount 7 644 Intellectual Property Statement 646 The IETF takes no position regarding the validity or scope of any 647 Intellectual Property Rights or other rights that might be claimed to 648 pertain to the implementation or use of the technology described in 649 this document or the extent to which any license under such rights 650 might or might not be available; nor does it represent that it has 651 made any independent effort to identify any such rights. Information 652 on the procedures with respect to rights in RFC documents can be 653 found in BCP 78 and BCP 79. 655 Copies of IPR disclosures made to the IETF Secretariat and any 656 assurances of licenses to be made available, or the result of an 657 attempt made to obtain a general license or permission for the use of 658 such proprietary rights by implementers or users of this 659 specification can be obtained from the IETF on-line IPR repository at 660 http://www.ietf.org/ipr. 662 The IETF invites any interested party to bring to its attention any 663 copyrights, patents or patent applications, or other proprietary 664 rights that may cover technology that may be required to implement 665 this standard. Please address the information to the IETF at 666 ietf-ipr@ietf.org. 668 Disclaimer of Validity 670 This document and the information contained herein are provided on an 671 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 672 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 673 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 674 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 675 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 676 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 678 Copyright Statement 680 Copyright (C) The Internet Society (2005). This document is subject 681 to the rights, licenses and restrictions contained in BCP 78, and 682 except as set forth therein, the authors retain all their rights. 684 Acknowledgment 686 Funding for the RFC Editor function is currently provided by the 687 Internet Society.