You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
SD-JWT VCs MUST be encoded using the SD-JWT format defined in Section 5 of [I-D.ietf-oauth-selective-disclosure-jwt]. A presentation of an SD-JWT VC MAY contain a Key Binding JWT.
Note that in some cases, an SD-JWT VC MAY have no selectively disclosable claims, and therefore the encoded SD-JWT will not contain any Disclosures.
The SD-JWT DC does not CONTAIN the Key Binding JWT. See the revised Figure 1. See #285.
However, a SD-JWT VC CAN be ASSOCIATED with a Key Binding JWT
The following changes are proposed:
A presentation of an SD-JWT DC CAN be associated with a Key Binding JWT.
Note that in some cases, an SD-JWT DC MAY have no selectively disclosable claims, and therefore the encoded SD-JWT will not be associated with any Disclosures.
The text was updated successfully, but these errors were encountered:
Although, I agree with the proposed idea (I also think that SD-JWT doesn't contain a KB-JWT, rather a KB-JWT may be associated to an SD-JWT presentation), yet I feel that this proposal should target SD-JWT and not SD-JWT-VC.
Section 3.2 states:
The SD-JWT DC does not CONTAIN the Key Binding JWT. See the revised Figure 1. See #285.
However, a SD-JWT VC CAN be ASSOCIATED with a Key Binding JWT
The following changes are proposed:
The text was updated successfully, but these errors were encountered: