Network Working Group P. Hoffman
Request for Comments: 4157 VPN Consortium
Category: Historic August 2005
Network Working Group P. Hoffman
Request for Comments: 4157 VPN Consortium
Category: Historic August 2005
The prospero URI Scheme
prospero 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 prospero 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中指定的prospero统一资源标识符（URI）方案。本文件的目的是使RFC 1738过时，同时将有关方案的信息保持在标准轨道上。
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 prospero URI scheme from it to allow that material to remain on standards track.
许多URI方案的最初定义出现在RFC1738[RFC1738]中。由于该文档已过时，因此本文档将从中复制prospero URI方案，以使该材料保持在标准轨道上。
The prospero URL scheme is used to designate resources that are accessed through the Prospero Directory Service. The Prospero protocol is described in the original Prospero specification [PROSP].
prospero URL方案用于指定通过prospero目录服务访问的资源。Prospero协议在原始Prospero规范[PROSP]中进行了描述。
Historical note: The Prospero protocol was not widely implemented and almost no Prospero servers are in use today.
历史记录：Prospero协议并未得到广泛实施，目前几乎没有使用Prospero服务器。
A prospero URL takes the form:
prospero URL的形式如下：
prospero://<host>:<port>/<hsoname>;<field>=<value>
prospero://<host>:<port>/<hsoname>;<field>=<value>
If :<port> is omitted, the port defaults to 1525. No username or password is allowed.
如果省略：<port>，则端口默认为1525。不允许使用用户名或密码。
The <hsoname> is the host-specific object name in the Prospero protocol, suitably encoded. This name is opaque and interpreted by the Prospero server. The semicolon ";" is reserved and may not appear without quoting in the <hsoname>.
<hsoname>是Prospero协议中特定于主机的对象名，经过适当编码。此名称不透明，由Prospero服务器解释。分号“；”是保留的，在<hsoname>中不加引号不得出现。
Prospero URLs are interpreted by contacting a Prospero directory server on the specified host and port to determine appropriate access methods for a resource. The access methods might themselves be represented as different URLs. External Prospero links are represented as URLs of the underlying access method and are not represented as Prospero URLs.
Prospero URL通过联系指定主机和端口上的Prospero目录服务器来解释，以确定资源的适当访问方法。访问方法本身可能表示为不同的URL。外部Prospero链接表示为基础访问方法的URL，而不是Prospero URL。
Note that a slash "/" may appear in the <hsoname> without quoting, and no significance may be assumed by the application. Though slashes may indicate hierarchical structure on the server, such structure is not guaranteed. Note that many <hsoname>s begin with a slash, in which case the host or port will be followed by a double slash: the slash from the URL syntax, followed by the initial slash from the <hsoname> (e.g., <URL:prospero://example.com//pros/name> designates a <hsoname> of "/pros/name").
请注意，<hsoname>中可能会出现斜杠“/”而不加引号，并且应用程序可能不会假定其重要性。虽然斜杠可能表示服务器上的层次结构，但不能保证这种结构。请注意，许多<hsoname>以斜杠开头，在这种情况下，主机或端口后面将跟一个双斜杠：URL语法中的斜杠，后面是<hsoname>中的初始斜杠（例如，<URL:prospero://example.com//pros/name>指定一个“/pros/name”的<hsoname>。
In addition, after the <hsoname>, optional fields and values associated with a Prospero link may be specified as part of the URL. When present, each field/value pair is separated from each other and from the rest of the URL by a ";" (semicolon). The name of the field and its value are separated by a "=" (equal sign). If present, these fields serve to identify the target of the URL. For example, the OBJECT-VERSION field can be specified to identify a specific version of an object.
此外，在<hsoname>之后，可以将与Prospero链接相关联的可选字段和值指定为URL的一部分。存在时，每个字段/值对彼此分开，并用“；”（分号）与URL的其余部分分开。字段名称及其值用“=”（等号）分隔。如果存在，这些字段用于标识URL的目标。例如，可以指定OBJECT-VERSION字段来标识对象的特定版本。
Many security considerations for URI schemes are discussed in [RFC3986]. [PROSP] uses passwords in the clear for authentication, and offers no privacy, both of which are considered extremely unsafe in current practice.
[RFC3986]中讨论了URI方案的许多安全注意事项。[PROSP]在clear中使用密码进行身份验证，并且不提供隐私，在当前的实践中，这两者都被认为是极不安全的。
[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月。
[PROSP] Neuman, B. and S. Augart, "The Prospero Protocol", USC/Information Sciences Institute, June 1993.
[PROSP]Neuman，B.和S.Augart，“普洛斯彼罗协议”，南加州大学/信息科学研究所，1993年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编辑功能的资金目前由互联网协会提供。