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

> 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.
Would you please supply the exact text you want in its stead?  Several IESG
members insisted that this not go forward without a definition of what the
MD5 is being computed over and, from history, I assumed that was it.

   john