Re: [Txauth] Call for charter consensus - TxAuth WG
Aleksei Petrov <alekseipetrov@spotify.com> Sat, 07 March 2020 20:27 UTC
Return-Path: <alekseipetrov@spotify.com>
X-Original-To: txauth@ietfa.amsl.com
Delivered-To: txauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2432E3A19D8 for <txauth@ietfa.amsl.com>; Sat, 7 Mar 2020 12:27:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, 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 (1024-bit key) header.d=spotify.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 acfC1QXTnwir for <txauth@ietfa.amsl.com>; Sat, 7 Mar 2020 12:27:32 -0800 (PST)
Received: from mail-wm1-x329.google.com (mail-wm1-x329.google.com [IPv6:2a00:1450:4864:20::329]) (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 D9A333A19D5 for <txauth@ietf.org>; Sat, 7 Mar 2020 12:27:31 -0800 (PST)
Received: by mail-wm1-x329.google.com with SMTP id n8so1982665wmc.4 for <txauth@ietf.org>; Sat, 07 Mar 2020 12:27:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=spotify.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=SjD4O4TONr9vWk+o+b89F/aPmPNFiPDcvyC8UGzzkKc=; b=XrIY1ZpFImjg5VGtraCvn9gke1jAy2ca6GsG6PQBVF0ulK1D6vSYZqpBNRffqn2j9o x+/kyQC+6s5D4ymD3sVVg/f9XufEuaWBmL3AKMGBiLsPOBCP9lmxMmMyF0qcjf9ItkD8 D6QYUEo6xhTNuemFwMHCpTc5yxUoWfyAEHV8M=
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=SjD4O4TONr9vWk+o+b89F/aPmPNFiPDcvyC8UGzzkKc=; b=aFTyt/QvywOKF7VcqtYq8y1q2jXBbivGaR1vuab8w3cmeMaLvLAgWvV+u5vNt9+ta4 g5keEW5a5ChqFFFlw94iv9uRdVsEEzV7wFt38W4p7rYovjeJPi9Xat89JEG8lkqRb0Qu ZNrWP0Kh2NRitVhCCioStwgGbjbOgiG8y4eApbB/P9tpE8skcNn0QKjCvUW1C96tT9dc BftB6A4F3zj/m1hPBBmOwEjhi+Zv5iFn33AWFlL505vrPRpESf8bnAZl5TcjwltPeZFG V+Dzze+Kj+eDTOh0AwcQeoUNa5D1pR7D/+P8iAvxjSf4SM6JJ+45nS5Ml0HsD3l3pij5 Voug==
X-Gm-Message-State: ANhLgQ2pi4vI+VF9pCzwd1O4F4ogrMPcVmW1OE+Fn87iOlTADUK24QYs Bqe31BbA3o8nc8khDxIaU0I2yxzjSTn8SE+8EIM6Jw==
X-Google-Smtp-Source: ADFU+vs120v1UpcDgImK03Obb/+XN34MakOheCR81om/Y4cikROpaQHpEZDKwLRF58a79NqbtK2xOkM8L2NZ2TO6pec=
X-Received: by 2002:a1c:b743:: with SMTP id h64mr11014596wmf.88.1583612849680; Sat, 07 Mar 2020 12:27:29 -0800 (PST)
MIME-Version: 1.0
References: <A01F5301-54DF-41D4-8ABE-8B070180F6FE@gmail.com>
In-Reply-To: <A01F5301-54DF-41D4-8ABE-8B070180F6FE@gmail.com>
From: Aleksei Petrov <alekseipetrov@spotify.com>
Date: Sat, 07 Mar 2020 21:27:17 +0100
Message-ID: <CAEE7xS4p_gbh2LMmTxOQRkjByZBCFMyrSf2O_NQHObc_EKugRQ@mail.gmail.com>
To: Yaron Sheffer <yaronf.ietf@gmail.com>, txauth@ietf.org
Content-Type: multipart/alternative; boundary="0000000000005e09cd05a04999ba"
Archived-At: <https://mailarchive.ietf.org/arch/msg/txauth/WqT3SaM1xu36XUABrfiyTugqUW8>
Subject: Re: [Txauth] Call for charter consensus - TxAuth WG
X-BeenThere: txauth@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <txauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/txauth>, <mailto:txauth-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/txauth/>
List-Post: <mailto:txauth@ietf.org>
List-Help: <mailto:txauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/txauth>, <mailto:txauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 07 Mar 2020 20:27:34 -0000
> > 1. Do you support the charter text provided at the end of this email? Or > do you have major objections, blocking concerns or feedback (if so please > elaborate)? Yes > 2. Are you willing to author or participate in the development of the > drafts of this WG? Yes > 3. Are you willing to help review the drafts of this WG? Yes > 4. Are you interested in implementing drafts of this WG? Yes ---- Aleksei Petrov | Senior Software Engineer | User Platform Spotify AB Regeringsgatan 19 111 53 Stockholm On Fri, Mar 6, 2020 at 5:45 PM Yaron Sheffer <yaronf.ietf@gmail.com> wrote: > Hi Everyone, > > It appears that momentum is forming around the proposed formation of a > TxAuth working group. We’d like to more formally gauge interest in > proceeding with this work. Please do so by responding to the following > questions: > > 1. Do you support the charter text provided at the end of this email? Or > do you have major objections, blocking concerns or feedback (if so please > elaborate)? > > 2. Are you willing to author or participate in the development of the > drafts of this WG? > > 3. Are you willing to help review the drafts of this WG? > > 4. Are you interested in implementing drafts of this WG? > > The call will run for two weeks, until March 21. If you think that the > charter should be amended In a significant way, please reply on a separate > thread. > > The feedback provided here will help the IESG come to a decision on the > formation of a new WG. Given the constraints of the chartering process, > regardless of the outcome of this consensus call, we will be meeting in > Vancouver as a BoF. > > Thanks, > Yaron and Dick > > --- Charter Text Follows --- > > This group is chartered to develop a fine-grained delegation protocol for > authorization, identity, and API access. This protocol will allow an > authorizing party to delegate access to client software through an > authorization server. It will expand upon the uses cases currently > supported by OAuth 2.0 and OpenID Connect (itself an extension of OAuth > 2.0) to support authorizations scoped as narrowly as a single transaction, > provide a clear framework for interaction among all parties involved in the > protocol flow, and remove unnecessary dependence on a browser or user-agent > for coordinating interactions. > > The delegation process will be acted upon by multiple parties in the > protocol, each performing a specific role. The protocol will decouple the > interaction channels, such as the end user’s browser, from the delegation > channel, which happens directly between the client and the authorization > server (in contrast with OAuth 2.0 which is initiated by the client > redirecting the user’s browser). The client and AS will involve a user to > make an authorization decision as necessary through interaction mechanisms > indicated by the protocol. This decoupling avoids many of the security > concerns and technical challenges of OAuth 2.0 and provides a non-invasive > path for supporting future types of clients and interaction channels. > > Additionally, the delegation process will allow for: > > - Fine-grained specification of access > - Approval of AS attestation to identity claims > - Approval of access to multiple resources and APIs in a single interaction > - Separation between the party authorizing access and the party operating > the client requesting access > - A variety of client applications, including Web, mobile, single-page, > and interaction-constrained applications > > The group will define extension points for this protocol to allow for > flexibility in areas including: > > - Cryptographic agility for keys, message signatures, and proof of > possession > - User interaction mechanisms including web and non-web methods > - Mechanisms for conveying user, software, organization, and other pieces > of information used in authorization decisions > - Mechanisms for presenting tokens to resource servers and binding > resource requests to tokens and associated cryptographic keys > - Optimized inclusion of additional information through the delegation > process (including identity) > > Additionally, the group will provide mechanisms for management of the > protocol lifecycle including: > > - Discovery of the authorization server > - Revocation of active tokens > - Query of token rights by resource servers > > Although the artifacts for this work are not intended or expected to be > backwards-compatible with OAuth 2.0 or OpenID Connect, the group will > attempt to simplify migrating from OAuth 2.0 and OpenID Connect to the new > protocol where possible. > > This group is not chartered to develop extensions to OAuth 2.0, and as > such will focus on new technological solutions not necessarily compatible > with OAuth 2.0. Functionality that builds directly on OAuth 2.0 will be > developed in the OAuth Working Group, including functionality back-ported > from the protocol developed here to OAuth 2.0. > > The group is chartered to develop mechanisms for applying cryptographic > methods, such as JOSE and COSE, to the delegation process. This group is > not chartered to develop new cryptographic methods. > > The initial work will focus on using HTTP for communication between the > client and the authorization server, taking advantage of optimization > features of HTTP2 and HTTP3 where possible, and will strive to enable > simple mapping to other protocols such as COAP when doing so does not > conflict with the primary focus. > > Milestones to include: > - Core delegation protocol > - Key presentation mechanism bindings to the core protocol for TLS, > detached HTTP signature, and embedded HTTP signatures > - Identity and authentication conveyance mechanisms > - Guidelines for use of protocol extension points > > > -- > Txauth mailing list > Txauth@ietf.org > https://www.ietf.org/mailman/listinfo/txauth >
- [Txauth] Call for charter consensus - TxAuth WG Yaron Sheffer
- Re: [Txauth] Call for charter consensus - TxAuth … Aaron Parecki
- Re: [Txauth] Call for charter consensus - TxAuth … Aleksei Petrov
- Re: [Txauth] Call for charter consensus - TxAuth … Amanjeev Sethi
- Re: [Txauth] Call for charter consensus - TxAuth … Torsten Lodderstedt
- Re: [Txauth] Call for charter consensus - TxAuth … David Skaife
- Re: [Txauth] Call for charter consensus - TxAuth … Leif Johansson
- Re: [Txauth] Call for charter consensus - TxAuth … Florian Biesinger
- Re: [Txauth] Call for charter consensus - TxAuth … Lee McGovern
- Re: [Txauth] Call for charter consensus - TxAuth … Daniel DeGroff
- Re: [Txauth] Call for charter consensus - TxAuth … Justin Richer
- Re: [Txauth] Call for charter consensus - TxAuth … Sudipta Pal
- Re: [Txauth] Call for charter consensus - TxAuth … Dmitri Zagidulin
- Re: [Txauth] Call for charter consensus - TxAuth … Fabien Imbault
- Re: [Txauth] Call for charter consensus - TxAuth … Matthew De Haast
- Re: [Txauth] Call for charter consensus - TxAuth … Fabien Imbault
- Re: [Txauth] Call for charter consensus - TxAuth … Justin Richer
- Re: [Txauth] Call for charter consensus - TxAuth … Stephen Moore
- Re: [Txauth] Call for charter consensus - TxAuth … Tobias Looker
- Re: [Txauth] Call for charter consensus - TxAuth … Richard Backman, Annabelle
- Re: [Txauth] [EXTERNAL] Re: Call for charter cons… Mike Jones
- Re: [Txauth] [EXTERNAL] Re: Call for charter cons… Justin Richer
- Re: [Txauth] Call for charter consensus - TxAuth … Mike Jones
- Re: [Txauth] Call for charter consensus - TxAuth … Aaron Parecki
- Re: [Txauth] Call for charter consensus - TxAuth … Justin Richer
- Re: [Txauth] Call for charter consensus - TxAuth … Mike Jones
- Re: [Txauth] Call for charter consensus - TxAuth … David Skaife
- Re: [Txauth] Call for charter consensus - TxAuth … Justin Richer
- Re: [Txauth] Call for charter consensus - TxAuth … Torsten Lodderstedt
- Re: [Txauth] Call for charter consensus - TxAuth … Justin Richer
- Re: [Txauth] Call for charter consensus - TxAuth … Torsten Lodderstedt
- Re: [Txauth] Call for charter consensus - TxAuth … Justin Richer
- Re: [Txauth] Call for charter consensus - TxAuth … Torsten Lodderstedt
- Re: [Txauth] Call for charter consensus - TxAuth … Vladimir Dzhuvinov
- Re: [Txauth] Call for charter consensus - TxAuth … Torsten Lodderstedt
- Re: [Txauth] Call for charter consensus - TxAuth … Mike Jones
- Re: [Txauth] Call for charter consensus - TxAuth … Justin Richer
- Re: [Txauth] Call for charter consensus - TxAuth … Torsten Lodderstedt
- Re: [Txauth] Call for charter consensus - TxAuth … Justin Richer
- Re: [Txauth] Call for charter consensus - TxAuth … David Skaife
- Re: [Txauth] Call for charter consensus - TxAuth … Dick Hardt
- Re: [Txauth] Call for charter consensus - TxAuth … Nat Sakimura
- Re: [Txauth] Call for charter consensus - TxAuth … Vittorio Bertocci
- Re: [Txauth] Call for charter consensus - TxAuth … Vijay IETF
- Re: [Txauth] Call for charter consensus - TxAuth … Justin Richer
- Re: [Txauth] Call for charter consensus - TxAuth … Dick Hardt
- Re: [Txauth] Call for charter consensus - TxAuth … Mike Jones
- Re: [Txauth] Call for charter consensus - TxAuth … Dick Hardt
- Re: [Txauth] Call for charter consensus - TxAuth … Kim
- Re: [Txauth] Call for charter consensus - TxAuth … Brian Campbell
- Re: [Txauth] Call for charter consensus - TxAuth … Justin Richer
- Re: [Txauth] Call for charter consensus - TxAuth … Justin Richer
- Re: [Txauth] Call for charter consensus - TxAuth … Dick Hardt
- Re: [Txauth] Call for charter consensus - TxAuth … Torsten Lodderstedt
- Re: [Txauth] Call for charter consensus - TxAuth … Justin Richer
- Re: [Txauth] Call for charter consensus - TxAuth … Justin Richer
- Re: [Txauth] Call for charter consensus - TxAuth … Torsten Lodderstedt
- Re: [Txauth] Call for charter consensus - TxAuth … Justin Richer
- Re: [Txauth] Call for charter consensus - TxAuth … Torsten Lodderstedt
- Re: [Txauth] Call for charter consensus - TxAuth … Nat Sakimura
- Re: [Txauth] Call for charter consensus - TxAuth … Dick Hardt
- Re: [Txauth] Call for charter consensus - TxAuth … Justin Richer