IPP> FW: I-D ACTION:draft-ietf-tls-https-02.txt

IPP> FW: I-D ACTION:draft-ietf-tls-https-02.txt

IPP> FW: I-D ACTION:draft-ietf-tls-https-02.txt

Manros, Carl-Uno B cmanros at cp10.es.xerox.com
Mon Mar 1 12:51:36 EST 1999


John,

You are absolutely right. Can't understand why they don't change the
misleading name of this document.

Carl-Uno

> -----Original Message-----
> From: Wenn, John C [mailto:jwenn at cp10.es.xerox.com]
> Sent: Thursday, February 25, 1999 1:42 PM
> To: Manros, Carl-Uno B; IETF-IPP
> Cc: Wenn, John C; Herriot, Robert
> Subject: RE: IPP> FW: I-D ACTION:draft-ietf-tls-https-02.txt
> 
> 
> This draft describes the old-style/classic/depreciated method of doing
> security by https:// over a separte port number (443).  Since 
> this method
> has specifically been vetoed by the area director, the method 
> isn't one we
> should worry about.
> 
> /John
> 
> > -----Original Message-----
> > From: Manros, Carl-Uno B [mailto:cmanros at cp10.es.xerox.com]
> > Sent: Wednesday, February 24, 1999 3:11 PM
> > To: IETF-IPP
> > Cc: Wenn, John; Herriot, Bob
> > Subject: IPP> FW: I-D ACTION:draft-ietf-tls-https-02.txt
> > 
> > 
> > FYI,
> > 
> > It seems that this document tackles HTTP over TLS a bit 
> > differently from
> > what we have in our IPP/1.1 draft.
> > Seems that we should try to harmonize this with our solution 
> > in the March
> > IETF meeting.
> > 
> > Carl-Uno
> > 
> > -----Original Message-----
> > From: Internet-Drafts at ietf.org [mailto:Internet-Drafts at ietf.org] 
> > Sent: Wednesday, February 24, 1999 2:33 PM
> > To: IETF Transport Layer Security WG
> > Cc: ietf-tls at consensus.com
> > Subject: I-D ACTION:draft-ietf-tls-https-02.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		: HTTP Over TLS
> > 	Author(s)	: E. Rescorla
> > 	Filename	: draft-ietf-tls-https-02.txt
> > 	Pages		: 6
> > 	Date		: 22-Feb-99
> > 	
> >    This memo describes how to use TLS to secure HTTP 
> connections over
> >    the Internet. Current practice is to layer HTTP over SSL 
> > (the prede-
> >    cessor to TLS), distinguishing secured traffic from 
> > insecure traffic
> >    by the use of a different server port. This document 
> documents that
> >    practice using TLS. A companion document describes a 
> > method for using
> >    HTTP/TLS over the same port as normal HTTP.
> > 
> > A URL for this Internet-Draft is:
> > http://www.ietf.org/internet-drafts/draft-ietf-tls-https-02.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-https-02.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 at ietf.org.
> > In the body type:
> > 	"FILE /internet-drafts/draft-ietf-tls-https-02.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.
> > 
> > 
> 



More information about the Ipp mailing list