------_=_NextPart_000_01BEBE64.E7091CF6
Content-Type: text/plain;
charset="ISO-8859-1"
FYI,
Carl-Uno
-----Original Message-----
From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
Sent: Thursday, June 24, 1999 4:24 AM
To: IETF Transport Layer Security WG
Cc: ietf-tls@consensus.com
Subject: I-D ACTION:draft-ietf-tls-http-upgrade-01.txt
A New Internet-Draft is available from the on-line Internet-Drafts
directories.
This draft is a work item of the Transport Layer Security Working Group of
the IETF.
Title : Upgrading to TLS Within HTTP/1.1
Author(s) : R. Khare, S. Lawrence
Filename : draft-ietf-tls-http-upgrade-01.txt
Pages : 12
Date : 23-Jun-99
This memo proposes a mechanism to upgrade HTTP/1.1 connections to use
Transport Layer Security (TLS). Using an Upgrade: TLS/x.y request
header would allow unsecured and secured traffic to share the same
port (in this case, 80). A companion document describes the current
practice of using a separate port for HTTP over TLS,
<draft-ietf-tls-https-01.txt>.
A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-tls-http-upgrade-01.txt
Internet-Drafts are also 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-tls-http-upgrade-01.txt".
A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
Internet-Drafts can also be obtained by e-mail.
Send a message to:
mailserv@ietf.org.
In the body type:
"FILE /internet-drafts/draft-ietf-tls-http-upgrade-01.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_01BEBE64.E7091CF6
Content-Type: message/rfc822
Content-Location: ATT-0-6863F57D402AD311A2DA00805F15CE85
To:
Subject:
Date: Thu, 24 Jun 1999 10:00:34 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2232.9)
Content-Type: multipart/mixed;
boundary="----_=_NextPart_002_01BEBE64.E7091CF6"
------_=_NextPart_002_01BEBE64.E7091CF6
Content-Type: text/plain
------_=_NextPart_002_01BEBE64.E7091CF6
Content-Type: application/octet-stream;
name="ATT28630.txt"
Content-Disposition: attachment;
filename="ATT28630.txt"
Content-Location: ATT-0-6663F57D402AD311A2DA00805F15CE85-A
TT28630.txt
Content-type: message/external-body;
access-type="mail-server";
server="mailserv@ietf.org"
Content-Type: text/plain
Content-ID: <19990623144244.I-D@ietf.org>
ENCODING mime
FILE /internet-drafts/draft-ietf-tls-http-upgrade-01.txt
------_=_NextPart_002_01BEBE64.E7091CF6
Content-Type: message/external-body;
site="internet-drafts";
dir="draft-ietf-tls-http-upgrade-01.txt";
mode="ftp.ietf.org";
access-type="anon-ftp"
Content-Location: ATT-1-6763F57D402AD311A2DA00805F15CE85-d
raft-ie.url
------_=_NextPart_002_01BEBE64.E7091CF6--
------_=_NextPart_000_01BEBE64.E7091CF6--