A canonical URI-based identifier that names a workload within a trust domain, to be carried in X.509 certificates and JWT-based tokens for authentication, authorization and policy.
No explainer written for this spec yet. The summary, relations and documented support below are maintained.
A canonical URI-based identifier that names a workload within a trust domain, to be carried in X.509 certificates and JWT-based tokens for authentication, authorization and policy.
flowchart LR s_wimse_identifier["Workload Identifier"] s_wimse_arch["WIMSE Architecture"] s_spiffe["SPIFFE"] style s_wimse_identifier stroke-width:3px s_wimse_identifier -->|Builds on| s_wimse_arch s_wimse_identifier -->|Works with| s_spiffe
Adoption lists only support stated in official documentation (the vendor's or project's own, or a standards body's page naming it), and a weekly check confirms the cited phrase is still on that page. Experimental, alpha and beta support is counted separately as preview.
No sourced support entries collected yet. This says nothing about how widely it is used.
Revisions from the Datatracker, explanations from this site's daily runs, and mailing-list subjects naming the draft.
Review of draft-ietf-wimse-identifier-04
The only comment concerns the last paragraph of Section 5. It proposes changing the final words from credentials to WIMSE workload credentials, so readers know it refers to the credential formats of [WIMSE-CREDENTIALS]. The review otherwise finds the document well written. This is a terminology fix with no protocol change.