RFC 2368 on The mailto URL scheme
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RFC 2368 on The mailto URL scheme



A new Request for Comments is now available in online RFC libraries.


        RFC 2368:

        Title:      The mailto URL scheme
	Author(s):  P. Hoffman, L. Masinter, J. Zawinski
	Status:     Proposed Standard
	Date:       July 1998
        Mailbox:    phoffman at imc.org, masinter at parc.xerox.com,
		    jwz at netscape.com
	Pages:      10
        Characters: 16502
        Updates:    1738, 1808

        URL:        ftp://ftp.isi.edu/in-notes/rfc2368.txt


This document defines the format of Uniform Resource Locators (URL)
for designating electronic mail addresses. It is one of a suite of
documents which replace RFC 1738, 'Uniform Resource Locators', and
RFC 1808, 'Relative Uniform Resource Locators'. The syntax of
'mailto' URLs from RFC 1738 is extended to allow creation of more RFC
822 messages by allowing the URL to express additional header and body
fields.

This is now a Proposed 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 at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info at RFC-EDITOR.ORG
        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 RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Alegre Ramos
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.
<ftp://ftp.isi.edu/in-notes/rfc2368.txt>

Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.

Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.