All, Based on the feedback on the mailing list, the chairs think that there is enough support to adopt this draft as a WG document. Dick provided some comments during this call for adoption that should be addressed in the WG document.
Authors, Feel free to submit an initial WG document that contains the* same content of v05*. Regards, Rifaat & Hannes On Sat, Sep 6, 2025 at 11:40 PM Kevin Swiber <[email protected]> wrote: > I support adoption of this draft as a WG document. It’s addressing key > concerns that enable enterprise adoption of OAuth Identity and Authorization > Chaining Across Domains (draft-ietf-oauth-identity-chaining), which is > currently in WG Last Call. While I agree with some of the feedback others > have left in this thread, I’m comfortable moving forward with this draft as a > WG document so that it may continue to be refined. > > Best, > > Kevin Swiber > > On Mon, Aug 25, 2025 at 1:39 PM Rifaat Shekh-Yusef via Datatracker > <[email protected]> <[email protected]>> wrote: > > > > > Subject: Call for adoption: > > draft-parecki-oauth-identity-assertion-authz-grant-05 (Ends 2025-09-08) > > > > This message starts a 2-week Call for Adoption for this document. > > > > Abstract: > > This specification provides a mechanism for an application to use an > > identity assertion to obtain an access token for a third-party API by > > coordinating through a common enterprise identity provider using > > Token Exchange [RFC8693] and JWT Profile for OAuth 2.0 Authorization > > Grants [RFC7523]. > > > > File can be retrieved from: > > > > https://datatracker.ietf.org/doc/draft-parecki-oauth-identity-assertion-authz-grant/ > > > > Please reply to this message keeping [email protected] in copy by indicating > > whether you support or not the adoption of this draft as a WG document. > > Comments to motivate your preference are highly appreciated. > > > > Authors, and WG participants in general, are reminded of the Intellectual > > Property Rights (IPR) disclosure obligations described in BCP 79 [2]. > > Appropriate IPR disclosures required for full conformance with the > > provisions > > of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of any. > > Sanctions available for application to violators of IETF IPR Policy can be > > found at [3]. > > > > Thank you. > > [1] https://datatracker.ietf.org/doc/bcp78/ > > [2] https://datatracker.ietf.org/doc/bcp79/ > > [3] https://datatracker.ietf.org/doc/rfc6701/ > > > > > > > > _______________________________________________ > > OAuth mailing list -- [email protected] > > To unsubscribe send an email to [email protected] > > > > _______________________________________________ > OAuth mailing list -- [email protected] > To unsubscribe send an email to [email protected] >
_______________________________________________ OAuth mailing list -- [email protected] To unsubscribe send an email to [email protected]
