-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 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... >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 - -- richard @ highwayman . com "Nothing seems the same Still you never see the change from day to day And no-one notices the customs slip away" -----BEGIN PGP SIGNATURE----- Version: PGPsdk version 1.7.1 iQA/AwUBarKLrWHfC/FfW545EQKQCQCeKFrVMKFJoUdtcEW7k2jz2hYXp3MAn17i OIMI/tCf/YyrmpX0KDbweZwo =1z/b -----END PGP SIGNATURE----- _______________________________________________ Ietf-dkim mailing list -- [email protected] To unsubscribe send an email to [email protected]
