Re: [dmarc-ietf] DNS library queries for DKIM and DMARC records?

"John Levine" <johnl@taugh.com> Sun, 14 April 2019 03:20 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 46C7B120351 for <dmarc@ietfa.amsl.com>; Sat, 13 Apr 2019 20:20:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=EeYqes7j; dkim=pass (1536-bit key) header.d=taugh.com header.b=DTVeOLKy
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 IdsciepNsmqf for <dmarc@ietfa.amsl.com>; Sat, 13 Apr 2019 20:20:52 -0700 (PDT)
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 7312312034D for <dmarc@ietf.org>; Sat, 13 Apr 2019 20:20:52 -0700 (PDT)
Received: (qmail 23506 invoked from network); 14 Apr 2019 03:20:49 -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=5bce.5cb2a711.k1904; bh=VSOnkeVJmUL+Vw0oTINr00/rkJDJ7UUM17sJ8mvea+I=; b=EeYqes7j8KSbtxeOUhh7nT6HlotfF3biILvmqfOAmgXJv25WeqqnZEixRPPq6nuxDVv7KBb9wMsPdw4HBbnk4qv0SCpGmuk9fiRJuB9c0cStGmiBulny8hCIlxEehmcN4dzW/vv0Z2sT68X5A+n1cdtK8y9OrEBBncfQIzsTwkWSqQymnXu3J+yZDQIXp45WtKTbWQIwM0kqn+bG+cjgMR+cBdKp0WYkNh1il8Cceu1TZy/8zgtvd1CJoWoQC8xN
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=5bce.5cb2a711.k1904; bh=VSOnkeVJmUL+Vw0oTINr00/rkJDJ7UUM17sJ8mvea+I=; b=DTVeOLKyrSfPHK9gfnL6THwaLggTH3qfNhUbnp/OXGvvOqd7P62u/f7Xvjbh3T9BS0Rf6lydIM/3OFEP27qWesKWNbKme15SUnbTCc5VnwPhXy7ZGdYaZU72Kh8fssiI3fBt3EMWktM/Kn+xRIuRmKcEN052MNujrvnyi3eBAlp0BIHW8eY9BenE++iXXSpAVDMD7E9OujJU8VyjYFKk1R7dXyEUZfvSEarhCRg+mvVe9jX2Lls5TUdXDCw27lqt
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 ESMTP via TCP6; 14 Apr 2019 03:20:49 -0000
Received: by ary.qy (Postfix, from userid 501) id 113592011EB715; Sat, 13 Apr 2019 23:20:48 -0400 (EDT)
Date: Sat, 13 Apr 2019 23:20:48 -0400
Message-Id: <20190414032049.113592011EB715@ary.qy>
From: John Levine <johnl@taugh.com>
To: dmarc@ietf.org
Cc: dcrocker@gmail.com
In-Reply-To: <b8667ee0-d0c5-6bc2-c20e-1150ce910133@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/YoflQemIqTuuXJaOx3_CWEcMrUQ>
Subject: Re: [dmarc-ietf] DNS library queries for DKIM and DMARC records?
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: Sun, 14 Apr 2019 03:20:54 -0000

In article <b8667ee0-d0c5-6bc2-c20e-1150ce910133@gmail.com> you write:
>On 4/10/2019 8:37 PM, Scott Kitterman wrote:
>>>>> print(response.additional)
>> []
>Turns out that's what I was especially hoping to see.

As I understand it, your design depends on putting NXDOMAIN signals
in the additional section to show that there aren't any boundaries
between the names it returns.  How do you plan to do that?

R's,
John