As long as a specific service can make an ext containing the body hash required, I think this is fine. Can the spec include body hash as an example of an ext?
Thanks, Peter On Sat, Nov 19, 2011 at 10:39 AM, Eran Hammer-Lahav <[email protected]> wrote: > I want to reaffirm our previous consensus to drop the body-hash parameter > and leave the ext parameter. Body-hash as currently specified is going to > cause significant interop issues due to character (and other) encoding > issues. Providers who desire to MAC the body can define their own ext use > case. > > > > Let me know if you have an objection to this change. > > > > EHL > > > _______________________________________________ > OAuth mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/oauth > -- Peter M. Wolanin, Ph.D. : Momentum Specialist, Acquia. Inc. [email protected] : 781-313-8322 "Get a free, hosted Drupal 7 site: http://www.drupalgardens.com"; _______________________________________________ OAuth mailing list [email protected] https://www.ietf.org/mailman/listinfo/oauth
