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

Dave Crocker <dcrocker@gmail.com> Wed, 10 April 2019 19:36 UTC

Return-Path: <dcrocker@gmail.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 7211D12062B for <dmarc@ietfa.amsl.com>; Wed, 10 Apr 2019 12:36:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 QnZMj2zcZK81 for <dmarc@ietfa.amsl.com>; Wed, 10 Apr 2019 12:36:40 -0700 (PDT)
Received: from mail-oi1-x236.google.com (mail-oi1-x236.google.com [IPv6:2607:f8b0:4864:20::236]) (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 343831205DF for <dmarc@ietf.org>; Wed, 10 Apr 2019 12:36:40 -0700 (PDT)
Received: by mail-oi1-x236.google.com with SMTP id v84so2834957oif.4 for <dmarc@ietf.org>; Wed, 10 Apr 2019 12:36:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:subject:to:message-id:date:user-agent:mime-version :content-language:content-transfer-encoding; bh=uUVj4ecjCz7d4undUkQdxcuNUuLpktQ8w30oWp6Ix54=; b=D9ulzfHKmHi4/WARyhRr8pKryOVUPH5u/81Tjdfj7gXH1QIlfTWg/yUXShptWvZV4R 1WXHvAMFUlelV7EFDch+Snv6tvA0zNX9E2ctD1IhZvoaE4rufQyW0rCunvU6rHE7WVyH VjcFhTRYOhqzMA02Z+aLZq21A8abxrSk07jTVjI5lvPLcrbgwUV4TXeoZGGVlnQ2Tp5Z 3MzhTL1JPAUJvHKaTXBWw84Ul706HFAcEC8iggBDzkbkhdKaJmuw3BnHXNS+JhTgbO4m 3aHmGQkTCMlRnzd9zpbZEFnT5Ej6Rj/kafPzoLjRenbhTtFE+CbBsVJ1puQtMcxmGRBr uSIQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:subject:to:message-id:date:user-agent :mime-version:content-language:content-transfer-encoding; bh=uUVj4ecjCz7d4undUkQdxcuNUuLpktQ8w30oWp6Ix54=; b=YY+4XOn3u4XvzNTdRBLJvJ/C/v8SlFM8TIFHAYiqb206An0lw5JG3XF0CU2U3nlRMI Ocnfhj5eEoZKNZWpaFuAepLi3i/foNYTp7wEUCxg7jZGoUWQXs+3U9MvK06mIpp/Rzp2 Ixmjuh9Hw3okZfWsouVs+fYVIXH2pwKykl0ut227CNAnn8s9YZqI1H1Rf0TaGdse004F f1KG8zrRVEwnLzftmZ/S7/zDPWiJsDAaxfll1A508rdFRiqCaob1Bmb9rvR2lLGZUVQK FzkjTaVJpZnb4iutERfVoQ63J8M78KHvG9N+ihnYzNgUmWNyy5xD0nlQARLRkm7pRR0t aWWA==
X-Gm-Message-State: APjAAAXfYS33zAaARqhR9CSy0jLiVEPDS8VOGezQuYRi9o6EPMrp5Sgm p18AoHt0g0YP776BJESWzbMdsx0L
X-Google-Smtp-Source: APXvYqyUK+9ogkBTcnTx6wqgFYNWMHE/oKIDWpsQI5d/lj9IIrv0bVjhxxbfKRCE+eg8zDDVoYIysA==
X-Received: by 2002:aca:cf92:: with SMTP id f140mr3745639oig.48.1554924998993; Wed, 10 Apr 2019 12:36:38 -0700 (PDT)
Received: from ?IPv6:2600:1700:a3a0:4c80:a513:542:b741:80cf? ([2600:1700:a3a0:4c80:a513:542:b741:80cf]) by smtp.gmail.com with ESMTPSA id v201sm11419461oia.39.2019.04.10.12.36.38 for <dmarc@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 10 Apr 2019 12:36:38 -0700 (PDT)
From: Dave Crocker <dcrocker@gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Message-ID: <571ce243-a8b0-094d-0d59-06f1432bd741@gmail.com>
Date: Wed, 10 Apr 2019 12:36:34 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/uDXIbNNv33A9_wegCdlombV0uno>
Subject: [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: Wed, 10 Apr 2019 19:36:50 -0000

Folks,

Howdy.

I'm trying to get a bit of education about reality.  Always dangerous, 
but I've no choice...


For the software you know about, how are queries to the DNS performed, 
to obtain the TXT records associated with DKIM and/or DMARC?

I'm trying to understand the breadth and limitations of returned 
information that is filtered or passed by the code that is actually in 
use.  Which libraries and which calls from those libraries.


Thanks.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net