Re: DKIM Body Count/Length

----- Original Message ----- 
From: "Michael Thomas" <mike(_at_)mtcc(_dot_)com>
To: "Hector Santos" <hsantos(_at_)santronics(_dot_)com>

> > But the example in the specs shows otherwise:
> >
> >    A: <SP> X <CRLF>
> >    B: <SP> Y <CRLF>
> >     <SP> Z <CRLF>
> >    <CRLF>
> >    C <CRLF>
> >    D <SP><TAB><SP> E <CRLF>
> >
> >       is canonicalized to:
> >
> >    a:X<CRLF>b:YZ<CRLF><CRLF>CDE
> >
> > Based on this example, the two parts are:
> >
> >  canonicalized header: a:X<CRLF>b:YZ<CRLF>
> >  canonicalized body: <CRLF>CDE
> >
> > Therefore the the l= count size includes the CRLF presiding the body.
>
> I think you're reading too much into the example. The example is,
> I think, showing the nowsp canonicalization. The point being to show
> where the syntactic CRLF's are actually given to the hash (vs. eaten
> by the nowsp algorithm).

Reading too much or not, this technical language needs to be concise.  

So the example should state:

  canonicalized header: a:X<CRLF>b:YZ<CRLF>
  canonicalized body: CDE

and the SHA1 hashing is based on:

    SHA1(canonicalized header)
    SHA1(CRLF)  ????
    SHA1(canonicalized body)

Thanks for your feedback.

-- 
Hector Santos, Santronics Software, Inc.
http://www.santronics.com