>From ipp-owner at pwg.org Fri Jul 31 17:14:04 1998
Received: from mailhub.btwebworld.com [193.113.211.246]
by neodymium.btinternet.com with smtp (Exim 1.70 #1)
id 0z2Hog-0005kZ-00; Fri, 31 Jul 1998 17:14:02 +0100
Received: from mail.btwebworld.com by mailhub.btwebworld.com (SMI-8.6/SMI-SVR4)
id RAA22854; Fri, 31 Jul 1998 17:15:04 +0100
Received: by mail.btwebworld.com (SMI-8.6/SMI-SVR4)
id RAA27801; Fri, 31 Jul 1998 17:13:47 +0100
Received: from lists.underscore.com (actually host uscore-1.mv.com) by mail.btwebworld.com with SMTP (Messageware MTA (NEXOR)) with ESMTP; Thu, 30 Jul 1998 16:13:12 -2400
Received: from localhost (daemon at localhost) by lists.underscore.com (8.7.5/8.7.3) with SMTP id MAA01684 for <C.Lacey at datatrade.co.uk>; Fri, 31 Jul 1998 12:14:18 -0400 (EDT)
Received: by pwg.org (bulk_mailer v1.5); Fri, 31 Jul 1998 12:14:02 -0400
Received: (from daemon at localhost) by lists.underscore.com (8.7.5/8.7.3) id MAA01636 for ipp-outgoing; Fri, 31 Jul 1998 12:10:59 -0400 (EDT)
Message-ID: <3683AF7E2328D211A2BA00805F15CE8505CC32 at x-crt-es-ms1.cp10.es.xerox.com>
From: "Manros, Carl-Uno B" <cmanros at cp10.es.xerox.com>
To: "'IETF-IPP'" <ipp at pwg.org>
Subject: IPP> FW: I-D ACTION:draft-ietf-http-v11-spec-rev-04.txt
Date: Fri, 31 Jul 1998 09:07:50 PDT
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.1960.3)
Content-Type: multipart/mixed;
boundary="---- =_NextPart_000_01BDBC9D.5E02DC18"
Sender: owner-ipp at pwg.org
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------ =_NextPart_000_01BDBC9D.5E02DC18
Content-Type: text/plain
FYI,
This text for HTTP 1.1 is likely to soon replace RFC 2068.
Carl-Uno
-----Original Message-----
From: Internet-Drafts at ietf.org [mailto:Internet-Drafts at ietf.org]
Sent: Thursday, July 30, 1998 6:47 AM
To: IETF-Announce
Cc: http-wg at cuckoo.hpl.hp.com
Subject: I-D ACTION:draft-ietf-http-v11-spec-rev-04.txt
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 : Hypertext Transfer Protocol -- HTTP/1.1
Author(s) : J. Mogul, T. Berners-Lee, L. Masinter,
P. Leach, R. Fielding, H. Nielsen, J. Gettys
Filename : draft-ietf-http-v11-spec-rev-04.txt
Pages : 155
Date : 29-Jul-98
The Hypertext Transfer Protocol (HTTP) is an application-level protocol
for distributed, collaborative, hypermedia information systems. It is a
generic, stateless, protocol which can be used for many tasks, such as
name servers and distributed object management systems, through
extension of its request methods. A feature of HTTP is the typing and
negotiation of data representation, allowing systems to be built
independently of the data being transferred.
HTTP has been in use by the World-Wide Web global information initiative
since 1990. This specification defines the protocol referred to as
'HTTP/1.1', and is an update to RFC2068 [33].
At the time of submission, there were no remaining outstanding issues
after a working group last call. The HTTP/1.1 issues list can be found
at http://www.w3.org/Protocols/HTTP/Issues/. Linked from this page are
also Postscript and Microsoft Word versions (with versions with change
bars) of this document which are easier to review than this text
document.
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-v11-spec-rev-04.txt".
A URL for the Internet-Draft is:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-http-v11-spec-rev-04.txt
Internet-Drafts directories are located at:
Africa: ftp.is.co.za
Europe: ftp.nordu.net
ftp.nis.garr.it
Pacific Rim: munnari.oz.au
US East Coast: ftp.ietf.org
US West Coast: ftp.isi.edu
Internet-Drafts are also available by mail.
Send a message to: mailserv at ietf.org. In the body type:
"FILE /internet-drafts/draft-ietf-http-v11-spec-rev-04.txt".
NOTE: The mail server at ietf.org 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
Internet-Draft.
------ =_NextPart_000_01BDBC9D.5E02DC18
Content-Type: message/rfc822
To:
Subject:
Date: Fri, 31 Jul 1998 08:33:27 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.1960.3)
Content-Type: multipart/mixed;
boundary="---- =_NextPart_002_01BDBC9D.5E02DC18"
------ =_NextPart_002_01BDBC9D.5E02DC18
Content-Type: text/plain
------ =_NextPart_002_01BDBC9D.5E02DC18
Content-Type: application/octet-stream;
name="ATT01830.txt"
Content-Disposition: attachment;
filename="ATT01830.txt"
Content-type: message/external-body;
access-type="mail-server";
server="mailserv at ietf.org"
Content-Type: text/plain
Content-ID: <19980729123623.I-D at ietf.org>
ENCODING mime
FILE /internet-drafts/draft-ietf-http-v11-spec-rev-04.txt
------ =_NextPart_002_01BDBC9D.5E02DC18
Content-Type: message/external-body;
site="internet-drafts";
dir="draft-ietf-http-v11-spec-rev-04.txt";
mode="ftp.ietf.org";
access-type="anon-ftp"
------ =_NextPart_002_01BDBC9D.5E02DC18--
------ =_NextPart_000_01BDBC9D.5E02DC18--