Skip to main content

On the use of HTTP as a Substrate
draft-moore-using-http-01

The information below is for an old version of the document that is already published as an RFC.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 3205.
Author Keith Moore
Last updated 2020-07-29 (Latest revision 2000-10-17)
RFC stream Legacy stream
Intended RFC status Best Current Practice
Formats
Stream Legacy state (None)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Became RFC 3205 (Best Current Practice)
Telechat date (None)
Responsible AD (None)
Send notices to (None)
draft-moore-using-http-01
A new Request for Comments is now available in online RFC libraries.

        BCP 56
        RFC 3205

        Title:      On the use of HTTP as a Substrate
        Author(s):  K. Moore
        Status:     Best Current Practice
        Date:       February 2002
        Mailbox:    moore@cs.utk.edu
        Pages:      14
        Characters: 34785
        Updates/Obsoletes/SeeAlso:  None

        I-D Tag:    draft-moore-using-http-01.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3205.txt

Recently there has been widespread interest in using Hypertext
Transfer Protocol (HTTP) as a substrate for other applications-level
protocols.  This document recommends technical particulars of such
use, including use of default ports, URL schemes, and HTTP security
mechanisms. 

This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements.  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@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

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

        To: rfc-info@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@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@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.