Re: [dmarc-ietf] Lookup Limitations For Public Suffix Domains

Scott Kitterman <sklist@kitterman.com> Sat, 01 December 2018 01:04 UTC

Return-Path: <sklist@kitterman.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 BE825128D68 for <dmarc@ietfa.amsl.com>; Fri, 30 Nov 2018 17:04:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (unsupported algorithm ed25519-sha256)" header.d=kitterman.com header.b=FObd2/84; dkim=pass (2048-bit key) header.d=kitterman.com header.b=Fn9faUAd
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 3XzPZoT6MG0H for <dmarc@ietfa.amsl.com>; Fri, 30 Nov 2018 17:04:08 -0800 (PST)
Received: from mailout03.controlledmail.com (mailout03.controlledmail.com [208.43.65.50]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0EC75128CB7 for <dmarc@ietf.org>; Fri, 30 Nov 2018 17:04:08 -0800 (PST)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201803e; t=1543626245; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from : subject : date; bh=n8r0aq0nl6LhA6vkgumIcfOYTA7jOq0UQxdshehZPKM=; b=FObd2/84mfBKMT9RX1V3xR1jAP2WkpshgTqKJywY/9AlslnsTaxQfADM nFB/7Fp8xvf+CkbK+19KgmEOdtGYCw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201803r; t=1543626245; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from : subject : date; bh=n8r0aq0nl6LhA6vkgumIcfOYTA7jOq0UQxdshehZPKM=; b=Fn9faUAdx60YhKQIFER5tOMxSBU3UfClpGoKGUALlzRvf6ldH2PS7My0 EEPBgx9qb9Bkb44b9g1PTq75cu20VrkJwloq92n3TGJrOhn5CEI8xqitFd hXjEQyW8e6Mr++tLDJZBpknW6uk91Efhs9ClKhQCo7kTcsrJSGPdGOczva YibEFaDbPSND1AW7O94dC8+t9QrcS0MUWWeh5as7lA+ta1xELNC7UdG1jo BA/uLbFIgfbisxKg274LvQHtLtOUwNKB5tlTfzu9wEbHaLNgp38a2qaes5 g9z3r7zQzutqzhg5drcisCK81+axH4RmuPelOaQjqsXSEepBoUOK1Q==
Received: from kitterma-e6430.localnet (mobile-166-170-35-7.mycingular.net [166.170.35.7]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout03.controlledmail.com (Postfix) with ESMTPSA id EB6F9C40190 for <dmarc@ietf.org>; Fri, 30 Nov 2018 19:04:04 -0600 (CST)
From: Scott Kitterman <sklist@kitterman.com>
To: dmarc@ietf.org
Date: Fri, 30 Nov 2018 20:04:04 -0500
Message-ID: <6368515.cyHHj4lf58@kitterma-e6430>
User-Agent: KMail/4.13.3 (Linux/3.13.0-158-generic; KDE/4.13.3; x86_64; ; )
In-Reply-To: <20181201003301.1DFFA200915FC3@ary.qy>
References: <20181201003301.1DFFA200915FC3@ary.qy>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/I0Qj__UVTE7qTYyrV-jqBIsUy2Y>
Subject: Re: [dmarc-ietf] Lookup Limitations For Public Suffix Domains
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
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: Sat, 01 Dec 2018 01:04:10 -0000

On Friday, November 30, 2018 07:33:00 PM John Levine wrote:
> In article <3881693.rR9BVk4Dlq@kitterma-e6430> you write:
> >2.  Externalize signaling about PSD participation.  As discussed in the
> >Privacy Considerations (section 4.1), we were concerned about the privacy
> >implications of feedback on organizational domain traffic for
> >organizational domains that don't participate in DMARC being
> >inappropriately captured by public suffix operators.
> 
> It seems to me this horse left the barn a long time ago.  Mail systems
> routinely check domains in HELO and in MAIL FROM against DNSBLs, which
> is at least as loggy as anything a DNS version of this check will do.
> 
> Also, if you really want to keep people from logging your queries, you
> can set up a local mirror of the DNS zone, and update it in the usual
> way with AXFR and IXFR.  Whatever one might have in mind for a text
> version of this, a binary AXFR would be about as fast and IXFR of just
> the occasional change faster.
> 
> Take a look at my DBOUND proposal.  I think it would be just the
> ticket for this application.

I've lost track.  Which draft was that?

I don't agree that a situation being bad is a reasonable reason not to try and 
keep it from getting worse.  I think the implications of the DMARC feedback 
reports are greater than logging queries.

Scott K