-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
If you read RFC6376 (DKIM1) you will see that a number of pages are
spent instructing IANA to set up registries
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 51
7.1. Email Authentication Methods Registry . . . . . . . . . . 51
7.2. DKIM-Signature Tag Specifications . . . . . . . . . . . . 51
7.3. DKIM-Signature Query Method Registry . . . . . . . . . . . 52
7.4. DKIM-Signature Canonicalization Registry . . . . . . . . . 52
7.5. _domainkey DNS TXT Resource Record Tag Specifications . . 53
7.6. DKIM Key Type Registry . . . . . . . . . . . . . . . . . . 53
7.7. DKIM Hash Algorithms Registry . . . . . . . . . . . . . . 54
7.8. DKIM Service Types Registry . . . . . . . . . . . . . . . 54
7.9. DKIM Selector Flags Registry . . . . . . . . . . . . . . . 55
7.10. DKIM-Signature Header Field . . . . . . . . . . . . . . . 55
with the exception of adding an elliptic curve key type these registries
contain the same information today as 15 years ago ...
... this leads to the conclusion that these registries serve no
practical purpose (you can get more information from reading RFC6376 and
(although there is little evidence anyone has read it) RFC8463
I therefore suggest that we do not bother with IANA registries for DKIM2
and in the fullness of time, when we write an RFC to move DKIM1 to
historic, we close them at the same time... or we could close them to
new entries now (albeit if no-one looks at them, it's probably not worth
bothering to do that).
If we agree on this I can remove a TBA from the next version of the spec
- --
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/AwUBao3X7WHfC/FfW545EQJBZgCgtafqzCzahhkGKAE5/RdW0cp3910An3Ch
vFwZtjkiuZYGr7XwFMn1JDCP
=XmPI
-----END PGP SIGNATURE-----
_______________________________________________
Ietf-dkim mailing list -- [email protected]
To unsubscribe send an email to [email protected]
