Original text:
The Issuer parameters can be obtained from an Issuer via a directory object, which is a JSON object (RFC8259, Section 4) whose values are <del> other JSON values (RFC8259, Section 3) for the parameters. </del>  <del> Each "token-keys" JSON object contains the following fields and corresponding raw values. </del>  Issuers MAY advertise multiple token-keys for the same token-type to support key rotation.  In this case, Issuers indicate preference for Altogether, the Issuer's directory could look like: <del> Issuer directory resources have the media type "application/json" and are located at the well-known location /.well-known/token-issuer- directory; see wkuri-reg for the registration information for this well-known URI. </del>  4. 8.  8.1. This document updates the "Well-Known URIs" Registry WellKnownURIs This specification defines the following protocol messages, along with their corresponding media types:  TokenRequest: "application/private-token-request" TokenResponse: "application/private-token-response" application <del> private-token-request </del>  N/A application  private-token-response N/A

Reviewer comments:
The caption for is: "'xxx' Well-Known URI", which is probably wrong.
This is a bit of a hard one to decide for me, but I think that you want to define a media type for the JSON directory. I know that in most cases the content will be served from a .well-known location, but that isn't always.
What would be the benefit of a media type here if the content will always be JSON? That is, I don't see how a media type would influence consumers of the resource.
So that you can make it clear that it is this specific JSON, as opposed to some other JSON.
The table appears without the text referring to it, even with an "as follows". It might be better to reference it directly.

Revised text:
The Issuer parameters can be obtained from an Issuer via a directory object, which is a JSON object (RFC8259, Section 4) whose values are  <ins> other JSON values (RFC8259, Section 3) for the parameters.  The contents of this JSON object are defined in directory-values. </ins>  <ins> Each "token-keys" JSON object contains the fields and corresponding raw values defined in tokenkeys-values. </ins> Issuers MAY advertise multiple token-keys for the same token-type to support key rotation.  In this case, Issuers indicate preference for Altogether, the Issuer's directory could look like:  <ins> Issuer directory resources have the media type "application/token- issuer-directory" and are located at the well-known location /.well- known/token-issuer-directory; see wkuri-reg for the registration information for this well-known URI. </ins> 4. 8. <ins> This section contains considerations for IANA. </ins> 8.1. This document updates the "Well-Known URIs" Registry WellKnownURIs This specification defines the following protocol messages, along with their corresponding media types: <ins> Token issuer directory: "application/token-issuer-directory" </ins> TokenRequest: "application/private-token-request" TokenResponse: "application/private-token-response" application  <ins> token-issuer-directory </ins> N/A application <ins> private-token-request N/A None "binary" see N/A this specification N/A N/A see Authors' Addresses section COMMON N/A see Authors' Addresses section IESG 8.3.3. application </ins> private-token-response N/A