9.5. Dynamic Client Registration Metadata Registration
Per this specification, the following client metadata definitions have been registered in the IANA "OAuth Dynamic Client Registration Metadata" registry [IANA.OAuth.Parameters] established by [RFC7591]:
Client Metadata Name: tls_client_certificate_bound_access_tokens
Client Metadata Description: Indicates the client's intention to use mutual-TLS client certificate-bound access tokens.
Change Controller: IESG
Specification Document(s): Section 3.4 of RFC 8705
Client Metadata Name: tls_client_auth_subject_dn
Client Metadata Description: String value specifying the expected subject DN of the client certificate.
Change Controller: IESG
Specification Document(s): Section 2.1.2 of RFC 8705
Client Metadata Name: tls_client_auth_san_dns
Client Metadata Description: String value specifying the expected dNSName SAN entry in the client certificate.
Change Controller: IESG
Specification Document(s): Section 2.1.2 of RFC 8705
Client Metadata Name: tls_client_auth_san_uri
Client Metadata Description: String value specifying the expected uniformResourceIdentifier SAN entry in the client certificate.
Change Controller: IESG
Specification Document(s): Section 2.1.2 of RFC 8705
Client Metadata Name: tls_client_auth_san_ip
Client Metadata Description: String value specifying the expected iPAddress SAN entry in the client certificate.
Change Controller: IESG
Specification Document(s): Section 2.1.2 of RFC 8705
Client Metadata Name: tls_client_auth_san_email
Client Metadata Description: String value specifying the expected rfc822Name SAN entry in the client certificate.
Change Controller: IESG
Specification Document(s): Section 2.1.2 of RFC 8705