-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
In message <[email protected]>, Timo
Gerke <[email protected]> writes
>If you, Bron and Wei keep on using JSON, you should consider
>flattening it like an array of flat objects:
>
>[
> {
> "host": "mail.example.com",
> "selector": "dkim2-s1",
> "h": "from:to:subject:date",
> "sig": "signature-1",
> "sig-alg": "aes256-gcm-sha512",
> "hash": "sha512-header-hash-1",
> "sig-exp": 1789311600,
> "key-exp": 1820847600
this does not seem relevant to the current version of the IETF-draft
that is being discussed in this working group. We are not using JSON for
this type of information -- and have not done so for some time
- --
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/AwUBaqa132HfC/FfW545EQJQYwCfS+wJiRpCms9K42K0Hf0KFZf9wXoAnRJ7
BxngvTM7H23wDBRDFI87HJY3
=+JXG
-----END PGP SIGNATURE-----
_______________________________________________
Ietf-dkim mailing list -- [email protected]
To unsubscribe send an email to [email protected]