Extensibility: how do we support extensibility for trust frameworks, evidence types, verification methods and id documents?
Issue #1093
closed
Can we setup IANA registries?
Comments (5)
-
-
reporter - changed title to Extensibility: how do we support extensibility for trust frameworks, evidence types, verification methods and id documents?
-
- changed status to open
more description needed.
-
We typically query for supported features via the Discovery metadata. We should do that. Documents can define values even if they aren’t put in a registry.
-
reporter - changed status to closed
- Log in to comment
Some Connect specs use IANA registries - which can only be created by RFCs. For instance, we created the OAuth Authorization Server Metadata registry https://www.iana.org/assignments/oauth-parameters/oauth-parameters.xhtml#authorization-server-metadata well after we created OpenID Connect Discovery. We registered the metadata values once the registry was created.
In other cases, the OpenID specs define parameters and some initial values but say that other values can be defined by other specs. For instance, the Subject Identifier Types defined at https://openid.net/specs/openid-connect-core-1_0.html#SubjectIDTypes use this model.