I oppose adoption of this draft. Neil (and others but Neil in particular) has articulated a number of concerns better than I could. But in general, introducing an additional WG-sanctioned mechanism will create uncertainty and harm interoperability without sufficient justification for doing so.
On Mon, Sep 21, 2026 at 1:17 PM Rifaat Shekh-Yusef <[email protected]> wrote: > All, > > This is an official call for adoption for the *OAuth Proof of Possession > Tokens with HTTP Message Signatures *draft: > https://www.ietf.org/archive/id/draft-richer-oauth-httpsig-03.html > > Please, reply on the mailing list, on whether you support or oppose the > adoption of this draft as a WG document by *October 5th*. > > Regards, > Rifaat & Hannes > _______________________________________________ > OAuth mailing list -- [email protected] > To unsubscribe send an email to [email protected] > -- _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]
