I support adoption. On Thu, Nov 13, 2025 at 2:17 PM Lombardo, Jeff <jeffsec= [email protected]> wrote:
> I support adoption > > Jean-François “Jeff” Lombardo | Amazon Web Services > > Architecte Principal de Solutions, Spécialiste de Sécurité > Principal Solution Architect, Security Specialist > Montréal, Canada > > Commentaires à propos de notre échange? Exprimez-vous ici. > > Thoughts on our interaction? Provide feedback here. > > -----Original Message----- > From: Rifaat Shekh-Yusef via Datatracker <[email protected]> > Sent: November 13, 2025 3:03 PM > To: [email protected]; > [email protected]; [email protected] > Subject: [EXT] [OAUTH-WG] Call for adoption: > draft-watson-oauth-refresh-token-expiration-01 (Ends 2025-11-27) > > CAUTION: This email originated from outside of the organization. Do not > click links or open attachments unless you can confirm the sender and know > the content is safe. > > > > AVERTISSEMENT: Ce courrier électronique provient d’un expéditeur externe. > Ne cliquez sur aucun lien et n’ouvrez aucune pièce jointe si vous ne pouvez > pas confirmer l’identité de l’expéditeur et si vous n’êtes pas certain que > le contenu ne présente aucun risque. > > > > Subject: Call for adoption: draft-watson-oauth-refresh-token-expiration-01 > (Ends 2025-11-27) > > This message starts a 2-week Call for Adoption for this document. > > Abstract: > This specification extends OAuth 2.0 [RFC6749] by adding new token > endpoint response parameters to specify refresh token expiration and > user authorization expiration. > > File can be retrieved from: > > https://datatracker.ietf.org/doc/draft-watson-oauth-refresh-token-expiration/ > > 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] > -- <https://fusionauth.io> Dan Moore Sr. Director, CIAM Strategy & Identity Standards @ FusionAuth <https://fusionauth.io/> 11080 Circle Point Rd Suite 405, Westminster, CO 80020 <https://github.com/FusionAuth> <https://twitter.com/FusionAuth> <https://www.linkedin.com/company/fusionauth> <https://www.youtube.com/c/fusionauth>
_______________________________________________ OAuth mailing list -- [email protected] To unsubscribe send an email to [email protected]
