Kristina

I think there is a nuance in "silent on the matter of trust models and mechanisms". Meaning that for interoperability, I believe, HAIP needs to specify the key resolution mechanisms,...

also please see #156

does this belong in VCI now?

@peppelinux can you please move it to OpenID4VCI almost as-is?

closing via https://github.com/openid/OpenID4VCI/pull/455

the point of `https://` in HAIP was that the issuer can use the same `iss` value in sd-jwt vc to support various key resolution mechanisms - web-based key resolution (.well-known/jwt_vc_issuer...

i agree this issue can be closed

We do not have an agreement to use OpenID Federation in HAIP right now. and I am honestly very reluctant to add it. X.509 approach does not need OIDC.Fed. and...

great discussion, but please raise it under ttps://github.com/oauth-wg/oauth-sd-jwt-vc instead.

HAIP already says in this section https://openid.github.io/oid4vc-haip-sd-jwt-vc/openid4vc-high-assurance-interoperability-profile-sd-jwt-vc-wg-draft.html#section-7-5.5, which should be clear enough. > The cnf claim [[RFC7800](https://openid.github.io/oid4vc-haip-sd-jwt-vc/openid4vc-high-assurance-interoperability-profile-sd-jwt-vc-wg-draft.html#RFC7800)] MUST conform to the definition given in [[I-D.ietf-oauth-sd-jwt-vc](https://openid.github.io/oid4vc-haip-sd-jwt-vc/openid4vc-high-assurance-interoperability-profile-sd-jwt-vc-wg-draft.html#I-D.ietf-oauth-sd-jwt-vc)]. Implementations conforming to this profile...