IETF Logo Mail Archive

Re: [DNSOP] Error handling in CAA

Tony Finch <dot@dotat.at> Wed, 22 November 2017 12:09 UTC

Return-Path: <dot@dotat.at>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F1F0129415 for <dnsop@ietfa.amsl.com>; Wed, 22 Nov 2017 04:09:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 I81dRJ9GgFqM for <dnsop@ietfa.amsl.com>; Wed, 22 Nov 2017 04:09:53 -0800 (PST)
Received: from ppsw-32.csi.cam.ac.uk (ppsw-32.csi.cam.ac.uk [131.111.8.132]) (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 BBA7A12940C for <dnsop@ietf.org>; Wed, 22 Nov 2017 04:09:53 -0800 (PST)
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://help.uis.cam.ac.uk/email-scanner-virus
Received: from grey.csi.cam.ac.uk ([131.111.57.57]:50223) by ppsw-32.csi.cam.ac.uk (ppsw.cam.ac.uk [131.111.8.136]:25) with esmtps (TLSv1:ECDHE-RSA-AES256-SHA:256) id 1eHTqh-0011E0-32 (Exim 4.89) for dnsop@ietf.org (return-path <dot@dotat.at>); Wed, 22 Nov 2017 12:09:51 +0000
Date: Wed, 22 Nov 2017 12:09:51 +0000
From: Tony Finch <dot@dotat.at>
To: dnsop WG <dnsop@ietf.org>
In-Reply-To: <20171121205403.GT3322@mournblade.imrryr.org>
Message-ID: <alpine.DEB.2.11.1711221205030.4416@grey.csi.cam.ac.uk>
References: <3e958c19-016f-b413-78c5-4fd3c7c41daa@eff.org> <20171118211000.GR3322@mournblade.imrryr.org> <alpine.DEB.2.11.1711201256440.32058@grey.csi.cam.ac.uk> <20171121205403.GT3322@mournblade.imrryr.org>
User-Agent: Alpine 2.11 (DEB 23 2013-08-11)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/FCjtUgImszoLJgphUEeauDMDu6k>
Subject: Re: [DNSOP] Error handling in CAA
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Nov 2017 12:09:55 -0000

Viktor Dukhovni <ietf-dane@dukhovni.org> wrote:
>
> > No, you need to lookup the domain's DS records to determine its DNSSEC
> > status.
>
> Actually, I chose my recommendation of SOA lookup after some thought
> and with care.  A domain may have no DS records, and yet be signed
> because it is not a (delegated) zone apex domain.  Furthermore, an
> SOA query elicts data from the domain itself, not the parent, and
> thus ensures that any published DS records up the tree yield working
> signatures for records in the zone containing the domain.

OK I thought you meant to query for the SOA of the zone containing the CAA
domain, and I meant to query for the closest enclosing negatively or
positively resolvable DS.

The CAA search has to walk the DNS tree anyway, so finding the closest
enclosing DS is a similar kind of process.

> If the SOA lookup fails, then the domain is severely broken

No, it might just be private.

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/  -  I xn--zr8h punycode
Tyne, Dogger, Fisher, German Bight, Humber, Thames: South or southwest 6 to
gale 8, occasionally severe gale 9 except Tyne. Rough or very rough,
occasionally very high for a time in Biscay. Rain or showers. Good,
occasionally poor.

v2.23.0 | Report a Bug | By Email