Network Working Group                                         P. Hoffman
Request for Comments: 4156                                VPN Consortium
Category: Historic                                           August 2005
        
Network Working Group                                         P. Hoffman
Request for Comments: 4156                                VPN Consortium
Category: Historic                                           August 2005

The wais URI Scheme

wais-URI方案

Status of This Memo

关于下段备忘

This memo defines a Historic Document for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited.

此备忘录定义了互联网社区的历史文档。它没有规定任何类型的互联网标准。本备忘录的分发不受限制。

Copyright Notice

版权公告

Copyright (C) The Internet Society (2005).

版权所有（C）互联网协会（2005年）。

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 made obsolete while keeping the information about the scheme on standards track.

本文档指定了最初在RFC 1738中指定的wais统一资源标识符（URI）方案。本文件的目的是使RFC 1738过时，同时将有关方案的信息保持在标准轨道上。

1. Introduction
1. 介绍

URIs were previously defined in RFC 2396 [RFC2396], which was updated by RFC 3986 [RFC3986]. Those documents also specify how to define schemes for URIs.

URI先前在RFC 2396[RFC2396]中定义，并由RFC 3986[RFC3986]更新。这些文档还指定了如何定义URI的方案。

The first definitions for many URI schemes appeared in RFC 1738 [RFC1738]. Because that document has been made obsolete, this document copies the wais URI scheme from it to allow that material to remain on standards track.

许多URI方案的最初定义出现在RFC1738[RFC1738]中。由于该文档已过时，因此本文档将从中复制wais URI方案，以使该材料保持在标准轨道上。

2. Scheme Definition
2. 方案定义

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.

WAIS URL方案用于指定WAIS数据库、搜索或WAIS数据库中可用的单个文档。RFC 1625[RFC1625]中描述了WAIS协议。尽管WAIS协议基于Z39.50-1988，但WAIS URL方案不适用于任意Z39.50服务。

Historical note: The WAIS protocol was not widely implemented and almost no WAIS servers are in use today.

历史注释：WAIS协议未得到广泛实施，目前几乎没有使用WAIS服务器。

A WAIS URL takes one of the following forms:

WAIS URL采用以下形式之一： 

      wais://<host>:<port>/<database>
      wais://<host>:<port>/<database>?<search>
      wais://<host>:<port>/<database>/<wtype>/<wpath>
        
      wais://<host>:<port>/<database>
      wais://<host>:<port>/<database>?<search>
      wais://<host>:<port>/<database>/<wtype>/<wpath>

If :<port> 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. <database> is the name of the WAIS database being queried.

如果省略：<port>，则端口默认为210。第一个表单指定可用于搜索的WAIS数据库。第二个表单指定一个特定的搜索<database>是正在查询的WAIS数据库的名称。

The third form designates a particular document, within a WAIS database, to be retrieved. In this form <wtype> 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 is returned along with the internal object identifier in the search response. The <wtype> is included in the URL in order to give the client interpreting the URL adequate information to actually retrieve the document.

第三个表单指定要检索的WAIS数据库中的特定文档。在这种形式中，<wtype>是对象类型的WAIS名称。许多WAIS实现要求客户端在检索之前知道对象的“类型”；在搜索响应中，该类型与内部对象标识符一起返回。URL中包含<wtype>，以便为解释URL的客户端提供足够的信息，以便实际检索文档。

The <wpath> 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.

WAIS URL的<wpath>由WAIS文档id组成。WAIS文档id应不透明处理；它只能由发布它的服务器分解。

3. Security Considerations
3. 安全考虑

Many security considerations for URI schemes are discussed in [RFC3986]. There are no security considerations listed in [RFC1625], but it should be noted that there is no privacy nor authentication specified in the WAIS protocol.

[RFC3986]中讨论了URI方案的许多安全注意事项。[RFC1625]中没有列出安全考虑因素，但应注意的是，WAIS协议中没有指定隐私或身份验证。

4. Informative References
4. 资料性引用

[RFC1738] Berners-Lee, T., Masinter, L., and M. McCahill, "Uniform Resource Locators (URL)", RFC 1738, December 1994.

[RFC1738]Berners Lee，T.，Masinter，L.，和M.McCahill，“统一资源定位器（URL）”，RFC 17381994年12月。

[RFC2396] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform Resource Identifiers (URI): Generic Syntax", RFC 2396, August 1998.

[RFC2396]Berners Lee，T.，Fielding，R.，和L.Masinter，“统一资源标识符（URI）：通用语法”，RFC 2396，1998年8月。

[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform Resource Identifier (URI): Generic Syntax", STD 66, RFC 3986, January 2005.

[RFC3986]Berners Lee，T.，Fielding，R.，和L.Masinter，“统一资源标识符（URI）：通用语法”，STD 66，RFC 3986，2005年1月。

[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.

[RFC1625]圣皮埃尔，M.，富尔顿，J.，加米尔，K.，戈德曼，J.，卡勒，B.，昆泽，J.，莫里斯，H.，和F.希特卡特，“Z39.50-1988年的WAIS”，RFC 16251994年6月。

Author's Address

作者地址

Paul Hoffman VPN Consortium 127 Segre Place Santa Cruz, CA 95060 US

美国加利福尼亚州圣克鲁斯塞格雷广场127号保罗·霍夫曼私人有限公司，邮编95060 

   EMail: paul.hoffman@vpnc.org
        
   EMail: paul.hoffman@vpnc.org

Full Copyright Statement

完整版权声明

Copyright (C) The Internet Society (2005).

版权所有（C）互联网协会（2005年）。

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.

本文件受BCP 78中包含的权利、许可和限制的约束，除其中规定外，作者保留其所有权利。

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.

本文件及其包含的信息是按“原样”提供的，贡献者、他/她所代表或赞助的组织（如有）、互联网协会和互联网工程任务组不承担任何明示或暗示的担保，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。

Intellectual Property

知识产权

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.

IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何独立努力来确定任何此类权利。有关RFC文件中权利的程序信息，请参见BCP 78和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.

向IETF秘书处披露的知识产权副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果，可从IETF在线知识产权存储库获取，网址为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.

IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涵盖实施本标准所需技术的专有权利。请将信息发送至IETF的IETF-ipr@ietf.org.

Acknowledgement

确认

Funding for the RFC Editor function is currently provided by the Internet Society.

RFC编辑功能的资金目前由互联网协会提供。