Re: [OAUTH-WG] Stephen Farrell's Discuss on draft-ietf-oauth-dyn-reg-28: (with DISCUSS and COMMENT)

Stephen Farrell <stephen.farrell@cs.tcd.ie> Fri, 24 April 2015 13:00 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA5C21B2F01; Fri, 24 Apr 2015 06:00:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JHz_2LUJxAJb; Fri, 24 Apr 2015 06:00:28 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 37E891B2F00; Fri, 24 Apr 2015 06:00:28 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id D6E10BE55; Fri, 24 Apr 2015 14:00:26 +0100 (IST)
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v05gHk7vXTQV; Fri, 24 Apr 2015 14:00:26 +0100 (IST)
Received: from [134.226.36.180] (stephen-think.dsg.cs.tcd.ie [134.226.36.180]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id A682DBE54; Fri, 24 Apr 2015 14:00:26 +0100 (IST)
Message-ID: <553A3E6B.4040603@cs.tcd.ie>
Date: Fri, 24 Apr 2015 14:00:27 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: Justin Richer <jricher@mit.edu>, oauth@ietf.org, The IESG <iesg@ietf.org>, oauth-chairs@ietf.org, draft-ietf-oauth-dyn-reg@ietf.org
References: <20150424115205.3265.73381.idtracker@ietfa.amsl.com> <553A36DE.5040501@mit.edu>
In-Reply-To: <553A36DE.5040501@mit.edu>
OpenPGP: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/oauth/MZojTcJG708oug7MeHqLG7ooCQc>
Subject: Re: [OAUTH-WG] Stephen Farrell's Discuss on draft-ietf-oauth-dyn-reg-28: (with DISCUSS and COMMENT)
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/oauth>, <mailto:oauth-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/oauth/>
List-Post: <mailto:oauth@ietf.org>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Apr 2015 13:00:30 -0000


On 24/04/15 13:28, Justin Richer wrote:
>>
> 
> It can get as bad as the web, which is pretty bad, but I hope we don't
> have to point that out in great detail in every RFC that deals with the
> web. :) I think the drive-by-download malware example is a good one, and
> we could add another concrete one if you've got an idea, but I think the
> advice we have is sound and actionable and we should avoid having this
> spec be a catalogue of "bad things what can happen on the web". If there
> is such a reference, I'm happy to point to it!

That's fair. I'm not aware of a really good reference tbh. I
wonder is there any relevant bits in the OAuth threat analysis?
(I've not looked.) Or just a pointer to some well known
incident might help.

But this is a non-blocking comment, so you should feel entirely
free to handle it as you think best.

Cheers,
S.