Tim Cappalli
Tim Cappalli
## Proposed Change 6.2 Authenticator Taxonomy examples list needs to be refreshed for ecosystem changes related to passkeys
We've long discussed the challenges with the event specs, which are effectively just dictionaries, being formal specifications that go through full OIDF process. This can make it challenging to add...
`credential_type` and then all credential specific properties need to be part of a structure data model (`x509_issuer`, `x509_serial`, `fido2_aaguid`) Might want to use AMR claim as a reference.
In order to potentially create IANA registries for shared/extensible elements, we need to identify requirements in a dedicated section of the spec, similar to OpenID Connect.
We currently have `reason_admin` and `reason_user`, there has been interest in exploring a standardized `reason_code` claim.
Example, an IdP using Connect for the sign in, then a managed device with the device compliance change event, resulting in either a session revoked or assurance level change to...
Before the next implementer's draft, clean up the markdown source to follow up MD formatting best practices (Headings should be surrounded by blank lines, etc).
Example: `urn:openid:sharedsignals:caep:session-revoked:1.0`
Subject Identifiers for Security Event Tokens is now RFC9493. We should update any references.