Dear,
I got recommendation to propose changes in that mailing group.
My work depend on appropriate protection of our brand, however this
tasks require also management of records required for that protection.
We have huge problem with identification of selector records required by
DKIM and also this make for us problem with compatibility. We would like
to strongly follow RFCs, but sometimes v=DKIM1 tag are resolved like
issue as well as sometime missing of that tag do the same. This is a
reason, why I would like to propose mitigation of problem, caused by
word RECOMMENDED in standard RFC 6376:
v= Version of the DKIM key record (plain-text; RECOMMENDED, default
is "DKIM1"). If specified, this tag MUST be set to "DKIM1"
(without the quotes). This tag MUST be the first tag in the
record. Records beginning with a "v=" tag with any other value
MUST be discarded. Note that Verifiers must do a string
comparison on this value; for example, "DKIM1" is not the same as
"DKIM1.0".
I would like to recommend change work RECOMMENDED to MANDATORY, where whole
article be after change
v= Version of the DKIM key record (plain-text; MANDATORY, default
is "DKIM1"). If specified, this tag MUST be set to "DKIM1"
(without the quotes). This tag MUST be the first tag in the
record and this tag must exist. Records beginning with
a "v=" tag with any other valueMUST be discarded. Note that
Verifiers must do a string comparison on this value; for
example, "DKIM1" is not the same as "DKIM1.0".
--
-- --- ----- -
Jan Dušátko
Tracker number: +420 602 427 840
e-mail: j...@dusatko.org
GPG Signature: https://keys.dusatko.org/E535B585.asc
GPG Encrypt: https://keys.dusatko.org/B76A1587.asc
_______________________________________________
Ietf-dkim mailing list
Ietf-dkim@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-dkim
