standard protocol like DNS makes lot of sense.
people should be able to publish link to public key as well.
and changes can also be captured in a blockchain .
some of the fields should be protected as configured by the user and who is asking for the information should be logged as well. some data can be permissioned and available on approval only, this could be resume link, physical address, government issues ids
Do you have a link you can share?
> people should be able to publish link to public key as well.
There's a actually a standard for this: https://www.df7cb.de/blog/2007/openpgp-dns.html
I would prefer if you could just dump the whole key in DNS itself, but TXT records are limited to 255 bytes.
> and changes can also be captured in a blockchain .
What's your use case for wanting to know the delta over time?
> some of the fields should be protected as configured by the user and who is asking for the information should be logged as well. some data can be permissioned and available on approval only, this could be resume link, physical address, government issues ids
I was mostly thinking in terms of "public" information. I can see wanting permissions for things like physical address.
The article you've linked also mentions CERT RRs, which include keys themselves, and there's also DANE's OPENPGPKEY [1].
Besides, each string of a TXT record is limited, but they can consist of multiple strings, so whole keys can be stored in those as well (as it's done for DKIM records, for instance).
See: https://datatracker.ietf.org/doc/draft-koch-openpgp-webkey-s...