Re: [OAUTH-WG] OAuth 2.1-03 - WG adoption?
Sascha Preibisch <saschapreibisch@gmail.com> Mon, 06 July 2020 23:01 UTC
Return-Path: <saschapreibisch@gmail.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 D8A883A0BD4 for <oauth@ietfa.amsl.com>; Mon, 6 Jul 2020 16:01:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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=gmail.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 eYYvjYx62eGE for <oauth@ietfa.amsl.com>; Mon, 6 Jul 2020 16:01:15 -0700 (PDT)
Received: from mail-wm1-x334.google.com (mail-wm1-x334.google.com [IPv6:2a00:1450:4864:20::334]) (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 0D7103A0BD1 for <oauth@ietf.org>; Mon, 6 Jul 2020 16:01:15 -0700 (PDT)
Received: by mail-wm1-x334.google.com with SMTP id o8so40911790wmh.4 for <oauth@ietf.org>; Mon, 06 Jul 2020 16:01:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=r47HpAQNlBYt7gV3OY20zKFBeg76+lnn1Y9GJA6KHKo=; b=SxN+iBB3DOxROScGI5mlDit53tK3SbWx6nlb4RFX60VwmQxxJYdMKhBEmz2bccnw+z QGF+EUVrBwE8Sx2OEwFoHVC3Q2BkGSmu7T9fIn29Xn5u43tmPTWqCSrkkWnaScukU8sT Vd1PGAzCzh8v1SXvurtgET5b6zqM39Qm/3OY46ZdiYlWbLrNX+0RF5s2dc/YVmNiwdxP AOhpPQ3I6egtYIuPtEJVMieMbZXUXncIwe55naVEgRzUG9j3kOX97bV864kkoW/wfkJH +2TAcp9DD6W1G9s5Cmi1K0uU6Od2GQIrvPhFU6frbc3DHImBpDvGuqUQmtWaFPtOdnu8 kAuQ==
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=r47HpAQNlBYt7gV3OY20zKFBeg76+lnn1Y9GJA6KHKo=; b=dQfweIv76WKkDe9ihH/r7hYolzi4YBi1oqOPpw32T4BfhBTeSP0xrVZjnRaEuLdgdF NeFNreHRfE8Nz+JAaLb44bia4zCBi9JDRl68zc7Nds5UYrChPxl/IvC9g0cgSCtVMutv 0rWq3SeVo81DjUDJhS55Ws+eqEVpyblV54TMIDeRScDlBLbdPhA0G1UtbE0oIpi4Nqfh Qk6zXiN4GQYwnr/Unay1Isr7gxSci8EJyJP2MeDPn19BKZ+q+fkF0TAElBAY+oPkUADE dbi3twBS3c+0+/TZLsUq1B83LT6bK1CXQwK/aFzHSmnIAmNjBNUaR9OpBhROeVMPDYcM Eilg==
X-Gm-Message-State: AOAM532KD2HpKxbfTMFjFKgPk4nNyf3LvL/QZ4BWNCjTqCFAC+ES90VX S2iIwyqkYhPQBHZjYxCBipiNeaTn+hx67OUhtC9MDMNL
X-Google-Smtp-Source: ABdhPJzMlGPcH86aPyLUvaLGnQMCS2rIn/XcSSxpeZvbrzde9Bfdf+A3rP263Hd26VZ8gG1DfqxcZXRznI5RfcyvguA=
X-Received: by 2002:a05:600c:2483:: with SMTP id 3mr1245827wms.120.1594076473249; Mon, 06 Jul 2020 16:01:13 -0700 (PDT)
MIME-Version: 1.0
References: <CAD9ie-uOiy92_68YzLajEDr4kjoKwvmn1aQiz6_=HojpbWYtPA@mail.gmail.com> <CAP=vD9uL2CRFr0ACxtOA=0UiL6soUbS5wGZS0SSLheqfoqC9_Q@mail.gmail.com> <CAD9ie-srhMovGh8pjhas6FdcNSH-KqCPZZkYtrs+ueO-PeeLfw@mail.gmail.com>
In-Reply-To: <CAD9ie-srhMovGh8pjhas6FdcNSH-KqCPZZkYtrs+ueO-PeeLfw@mail.gmail.com>
From: Sascha Preibisch <saschapreibisch@gmail.com>
Date: Mon, 06 Jul 2020 16:00:00 -0700
Message-ID: <CAP=vD9sMXv6EYmS3zicyJt1PPE_vdqSTMM=kvKfEFe2Nf4ARvA@mail.gmail.com>
To: Dick Hardt <dick.hardt@gmail.com>
Cc: IETF oauth WG <oauth@ietf.org>
Content-Type: multipart/related; boundary="000000000000ef03c005a9cdd9df"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/EGg7f-B7pAoDNJmSB_mUbUPOXIM>
Subject: Re: [OAUTH-WG] OAuth 2.1-03 - WG adoption?
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, 06 Jul 2020 23:01:18 -0000
Thanks, Dick! That slide compares easier than the documents next to each other, for sure! I will continue with my comparison and provide feedback as soon as I feel it's worth talking about it. Regards, Sascha On Mon, 6 Jul 2020 at 15:19, Dick Hardt <dick.hardt@gmail.com> wrote: > Hey Sascha > > This slide below from one of Aaron's presentations may help guide you what > OAuth 2.1 is about. > > There are no "new" features -- everything already exists. > There are no changed definitions. We added "credentialed" client. > > Yes, this list is the right place to discuss the OAuth 2.1 doc ... :) > > /Dick > > [image: image.png] > ᐧ > > On Mon, Jul 6, 2020 at 2:46 PM Sascha Preibisch <saschapreibisch@gmail.com> > wrote: > >> Hi all! >> >> I am reading through this document for the first time. I am mainly >> looking at it in comparison to OAuth 2.0 (RFC 6749) and with the eyes >> of a developer. I am trying to understand where phrases have changed >> and, of course, where features are changing. >> >> What is the best way to provide feedback? In this mailing list? >> >> Thanks, >> Sascha >> >> On Mon, 6 Jul 2020 at 09:44, Dick Hardt <dick.hardt@gmail.com> wrote: >> > >> > Aaron, Torsten, and I -- with some help from Daniel -- have created a >> new version of draft-pareck-oauth-v2-1. I think we are ready for a WG >> adoption call (assuming the updated charter). >> > >> > Here is the doc: >> > >> > https://tools.ietf.org/html/draft-parecki-oauth-v2-1-03 >> > >> > Here is a link to the diff from -02: >> > >> > https://tools.ietf.org/rfcdiff?url2=draft-parecki-oauth-v2-1-03.txt >> > >> > This version incorporates feedback from the WG, as well as editorial >> changes to improve readability. Highlights: >> > >> > - Appendix of current known extensions, and references to the Appendix >> so that readers become aware of related work. >> > >> > - defined new client type - credentialed clients - a client that has >> credentials, but the AS has not confirmed the identity of the client. >> Confidential clients have had their identity confirmed by the AS. We talked >> about changing the names of confidential and public, but thought that would >> be confusing. This new definition cleans up the text substantially. >> > >> > - consistent use of redirect URI rather than mixing in redirect >> endpoint URI and redirect endpoint. >> > >> > - adopted new language on when PKCE is required. >> > >> > - removed IANA section (nothing new is in 2.1) >> > >> > / Dick >> > >> > >> > >> > _______________________________________________ >> > OAuth mailing list >> > OAuth@ietf.org >> > https://www.ietf.org/mailman/listinfo/oauth >> >
- [OAUTH-WG] OAuth 2.1-03 - WG adoption? Dick Hardt
- Re: [OAUTH-WG] OAuth 2.1-03 - WG adoption? Sascha Preibisch
- Re: [OAUTH-WG] OAuth 2.1-03 - WG adoption? Dick Hardt
- Re: [OAUTH-WG] OAuth 2.1-03 - WG adoption? Sascha Preibisch
- Re: [OAUTH-WG] OAuth 2.1-03 - WG adoption? Sascha Preibisch
- Re: [OAUTH-WG] OAuth 2.1-03 - WG adoption? Vladimir Dzhuvinov
- Re: [OAUTH-WG] OAuth 2.1-03 - WG adoption? Sascha Preibisch
- Re: [OAUTH-WG] OAuth 2.1-03 - WG adoption? Dick Hardt
- Re: [OAUTH-WG] OAuth 2.1-03 - WG adoption? Sascha Preibisch