- From: Rodney Thayer <rodney@sabletech.com>
- Date: Mon, 16 Dec 1996 18:08:34 -0500
- To: ietf-tls@w3.org
-----BEGIN PGP SIGNED MESSAGE-----
Ooh. He's right, isn't he?
I believe it, but is there an RFC one can quote to reference these
guidelines?
So the common denominator among (the tls doc) and (the common exportable
Netscape) and (the common exportable MS Internet Explorer) would
end up being MD5 or SHA-1 digesting, and 40-bit DES.
This is valid, and this is supported by N. and MS., correct?
It seems to me that it would be worth making sure we don't write a draft
that isn't irrelevant to the (ahem) 'best current practice'...
>From: dpkemp@missi.ncsc.mil (David P. Kemp)
>To: ietf-tls@w3.org
>Subject: CipherSuites for unpublished algorithms
> IETF guidelines are that unpublished algorithms are not to be
>included in Standards-Track documents, but they may be specified
>in accompanying Informational RFCs.
-----BEGIN PGP SIGNATURE-----
Version: 4.0 Business Edition
Comment: PGP by ViaCrypt
iQCVAgUBMrXV7cKmlvJNktGxAQGAHQP+PFtwMFkNMs2HMRG1vW36H7C8KdzPjgKZ
HWdzG+PWamSfSwh7z2I57iD8OFvtfMTAlVw71WSX9EGaTdkhh9L88kih9qJxIq/F
Ai8TNFeK8jTUPtgh65OeEtRgmrcRZjfTVgLKMHl6T+7TIQ9cwzozHL4QTSVDYvgF
Qm41lgNcv5c=
=IYI1
-----END PGP SIGNATURE-----
Rodney Thayer <rodney@sabletech.com> +1 617 332 7292
Sable Technology Corp, 246 Walnut St., Newton MA 02160 USA
Fax: +1 617 332 7970 http://www.shore.net/~sable
"Developers of communications software"
Received on Monday, 16 December 1996 18:02:47 UTC