Skip to content

Use IANA.media-types so the tooling can find the media types registry without an explicit target #167

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Use IANA.media-types so the tooling can find the media types registry without an explicit target #167

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 6 additions & 4 deletions draft-ietf-oauth-identity-chaining.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -60,9 +60,7 @@ informative:
RFC6838: # Media Type Specifications and Registration Procedures
RFC9700: # Best Current Practice for OAuth 2.0 Security
RFC9728: # OAuth 2.0 Protected Resource Metadata
IANA-MediaTypes:
target: https://www.iana.org/assignments/media-types/
title: IANA Media Types Registry
IANA.media-types:

--- abstract

Expand Down Expand Up @@ -316,7 +314,7 @@ The registry records the supported token types that can be requested in an {{RFC
## Media Types
This specification does not define any new media types.

It is RECOMMENDED that any profile or deployment-specific implementation adopt explicit typing as defined in JSON Web Token Best Current Practices {{RFC8725}} and define a new media type {{RFC2046}} in the "Media Types" registry {{IANA-MediaTypes}} in the manner described in {{RFC6838}}.
It is RECOMMENDED that any profile or deployment-specific implementation adopt explicit typing as defined in JSON Web Token Best Current Practices {{RFC8725}} and define a new media type {{RFC2046}} in the "Media Types" registry {{IANA.media-types}} in the manner described in {{RFC6838}}.

# Security Considerations {#Security}

Expand Down Expand Up @@ -539,6 +537,10 @@ The editors would like to thank Joe Jubinski, Justin Richer, Dean H. Saxe, and o

\[\[ To be removed from the final specification ]]

-06

* Use IANA.media-types so the tooling can find the media types registry without an explicit target

-05

* Editorial pass on Appendix for consistency
Expand Down