Michael B. Jones

I'm curious - which of the algorithms did you build? All of Single-Use, BBS, and MAC?

My initial gut reaction to this is that ZKPs are more like signatures than encryption. I *think* that encryption is out of scope. That said, we may want to describe...

I'm skeptical of adding multiple signatures/proofs over the same payloads. It seems like a lot of complexity to add to support an infrequent scenario. That said, I'd be willing to...

@dwaite and I propose to close this unless concrete use cases necessitating multiple signatures is endorsed by the working group.

https://datatracker.ietf.org/doc/draft-jones-jose-fully-specified-algorithms/ was created to deal with this problem. It proposes new fully-specified algorithm identifiers that include the curve choice. See https://www.ietf.org/archive/id/draft-jones-jose-fully-specified-algorithms-01.html#name-elliptic-curve-digital-sign for specifics. Once these are registered with IANA, we...

As an update, the IETF JOSE working group did adopt the fully-specified algorithms spec. Its current status can be viewed at https://datatracker.ietf.org/doc/draft-ietf-jose-fully-specified-algorithms/. I plan to ask for working group last...

I believe this was addressed by https://github.com/json-web-proofs/json-web-proofs/pull/106, which defined the `alg` header parameter.

Yes, we certainly want to be able to have claims like "address" that are structured. However, I don't think we want to go down the road that SD-JWT did to...

We are chartered to do the CBOR/COSE/CWT version of JWPs in this working group. I believe that spreading the work between working groups would only create unnecessary divergence in the...

I believe this was addressed by PR #106