On Fri, Oct 8, 2021 at 12:39 PM Richard Backman, Annabelle < richa...@amazon.com> wrote:
> > Blocking WG development of an OAuth 2.0 profile of Message Signatures > behind widespread deployment of Message Signatures risks creating a > deadlock where the WG is waiting for implementations from would-be > implementers who are waiting for guidance from the WG. Worse, rejecting the > draft is likely to further discourage these parties from implementing > Message Signatures, as it suggests the WG is not interested in > standardizing its usage with OAuth 2.0. If the main use case for HTTP Signing is the OAuth WG, then effectively the OAuth WG is developing HTTP Signing and it is not really a general purpose standard. IE, if the success of HTTP Signing is tied to the OAuth WG adopting the draft, then Mike's arguments about the WG already doing this work is valid. ᐧ
_______________________________________________ OAuth mailing list OAuth@ietf.org https://www.ietf.org/mailman/listinfo/oauth
