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

Kyle Rose <krose@krose.org> Mon, 28 October 2019 21:02 UTC

Return-Path: <krose@krose.org>
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 637EF120096 for <oauth@ietfa.amsl.com>; Mon, 28 Oct 2019 14:02:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=krose.org
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 2WC8F4RAhtRG for <oauth@ietfa.amsl.com>; Mon, 28 Oct 2019 14:02:26 -0700 (PDT)
Received: from mail-yb1-xb35.google.com (mail-yb1-xb35.google.com [IPv6:2607:f8b0:4864:20::b35]) (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 8B07D120086 for <oauth@ietf.org>; Mon, 28 Oct 2019 14:02:26 -0700 (PDT)
Received: by mail-yb1-xb35.google.com with SMTP id d12so4585678ybn.7 for <oauth@ietf.org>; Mon, 28 Oct 2019 14:02:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=krose.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=MfB80EVlyKBwZhgn9SnOsWsEsBH4+rOB0uomqTcNt8o=; b=i09gY5MI0lrGg1J022wE4MDffvIyj3yxcOFizQuTnrBXvHU4PK43B9bHSgdDzbXkx/ 0O7wDIe2go9FvSTZrK1ZFA+IUjFEte/WH+IqwhOtWbK2xQWAfQ5HanPHBIxES0KmTTNo ImPH7QPUt+UYvMfabCvZPhyBSm6r9ATKxzEPM=
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=MfB80EVlyKBwZhgn9SnOsWsEsBH4+rOB0uomqTcNt8o=; b=tAcUZKFT8ZLpy3otjYBTgE0y/+P52WkaJhg7lcyJ8TRuAgZY8lHpyjZam6Q+nzd3KL FaA8mlXTk5PYyUvJsJIcBFo7GZML9c6x2BdkmS/qsyiuFijE4WPk2xcF1kDHg89v5vPX pvBdx2RNdJVrcy/lHXjUgnjfFMvkvEWAwMK1HWHGcuJFiLOQL0+dWFnd80k3TGfJzOIx IluhssEsGF3mSC6NEHq+tN6pxQsCwCvrba9Egd/we4efUqRLhM8+3LFtr1Gixvwhz3rY y+1G+O1B28CXxkH/5D0PnHYMDe6xWwmC1AD+pxUpd15W4sjWTOKb+R5yuT5y0l4fwIfh QhKQ==
X-Gm-Message-State: APjAAAXg/Glc6a0aT3j4LJQ2hxizRIdK6Hdo74KAwlokA93xtUOV8EIF hGibhEmmCXVla1tYxCVcol54eLisNXEGUPrPxnc6RA==
X-Google-Smtp-Source: APXvYqzz6xwnGMTe2PLcAvlCswLbT26sr3yavS6zK6r+RZkM0XBvz66GZ1j3rvDtoOyA9AOlsAC4LUlATwyd4uAldAc=
X-Received: by 2002:a25:bdd4:: with SMTP id g20mr15146086ybk.127.1572296545196; Mon, 28 Oct 2019 14:02:25 -0700 (PDT)
MIME-Version: 1.0
References: <CAD9ie-snTrsJUd76_sfZLsN6mVOQt+8z0MazSYe3bGDvnsMUJw@mail.gmail.com> <CAJU8_nVyP5sezDMw3ybvRW1zEFKQZfObWqR69B+cZaVgiiYeBA@mail.gmail.com> <2348A854-97C5-45E3-BA4E-3E641B0D6DDE@mit.edu>
In-Reply-To: <2348A854-97C5-45E3-BA4E-3E641B0D6DDE@mit.edu>
From: Kyle Rose <krose@krose.org>
Date: Mon, 28 Oct 2019 17:02:10 -0400
Message-ID: <CAJU8_nXm5OWrrOTL4tscg8d5znyHfFqYVgqFEBsCGmSyJLzqsQ@mail.gmail.com>
To: Justin Richer <jricher@mit.edu>
Cc: Dick Hardt <dick.hardt@gmail.com>, oauth@ietf.org, txauth@ietf.org
Content-Type: multipart/alternative; boundary="0000000000000efc590595fed198"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/0WLCRI0jRmEOoAejsJNb4DOY4T0>
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 21:02:29 -0000

Got it. Thanks. I'll shop around for another venue.

On Mon, Oct 28, 2019, 4:57 PM Justin Richer <jricher@mit.edu> wrote:

> 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> 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
>
>
>