Michael B. Jones
Michael B. Jones
Fixed by PR #106
Where we mean "public key", we should use the term "public key". Using a different term would create an unnecessary level of indirection.
Being able to represent and use non-ZKP algorithms is a forcing function that we're writing the specifications in widely-applicable manner. That doesn't mean that, in the end, we need to...
Per discussions at IETF 120 in Vancouver, it makes sense to keep several algorithms in the specs to ensure that the representations we're using are flexible and general-purpose.
Yes, we need to track this uodate.
Typographically, we should use names like "Issuer Header" rather than `issuer_header` for things that are not parameter or field names.
I will talk to people about this at IETF 119 in Brisbane.
> If coming back over an API as a response it is helpful to get the JSON serialization compared to compact Helpful how? I'll make two guesses as to what...
Clearly the issuer and holder algorithms have to be able to be different. I'll review the specs with this in mind.
Let's consider this together with #57. On the surface of it, it seems that we have to to address that one to address this one.