RE: Protocol Action: Upgrading to TLS Within HTTP/1.1 to Proposed Standard

Date view Thread view Subject view Author view

From: Josh Cohen (joshco@Exchange.Microsoft.com)
Date: Mon Jan 31 2000 - 17:33:41 PST


so, does anyone know where the two required
interaoperable implementations are ?

> -----Original Message-----
> From: Rohit Khare [mailto:rohit@uci.edu]
> Sent: Monday, January 31, 2000 2:47 PM
> To: FoRK@xent.com
> Subject: Fwd: Protocol Action: Upgrading to TLS Within HTTP/1.1 to
> Proposed Standard
>
>
> >To: IETF-Announce: ;
> >Cc: RFC Editor <rfc-editor@isi.edu>
> >Cc: Internet Architecture Board <iab@isi.edu>
> >Cc: ietf-tls@consensus.com
> >From: The IESG <iesg-secretary@ietf.org>
> >Subject: Protocol Action: Upgrading to TLS Within HTTP/1.1
> to Proposed
> > Standard
> >Date: Mon, 31 Jan 2000 15:52:52 -0500
> >Sender: scoya@cnri.reston.va.us
> >
> >
> >
> >The IESG has approved the Internet-Draft 'Upgrading to TLS Within
> >HTTP/1.1' <draft-ietf-tls-http-upgrade-05.txt> as a Proposed
> Standard.
> >This document is the product of the Transport Layer Security Working
> >Group. The IESG contact persons are Jeffrey Schiller and Marcus
> >Leech.
> >
> >
> >
> >Technical Summary
> >
> >'HTTP Over TLS' documents how TLS is used today to secure 'https' URL
> >connections. 'Upgrading to TLS Within HTTP/1.1' defines a
> mechanism for
> >"upgrading" a non-secure http connection to a secure
> connection making
> >use of TLS without requiring the use of an additional port
> (as is used
> >in https). This is important because protocols beyond simple web
> >browsing are being layered on top of HTTP. For each such
> protocol today
> >we require two new port assignments. One of the protocol
> without TLS and
> >one for the protocol with TLS. The adoption of the
> techniques described
> >in 'Upgrading to TLS Within HTTP/1.1' will alleviate the need for the
> >second port, thus preserving our scarce TCP port space.
> >
> >Working Group Summary
> >
> >The working group supports these documents and the versions of the
> >documents here address the issues raised during IETF Wide last call.
> >
> >Protocol Quality
> >
> >Jeff Schiller has reviewed these documents for the IESG.
>


Date view Thread view Subject view Author view

This archive was generated by hypermail 2b29 : Mon Jan 31 2000 - 19:53:21 PST