[OAUTH-WG] Incorporate or Reference RFC8628 Device Authorization Grant?

Phillip Hunt <phil.hunt@independentid.com> Tue, 12 May 2020 21:38 UTC

Return-Path: <phil.hunt@independentid.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 331403A0C1B for <oauth@ietfa.amsl.com>; Tue, 12 May 2020 14:38:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=independentid-com.20150623.gappssmtp.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 EvPeMINH4fPR for <oauth@ietfa.amsl.com>; Tue, 12 May 2020 14:38:54 -0700 (PDT)
Received: from mail-pj1-x1030.google.com (mail-pj1-x1030.google.com [IPv6:2607:f8b0:4864:20::1030]) (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 F1CA73A0C11 for <oauth@ietf.org>; Tue, 12 May 2020 14:38:53 -0700 (PDT)
Received: by mail-pj1-x1030.google.com with SMTP id hi11so10176969pjb.3 for <oauth@ietf.org>; Tue, 12 May 2020 14:38:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=independentid-com.20150623.gappssmtp.com; s=20150623; h=from:mime-version:subject:date:references:to:in-reply-to:message-id; bh=H4UNJmPc7YJXEaEWZA4XY3YCdl3GOQVHXDtkjcdYJWg=; b=GzKYxwEBgG55qochkVCUAKz9MXx1RVATY8v2KSMK9YQvnoeLRMX8X1oF7cG0qzYNSZ /e04j7AgfMRJtFli9d3ne9gz72qKwCf08qIW4Pwt2TS6xtPdgOEaflPFEvcwXQfeBynE GePXHdzLPkBvBXkeCfBz3lxYbdwCiZDA48MFvgzknLThTzKHqEn4/9oNg1ImeB6gS/cG YucarNuYnI4j7NleTqzSPfYEoQywIvCQdd+18G3gNN6zxXrVC07QGnN2O/n9lUTsWbIL yP4X/87SvAewJopvMv6IbSA/Ei2ewXEid1oMRophkk/qB78kzztQA/0mQcRoatuJToM0 a2Kg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:subject:date:references:to :in-reply-to:message-id; bh=H4UNJmPc7YJXEaEWZA4XY3YCdl3GOQVHXDtkjcdYJWg=; b=O/kNmht8CdRpLELlsQdU6WHmHhCrSEdyj0SxxPsL092mDvR2JdjuwzLZPzL5rdxsyo INw+IYJM8IVcKucQS1CSX1S6Bfp7HelKgAKn1oZ4+2/PvKAfFaOGGKGDyuMVzauhaRwf 4REz59r6kvZDjMEjKiBiq/yOtlFnGfqZNHQmpaul/qTNgkFUvmdd7MBPv1OylJakZgyg Jd+79/xbPMYv0l9nzeAmM3IASN3fpIfatMSWwzHnOKEV/k2KkdtCMlyJ8jsLXz5uP2yc U18JnFN6tDqf/48pSVDOg+Ragx+sYmGIj06mu7IIYhbImMl9xdt5vv0VyPq+1fhsoRmS lPMg==
X-Gm-Message-State: AGi0Pubp/pEUqE7abi4sp6wwu0PDGKvC7IJTCVH1vqntitv9SVWNAzFY qxiJyi61KJmIXtUvBt469grqGDfCHS2dCA==
X-Google-Smtp-Source: APiQypJLzKwyutgWvveDphBrGBCD3wJcROkC6WwyjuVRiHKJBqe5V13jO9+bCDuatUkD5dNBK+J/Wg==
X-Received: by 2002:a17:902:b694:: with SMTP id c20mr21705340pls.313.1589319533137; Tue, 12 May 2020 14:38:53 -0700 (PDT)
Received: from node-1w7jr9qrfoxxakjm870ptorud.ipv6.telus.net (node-1w7jr9qrfoxxakjm870ptorud.ipv6.telus.net. [2001:569:7a71:1d00:c84c:ebec:f776:a3f5]) by smtp.gmail.com with ESMTPSA id 189sm12674608pfd.55.2020.05.12.14.38.52 for <oauth@ietf.org> (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 12 May 2020 14:38:52 -0700 (PDT)
From: Phillip Hunt <phil.hunt@independentid.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_4E5342A0-FA70-4DBD-B88A-9FCD55C75ACE"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Date: Tue, 12 May 2020 14:38:50 -0700
References: <CAOW4vyNY768vqFtxxHXNd2u+VXFoiW=+BG+AJNW0Ee9H13V3zQ@mail.gmail.com> <77C31557-E3C3-4A02-9579-DEFB2CD5A683@manicode.com> <CAOW4vyM3Vi4eHCCn1x5-0K0S8pP5qtpTByNYS4DP8EaSqiWn5Q@mail.gmail.com> <CAGBSGjrhRpKaG9UdLy+OphSYwPAK7d=kVJNRkkdDV=HHjKMynQ@mail.gmail.com> <94617b561b934791933f171f5baa51cb@novatec-gmbh.de>
To: OAuth WG <oauth@ietf.org>
In-Reply-To: <94617b561b934791933f171f5baa51cb@novatec-gmbh.de>
Message-Id: <87EC353D-267A-4144-8500-79163E006279@independentid.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/syo4B6VldH1-joUBGW2YGYx_9yM>
Subject: [OAUTH-WG] Incorporate or Reference RFC8628 Device Authorization Grant?
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.29
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, 12 May 2020 21:38:55 -0000

One of the use cases brought up in the ROPC thread mentioned that redirect was hard to do in some cases (like IoT). This reminded me of RFC8628, the OAuth Device Authorization Grant. I mention it because for *some* of the cases who say redirection is hard may be able to use the Device Authz Grant.

Would it be worth including a section in OAuth 2.1 referencing RFC8628 or, possibly incorporating it?

Phil Hunt
@independentid
phil.hunt@independentid.com