idnits 2.17.1 draft-reschke-webdav-mount-02.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 656. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 633. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 640. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 646. ** 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 (October 10, 2005) is 6771 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: April 13, 2006 October 10, 2005 6 Mounting WebDAV (Web Distributed Authoring and Versioning) servers 7 draft-reschke-webdav-mount-02 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 April 13, 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 protocol 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 . . . . . . . . . . . . . 6 80 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 81 6.1 MIME type registration . . . . . . . . . . . . . . . . . . 6 82 7. Security Considerations . . . . . . . . . . . . . . . . . . . 8 83 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 8 84 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8 85 9.1 Normative References . . . . . . . . . . . . . . . . . . . 8 86 9.2 Informative References . . . . . . . . . . . . . . . . . . 9 87 Author's Address . . . . . . . . . . . . . . . . . . . . . . . 9 88 A. Alternative approaches . . . . . . . . . . . . . . . . . . . . 9 89 A.1 ...through HTML/CSS extensions . . . . . . . . . . . . . . 9 90 A.2 ...through custom URI schemes . . . . . . . . . . . . . . 9 91 B. Implementations . . . . . . . . . . . . . . . . . . . . . . . 10 92 B.1 Example implementation for Webfolder client . . . . . . . 10 93 B.2 Xythos . . . . . . . . . . . . . . . . . . . . . . . . . . 13 94 C. Change Log (to be removed by RFC Editor before publication) . 13 95 C.1 Since draft-reschke-webdav-mount-00 . . . . . . . . . . . 13 96 C.2 Since draft-reschke-webdav-mount-01 . . . . . . . . . . . 14 97 D. Resolved issues (to be removed by RFC Editor before 98 publication) . . . . . . . . . . . . . . . . . . . . . . . . . 14 99 D.1 wfimplopennotoptional . . . . . . . . . . . . . . . . . . 14 100 E. Open issues (to be removed by RFC Editor prior to 101 publication) . . . . . . . . . . . . . . . . . . . . . . . . . 14 102 E.1 edit . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 103 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 104 Intellectual Property and Copyright Statements . . . . . . . . 16 106 1. Introduction 108 By definition, a WebDAV server ([RFC2518]) is an HTTP server as well 109 ([RFC2616]). Most WebDAV servers can be (at least partly) operated 110 from an HTML-based user interface in a web browser. However, it is 111 frequently desirable to be able to switch from an HTML-based view to 112 a presentation provided by a native WebDAV client, directly 113 supporting the authoring features defined in WebDAV and related 114 specifications. 116 For example, many educational institutions use WebDAV servers as a 117 mechanism for sharing documents among students. Each student owns a 118 separate collection structure on a WebDAV server, often called their 119 "locker". Ideally, when a user clicks on a link in an HTML page 120 provided by the university (perhaps by their university Web portal), 121 an editable view of their locker will appear. 123 For completeness, Appendix A lists other approaches that have been 124 implemented in existing clients. 126 2. Terminology 128 The terminology used here follows and extends that in the WebDAV 129 Distributed 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; it's URL is computed by concatenating 186 this element's value with the URL obtained from the 187 (Section 3.2) element (see Section 7 for a discussion about why this 188 element only supports displaying collections rather than opening 189 arbitrary documents). 191 3.4 dm:username 193 The server can use the optional element to specify the 194 name of the authenticated principal. A client can use this value to 195 select a matching mount point (different users may have mounted the 196 URL with different credentials under different local mount points) or 197 to provide a meaningful default for a authentication dialogue. 199 4. Example 201 In the example below, the server instructs the user agent to mount 202 the WebDAV URL "http://www.example.com/documents/" in its WebDAV 203 client, and then to display the contents of the child collection 204 "/user42/inbox/", identified by the URL 205 "http://www.example.com/documents/user42/inbox/". 207 >> Request: 209 GET /Coll/&mount-me HTTP/1.1 210 Host: www.example.com 212 >> Response: 214 HTTP/1.1 200 OK 215 Content-Type: application/davmount+xml 216 Content-Length: xxx 218 219 http://www.example.com/documents/ 220 user42/inbox/ 221 223 5. Internationalization Considerations 225 This document does not introduce any new internationalization 226 considerations beyond those discussed in [RFC2518], Section 16. 228 6. IANA Considerations 230 6.1 MIME type registration 232 MIME media type name: 234 application 236 MIME subtype name: 238 davmount+xml 240 Mandatory parameters: 242 none 244 Optional parameters: 246 "charset": This parameter has identical semantics to the charset 247 parameter of the "application/xml" media type as specified in 248 [RFC3023]. 250 Encoding considerations: 252 Identical to those of "application/xml" as described in [RFC3023], 253 section 3.2. 255 Security considerations: 257 As defined in this specification. In addition, as this media type 258 uses the "+xml" convention, it shares the same security 259 considerations as described in [RFC3023], section 10. 261 Interoperability considerations: 263 There are no known interoperability issues. 265 Published specification: 267 This specification. 269 Additional information: 271 Magic number(s): 273 As specified for "application/xml" in [RFC3023], section 3.2. 275 File extension: 277 .davmount 279 Fragment identifiers: 281 As specified for "application/xml" in [RFC3023], section 5. 283 Base URI: 285 As specified in [RFC3023], section 6. 287 Macintosh File Type code: 289 TEXT 291 Person and email address to contact for further information: 293 Julian Reschke 295 Intended usage: 297 COMMON 299 Author/Change controller: 301 IESG 303 7. Security Considerations 305 All security considerations connected to HTTP/WebDAV and XML apply 306 for this specification as well, namely [RFC2518] (Section 17) and 307 [RFC3470] (Section 7). 309 In addition, client implementers must be careful when implementing 310 the element (see Section 3.3). It MUST NOT be used to 311 initiate any action beyond displaying the contents of a WebDAV 312 collection (supporting "opening" documents could be abused to trick a 313 user into letting the operating system's shell execute arbitrary 314 content, possibly running it as an executable program). 316 8. Acknowledgements 318 This draft has benefited from thoughtful discussion by Emile Baizel, 319 Joe Gregorio, Michal Gregr, Jim Luther, Jaroslav Mazanec, and Jim 320 Whitehead. 322 9. References 324 9.1 Normative References 326 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 327 Requirement Levels", BCP 14, RFC 2119, March 1997. 329 [RFC2518] Goland, Y., Whitehead, E., Faizi, A., Carter, S., and D. 330 Jensen, "HTTP Extensions for Distributed Authoring -- 331 WEBDAV", RFC 2518, February 1999. 333 [RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., 334 Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext 335 Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999. 337 [RFC3023] Murata, M., St.Laurent, S., and D. Kohn, "XML Media 338 Types", RFC 3023, January 2001. 340 [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform 341 Resource Identifier (URI): Generic Syntax", STD 66, 342 RFC 3986, January 2005. 344 [XML] Bray, T., Paoli, J., Sperberg-McQueen, C., Maler, E., and 345 F. Yergeau, "Extensible Markup Language (XML) 1.0 (Third 346 Edition)", W3C REC-xml-20040204, February 2004, 347 . 349 9.2 Informative References 351 [RFC3470] Hollenbeck, S., Rose, M., and L. Masinter, "Guidelines for 352 the Use of Extensible Markup Language (XML) within IETF 353 Protocols", RFC 3470, BCP 70, January 2003. 355 [WEBARCH] Walsh, N. and I. Jacobs, "Architecture of the World Wide 356 Web, Volume One", W3C REC REC-webarch-20041215, 357 December 2004, 358 . 360 Author's Address 362 Julian F. Reschke 363 greenbytes GmbH 364 Salzmannstrasse 152 365 Muenster, NW 48159 366 Germany 368 Phone: +49 251 2807760 369 Fax: +49 251 2807761 370 Email: julian.reschke@greenbytes.de 371 URI: http://greenbytes.de/tech/webdav/ 373 Appendix A. Alternative approaches 375 A.1 ...through HTML/CSS extensions 377 Microsoft Internet Explorer implements a CSS extension that allows 378 switching to it's own WebDAV client ("Webfolder", see ). However, at the time of this writing this extension 381 was not implemented by any other user agent. 383 A.2 ...through custom URI schemes 385 The "kio" library of the "K Desktop Enviroment" 386 () uses the URI scheme "webdav" to dispatch to 387 the system's WebDAV client. This URI scheme is not registered, nor 388 supported on other platforms. Furthermore, W3C's "Architecture of 389 the World Wide Web, Volume One" explicitly advises against defining 390 new schemes when existing schemes can be used: 392 "A specification SHOULD reuse an existing URI scheme (rather than 393 create a new one) when it provides the desired properties of 394 identifiers and their relation to resources." 396 (see [WEBARCH], Section 2.4) 398 Appendix B. Implementations 400 B.1 Example implementation for Webfolder client 402 The figure below shows a sample implementation of a dispatcher for 403 the application/davmount+xml datatype, suited for Win32 systems and 404 the Microsoft "Webfolder" client. 406 // sample implementation of application/davmount+xml 407 // dispatcher for Windows Webfolder client 408 // 409 // to install/uninstall: 410 // wscript davmount.js 411 // 412 // to open the webfolder: 413 // wscript davmount.js filename 414 // (where filename refers to an XML document with MIME type 415 // application/davmount+xml) 417 var EXTENSION = ".davmount"; 418 var MIMETYPE = "application/davmount+xml"; 419 var REGKW = "WebDAV.mount"; 420 var NS = "xmlns:m='http://purl.org/NET/webdav/mount"; 422 // remove keys/entries from the registry 424 function regdel(shell, key) { 425 try { 426 var x = shell.RegRead(key); 427 try { 428 shell.RegDelete(key); 429 } 430 catch(e) { 431 WScript.Echo("Error removing key " + key + ": " + e); 432 } 433 } 434 catch(e) { 435 // entry not present 436 } 437 } 439 // methods for registering/unregistering the handler 441 function install() { 443 var WshShell = new ActiveXObject("WScript.Shell"); 444 if (WshShell == null) { 445 WScript.Echo("Couldn't instantiate WScript.Shell object"); 446 return 2; 447 } 449 var fso = new ActiveXObject("Scripting.FileSystemObject"); 451 var RegExt = "HKCR\\" + EXTENSION + "\\"; 452 var RegMimeType = "HKCR\\MIME\\DataBase\\Content Type\\" 453 + MIMETYPE + "\\"; 454 var RegKw = "HKCR\\" + REGKW + "\\"; 456 var extension = null; 457 try { 458 extension = WshShell.RegRead(RegMimeType + "Extension"); 459 } 460 catch (e) { 461 } 463 if (extension == null) { 464 var but = WshShell.popup("Install the dispatcher for mime type " 465 + MIMETYPE + "?", 0, MIMETYPE + " installation", 4); 467 if (but == 6) { 468 try { 469 WshShell.RegWrite(RegExt, REGKW); 470 WshShell.RegWrite(RegExt + "Content Type", MIMETYPE); 471 WshShell.RegWrite(RegMimeType + "Extension", EXTENSION); 472 WshShell.RegWrite(RegKw, "WebDAV Mount Request"); 473 WshShell.RegWrite(RegKw + "DefaultIcon\\", 474 "shell32.dll,103"); 475 var path = fso.getAbsolutePathName("davmount.js"); 476 WshShell.RegWrite(RegKw + "shell\\open\\command\\", 477 "%SystemRoot%\\system32\\wscript.exe /nologo \"" 478 + path + "\" \"%1\"", "REG_EXPAND_SZ"); 479 } 480 catch (e) { 481 WScript.Echo("Error writing to registry"); 482 return 1; 483 } 485 return 0; 486 } 487 else { 488 return 1; 489 } 490 } 491 else { 492 var but = WshShell.popup("Remove the dispatcher for mime type " 493 + MIMETYPE + "?", 0, MIMETYPE + " installation", 4); 495 if (but == 6) { 496 regdel(WshShell, RegExt + "Content Type"); 497 regdel(WshShell, RegExt); 498 regdel(WshShell, RegKw + "shell\\open\\command\\"); 499 regdel(WshShell, RegKw + "DefaultIcon\\"); 500 regdel(WshShell, RegKw); 501 regdel(WshShell, RegMimeType + "Extension"); 502 regdel(WshShell, RegMimeType); 503 return 0; 504 } 505 else { 506 return 1; 507 } 508 } 509 } 511 if (WScript.Arguments.length == 0) { 512 // install/uninstall 513 WScript.Quit(install()); 514 } 515 else { 516 // try to invoke Webfolder 518 var inp = new ActiveXObject("MSXML2.DOMDocument"); 519 if (! inp.load(WScript.Arguments(0))) { 520 WScript.Echo("Can't read from '" 521 + WScript.Arguments(0) + "'!"); 522 WScript.Quit(2); 523 } 525 inp.setProperty("SelectionLanguage", "XPath"); 526 inp.setProperty("SelectionNamespaces", 527 "xmlns:m='http://purl.org/NET/webdav/mount'"); 529 var n1 = inp.selectSingleNode("/m:mount/m:url"); 530 var n2 = inp.selectSingleNode("/m:mount/m:open"); 532 if (n1 == null) { 533 WScript.Echo(" element missing."); 534 WScript.Quit(2); 535 } 537 var ie = new ActiveXObject("InternetExplorer.Application"); 539 ie.Navigate("about:blank"); 540 var doc = ie.Document; 542 var folder = doc.createElement("span"); 543 folder.addBehavior("#default#httpFolder"); 545 var result = folder.navigate(n1.text + 546 (n2 == null ? "" : n2.text)); 548 // close the window again when there was no element 549 if (n2 == null) ie.Quit(); 551 if (result != "OK") { 552 if (result == "PROTOCOL_NOT_SUPPORTED") { 553 WScript.Echo("This site doesn't seem to support WebDAV."); 554 WScript.Quit(1); 555 } 556 else { 557 WScript.Echo("Unexpected status: " + result); 558 WScript.Quit(2); 559 } 560 } 561 } 563 B.2 Xythos 565 The "Xythos Drive" WebDAV client for WebDAV supports this 566 specification starting with version 4.4. 568 Appendix C. Change Log (to be removed by RFC Editor before publication) 570 C.1 Since draft-reschke-webdav-mount-00 572 Add implementations section; add sample implementation for Microsoft 573 Webfolder client. Add acknowledgments section. 575 C.2 Since draft-reschke-webdav-mount-01 577 Be consistent in using trailing slashes on collection URLs in 578 examples. Fix webfolder reference impl not to require 579 element. Update acknowledgments. Incorporate some of JimW's 580 suggestions in abstract and introduction. Expand security 581 considerations regarding and fwd-reference it from the spec. 583 Appendix D. Resolved issues (to be removed by RFC Editor before 584 publication) 586 Issues that were either rejected or resolved in this version of this 587 document. 589 D.1 wfimplopennotoptional 591 Type: change 593 julian.reschke@greenbytes.de (2005-09-22): Fix Webfolder reference 594 impl not to require open element. 596 Resolution (2005-09-22): Fixed. 598 Appendix E. Open issues (to be removed by RFC Editor prior to 599 publication) 601 E.1 edit 603 Type: edit 605 julian.reschke@greenbytes.de (2005-09-17): Umbrella issue for 606 editorial fixes/enhancements. 608 Index 610 A 611 application/mount 612 xml MIME type 6 614 D 615 dm:mount 5 616 dm:opent 5 617 dm:url 5 618 dm:username 5 620 M 621 MIME type 622 application/mount 6 624 Intellectual Property Statement 626 The IETF takes no position regarding the validity or scope of any 627 Intellectual Property Rights or other rights that might be claimed to 628 pertain to the implementation or use of the technology described in 629 this document or the extent to which any license under such rights 630 might or might not be available; nor does it represent that it has 631 made any independent effort to identify any such rights. Information 632 on the procedures with respect to rights in RFC documents can be 633 found in BCP 78 and BCP 79. 635 Copies of IPR disclosures made to the IETF Secretariat and any 636 assurances of licenses to be made available, or the result of an 637 attempt made to obtain a general license or permission for the use of 638 such proprietary rights by implementers or users of this 639 specification can be obtained from the IETF on-line IPR repository at 640 http://www.ietf.org/ipr. 642 The IETF invites any interested party to bring to its attention any 643 copyrights, patents or patent applications, or other proprietary 644 rights that may cover technology that may be required to implement 645 this standard. Please address the information to the IETF at 646 ietf-ipr@ietf.org. 648 Disclaimer of Validity 650 This document and the information contained herein are provided on an 651 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 652 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 653 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 654 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 655 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 656 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 658 Copyright Statement 660 Copyright (C) The Internet Society (2005). This document is subject 661 to the rights, licenses and restrictions contained in BCP 78, and 662 except as set forth therein, the authors retain all their rights. 664 Acknowledgment 666 Funding for the RFC Editor function is currently provided by the 667 Internet Society.