Re: Protocol Action: The Content-MD5 Header Field to Draft Standard

The IESG <iesg-secretary(_at_)CNRI(_dot_)Reston(_dot_)VA(_dot_)US> writes:
> (ii) In the third paragraph of section 2, change "canonical form of
> the data." to "canonical form of the MIME body part.  The MIME body
> part definition appears in the MIME definition [1]."
This change is technically incorrect.  The MIME "body part", as
defined by RFC 1521, contains both headers and the transfer-encoded
form of the data.  It is not what the MD5 algorithm is computed on.

-- 
_.John G. Myers         Internet: jgm+(_at_)CMU(_dot_)EDU
                        LoseNet:  ...!seismo!ihnp4!wiscvm.wisc.edu!give!up