Hi All, Hopefully the collective memory of this group can answer me the question: why was colon chosen as the separator for the h= value? Even as I type the question I suspect it's because "header field" has a quite permissive ABNF and colon is for sure not permitted since it's the separator!
Anyways, I'm considering updating Message-Instance to use colon as the separator for the b and h.header values as well, so the format is more regular and more easily parsed. ... In other open questions; whether Message-Instance should sign all headers or just a named list. I've heard strong arguments for both, and I expect to dedicate time in our next interim to discussing them. And finally, should we be using relaxed/strict (relaxed for the header, strict for the body) in Message-Instance? This aligns better with the oblivious signatures work, allowing the same normalisations for both. Relaxed for the body allows for more shenanigans around significant whitespace (particularly the '-- ' signature separator, and format=flowed parts), which is an argument against it. Bron. -- Bron Gondwana, CEO, Fastmail Pty Ltd / Fastmail US LLC [email protected]
_______________________________________________ Ietf-dkim mailing list -- [email protected] To unsubscribe send an email to [email protected]
