Re: [dmarc-ietf] Comment on draft-ietf-dmarc-psd

"John Levine" <johnl@taugh.com> Mon, 11 November 2019 22:31 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 193651201A3 for <dmarc@ietfa.amsl.com>; Mon, 11 Nov 2019 14:31:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.751
X-Spam-Level:
X-Spam-Status: No, score=-1.751 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=xy56hIOD; dkim=pass (1536-bit key) header.d=taugh.com header.b=UP+khSct
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 O74Mazr6a5wJ for <dmarc@ietfa.amsl.com>; Mon, 11 Nov 2019 14:31:13 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 83D87120133 for <dmarc@ietf.org>; Mon, 11 Nov 2019 14:31:13 -0800 (PST)
Received: (qmail 60813 invoked from network); 11 Nov 2019 22:31:11 -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; s=ed8a.5dc9e12f.k1911; i=printer-iecc.com@submit.iecc.com; bh=ON5W0PRWZVbU3Zd81lTbbhaA9YnE+k5k6HW6W5fj848=; b=xy56hIODCLyBGgirywoYR/D5l7PYyp3tU97qsBbJmRZpJRWTVHI3QfxTmis00Wwkyr7RSrBDWHECD4WCbMBacUcsKxJotwbFa5v/V4zUwYVZjkbWwk9YMbc1a6mhI5HoEjTT9XUtErEyMtkGFGCRHTbjxrO4KEbfjig4VaWreSMsbrn7JiVtZ77RLTkwIqLN0HxMqet/BWavswxIi9wN1kkKKBApEUYmJVX8RIRK/Ynn+dk092LZ3Z/V2j9+QXVb
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; s=ed8a.5dc9e12f.k1911; olt=printer-iecc.com@submit.iecc.com; bh=ON5W0PRWZVbU3Zd81lTbbhaA9YnE+k5k6HW6W5fj848=; b=UP+khSctusZckqM+hjceVD/92vpyyi9O3SxsEjBHbIcNak5fj24pfTTeeCBBjsCo02Jx8ZI1j6TUwIs8+fAqOHuUcz2tkru/LQbAf3UtxKfNQpERiNqN8vAFsHfSw1yLybs/WLFSR7lIh4t+30rjElw/ufOeHvt1doJ68gWb18JUYZP1PySIehVMBnj7gZnBhvhYkRX3mF3jUoJHmbGj1ARmwl7mwErVvOBDLHzAU1UgrADF3wfQZVm1B4Hk7aGI
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 ESMTPSA (TLS1.2 ECDHE-RSA AES-256-GCM AEAD, printer@iecc.com) via TCP6; 11 Nov 2019 22:31:11 -0000
Received: by ary.qy (Postfix, from userid 501) id D6663EA2E32; Mon, 11 Nov 2019 17:31:10 -0500 (EST)
Date: 11 Nov 2019 17:31:10 -0500
Message-Id: <20191111223110.D6663EA2E32@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: dmarc@ietf.org
Cc: tjw.ietf@gmail.com
In-Reply-To: <CADyWQ+Houc21vE5Hu8nVeEMQw_u0VxD=taVJcqgwk9NObrduzw@mail.gmail.com>
Organization: Taughannock Networks
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/wJmyLe-W0yuLyvLc_xr_QtdB4hw>
Subject: Re: [dmarc-ietf] Comment on draft-ietf-dmarc-psd
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: Mon, 11 Nov 2019 22:31:15 -0000

In article <CADyWQ+Houc21vE5Hu8nVeEMQw_u0VxD=taVJcqgwk9NObrduzw@mail.gmail.com>; you write:
>https://datatracker.ietf.org/doc/draft-brotman-rdbd/
>
>which defines a mechanism where two domains can state they are related, or
>not related via DNS records.
>What one wishes to use this information is left to them.
>
>It would be great to get y'all giving feedback

If it's useful at all, which I don't think it is, it's definitely not
useful for PSD since it's intended to describe cross-tree
relationships, not the vertical ones that the PSL identifies and that
PSD needs.

This proposal also invents yet another signature scheme, presumably
for the benefit of people who don't think DNSSEC will ever work, which
is strange since the lead author works for Comcast who have what is
probably the world's biggest set resolvers that validate and use
DNSSEC and DANE.

R's,
John

PS: It's not that I think there are no cross-tree relationships to
describe, it's that we know from Andrew Sullivan's failed SOPA
proposal that doing it one label at a time rather than subtree
to subtree isn't viable.