Thanks Ketan, I think you are right on both parts and we'll remove or move the respective text appropriately.
On Tue, Jun 2, 2026 at 10:45 AM Ketan Talaulikar via Datatracker < [email protected]> wrote: > Ketan Talaulikar has entered the following ballot position for > draft-ietf-oauth-identity-chaining-13: No Objection > > When responding, please keep the subject line intact and reply to all > email addresses included in the To and CC lines. (Feel free to cut this > introductory paragraph, however.) > > > Please refer to > https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ > for more information about how to handle DISCUSS and COMMENT positions. > > > The document, along with other ballot positions, can be found here: > https://datatracker.ietf.org/doc/draft-ietf-oauth-identity-chaining/ > > > > ---------------------------------------------------------------------- > COMMENT: > ---------------------------------------------------------------------- > > Thanks to the authors and the WG for their work on this document. > > I would like to point out that there is some text in the IANA > Considerations > that does not belong there (i.e., it does not have any instructions for > IANA) > per RFC8126. > > "The parameter indicates the supported token types that can be requested > in an > [RFC8693] Token Exchange." This seems like a repeat of the Metadata > Description > and can be deleted? > > And then the section 4.2 below is more for information of readers and not > something for IANA team to act on. This is better moved somewhere else in > the > document, I don't have a good suggestion as to where that might be. > > 4.2. Media Types > This specification does not define any new media types. > > Profiles or deployment-specific implementations can 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]. > > > > -- _CONFIDENTIALITY NOTICE: This email may contain confidential and privileged material for the sole use of the intended recipient(s). Any review, use, distribution or disclosure by others is strictly prohibited. If you have received this communication in error, please notify the sender immediately by e-mail and delete the message and any file attachments from your computer. Thank you._
_______________________________________________ OAuth mailing list -- [email protected] To unsubscribe send an email to [email protected]
