[OAUTH-WG] missing IANA registration for ? Fwd: I-D Action: draft-ietf-oauth-device-flow-12.txt
Brian Campbell <bcampbell@pingidentity.com> Mon, 01 October 2018 22:23 UTC
Return-Path: <bcampbell@pingidentity.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 BCB0912008A for <oauth@ietfa.amsl.com>; Mon, 1 Oct 2018 15:23:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.201
X-Spam-Level:
X-Spam-Status: No, score=-1.201 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, MIME_BOUND_DIGITS_15=0.798, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=pingidentity.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 gMUKtT2_lyVd for <oauth@ietfa.amsl.com>; Mon, 1 Oct 2018 15:23:47 -0700 (PDT)
Received: from mail-io1-xd2b.google.com (mail-io1-xd2b.google.com [IPv6:2607:f8b0:4864:20::d2b]) (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 D6399130E6F for <oauth@ietf.org>; Mon, 1 Oct 2018 15:23:46 -0700 (PDT)
Received: by mail-io1-xd2b.google.com with SMTP id n18-v6so10793363ioa.9 for <oauth@ietf.org>; Mon, 01 Oct 2018 15:23:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pingidentity.com; s=gmail; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=pKVt/croT8RGsgemLkxG91YYv7921pZnVaJmyqxLCgc=; b=DLiFuW76L54JbWB9wOv/V5nYr7K01yrwOAmF68iqnFE6IaLKrE0WuYtv79ySmeiWPF a5jAa/93BTiGv44r2rU1ZEAOtgDlVjRQhP/qiCKHraRkpjbm4qsScZ7upzwwh7m+Yc70 TVt+XTb1ctkMkSW+HXzy8Pfy7OCrf4QYubQlc=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=pKVt/croT8RGsgemLkxG91YYv7921pZnVaJmyqxLCgc=; b=EUoKcJCpYfeFsRfDPqfTsG/wMveU0rLetynlzCSYfY0w773k9qkfMe1UZfzu4VDCk9 3T3VT8+QKZY1wnvfaN7UWQX+1n42PhH2ttrdyo/ENc3qGdYGt2Qt6TvyRNMFF/du6plg W3kBpA8xNLy4mtl3TInub/VCpAS0o5SZ95CuLabl2QPFRkwwBCZgen7kFuOiK33LjsbQ 1dKoPH2Jc7hMsguD/aieMi7CKC0Xir9Vaat5gB0eX1VT23ivDHUXrs2+Iwb/o2DOQJjL 19FnTD7i/+MyxM1BiQlmnqr8fSnSpldNJGUGHiVLUxU3RavMXbufk3O++ZvMZO0mO3A1 NlLw==
X-Gm-Message-State: ABuFfoiF6PaNQWxI1fExRUHN7oHQ4d8zgAKt31uIl2oNUFvBgtiZeNeR V+2SS3x3LBxWJly9hCqtRnhMerrqPgzS7mJFvd6UR3a3zuFKfbyJoZj5beQ1EESt/8xKp94BqK5 15zXA06mh58BrxBvoAgM=
X-Google-Smtp-Source: ACcGV62GXt1XI+wcxGenrpbdnH+Qb8zyUMGeSxmtC+kvqh+fBns5Aapk4CHXnAElsBE31gUD1Ix5HyZdfqzBGJifhDQ=
X-Received: by 2002:a6b:7104:: with SMTP id q4-v6mr6493500iog.138.1538432624519; Mon, 01 Oct 2018 15:23:44 -0700 (PDT)
MIME-Version: 1.0
References: <153316758904.21922.15270209647384469158@ietfa.amsl.com>
In-Reply-To: <153316758904.21922.15270209647384469158@ietfa.amsl.com>
From: Brian Campbell <bcampbell@pingidentity.com>
Date: Mon, 01 Oct 2018 16:23:18 -0600
Message-ID: <CA+k3eCQz7zDCBi5wJVCoG1cLGhrVn3pe-EX0xQWDr_GnVw5zzw@mail.gmail.com>
To: oauth <oauth@ietf.org>, draft-ietf-oauth-device-flow@ietf.org
Content-Type: multipart/alternative; boundary="0000000000001885690577324222"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/PW8rPd-dEYjZhK4n8Gv09WlU57U>
Subject: [OAUTH-WG] missing IANA registration for ? Fwd: I-D Action: draft-ietf-oauth-device-flow-12.txt
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: Mon, 01 Oct 2018 22:23:49 -0000
I realize this is very late in this draft's life cycle but I just noticed it while working on something different but coincidentally similar. The device flow defines a device_code parameter to be used in the access token request to the token endpoint[1] but doesn't register it as a token request parameter in the IANA Considerations[2] as would be expected/suggested by RFC6749's OAuth Parameters Registry[3]. Should the device flow register the device_code parameter? Seems like it probably should. [1] https://tools.ietf.org/html/draft-ietf-oauth-device-flow-12#section-3.4 [2] https://tools.ietf.org/html/draft-ietf-oauth-device-flow-12#section-7 [3] https://tools.ietf.org/html/rfc6749#section-11.2 ---------- Forwarded message --------- From: <internet-drafts@ietf.org> Date: Wed, Aug 1, 2018 at 5:53 PM Subject: [OAUTH-WG] I-D Action: draft-ietf-oauth-device-flow-12.txt To: <i-d-announce@ietf.org> Cc: <oauth@ietf.org> A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Web Authorization Protocol WG of the IETF. Title : OAuth 2.0 Device Flow for Browserless and Input Constrained Devices Authors : William Denniss John Bradley Michael B. Jones Hannes Tschofenig Filename : draft-ietf-oauth-device-flow-12.txt Pages : 20 Date : 2018-08-01 Abstract: This OAuth 2.0 authorization flow for browserless and input- constrained devices, often referred to as the device flow, enables OAuth clients to request user authorization from devices that have an Internet connection, but don't have an easy input method (such as a smart TV, media console, picture frame, or printer), or lack a suitable browser for a more traditional OAuth flow. This authorization flow instructs the user to perform the authorization request on a secondary device, such as a smartphone. There is no requirement for communication between the constrained device and the user's secondary device. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-oauth-device-flow/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-oauth-device-flow-12 https://datatracker.ietf.org/doc/html/draft-ietf-oauth-device-flow-12 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-oauth-device-flow-12 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ _______________________________________________ OAuth mailing list OAuth@ietf.org https://www.ietf.org/mailman/listinfo/oauth -- _CONFIDENTIALITY NOTICE: This email may contain confidential and privileged material for the sole use of the intended recipient(s). Any review, use, distribution or disclosure by others is strictly prohibited. If you have received this communication in error, please notify the sender immediately by e-mail and delete the message and any file attachments from your computer. Thank you._
- [OAUTH-WG] I-D Action: draft-ietf-oauth-device-fl… internet-drafts
- [OAUTH-WG] missing IANA registration for ? Fwd: I… Brian Campbell
- Re: [OAUTH-WG] missing IANA registration for ? Fw… William Denniss