Network Working Group P. Hoffman Internet-Draft VPN Consortium Expires: March 19, 2005 September 18, 2004 The wais URI Scheme draft-hoffman-wais-uri-01.txt Status of this Memo By submitting this Internet-Draft, I certify that any applicable patent or other IPR claims of which I am aware have been disclosed, and any of which I become aware will be disclosed, in accordance with RFC 3668. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. This Internet-Draft will expire on March 19, 2005. Copyright Notice Copyright (C) The Internet Society (2004). All Rights Reserved. Abstract This document specifies the wais Uniform Resource Identifier (URI) scheme that was originally specified in RFC 1738. The purpose of this document is to allow RFC 1738 to be moved to historic while keeping the information about the scheme on standards track. 1. Introduction URIs are were previously defined in RFC 2396 [RFC2396], which was updated by draft-fielding-uri-rfc2396bis [2396bis]. Those documents also specify how to define schemes for URIs. Hoffman Expires March 19, 2005 [Page 1] Internet-Draft The wais URI Scheme September 2004 The first definition for many URI schemes appeared in RFC 1738 [RFC1738]. Because that document has been moved to Historic status, this document copies the wais URI scheme from it to allow that material to remain on standards track. 2. Scheme Definition The WAIS URL scheme is used to designate WAIS databases, searches, or individual documents available from a WAIS database. The WAIS protocol is described in RFC 1625 [RFC1625]. Although the WAIS protocol is based on Z39.50-1988, the WAIS URL scheme is not intended for use with arbitrary Z39.50 services. Historical note: The WAIS protocol was not widely implemented and almost no WAIS servers are in use today. A WAIS URL takes one of the following forms: wais://:/ wais://:/? wais://:/// If : is omitted, the port defaults to 210. The first form designates a WAIS database that is available for searching. The second form designates a particular search. is the name of the WAIS database being queried. The third form designates a particular document within a WAIS database to be retrieved. In this form is the WAIS designation of the type of the object. Many WAIS implementations require that a client know the "type" of an object prior to retrieval, the type being returned along with the internal object identifier in the search response. The is included in the URL in order to allow the client interpreting the URL adequate information to actually retrieve the document. The of a WAIS URL consists of the WAIS document-id. The WAIS document-id should be treated opaquely; it may only be decomposed by the server that issued it. 3. Security Considerations There are many security considerations for URI schemes discussed in draft-fielding-uri-rfc2396bis [2396bis]. 4 Informative References [RFC1738] Berners-Lee, T., Masinter, L. and M. McCahill, "Uniform Hoffman Expires March 19, 2005 [Page 2] Internet-Draft The wais URI Scheme September 2004 Resource Locators (URL)", RFC 1738, December 1994. [RFC2396] Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform Resource Identifiers (URI): Generic Syntax", RFC 2396, August 1998. [2396bis] Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform Resource Identifiers (URI): Generic Syntax", work in progress, draft-fielding-uri-rfc2396bis-nn.txt. [RFC1625] St. Pierre, M., Fullton, J., Gamiel, K., Goldman, J., Kahle, B., Kunze, J., Morris, H. and F. Schiettecatte, "WAIS over Z39.50-1988", RFC 1625, June 1994. Author's Address Paul Hoffman VPN Consortium 127 Segre Place Santa Cruz, CA 95060 US EMail: paul.hoffman@vpnc.org Hoffman Expires March 19, 2005 [Page 3] Internet-Draft The wais URI Scheme September 2004 Intellectual Property Statement The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79. Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org. Disclaimer of Validity This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Copyright Statement Copyright (C) The Internet Society (2004). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. Acknowledgment Funding for the RFC Editor function is currently provided by the Internet Society. Hoffman Expires March 19, 2005 [Page 4]