IETF Logo Mail Archive

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

Kyle Rose <krose@krose.org> Mon, 28 October 2019 17:55 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 267BF120125 for <oauth@ietfa.amsl.com>; Mon, 28 Oct 2019 10:55:50 -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=unavailable 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 hvJ-Yqnxefl1 for <oauth@ietfa.amsl.com>; Mon, 28 Oct 2019 10:55:48 -0700 (PDT)
Received: from mail-yb1-xb36.google.com (mail-yb1-xb36.google.com [IPv6:2607:f8b0:4864:20::b36]) (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 2B41B12007A for <oauth@ietf.org>; Mon, 28 Oct 2019 10:55:48 -0700 (PDT)
Received: by mail-yb1-xb36.google.com with SMTP id d12so4355916ybn.7 for <oauth@ietf.org>; Mon, 28 Oct 2019 10:55:48 -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=lNBQTadQFiA4VQRvLXhGqCtLrgBi7CBnJExSBU174js=; b=bgcvAcmcmct9lpJZLmKWdYnCTY2AujOyXuY3yisnCyIbHFA81UymIMQ3TU1Mdd1DVA yvEXvQRc0PtYhnHdOnT1EYg/IyH7n8UU6NpyZh4Oss8TnDEPtdeIQU/ZBSt696rPHSHJ rOGoxWUbN6d27+2lHe2uA5u01NQILDao/D+Oc=
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=lNBQTadQFiA4VQRvLXhGqCtLrgBi7CBnJExSBU174js=; b=qC6KNW9cuA+poOheXgFyOI0EOzDhtOq+TBhF+TE83bTwbVOhf0/t6/29JsgMbeBz16 wd2OZ33ywC4JeT//7ae2I/2jP0G0NHiX0FvkFZLFSvP7EwU+V3RA4y2iZxeT4PPiY5dc 04UZMzYuUwdcLEqmyAunJxk4K8XcoPf3v3laJ794U/jfNY31t/4gYdsMyoMwhVDBosBK haz+kVMqq+ujtZsjvIuELDVv8SXelW2YtQQN2BRfS2Fzvk6xZdBW6T1Dg5OGf3gNPqKR AHvh2A9sitIb/x81/5nXDExi6wiBjjYy0vTsodCS6sgqVMSoYyIW7RzInleyl/tqtOrc 1Prw==
X-Gm-Message-State: APjAAAUTlSn0JvFeIV5hfbG9uigpFQLXpL7l6ta3K7H10HK4d4sbOm4R GzywOQphU0dRJMJc0nsJit86h5Uo57s/qjeofwbgvw==
X-Google-Smtp-Source: APXvYqyAnjWEtmYedGJP6P39RB4AzHQ1VW7zQkPsnDpHPPJf6FEhywIgoa3uFSswQiNgH/6vx/bCrTbwPSDJAcj3u9s=
X-Received: by 2002:a25:414f:: with SMTP id o76mr13650962yba.401.1572285346910; Mon, 28 Oct 2019 10:55:46 -0700 (PDT)
MIME-Version: 1.0
References: <CAD9ie-snTrsJUd76_sfZLsN6mVOQt+8z0MazSYe3bGDvnsMUJw@mail.gmail.com>
In-Reply-To: <CAD9ie-snTrsJUd76_sfZLsN6mVOQt+8z0MazSYe3bGDvnsMUJw@mail.gmail.com>
From: Kyle Rose <krose@krose.org>
Date: Mon, 28 Oct 2019 13:55:28 -0400
Message-ID: <CAJU8_nVyP5sezDMw3ybvRW1zEFKQZfObWqR69B+cZaVgiiYeBA@mail.gmail.com>
To: Dick Hardt <dick.hardt@gmail.com>
Cc: oauth@ietf.org, txauth@ietf.org
Content-Type: multipart/alternative; boundary="00000000000096ab9e0595fc35f4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/aXSBri2s27i0xVLjhJbVpQrU8z0>
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 17:55:51 -0000

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

v2.23.0 | Report a Bug | By Email