Re: RFC-to-be - SHA Message-Digest Algorithm

"Jeffrey I. Schiller" <jis@mit.edu> Thu, 21 March 1996 15:06 UTC

Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa16938; 21 Mar 96 10:06 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa16934; 21 Mar 96 10:05 EST
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa07494; 21 Mar 96 10:05 EST
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa16925; 21 Mar 96 10:05 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa16921; 21 Mar 96 10:05 EST
Received: from BIG-SCREW.MIT.EDU by CNRI.Reston.VA.US id aa07489; 21 Mar 96 10:05 EST
Received: by big-screw id AA23623; Thu, 21 Mar 96 10:05:38 -0500
X-Sender: jis@e40-po.mit.edu (Unverified)
Message-Id: <ad77202f02021004ebac@[18.162.1.1]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Thu, 21 Mar 1996 10:05:45 -0500
To: jkrey@isi.edu
X-Orig-Sender: iesg-request@IETF.CNRI.Reston.VA.US
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: "Jeffrey I. Schiller" <jis@mit.edu>
Subject: Re: RFC-to-be - SHA Message-Digest Algorithm
Cc: jis@mit.edu, iesg@CNRI.Reston.VA.US, rfc-editor@isi.edu

At 15:15 3/19/96, jkrey@ISI.EDU wrote:
>Jeff,
>
>The RFC Editor has received an "Informational" RFC-to-be on,
>"SHA Message-Digest Algorithm".  Two week timeout is initiated:
>2 April 96.

Got it. Note: Please do not publish this document unless you *do* hear back
from me. This is an individual submission attempting to document a
government standard algorithm. I want to ensure that in fact it is a
faithful representation of the algorithm. To do this will require me not
only to read the document, but to obtain the original document from NIST,
extract the software fragment the author has enclosed and convince myself
that it is an accurate rendition of the algorithm.

This work will require more then the usual read through of the document and
I may not be able to complete this work in two weeks.

                                -Jeff