IETF Logo Mail Archive

Re: [OAUTH-WG] [Txauth] Tx Auth BOF agenda items

Justin Richer <jricher@mit.edu> Mon, 28 October 2019 20:57 UTC

Return-Path: <jricher@mit.edu>
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 47E7F120072; Mon, 28 Oct 2019 13:57:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 8XKgRLMH8Ycg; Mon, 28 Oct 2019 13:57:22 -0700 (PDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 70F64120024; Mon, 28 Oct 2019 13:57:22 -0700 (PDT)
Received: from [192.168.1.7] (static-71-174-62-56.bstnma.fios.verizon.net [71.174.62.56]) (authenticated bits=0) (User authenticated as jricher@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id x9SKvIoM008870 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 28 Oct 2019 16:57:19 -0400
From: Justin Richer <jricher@mit.edu>
Message-Id: <2348A854-97C5-45E3-BA4E-3E641B0D6DDE@mit.edu>
Content-Type: multipart/alternative; boundary="Apple-Mail=_EB174CE9-782C-4C0A-BC1B-D4AE5F9E7A22"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Mon, 28 Oct 2019 16:57:18 -0400
In-Reply-To: <CAJU8_nVyP5sezDMw3ybvRW1zEFKQZfObWqR69B+cZaVgiiYeBA@mail.gmail.com>
Cc: Dick Hardt <dick.hardt@gmail.com>, oauth@ietf.org, txauth@ietf.org
To: Kyle Rose <krose@krose.org>
References: <CAD9ie-snTrsJUd76_sfZLsN6mVOQt+8z0MazSYe3bGDvnsMUJw@mail.gmail.com> <CAJU8_nVyP5sezDMw3ybvRW1zEFKQZfObWqR69B+cZaVgiiYeBA@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/PDPPO00L-OH0DOXMbpMqfMas3js>
Subject: Re: [OAUTH-WG] [Txauth] Tx Auth BOF agenda items
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, 28 Oct 2019 20:57:24 -0000

The intended scope is to provide a transactional model for doing authorization delegation, not for authenticating a transaction itself. I can understand the confusion! Naming things is hard. 

 — Justin

> On Oct 28, 2019, at 1:55 PM, Kyle Rose <krose@krose.org> wrote:
> 
> On Mon, Oct 28, 2019 at 11:39 AM Dick Hardt <dick.hardt@gmail.com <mailto:dick.hardt@gmail.com>> wrote:
> Hey OAuthers
> 
> As chair of the Tx BOF coming up in Singapore on Nov 18 @ 5:30-7:30PM	Monday Afternoon, I'm gathering who would be interested in making presentations, and how much time you would like. 
> 
> Is this BoF limited to authorization, or would something like end-to-end authentication of transaction request/response via a less trusted intermediary (e.g., an API gateway or CDN) for purposes of limiting transitive trust be in scope? I'm thinking of something akin to OSCORE-style transactions, but more general (e.g., not specific to constrained computing environments, not forcing the use of CBOR).
> 
> Thanks,
> Kyle
> -- 
> Txauth mailing list
> Txauth@ietf.org
> https://www.ietf.org/mailman/listinfo/txauth

v2.23.0 | Report a Bug | By Email