> 3) A Standards Track document specifying how to encode public > keys as JSON-structured objects. >
I would like to push back on the idea of only supporting naked public keys. It is my understanding that common cryto libraries, e.g. OpenSSL, expect public keys to be in certificates and the coding to get them to accept a naked key as input is ugly. I don't think they care if the cert is self signed or even signed at all, its just a format issue. Hal _______________________________________________ woes mailing list [email protected] https://www.ietf.org/mailman/listinfo/woes
