Hi!
On 9/22/26 16:07, Richard Clayton wrote:
In message <[email protected]>, Hannah Stern
<[email protected]> writes
>> https://datatracker.ietf.org/doc/draft-gondwana-dkim2-debug-header/
>>
>> Please feel free to add the same thing to your generators and
>> validators as we test things :)
> This creates a _third_ variant of tag-list/tag-value-list.
> We already have:
> - Trailing semicolon allowed but optional (DNS)
> - Trailing semicolon mandatory (Message-Instance/DKIM2-Signature) as
per the
> latest draft
> - Trailing semicolon forbidden (your new draft)
I think Bron should change his draft to make it mandatory. Wei should
change the DNS draft to make it mandatory going forward but note that
legacy DNS entries omit it...
In practice that will make not much difference from keeping it optional
for DNS. So my impression is we'll need two variants of tag-value
parsing anyway (once the debug draft is fixed to not make its third
variant).
Hence I'd perhaps left it optional for M-I and D2-S, too, as we need
that parser variant anyway.
> For me this is another argument for unifying them again and not
splitting the
> generic t-v-list syntax again in future.
> My suggestion for the unified syntax would be the DNS one because we
have to
> support that anyway if we want to be interoperable with existing
DKIM DNS
> records.
> How this would be _textually_ refactored would be a separate issue.
Perhaps in
> "spec" and referring to that from the DNS draft (and your draft).
It did somewhat simplify the "spec" document not to have the t-v-list
definition at all... but if the WG would like it back then that could be
done
I'm a bit agnostic about how to go on in the spec language. As long as
de facto the "overarching" tag/value syntax won't diverge between M-I
and D2-S, I think we'll be fine.
From a parsing view I like the layered approach: First parse generic
t-v syntax, then the specific values according to their respective
requirements. That biases me somewhat towards generic t-v syntax, and
for the descriptions of M-I and D2-S only have EBNF for their respective
tag values. Right now it just _happens_ to be that all tag values have a
syntax that is a subset of the generic t-v syntax (as now still visible
for extension tags).
Hannah.
--
Hannah Stern
Software Developer
Mail Transfer Development
1&1 Mail & Media Development & Technology GmbH | | |
Phone: +49 721 91374-4519
E-Mail: [email protected] | Web: www.mail-and-media.com www.gmx.net
www.web.de www.mail.com www.united-internet-media.de
Hauptsitz Montabaur, Amtsgericht Montabaur, HRB 5452
Geschäftsführer: Alexander Charles, Dr. Michael Hagenau, Thomas Ludwig,
Dr. Verena Patzelt
Member of United Internet
Diese E-Mail kann vertrauliche und/oder gesetzlich geschützte
Informationen enthalten. Wenn Sie nicht der bestimmungsgemäße Adressat
sind oder diese E-Mail irrtümlich erhalten haben, unterrichten Sie bitte
den Absender und vernichten Sie diese E-Mail. Anderen als dem
bestimmungsgemäßen Adressaten ist untersagt, diese E-Mail zu speichern,
weiterzuleiten oder ihren Inhalt auf welche Weise auch immer zu verwenden.
This e-mail may contain confidential and/or privileged information. If
you are not the intended recipient of this e-mail, you are hereby
notified that saving, distribution or use of the content of this e-mail
in any way is prohibited. If you have received this e-mail in error,
please notify the sender and delete the e-mail.
_______________________________________________
Ietf-dkim mailing list -- [email protected]
To unsubscribe send an email to [email protected]
