IETF Logo Mail Archive

Re: [OAUTH-WG] An access token claim to identify data processing purposes

Roberto Polli <robipolli@gmail.com> Mon, 04 April 2022 16:02 UTC

Return-Path: <robipolli@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 0B4C23A0ADC for <oauth@ietfa.amsl.com>; Mon, 4 Apr 2022 09:02:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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 iTkctSbm-ru5 for <oauth@ietfa.amsl.com>; Mon, 4 Apr 2022 09:02:40 -0700 (PDT)
Received: from mail-il1-x135.google.com (mail-il1-x135.google.com [IPv6:2607:f8b0:4864:20::135]) (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 271B93A0B22 for <oauth@ietf.org>; Mon, 4 Apr 2022 09:02:40 -0700 (PDT)
Received: by mail-il1-x135.google.com with SMTP id d3so7187809ilr.10 for <oauth@ietf.org>; Mon, 04 Apr 2022 09:02:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=hqjIbKV1t4wu5ytHCGckoxo6qmV4FOw1wdZYijaH+Ps=; b=i7S4QlUolgbxgo1s+/nApgi4Zr5kvhGQAyXCbb1oe53G6X2+zRN67SswNQ+39CR+Zn keOW3w4ornpRJiEz4VB38A8853DbxT1guWRy4+a8rrceZO7dmzK2fFqw5Bs7ntr3eEg5 DRXQqo5DemSXJ0VJMTgkMnBEEWOy+6tSpV2Trkk/psofStSLZVOLX8qn+jo3M1DfURX1 K5FqT3XxiDHWdSCfTZE2qLi8DwOYT0HhV1xVWIiOT6lJ0KvpobI1r73V8ywcOZTCFlMr ZLup6a+p3AgYIG9S9DxtkmMJxCLyA+ArZd1yk8jFEzCIAR+U2dTgsnY5Y5xvTA/L7oWU K6NA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=hqjIbKV1t4wu5ytHCGckoxo6qmV4FOw1wdZYijaH+Ps=; b=CHW9dmNZpg3K5s//9j5lmJRfeWPs9cw1UlAUnxQuWPtYmKLA+ZtbFB/vxtz2dFQuMb XCCtGmaUTJqtp+iXW7gz6kwKXocFpLSdADSAiJTmY834GNbste9P9DgY7v13neila9uZ 8AjjbTIadiUUWaPelqOxouQkThWTsGfTkIvvW0CnVPgjVTyjcX04KAYSIdHNnwLBCsGq ujZnu0Nn+V9Y9lOp/ZI96qvw6mxn+OCcqYllfv+AgUQm4hrdXsWSebL3jHfiTnzh1RT+ pKhY24sL+lSBfGOpQl/U3Iyt1uq80iMbTz9yuYrYioOIAU0FdyzOwpxm8FRQ03NEuebl hWJA==
X-Gm-Message-State: AOAM532e1asfMG3SusJMEoewFzUoNxzbj4qyEPuZpEIGJAryaVPjtenT yeiJ4ShCWOzbf+lDlww9EJxzYl3/VidrrIkE/IsjTksPtvc=
X-Google-Smtp-Source: ABdhPJy+Tfxc8KY1BBHia5J3BczQyWcA60Jti490fH9VtG1CGS0UVs3gD7HjcU7Y8OkSQcRNMUsZnd3xhdaYpoLFOh0=
X-Received: by 2002:a05:6e02:2143:b0:2c9:bb85:847 with SMTP id d3-20020a056e02214300b002c9bb850847mr231555ilv.2.1649088158823; Mon, 04 Apr 2022 09:02:38 -0700 (PDT)
MIME-Version: 1.0
References: <CAP9qbHWPfswiPFhi4ijiYO8BcFJagWHROgBtqVZzB7zghdCzsg@mail.gmail.com> <CAHsNOKd3xe4EmhJvdGGE5V4fpq=sY0gWUvYJaGiMnVsrv7q-Dg@mail.gmail.com>
In-Reply-To: <CAHsNOKd3xe4EmhJvdGGE5V4fpq=sY0gWUvYJaGiMnVsrv7q-Dg@mail.gmail.com>
From: Roberto Polli <robipolli@gmail.com>
Date: Mon, 04 Apr 2022 18:02:27 +0200
Message-ID: <CAP9qbHVnENZwCZyygFdf0wqwE0fD_9yghV62vC4wpArSTYW9-A@mail.gmail.com>
To: Steinar Noem <steinar@udelt.no>
Cc: Giuseppe De Marco <giuseppe.demarco@teamdigitale.governo.it>, oauth <oauth@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000e9212b05dbd64118"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/yeqNA8sO1F6OlhNE10PT94eI4_4>
Subject: Re: [OAUTH-WG] An access token claim to identify data processing purposes
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, 04 Apr 2022 16:02:45 -0000

Thanks Noem,

Il giorno lun 4 apr 2022 alle ore 16:32 Steinar Noem <steinar@udelt.no> ha
scritto:
>>  I'm looking for a standard way to express data processing purposes in
access token/requests.
>>E.g an access token request/response should provide an identifier linked
to the reason that motivates
> Maybe you’ll find the work on RAR and identity assurance in OIDF
interesting?
> RAR could be used for indicating a “legitimate interest”, and IA could
cater for accountability.

You mean the authorization_details and verified_claims ?
Interesting! Is was wondering whether there was something more concise,
but I will investigate if that's viable for a machine-to-machine
interaction like the one
I'm working on.

Thanks again,
R:

v2.23.0 | Report a Bug | By Email