On Thu 28/Aug/2025 21:33:55 +0200 Richard Clayton wrote:
In message <[email protected]>, Alessandro Vesely
<[email protected]> writes
On Wed 27/Aug/2025 16:46:28 +0200 Richard Clayton wrote:
Title: DomainKeys Identified Mail Signatures v2 (DKIM2)
This draft is modelled on RFC 6376 and is intended to set out a formal
specification of DKIM2-Signature fields.
I found that document quite confusing to read.
difficult to address that comment without more detail .... I've had
others suggest that text about canonicalisation and header fields more
generally could be rather better arranged and I tend to agree...
I apologize for the misunderstanding, I thought the rest of the text would have
clarified how I had approached the document in proofreading mode, but then,
confronted with the already sacred wording of RFC 6376, I had to change my
approach. That's where the confusion originated.
At one point I ran iddiff on RFC 6376 and tried to read only the
changes. It is still a pain to do.>
of course rearranging things to improve the flow will make that
completely impractical ! and do you really want to learn that the NITS
system thinks it should be "public key" and not "public-key" ?
Wouldn't readability improve if you assumed full familiarity with RFC 6376 and
focus on the differences?
the document explicitly stresses the things that are the same as DKIM1
(the keys, the (implicit) use of relaxed/relaxed) but after that there's
not that much that is identical -- so I don't think this would be
especially helpful and it would be quite a lot of work
Oh, in that case please forget my comment. I thought eliminating entire,
nearly identical sections, such as 3.2 (Tag=Value Lists) for example, would
actually reduce the work required (including verifications.) Note that other
IETF documents do this, for example RFC 7489 which simply states:
DMARC records follow the extensible "tag-value" syntax for DNS-based
key records defined in DKIM [DKIM].
Best
Ale
--
_______________________________________________
Ietf-dkim mailing list -- [email protected]
To unsubscribe send an email to [email protected]
