IETF Logo Mail Archive

Re: [dmarc-ietf] PSD Related Privacy Considerations For Aggregate Reporting Draft

John Levine <johnl@taugh.com> Thu, 02 February 2023 17:57 UTC

Return-Path: <johnl@iecc.com>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FD8BC1575C1 for <dmarc@ietfa.amsl.com>; Thu, 2 Feb 2023 09:57:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.847
X-Spam-Level:
X-Spam-Status: No, score=-1.847 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, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b="Jysh0HuI"; dkim=pass (2048-bit key) header.d=taugh.com header.b="ia9D9Sc7"
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sRNC8TMBueas for <dmarc@ietfa.amsl.com>; Thu, 2 Feb 2023 09:57:25 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 70A9CC1516E1 for <dmarc@ietf.org>; Thu, 2 Feb 2023 09:57:24 -0800 (PST)
Received: (qmail 99949 invoked from network); 2 Feb 2023 17:57:22 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=1866a.63dbf982.k2302; bh=NmWZy8VMWN7W09RHSIawJSQrArHtBFK5Tmm03Ko92SI=; b=Jysh0HuIvC6nJfomOYILXCKUOxMBAgfOX+2TPasV7zmsGrcVqeJ0P5GCKIh3+1mj2VLlfAInmQenFmWA4f7XZYz9M8/YKVNE06yVmgfOcw+O0MsAkOx/6d79C+yrHIJtqgDCJ1h7ahjTtUvIf2xsbpwLYyp4OI2Co60t9MdODEht4Bi/Q+vnISMWPs2Dn72KbENI/Xk+3QuUthnuHOOe5uuDBjOWh3Jio+np06L6BE8GFLZ/uTf+I46G3M2Inu9MldUXPZHywvA4zzWojioY9BdxfDkf0JbmjhvYSgfy8kXrAgYDx4rQVTUUGPKbBHxCAzC8LQwsEEgpHTUAnwA2ZA==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=1866a.63dbf982.k2302; bh=NmWZy8VMWN7W09RHSIawJSQrArHtBFK5Tmm03Ko92SI=; b=ia9D9Sc7GOrEiIRkFrQcegNtTAPpYjjR3oAuDl3lJr0o+kgF7bak25usU+OH2qnbDDKQqoYnBlDe+wcwjcOivuevEMnMIpUG5n6mzsKEXNstHUS4J52+R/HxKAsKIb9kprxz6SolF49dUcC2NKJh281+RBM/m4G1cBVl6sesobm8KFfAh5ZXDGFNtshMl9l1A+O7syNgjI45mW8WCN/l35O5o+j57k70lx2bsNJ0ww7au65DZL8oDmdWKjb+FaMOoYISihnmbztYE2O4kjyB1QdpJj0dpig+RhwN0Y5TjaGwiImANuXxrDnYmLOLBJo3NF0wX6eWdLuRPS3CaJ99uw==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.3 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 02 Feb 2023 17:57:22 -0000
Received: by ary.qy (Postfix, from userid 501) id 572B7885024D; Thu, 2 Feb 2023 12:57:21 -0500 (EST)
Date: Thu, 02 Feb 2023 12:57:21 -0500
Message-Id: <20230202175721.572B7885024D@ary.qy>
From: John Levine <johnl@taugh.com>
To: dmarc@ietf.org
Cc: todd.herr@valimail.com
In-Reply-To: <CAHej_8=mDe15Soyt-VN7Sb_==8ggXQPJ=8a9vkdC1-PYJS-PWg@mail.gmail.com>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/K9pRC9oaH0gL6s5vysZYOhW85IY>
Subject: Re: [dmarc-ietf] PSD Related Privacy Considerations For Aggregate Reporting Draft
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmarc>, <mailto:dmarc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Feb 2023 17:57:30 -0000

It appears that Todd Herr  <todd.herr@valimail.com> said:
>-=-=-=-=-=-
>
>On Wed, Feb 1, 2023 at 7:14 PM Douglas Foster <
>dougfoster.emailstandards@gmail.com> wrote:
>
>>
>> What does matter is that the NP policy should only apply when the
>> organization domain is non-existent.   Existing domains have the right to
>> send using a non-existent subdomain.
>>
>
>I disagree with both statements here.

I'm with Todd.  Non-existent means the From: domain returns NXDOMAIN, as the current draft says.

While you technically have the right to send mail with any funky name
you want, in practice, the chances that anyone will accept it are
extremely low.

R's,
John

v2.23.0 | Report a Bug | By Email