From 8b4e44b2094fb4b23cfb0abd9932498346675a0b Mon Sep 17 00:00:00 2001 From: Brian Campbell Date: Sat, 12 Jul 2025 09:54:18 -0600 Subject: [PATCH] Use IANA.media-types so the tooling can find the media types registry without an explicit target --- draft-ietf-oauth-identity-chaining.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/draft-ietf-oauth-identity-chaining.md b/draft-ietf-oauth-identity-chaining.md index 72a4bce..4cc7d26 100644 --- a/draft-ietf-oauth-identity-chaining.md +++ b/draft-ietf-oauth-identity-chaining.md @@ -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 @@ -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} @@ -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