Return-Path: X-Original-To: oauth@ietfa.amsl.com Delivered-To: oauth@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 27CE221F899D for ; Sat, 19 Nov 2011 07:46:31 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -15.947 X-Spam-Level: X-Spam-Status: No, score=-15.947 tagged_above=-999 required=5 tests=[AWL=-0.763, BAYES_40=-0.185, HTML_MESSAGE=0.001, USER_IN_DEF_WHITELIST=-15] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pSYp2L3VTC-q for ; Sat, 19 Nov 2011 07:46:30 -0800 (PST) Received: from nm19.bullet.mail.sp2.yahoo.com (nm19.bullet.mail.sp2.yahoo.com [98.139.91.89]) by ietfa.amsl.com (Postfix) with SMTP id 807F521F891D for ; Sat, 19 Nov 2011 07:46:30 -0800 (PST) Received: from [98.139.91.62] by nm19.bullet.mail.sp2.yahoo.com with NNFMP; 19 Nov 2011 15:46:27 -0000 Received: from [98.139.91.32] by tm2.bullet.mail.sp2.yahoo.com with NNFMP; 19 Nov 2011 15:46:27 -0000 Received: from [127.0.0.1] by omp1032.mail.sp2.yahoo.com with NNFMP; 19 Nov 2011 15:46:27 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 410995.60872.bm@omp1032.mail.sp2.yahoo.com Received: (qmail 62762 invoked by uid 60001); 19 Nov 2011 15:46:26 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo-inc.com; s=ginc1024; t=1321717586; bh=QUVkSgpb1vjR0paV1/l+EIMjmSWM+/k7IdX+ZqpjrGE=; h=X-YMail-OSG:Received:X-RocketYMMF:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=KMWd1pqOGERe8rCRKpDwxsCXtKbHo0s6b7FAdI+MoqxTRCF5A9Ip31qwjX+6nO4bDol2SMlPlzCTw6JWCuY84aDtAbhePwB85aEuqS0i17IRqntLF9Jr9Q47vMi3jUe2rNB7I5DlQCQtUmA9L5gnPxLuael65S745GtNEmtmPEU= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=ginc1024; d=yahoo-inc.com; h=X-YMail-OSG:Received:X-RocketYMMF:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=pRG/IhStLXDF/fwrprMEbnzDYoTX1f7m14NwV0fWQLwOF06aZifkwjmj0vSNCVEVmRtmWoJwZRyCOW3U/7NCm85fbkyV+IUnS0kkKUAHmz5kEI4yIvq4yXrb7EYxzm86Qnjz76u2Nvkeu3POH2HOrND8g1VKdIidnv5mvOagi6s=; X-YMail-OSG: bPKDCbkVM1mbcWor1t8Z0qIufMCc_k9NNEuq_iqw.4yzG.Q mZRdfG8BpQgz2a8WYeoA.Za3ON9groLQOFuhYA0Mio0kBSe2BUq_LJOU05Nr 5MMdklGhaCKdUKCDGh4Thyq4MJAt7lErI.6LjY7F9p2Zx6WblFoyQM1Y5Gg. qU9NwZ1tJeg8r6UTWbl7wo4kftNlN0zCnC.2StH90ERSjyHCgaJ2l0lse83H LN1hWmYT8J2BVCK987r42XtG9y1i3RgPjss3jQukTsMqyeFmTcyjMDG86nZO .gdgy6r4QYpzl3SAsAP_LpFIKJ4zCRMwVOyU5WuDoJmUv6sJsaDeQOZWpfV0 Kv0FJIQspqzD6YhlwvrDR5uQtGiB60g0MndpS8AqBO_lrChD3nOy2rbAQYQx BNNCebOU7JS8x Received: from [99.31.212.42] by web31804.mail.mud.yahoo.com via HTTP; Sat, 19 Nov 2011 07:46:26 PST X-RocketYMMF: william_john_mills X-Mailer: YahooMailWebService/0.8.115.331203 References: <90C41DD21FB7C64BB94121FBBC2E7234526735EDF1@P3PW5EX1MB01.EX1.SECURESERVER.NET> Message-ID: <1321717586.50797.YahooMailNeo@web31804.mail.mud.yahoo.com> Date: Sat, 19 Nov 2011 07:46:26 -0800 (PST) From: William Mills To: Eran Hammer-Lahav , OAuth WG In-Reply-To: <90C41DD21FB7C64BB94121FBBC2E7234526735EDF1@P3PW5EX1MB01.EX1.SECURESERVER.NET> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="835683298-1628337004-1321717586=:50797" Subject: Re: [OAUTH-WG] MAC: body-hash X-BeenThere: oauth@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: William Mills List-Id: OAUTH WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Nov 2011 15:46:31 -0000 --835683298-1628337004-1321717586=:50797 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable I haven't read the MAC spec recently enough, did you already deal with the = character set issue (if there was one) comparable to the ones in the Bearer= spec?=0A=0AI am +1 on the -body_hash +ext change.=0A=0A=0A=0A_____________= ___________________=0A From: Eran Hammer-Lahav =0ATo: = OAuth WG =0ASent: Saturday, November 19, 2011 7:39 AM=0ASu= bject: [OAUTH-WG] MAC: body-hash=0A =0A=0AI want to reaffirm our previous c= onsensus to drop the body-hash parameter and leave the ext parameter. Body-= hash as currently specified is going to cause significant interop issues du= e to character (and other) encoding issues. Providers who desire to MAC the= body can define their own ext use case.=0A=A0=0ALet me know if you have an= objection to this change.=0A=A0=0AEHL=0A__________________________________= _____________=0AOAuth mailing list=0AOAuth@ietf.org=0Ahttps://www.ietf.org/= mailman/listinfo/oauth --835683298-1628337004-1321717586=:50797 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable
I haven't read the MAC spec recently enough, did you already deal with th= e character set issue (if there was one) comparable to the ones in the Bear= er spec?

I am +1 on the = -body_hash +ext change.

From: Eran Hammer-Lahav <eran@h= ueniverse.com>
To: = OAuth WG <oauth@ietf.org>
= Sent: Saturday, November 19, 2011 7:39 AM
Subject: [OAUTH-WG] MAC: body-hash
=0A
I want to reaff= irm our previous consensus to drop the body-hash parameter and leave the ex= t 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
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/o= auth


--835683298-1628337004-1321717586=:50797--