Re: Telnet Encryption Specification

To: "Theodore Y. Ts'o" <tytso at mit.edu>
Subject: Re: Telnet Encryption Specification
From: Michael Boe <mboe at cisco.com>
Date: Tue, 3 Feb 1998 14:41:24 -0800 (PST)
Cc: krbdev at mit.edu, telnet-ietf at bsdi.com, Todd R Horting <thorting at spyrus.com>, housley at spyrus.com
Delivery-date: Tue, 03 Feb 1998 17:44:49 -0500
In-reply-to: <199802032126.QAA22120@dcl.MIT.EDU>
Reply-to: Michael Boe <mboe at cisco.com>
Sender: mboe at mboe-home-ss20.cisco.com

Ted,

Things being what they are, you and I will probably need to get together. I've
currently have a Telnet over TLS I-D in circulation (see
draft-ietf-tn3270e-telnet-tls-00.txt).

The proposed TLS/SSL mechanism doesn't use the RFC1416 style because that (a)
the TLS negotiation mechanism can't be shoehorned into the RFC1416-style (it
happens strictly at the binary level), and (b) TLS is really
encryption-then-optional-authentication but RFC1416 is really
authentication-then-maybe-encryption.  To summarize, the two don't mesh all
that well.

However, there's some overlap, particularly in the authentication area. I'd be
interested to here your thoughts in this area.

/msb

Follow-Ups:
- Re: Telnet Encryption Specification
  - From: Russ Housley

References:
- Telnet Encryption Specification
  - From: Theodore Y. Ts'o

Prev by Date: Re: Future of IANA (and IETF)
Next by Date: Re: COM names != US trade marks (was Re: Future of IANA)
Previous by thread: Telnet Encryption Specification
Next by thread: Re: Telnet Encryption Specification
Index(es):
- Date
- Thread

Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.

Re: Telnet Encryption Specification

Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.