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

Roberto Polli <robipolli@gmail.com> Mon, 04 April 2022 13:36 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 E33503A08AB for <oauth@ietfa.amsl.com>; Mon, 4 Apr 2022 06:36:04 -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, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 9NFdkbUEv-kv for <oauth@ietfa.amsl.com>; Mon, 4 Apr 2022 06:36:03 -0700 (PDT)
Received: from mail-io1-xd29.google.com (mail-io1-xd29.google.com [IPv6:2607:f8b0:4864:20::d29]) (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 994993A08A6 for <oauth@ietf.org>; Mon, 4 Apr 2022 06:36:03 -0700 (PDT)
Received: by mail-io1-xd29.google.com with SMTP id x4so11220904iop.7 for <oauth@ietf.org>; Mon, 04 Apr 2022 06:36:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:from:date:message-id:subject:to:cc; bh=ZBALgWUSYIBu0DbR0hQSzTvJ827KXVVE23ktE79NClQ=; b=Z22UJv99U2NQYBC/o0nko8N4eG1ymne7t/dB2+82/YhWojbHfy75AlkXcEmg8/13kq HOJ+dgmf+mvgxEEXeWHeRrvZIOVx2CBjLzix0insuUFsZbsHojKjDw2sX6xTgCmEysid J2d87kEdvLKV6uj+WCqyu4o0jxiJiJLZqmHVX3XZxJmTxLT/TnPjYpL5TcpjPbT2k+fY Fyo1XOUwy+OB0fv0QlYMMd+VmxOKJw/ycCdWW4te6M/Sg9/OOrxAhKhAvjZrcaojmxiq GT+rZDnp3OgIjv9Eejjaf4khk54C6ISSmurYDDyNW1+YvqpxaeJznV1h4ZqIf6V0AJtY Tkwg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=ZBALgWUSYIBu0DbR0hQSzTvJ827KXVVE23ktE79NClQ=; b=iQjCPLFZ53Bd/kcX8yzh/adUNc8vEZYpOVu6GuY0UQ7ptaD2yIe6JiBzsOI2VE6MBy k1hXigMp+I9TCVfK7NEroBJ7e0dPHdT525p04cITbDXngG659NDRZG1M/yriw32FR3Fu 4Spc4kleA76R+TAc2j70DD18cH5SqIQdGnVN31F/h7Yr1JTUkavC5LUyRlw0rx5W5ivH n8rfCM2kngQ8xmusq9AvlWjjjBuW+6KF0CGdK9Vg7fL5XlLOZzDCCbUZVroK9SNpC741 OpCTF2jyCeKeBAd37t0UUxgYS70iG233nwzXyTtqIP6PH7hpM8PPZGpU7CvEsDGej2Cc eNMg==
X-Gm-Message-State: AOAM5316dFl5T+75eL8V4OUxiOK6VMSfKkhPT29fPnEh5LBt+yG5NgQI l4mrr++Vm1ckDMW77Q9ZGAfA8U2Twan7FuhDiJyTfgc9
X-Google-Smtp-Source: ABdhPJwp28F71SY6IhpK8VxlvfiTeoCvqBF5xt307EMKDAHotHY80mHqSQRbo0HmOelwleanrnvatp1t498bW/Q08Zc=
X-Received: by 2002:a02:6649:0:b0:323:7945:c3eb with SMTP id l9-20020a026649000000b003237945c3ebmr12359841jaf.11.1649079361466; Mon, 04 Apr 2022 06:36:01 -0700 (PDT)
MIME-Version: 1.0
From: Roberto Polli <robipolli@gmail.com>
Date: Mon, 04 Apr 2022 15:35:50 +0200
Message-ID: <CAP9qbHWPfswiPFhi4ijiYO8BcFJagWHROgBtqVZzB7zghdCzsg@mail.gmail.com>
To: oauth <oauth@ietf.org>
Cc: Giuseppe De Marco <giuseppe.demarco@teamdigitale.governo.it>
Content-Type: multipart/alternative; boundary="0000000000008bf54a05dbd435a3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/WB7X7uGg-U89Et14xs0NJObGrFA>
Subject: [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 13:36:05 -0000

Hi folks,

I'm finding 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
a specific data processing.

The first idea is that this identifier is conveyed in a custom claim,
but maybe there's an existing claim/access token request parameter already.

If such a parameter does not exist, which is the procedure for registering
it?

Kind regards,
R: