Re: [OAUTH-WG] OAuth Device Flow spec renamed to “OAuth 2.0 Device Authorization Grant”
William Denniss <wdenniss@google.com> Wed, 13 March 2019 16:17 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 6232B13106D for <oauth@ietfa.amsl.com>; Wed, 13 Mar 2019 09:17:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.6
X-Spam-Level:
X-Spam-Status: No, score=-15.6 tagged_above=-999 required=5 tests=[DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] 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 yTydQSFBNLVy for <oauth@ietfa.amsl.com>; Wed, 13 Mar 2019 09:17:42 -0700 (PDT)
Received: from mail-io1-xd33.google.com (mail-io1-xd33.google.com [IPv6:2607:f8b0:4864:20::d33]) (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 52A111310B7 for <oauth@ietf.org>; Wed, 13 Mar 2019 09:17:37 -0700 (PDT)
Received: by mail-io1-xd33.google.com with SMTP id k21so2159790ior.13 for <oauth@ietf.org>; Wed, 13 Mar 2019 09:17:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=0jgrlCvTKk0kxuVOnDu+3DXp4PaXa70s7AXXnc+2UKU=; b=QpMRQk6+Ko81J7LmPQw8XHMkYnPlmS+HCK7+dZENYwopGqFzN30mQwIkWS11pks1hA Wfl4hZvhXQI9yDHuGrMa7odV5hxu9OWJWYz1R58ofcs/QN44ihbc4xuxX4UdtGbDHbUT wfWZaJ2Iz9JWhqhqKou1y2PJ8beHSU99toQhrhxV9xWPg/PjlduudhrK+mMFf2kB4FYd FcTjunaftt976nheknf8yBscTQkYckYmbOQpze80OkeoVZV9kjy9ONlqf2oX7NAmViMt e/NRmwtkLZKrZNV6r81vk6CF31V0R3giMoLo9QqZH+WeCZ7kUSyKBij3oDE80d6q9DXo ojMw==
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:cc; bh=0jgrlCvTKk0kxuVOnDu+3DXp4PaXa70s7AXXnc+2UKU=; b=BCh7UuBv2HYHpYreCJrua67+/p9TtXttNHqaNmvwwxupMoAH1SbnOwmhgUKZBtdMfs O0JyPJ8zt0yUw0BytWMZqNDp1IiJC64QtvZds0NzY+k9Ecb7irAgENsj1g9uW81AHM8E E5lIjsRdB0Gtej5BP0NFyxPMNDt4wCSEszMr1C3zyEeege9ufRPiuFEL8A3ILxFjnqT7 cI6uH3zLLDq1k+D9/no8d9Jfezf/M+0zjN7ryxcK3BY7HBtDnu+R2RomuO387hf53OIc G8EUNPsTeBWOgJ72qnlDg3mA5gtjfIJN12tVnXBY/hqNWK6D08AH6JQvIbBlQXFyA6Zw AzPg==
X-Gm-Message-State: APjAAAW9oapBh6iJXM/fUluKpfTknACx4otCaqZG0L2uXNUr0jmFhz6h 0KWPfvjvNgg/XBJU0ICB0vuHrkUImSj7CMryUlKw5Q==
X-Google-Smtp-Source: APXvYqyZ9A0CS1I8zsGTOD9bwZWO3lYADwL0Xgv+nmfvz7skyl0D1fWZy+MtKEGJ2IAv87Ya4PDUkiZFIL42JMlqhU4=
X-Received: by 2002:a6b:6218:: with SMTP id f24mr21433592iog.229.1552493856300; Wed, 13 Mar 2019 09:17:36 -0700 (PDT)
MIME-Version: 1.0
References: <MW2PR00MB030054A6819A3188A5010370F5490@MW2PR00MB0300.namprd00.prod.outlook.com>
In-Reply-To: <MW2PR00MB030054A6819A3188A5010370F5490@MW2PR00MB0300.namprd00.prod.outlook.com>
From: William Denniss <wdenniss@google.com>
Date: Wed, 13 Mar 2019 09:17:21 -0700
Message-ID: <CAAP42hDqfdeASxw=9D5Sdx=hA6YBdnEQ+-F1pCc0_=ebTWFY_w@mail.gmail.com>
To: Mike Jones <Michael.Jones@microsoft.com>
Cc: oauth <oauth@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000d2a2790583fc241f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/Njp16g4PqzIEx684zQDobg7t0-4>
Subject: Re: [OAUTH-WG] OAuth Device Flow spec renamed to “OAuth 2.0 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: Wed, 13 Mar 2019 16:17:45 -0000
Thank you for the recognition Mike, I'm happy to be the editor on this doc. Great write up on the blog! It's been great reading about all the people trying out the draft spec, clearly there is a lot of value to publish. Also thank you everyone who shared their results and feedback as they implemented it. I believe we managed to incorporate your feedback throughout the process, including the recent title change (which was long overdue! I never liked the prior title, despite the fact that I coined it). As the doc will hopefully soon be in the editor queue, the window for changes has likely come to a close. Happy implementing! On Mon, Mar 11, 2019 at 9:45 PM Mike Jones <Michael.Jones@microsoft.com> wrote: > I made a blog post about the renaming of the device spec and last-minute > clarifications applied at http://self-issued.info/?p=1959 and @selfissued > <https://twitter.com/selfissued>. Thanks again to William for doing the > heavy lifting! > > > > Hopefully this is the version that gets sent to the RFC Editor… > > > > -- Mike > > >
- [OAUTH-WG] OAuth Device Flow spec renamed to “OAu… Mike Jones
- Re: [OAUTH-WG] OAuth Device Flow spec renamed to … William Denniss