Re: [OAUTH-WG] WGLC for OAuth 2.0 Device Flow for Browserless and Input Constrained Devices

William Denniss <wdenniss@google.com> Tue, 02 January 2018 21:08 UTC

Return-Path: <wdenniss@google.com>
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 247DF1276AF for <oauth@ietfa.amsl.com>; Tue, 2 Jan 2018 13:08:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.01
X-Spam-Level:
X-Spam-Status: No, score=-2.01 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_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
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 ENrGadYud95g for <oauth@ietfa.amsl.com>; Tue, 2 Jan 2018 13:08:18 -0800 (PST)
Received: from mail-yb0-x234.google.com (mail-yb0-x234.google.com [IPv6:2607:f8b0:4002:c09::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E032D127076 for <oauth@ietf.org>; Tue, 2 Jan 2018 13:08:17 -0800 (PST)
Received: by mail-yb0-x234.google.com with SMTP id o84so20201648yba.8 for <oauth@ietf.org>; Tue, 02 Jan 2018 13:08:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=uq8RWUDCOat5mEv6g5bnoPznyvJvF/pj4tBb6F+28Kg=; b=qn9yD9Jssg/qAR6ZYoArotZPMlP4TenLboUbcLdan+wl0OjwzLxKx8YP0GbgHMk5x2 lTDfSHAZ4gnq3sff4BaH4djudjyzlxXajja6s7iWClQYPJg/Dwcf48HGZD0CbNdg42Qm J5+HaS7n2jze9BhIMCmcM3M1zNqIshEJVq12PihDnGH6n9yUbIQSC8oUq5yII0sKl2LU t7yV00ySbpmX63RlX5+8rZiH347YGyv7Im19ueQNXWD11Y7Rqi3bqZiTAEWbGPNFC8e3 ffarD8JfNqGRHoMI6yCUZO2MFPiaQ33Y07vL6hLUrgiSo1fMTzfJpyEHWbbF5jT84pqH VIWg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=uq8RWUDCOat5mEv6g5bnoPznyvJvF/pj4tBb6F+28Kg=; b=bfW20ritLcqbpWYhMTqlbA4xS8SgBsZvCEma820yEBPEOr8ESePafm+24+9Zr3m637 9rz83BjMuUtB2Ns4vXDYQJWYAawmfIwgJbEBUvBnPI6e2CT94bJEvb5Q4KXuoLsLd+Dk QFwHBvF3Nx+XaqRt9q6D3Cu4TVJkK1CERh1O6J3ySW4TLIp2gquc88NIhmbpYu4wRIp6 /SxQXRiAE9O7bqzO9+mjo0QbKNM5oP0RPtoKsKJ08iZ2CRgGTouZOqRpTUc6xzUOampL SbTrMX+Fy8mvv5jDZ+8T+v8RfTuoMG+/Ju9PhsnfkGzvRoBzAlZt8p1SvAD78A2glRAU ki7Q==
X-Gm-Message-State: AKGB3mKqUMJ0HY6YwtnJP/32YA2yPQY/NZ8R+JOPab2flwlgFA9C+8p9 ODoUkjsFUq5tAC0DvWg23Ieu81PyUdyo6hzAGQbps3yP
X-Google-Smtp-Source: ACJfBout5EwuROGckiSnX/j3MvZa6RJGjgmoLVhtdElD4AuNz3kcnOXiunJfSWj4imKMmqa2vGz7csS+q4y4/qh0Mvc=
X-Received: by 10.37.171.67 with SMTP id u61mr38690912ybi.91.1514927296640; Tue, 02 Jan 2018 13:08:16 -0800 (PST)
MIME-Version: 1.0
Received: by 10.129.160.146 with HTTP; Tue, 2 Jan 2018 13:07:56 -0800 (PST)
In-Reply-To: <b123d697-25ae-43df-2ef9-388c0adfdb92@connect2id.com>
References: <CAGL6epLJHUn+4E1jksJW=Zpu=DE84uQgARhHyPH3H8yAAkijOg@mail.gmail.com> <4e14a1ec-8b6d-476b-3949-8a0b63017232@connect2id.com> <CAAP42hBY74goaNvJBb0yQ9AG4aQAmyVGxJFxHrUYtDdefouEJA@mail.gmail.com> <b123d697-25ae-43df-2ef9-388c0adfdb92@connect2id.com>
From: William Denniss <wdenniss@google.com>
Date: Tue, 2 Jan 2018 13:07:56 -0800
Message-ID: <CAAP42hBxPhq_pMN7fON=HVW5kE=E=Xqt8Yo-9JHJOTBp6MuFLQ@mail.gmail.com>
To: Vladimir Dzhuvinov <vladimir@connect2id.com>
Cc: oauth <oauth@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c19ec7461104e0561d17fb6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/zs5Jdu5AZ9E6Jwp_mYXpeIqaOTo>
Subject: Re: [OAUTH-WG] WGLC for OAuth 2.0 Device Flow for Browserless and Input Constrained Devices
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 02 Jan 2018 21:08:20 -0000

On Fri, Dec 15, 2017 at 11:12 PM, Vladimir Dzhuvinov <
vladimir@connect2id.com> wrote:

> On 15/12/17 00:43, William Denniss wrote:
> > On Fri, Dec 8, 2017 at 11:42 AM, Vladimir Dzhuvinov <
> vladimir@connect2id.com
> >> wrote:
> >> Hi,
> >>
> >> I just got a question on Twitter about the slow_down error:
> >>
> >> https://tools.ietf.org/html/draft-ietf-oauth-device-flow-07#section-3.5
> >>
> >> The question was why slow_down is communicated via HTTP status code 400
> >> and not 429 (Too Many Requests).
> >>
> > We could, it seems to match the intent of that error code. Main reason
> it's
> > not like that so far is that 400 is the default for OAuth, I fear people
> > may not be checking for a 429. We don't strictly *need* the 429, since
> > we're returning data in machine readable format one way or another (i.e.
> > it's easy for the client to extract the "slow_down" response either way),
> > which differs from HTML over HTTP which is intended for end-user
> > consumption, making the specific status code more important.
> Yes, on a 400 clients will need to check the error JSON object anyway,
> so the "slow_down" cannot be missed. Whereas with 429 that becomes more
> likely.
>
> +1 to return "slow_down" with status 400 as it is with the other OAuth
> error codes.
>

Thanks for considering this Vladimir. To conclude this topic, it seems
there are no compelling reasons to change to the 429, and a reasonable
explanation of why it's a 400, so I think we should keep things as-is.

Rifaat: The deadline has passed on the WGLC, and I believe all comments
raised have been addressed. Can we now advance the draft?