Re: [DNSOP] CDS polling, was Re: [Ext] Re: Clarifying referrals (#35)

Tony Finch <dot@dotat.at> Tue, 14 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 427A8126D74 for <dnsop@ietfa.amsl.com>; Tue, 14 Nov 2017 04:09:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 h6C5pVGrMJGn for <dnsop@ietfa.amsl.com>; Tue, 14 Nov 2017 04:09:12 -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 88682120726 for <dnsop@ietf.org>; Tue, 14 Nov 2017 04:09:12 -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]:36202) 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 1eEa1T-0002xS-0e (Exim 4.89) (return-path <dot@dotat.at>); Tue, 14 Nov 2017 12:08:59 +0000
Date: Tue, 14 Nov 2017 12:08:59 +0000
From: Tony Finch <dot@dotat.at>
To: Evan Hunt <each@isc.org>
cc: Mark Andrews <marka@isc.org>, Edward Lewis <edward.lewis@icann.org>, "dnsop@ietf.org" <dnsop@ietf.org>
In-Reply-To: <20171113233756.GA37394@isc.org>
Message-ID: <alpine.DEB.2.11.1711140941060.14243@grey.csi.cam.ac.uk>
References: <20171113014445.ncldrwnuuvluecx7@mx4.yitter.info> <5A08FD96.8030907@redbarn.org> <20171113020736.ga7rzgst2hurb56h@mx4.yitter.info> <5A09068A.3030206@redbarn.org> <20171113032640.tbn7icsllm6jeeny@mx4.yitter.info> <C9AC653C-9A27-4DA3-A0FA-9F1BFD429962@icann.org> <alpine.DEB.2.11.1711131456200.26046@grey.csi.cam.ac.uk> <20171113183004.GA35038@isc.org> <436111CF-FCA8-44A2-B83D-6540DE6D64AC@icann.org> <66BA5F27-B044-459B-A2B2-54221FD768C6@isc.org> <20171113233756.GA37394@isc.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/uqUVTBm-TYuYOynXjbq68EF4Y2g>
Subject: Re: [DNSOP] CDS polling, was Re: [Ext] Re: Clarifying referrals (#35)
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: Tue, 14 Nov 2017 12:09:14 -0000

Evan Hunt <each@isc.org> wrote:
>
> In the present context, I was only suggesting this method be used for
> NOTIFY, not UPDATE -- to signal the parent that it should poll the child
> for CDS/CDNSKEY.  (I guess CSYNC could be included in the mix as well,
> though, for updating NS and glue.)

Yes.

> I would suggest the child should be polled periodically regardless. If
> the SRV record were spoofed, causing the child to send a NOTIFY to the
> wrong address, synchronization should still occur, just not as quickly.

The starting point for this thread was parental agents saying they don't
like polling, but having thought about this a bit more I think I agree
that it would be unwise not to poll. If there's a way to get polled early
by NOTIFY then that's probably still good for both parent and child -
parent can poll more slowly, and child can get prompt updates.

I read Mark Elkins' article with interest. I would prefer to use NOTIFY
rather than a web hook because it's much more plausible to imagine
supporting this inside a DNS server with some kind of notify-parent
feature.

I like the idea of being able to automatically discover where to send
parental notifies. But this can only work if the parental agent doesn't
require TSIG. On the other hand, we can't rely on autodiscovery because
I wouldn't bet on the registries publishing the necessary SRV records...

Any opinions on whether this is worth pursuing?

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/  -  I xn--zr8h punycode
Viking, North Utsire: Northwesterly backing westerly 5 to 7. Moderate or
rough, occasionally very rough later in north. Squally showers. Good.