The prospero URI Scheme (RFC4157)
Original Publication Date: 2005-Aug-01
Included in the Prior Art Database: 2005-Aug-27
Internet Society Requests For Comment (RFCs)
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.
Network Working Group P.
Request for Comments: 4157 VPN Consortium
Category: Historic August 2005
The prospero URI Scheme
Status of 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 (C) The Internet Society (2005).
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.
previously defined in RFC 2396 [RFC2396], which was updated
by RFC 3986 [RFC3986]. Those documents also specify how to define
schemes for URIs.
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.
2. Scheme Definition
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].
The Prospero protocol was not widely implemented and
almost no Prospero servers are in use today.
A prospero URL takes the form:
Hoffman Historic [Page 1]
RFC 4157 The prospero URI Scheme August 2005
If :<port> is omitted, the port defaults to 1525. No username or
password is allowed.
<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>.
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.
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 structu...