Dave Crocker wrote in <117c5879-7255-43cb-bfee-2ca9413be...@dcrocker.net>: |On 2/3/2024 11:29 AM, Dave Crocker wrote: |> DKIM is not a general message parsing engine | |btw, one might imagine a parsing engine that mixes a number of |functions, such as general message parsing AND DKIM validation. | |For such an engine, where a bare CR or bare LF might be illegal -- |though it now appears they aren't -- the error to raise is for the |general message processing, not for DKIM. | |This nicely demonstrates the importance of distinguishing between the |abstractions needed for public networking specifications, from various |local implementation choices a programmer might make.
I want to remark that my original question, if i recall correctly, was whether a lone CR or LF shall be treated as whitespace, or not. Because relaxed DKIM parsing normalizes adjacent whitespace. But CR and LF are not WSP, only CRLF is. The RFC 5322 parser i have written simply skips over such as whitespace, but the little DKIM thing must either treat them as literal bytes (what i have done now), or as "invalid" whitespace (what i was and am inclined to do, practically). --steffen | |Der Kragenbaer, The moon bear, |der holt sich munter he cheerfully and one by one |einen nach dem anderen runter wa.ks himself off |(By Robert Gernhardt) _______________________________________________ Ietf-dkim mailing list Ietf-dkim@ietf.org https://www.ietf.org/mailman/listinfo/ietf-dkim
