IETF Logo Mail Archive

[OAUTH-WG] Privacy Considerations section in OAuth 2.1?

Dick Hardt <dick.hardt@gmail.com> Mon, 10 August 2020 16:42 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 8074C3A0A06 for <oauth@ietfa.amsl.com>; Mon, 10 Aug 2020 09:42:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.435
X-Spam-Level:
X-Spam-Status: No, score=-0.435 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_FONT_LOW_CONTRAST=0.001, HTML_IMAGE_ONLY_08=1.651, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, URIBL_BLOCKED=0.001] autolearn=no 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 9kNPrEKxVwUC for <oauth@ietfa.amsl.com>; Mon, 10 Aug 2020 09:42:34 -0700 (PDT)
Received: from mail-lf1-x136.google.com (mail-lf1-x136.google.com [IPv6:2a00:1450:4864:20::136]) (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 E2E803A0A3A for <oauth@ietf.org>; Mon, 10 Aug 2020 09:42:33 -0700 (PDT)
Received: by mail-lf1-x136.google.com with SMTP id i80so5051901lfi.13 for <oauth@ietf.org>; Mon, 10 Aug 2020 09:42:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to:cc; bh=Eow0WXVUW/yUCSTWwf5W8aFgbZL3R0D3152d/Ncoglc=; b=DfVBx7fSSY0ZYI+oY3xCpLWls40jKa30vLZA4lPYr563tgh75zn1WYi2TYhdWFSxBq bd4YeJqSUE50/aTk6J72LsEJrPmAMoCE531tSSVWQAqBMxwNyPP8+Jnu4PTk2aeX2jAV vpnSwoub+TGrY9YV6TQlwKNWa9PcW9toZRn19d8K5rOwboeim5qpas2N14S/xoWJ65jE xDip6cKL2bKgo1JEd+u8e4ijYY8Lx+fgbGFao2vpRDNVx3KJn79TtkvVA3ExnLRUCHXj kECUFUglPnnkA+CKVv4jA+HsH1WOuioodmH6Yc+XnVycDqh7V77I3rAwd8xzVDo7n33J XyFg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=Eow0WXVUW/yUCSTWwf5W8aFgbZL3R0D3152d/Ncoglc=; b=rEDetx5JQkK+Ynoboxc+z9OpkU686UcUG6xZ1FtlSZVoAjMlnHjTbuLYknCcZOSmKj +tcHl0pHy+ZEJiy4NS51Y4hpUi+El/HYqp+0kzYw1AZs3yHXkE33Qs4SBaNF8KzVI6tk ZVdT9Jn7r8iOA5SZfZED71KGQs0d6iWt8jrfUBBWzdaKSU+ppq3ujXEpb+lxWtHDMl5J 1jF8FCLsBAXdp2Mym3Yg7rL89dwL6AOfmGPhkM+O+1aUkDOspQFcZhF6XdMSHVbKso6B 2HQR2F1fv8tpUq8jkDYtOVT7OdOnkhpt30KIFATrnnAH7rTAKeJ9jWmQNfBPNiE3je2M FK1A==
X-Gm-Message-State: AOAM531aLao6pNgiTr+j30SbotYNiU4ULSh8xC5/KBe7/TBKboYnOe9A MFQj9xlR8h4GU5dW+PFxw948RWUVprD3PfgKi/sT+qWM
X-Google-Smtp-Source: ABdhPJxl63Khf57ppvT2J+nhb9jb1RJgtsEcsJRDqKpTJtHcsK2AFHeeR9djRjc/5M5/5jOZwvCNdOBufrq3uYTH2nk=
X-Received: by 2002:a19:8044:: with SMTP id b65mr975228lfd.91.1597077751606; Mon, 10 Aug 2020 09:42:31 -0700 (PDT)
MIME-Version: 1.0
From: Dick Hardt <dick.hardt@gmail.com>
Date: Mon, 10 Aug 2020 09:41:55 -0700
Message-ID: <CAD9ie-uPT3Yp12gkkUaBEEwEc3P9uGdQpHTVPypf7gaescwKOw@mail.gmail.com>
To: oauth@ietf.org
Content-Type: multipart/alternative; boundary="00000000000010311205ac88a421"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/APBwFH-kcK3UcGmm4nd5nXL5-QI>
Subject: [OAUTH-WG] Privacy Considerations section in OAuth 2.1?
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, 10 Aug 2020 16:42:36 -0000

In the PAR meeting today, Denis requested there be a privacy considerations
section in PAR. I don't think there is anything specific in PAR that would
change the privacy considerations of OAuth, and am checking if there is WG
interest, and consensus, on including a Privacy Considerations section in
the OAuth 2.1 draft.

/Dick
ᐧ

v2.23.0 | Report a Bug | By Email