Re: [OAUTH-WG] Call for Adoption: OAuth 2.0 Mix-Up Mitigation

Anthony Nadalin <> Thu, 21 January 2016 03:43 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 25BEC1B2E0B for <>; Wed, 20 Jan 2016 19:43:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id QvanNqYmvn-I for <>; Wed, 20 Jan 2016 19:43:23 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id E99A51B2E0F for <>; Wed, 20 Jan 2016 19:43:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=selector1; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=TutfgZfmoqSfGMB8lewly0AMp4c/tkICUNRPIslZv0k=; b=fKGDpz1kotSRJ/ZrmWO2YgaMEkHlFJyfXc9XvoFvoVbNP3eDDbYDzhgBsK+iyDgs+EDO+puIb6OSELM4Lm5Vn5T/2AfAVuzXzT3vZLNB1VrV0dl11YF5G8Mi44A1sykCcb82a+2pikw09TN0F4xP6HbTJavXyGhfSiamW5xvoDs=
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.1.365.19; Thu, 21 Jan 2016 03:43:19 +0000
Received: from ([]) by ([]) with mapi id 15.01.0365.024; Thu, 21 Jan 2016 03:43:19 +0000
From: Anthony Nadalin <>
To: William Denniss <>, John Bradley <>, "Phil Hunt (IDM)" <>
Thread-Topic: [OAUTH-WG] Call for Adoption: OAuth 2.0 Mix-Up Mitigation
Date: Thu, 21 Jan 2016 03:43:19 +0000
Message-ID: <>
References: <> <> <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
authentication-results: spf=none (sender IP is );
x-originating-ip: []
x-ms-office365-filtering-correlation-id: 01655081-697a-48e0-e860-08d32215011f
x-microsoft-exchange-diagnostics: 1; BN3PR0301MB1234; 5:lQNOgWsbmLXQZQ0/AYtBDro3knmX/LOZ2nGXyB2yfppY8K9tgMpo4lHIXBsRmm//N2TseMPn4cOQ4ctMmZZMTI86qryQC13l27LtwokULBMoPNoCTJqM2SjFTf/jdZiAZ14LIWuhKWTu8WQ66xsFrA==; 24:WpNLW/STIpEHcpkXZkaqpAyXzLWE2+otTP9TpTEOdc/wCV/3FOAGLjZ+uueCZau+Xq3lRrg+hraMU41mwzBmtkTEmOMefZ+H/WAQuUdTT/U=
x-exchange-antispam-report-test: UriScan:; BCL:0; PCL:0; RULEID:; SRVR:BN3PR0301MB1234; UriScan:(189930954265078)(146099531331640);
x-microsoft-antispam-prvs: <>
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(61425038)(601004)(2401047)(5005006)(8121501046)(520078)(10201501046)(3002001)(61426038)(61427038); SRVR:BN3PR0301MB1234; BCL:0; PCL:0; RULEID:; SRVR:BN3PR0301MB1234;
x-forefront-prvs: 08286A0BE2
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(377454003)(53754006)(199003)(24454002)(36944003)(189002)(86612001)(76176999)(5005710100001)(1096002)(6116002)(40100003)(1220700001)(3846002)(5002640100001)(81156007)(19580395003)(93886004)(97736004)(10400500002)(54356999)(87936001)(86362001)(5003600100002)(189998001)(586003)(101416001)(102836003)(16236675004)(33656002)(5001770100001)(122556002)(105586002)(92566002)(15975445007)(19617315012)(19625215002)(790700001)(106116001)(5004730100002)(2900100001)(19580405001)(11100500001)(5001960100002)(50986999)(106356001)(77096005)(10090500001)(2950100001)(19609705001)(74316001)(76576001)(5008740100001)(4326007)(2906002)(99286002)(66066001)(10290500002)(19300405004)(8990500004)(42262002); DIR:OUT; SFP:1102; SCL:1; SRVR:BN3PR0301MB1234;; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en;
received-spf: None ( does not designate permitted sender hosts)
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_BN3PR0301MB1234F6D1E61154DBD11C4A3EA6C30BN3PR0301MB1234_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 21 Jan 2016 03:43:19.3210 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN3PR0301MB1234
Archived-At: <>
Cc: "" <>
Subject: Re: [OAUTH-WG] Call for Adoption: OAuth 2.0 Mix-Up Mitigation
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OAUTH WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 21 Jan 2016 03:43:26 -0000


From: OAuth [] On Behalf Of William Denniss
Sent: Wednesday, January 20, 2016 6:30 PM
To: John Bradley <>; Phil Hunt (IDM) <>
Subject: Re: [OAUTH-WG] Call for Adoption: OAuth 2.0 Mix-Up Mitigation

+1 for adoption, this is important work.

On Thu, Jan 21, 2016, 9:48 AM John Bradley <<>> wrote:
+1 for adoption

Mike and I are working on addressing the comments in a new draft for your reading pleasure shortly.

John B.

On Jan 20, 2016, at 10:26 PM, Phil Hunt (IDM) <<>> wrote:

+1 for adoption

+1 for Brian's comments


On Jan 20, 2016, at 14:42, Brian Campbell <<>> wrote:
I conditionally accept this document as a starting point for work in the OAuth working group on the assumption that the considerable simplifications discussed and accepted at<> will be incorporated.
This document is (should be) intended to provide a mitigation to a security problem. As such, it would be nice to see it progress a little faster than the typical WG document. The more quickly the document can progress and/or be perceived as stable, the better.

On Tue, Jan 19, 2016 at 4:49 AM, Hannes Tschofenig <<>> wrote:
Hi all,

this is the call for adoption of OAuth 2.0 Mix-Up Mitigation, see<>

Please let us know by Feb 9th whether you accept / object to the
adoption of this document as a starting point for work in the OAuth
working group.

Note: This call is related to the announcement made on the list earlier
this month, see<>. More
time for analysis is provided due to the complexity of the topic.

Hannes & Derek

OAuth mailing list<><>

OAuth mailing list<><>
OAuth mailing list<><>

OAuth mailing list<><>