W3C home > Mailing lists > Public > ietf-http-wg-old@w3.org > September to December 1997

I-D ACTION:draft-ietf-http-pep-05.txt

From: <Internet-Drafts@ns.ietf.org>
Date: Fri, 05 Dec 1997 11:14:08 -0500
Message-Id: <199712051614.LAA15578@ns.ietf.org>
To: IETF-Announce@ns.ietf.org
Cc: http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
X-Mailing-List: <http-wg@cuckoo.hpl.hp.com> archive/latest/4846
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the HyperText Transfer Protocol Working Group 
of the IETF.

	Title		: PEP - an Extension Mechanism for HTTP
	Author(s)	: D. Connolly, H. Nielsen, R. Khare, 
                          E. Prud'hommeaux
	Filename	: draft-ietf-http-pep-05.txt
	Pages		: 28
	Date		: 04-Dec-97
       HTTP is used increasingly in applications that need more facilities
       than the standard version of the protocol provides, ranging from
       distributed authoring, collaboration, and printing, to various remote        procedure call mechanisms. The Protocol Extension Protocol (PEP) is an
       extension mechanism designed to address the tension between private
       agreement and public specification and to accommodate extension of
       applications such as HTTP clients, servers, and proxies. The PEP
       mechanism is designed to associate each extension with a URI[2], and
       use a few new RFC 822[1] derived header fields to carry the extension
       identifier and related information between the parties involved in an
       extended transaction.
       This document defines PEP and describes the interactions between PEP
       and HTTP/1.1[7]. PEP is intended to be compatible with HTTP/1.0[5]
       inasmuch as HTTP/1.1 is compatible with HTTP/1.0 (see [7], section
       19.7). It is proposed that the PEP extension mechanism be included in
       future versions of HTTP.
       The PEP extension mechanism may be applicable to other information
       exchange not mentioned in this document. It is recommended that
       readers get acquainted with section 1.4 for a suggested reading of
       this specification and a list of sections specific for HTTP based

Internet-Drafts are available by anonymous FTP.  Login with the username
"anonymous" and a password of your e-mail address.  After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-http-pep-05.txt".
A URL for the Internet-Draft is:

Internet-Drafts directories are located at:

	Africa:	ftp.is.co.za
	Europe: ftp.nordu.net
	Pacific Rim: munnari.oz.au
	US East Coast: ds.internic.net
	US West Coast: ftp.isi.edu

Internet-Drafts are also available by mail.

Send a message to:	mailserv@ds.internic.net.  In the body type:
	"FILE /internet-drafts/draft-ietf-http-pep-05.txt".
NOTE:	The mail server at ds.internic.net can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the

Received on Friday, 5 December 1997 08:22:21 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:40:21 UTC