Key Commitment is NOT a "application/token-issuer-directory" resource
chris-wood opened this issue · 1 comments
chris-wood commented
The issuer protocol says that key commitments have the "application/token-issuer-directory" content type, but they are fundamentally a different type of resource. This seems like it will cause much confusion and interoperability failures in practice. Please pick a new resource type, or just use the existing Privacy Pass resource type as specified.
dvorak42 commented
That's a fair point, we'll discuss on what mediatype to use instead for now, though I think similarly token-issuer-directory is a bit generic for specifically privacypass keys (filed #373 on the privacypass repo to discuss).