IETF Logo Mail Archive

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

Dick Hardt <dick.hardt@gmail.com> Mon, 28 October 2019 18:03 UTC

Return-Path: <dick.hardt@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 6C71512007A; Mon, 28 Oct 2019 11:03:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, 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 (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 dWOhRbw49Kth; Mon, 28 Oct 2019 11:03:08 -0700 (PDT)
Received: from mail-lf1-x12b.google.com (mail-lf1-x12b.google.com [IPv6:2a00:1450:4864:20::12b]) (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 B9172120072; Mon, 28 Oct 2019 11:03:07 -0700 (PDT)
Received: by mail-lf1-x12b.google.com with SMTP id v4so5085338lfd.11; Mon, 28 Oct 2019 11:03:07 -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=vIG7iNOwuQwG8jMui0VjAqXMrzT9KWr3IxYaJxLv8e8=; b=i2i+Ep0XLN3Fqir9F3StWHJ43dTbyy4Gspamf8RIEatyATMIQMLZ37YjEfzOMtaskq 1A9vArjM7ihCy+HMZAKGvxaqZuYVIXet/YeAAr82bC6AIX4QrUO9ob87IdfXjBco0LPV CWYqqXp6MddYodW4t6cQrXqa45gKy+8hO8IdfxdyUh9bvBvj281QDPgM6d/dWSbDg58p f94oLB4KVh7ozhsWb18TxQHDClKK3hi4NPe1Je23J2o7bZcHmlTIubO4uaukh8Tk20GA VEd/bWpVFOlfJtVNI733s4ay+lQGYteLqySa5eXGfXc0/v2WcOiU2VVvceePSj7Pg2mc Gs0A==
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=vIG7iNOwuQwG8jMui0VjAqXMrzT9KWr3IxYaJxLv8e8=; b=HOptZMEx/5yJZyWdWzrZ3GF3j6q2N94jYV1ug+dZdOC4eVvO0oLe7HqPHvXYkVp7QO Z7byFK1drCLwQA2E3jY+rq+BAbKLwFNahX+z7zMwmh+6uQFcJs5il1rQN62Zxqepq4ba u0HwyaLs1639sAGGauHi8Nj3NaCqlSj6/8ho2bZZkZexJ6nm80lHVQHdrSAnm+NzCwC2 nCp+LggAPa+2Hfx1YJydem067OJSVpJQJXjRaF5HC1dbSmCxaL19yscSO2BnBprNMW0i ieQto6qrm07ixrRWqUquUAH1DfePkb0vSb1HfhHBD7CgZV7r3mWlYxjvgVU6VoysISAe kLMQ==
X-Gm-Message-State: APjAAAWs2stBT0Gob9Sp2HzaqEZVNCwWXxuZdX/SQzsngSD1kxUBY7DB tOT1A8gbnOpeE7RT3KgeK81WbQ0yh/uKECr/fjo=
X-Google-Smtp-Source: APXvYqwiH2dl1ShahlTmBK9AgN8pgBgUu9EbcrKDs3DzqwwvKUL3Q9EZOQV+NLZz8ONy9Khmjq5Sm2EJzUrGjwEnfos=
X-Received: by 2002:ac2:42c7:: with SMTP id n7mr12220096lfl.138.1572285785804; Mon, 28 Oct 2019 11:03:05 -0700 (PDT)
MIME-Version: 1.0
References: <CAD9ie-snTrsJUd76_sfZLsN6mVOQt+8z0MazSYe3bGDvnsMUJw@mail.gmail.com> <CAJU8_nVyP5sezDMw3ybvRW1zEFKQZfObWqR69B+cZaVgiiYeBA@mail.gmail.com>
In-Reply-To: <CAJU8_nVyP5sezDMw3ybvRW1zEFKQZfObWqR69B+cZaVgiiYeBA@mail.gmail.com>
From: Dick Hardt <dick.hardt@gmail.com>
Date: Mon, 28 Oct 2019 11:02:54 -0700
Message-ID: <CAD9ie-stgPmkgBHcfCCt7n+VeNqdJ=SPE30TgXNSCsOqh=RuUw@mail.gmail.com>
To: Kyle Rose <krose@krose.org>
Cc: oauth@ietf.org, txauth@ietf.org
Content-Type: multipart/alternative; boundary="000000000000bf93b60595fc4fa3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/5t4wZYnBZODEi0LhfNdUO_EzUes>
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 18:03:10 -0000

My understanding was it was transaction authorization.

(it is unfortunate that authorization and authentication both start with
'auth' in english - 'authN' and 'authZ' are preferred to 'auth' IMHO)

On Mon, Oct 28, 2019 at 10:55 AM 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
>

v2.23.0 | Report a Bug | By Email