-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 In message <20250411205917.169acc3d1...@ary.qy>, John Levine <jo...@taugh.com> writes
>It appears that Richard Clayton <rich...@highwayman.com> said: >>>> +------------+-------------------------------------------------+ >>>> | ds= | Signing key identifier (domain & selector) | >>> >>>So this appears to conflate selector with domain name being signed? Why? >>> >>>How is the domain name being signed identified separately? >> >>Let's turn that round ... why did DKIM1 put the selector and the >>associated domain into separate fields ? >> >>If there is a compelling reason for keeping then apart we should take >>note it -- > >If you combine them into one field how do you tell what's the selector and >what's >the domain? My DKIM setup uses selectors like 670e67f41a6d.k2504 so you can't >just >pick off the label before the first dot. You could use a separator character which was not permitted to occur in domain names ... I expect @ might confuse people :-) as would, from the positioning, underline, but colon might be suitable... - -- richard Richard Clayton Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. Benjamin Franklin 11 Nov 1755 -----BEGIN PGP SIGNATURE----- Version: PGPsdk version 1.7.1 iQA/AwUBZ/mOK2HfC/FfW545EQKZnwCfWTQB4UqUOSMo8Lwpr9vFV9F4tcUAoLsP AxzXokOKcafVbkciLsAa80jt =cVQ6 -----END PGP SIGNATURE----- _______________________________________________ Ietf-dkim mailing list -- ietf-dkim@ietf.org To unsubscribe send an email to ietf-dkim-le...@ietf.org
