A new Request for Comments is now available in online RFC libraries.
RFC 1808:
Title: Relative Uniform Resource Locators
Author: R. Fielding
Date: June 1995
Mailbox: fielding@ics.uci.edu
Pages: 16
Characters: 34,950
Updates/Obsoletes: none
URL: ftp://ds.internic.net/rfc/rfc1808.txt
A Uniform Resource Locator (URL) is a compact representation of the
location and access method for a resource available via the Internet.
When embedded within a base document, a URL in its absolute form may
contain a great deal of information which is already known from the
context of that base document's retrieval, including the scheme,
network location, and parts of the url-path. In situations where the
base URL is well-defined and known to the parser (human or machine),
it is useful to be able to embed URL references which inherit that
context rather than re-specifying it in every instance. This document
defines the syntax and semantics for such Relative Uniform Resource
Locators. This RFC is the product of the Uniform Resource Identifiers
Working Group of the IETF.
This is now a Prosposed Standard Protocol.
This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state and
status of this protocol. Distribution of this memo is unlimited.
This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@CNRI.RESTON.VA.US. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@ISI.EDU.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@ISI.EDU with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info@ISI.EDU
Subject: getting rfcs
help: ways_to_get_rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to admin@DS.INTERNIC.NET. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
Submissions for Requests for Comments should be sent to
RFC-EDITOR@ISI.EDU. Please consult RFC 1543, Instructions to RFC
Authors, for further information.
Joyce K. Reynolds
USC/Information Sciences Institute
..
Below is the data which will enable a MIME compliant Mail Reader
implementation to automatically retrieve the ASCII version
of the RFCs.
--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"
--OtherAccess
Content-Type: Message/External-body;
access-type="mail-server";
server="mailserv@ds.internic.net"
Content-Type: text/plain
Content-ID: <950614083714.RFC@ISI.EDU>
SEND /rfc/rfc1808.txt
--OtherAccess
Content-Type: Message/External-body;
name="rfc1808.txt";
site="ds.internic.net";
access-type="anon-ftp";
directory="rfc"
Content-Type: text/plain
Content-ID: <950614083714.RFC@ISI.EDU>
--OtherAccess--
--NextPart--