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

Evan Hunt <each@isc.org> Mon, 13 November 2017 18:30 UTC

Return-Path: <each@isc.org>
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 9DA43129B30 for <dnsop@ietfa.amsl.com>; Mon, 13 Nov 2017 10:30:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level:
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, 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 oZXAkxhVenNu for <dnsop@ietfa.amsl.com>; Mon, 13 Nov 2017 10:30:08 -0800 (PST)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [149.20.64.53]) (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 7609012944F for <dnsop@ietf.org>; Mon, 13 Nov 2017 10:30:08 -0800 (PST)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id 1B6D43B0102; Mon, 13 Nov 2017 18:30:05 +0000 (UTC)
Received: by bikeshed.isc.org (Postfix, from userid 10292) id C1194216C1C; Mon, 13 Nov 2017 18:30:04 +0000 (UTC)
Date: Mon, 13 Nov 2017 18:30:04 +0000
From: Evan Hunt <each@isc.org>
To: Tony Finch <dot@dotat.at>
Cc: Edward Lewis <edward.lewis@icann.org>, "dnsop@ietf.org" <dnsop@ietf.org>
Message-ID: <20171113183004.GA35038@isc.org>
References: <20171112075445.tf2ut5dxzhhnqe7l@mx4.yitter.info> <20171112131831.GA32208@laperouse.bortzmeyer.org> <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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <alpine.DEB.2.11.1711131456200.26046@grey.csi.cam.ac.uk>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/1pu1IfJSlHjtvyNvM1Az3_ZXakg>
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: Mon, 13 Nov 2017 18:30:10 -0000

On Mon, Nov 13, 2017 at 03:19:23PM +0000, Tony Finch wrote:
> It seems to me that a reasonable in-band mechanism would be to send a
> NOTIFY to the parental agent. I can only find a little discussion of this
> idea in 2014, and it wasn't very enthusiastic - there were questions like,
> how do you know where to send the NOTIFY? On the other hand there are
> similar questions about how you would make an out-of-band request.

Mark's idea to push updates to the parent instead of relying on polling
used a SRV query to identify the correct recipient of an UPDATE:

https://tools.ietf.org/html/draft-andrews-dnsop-update-parent-zones-04

The same trick could be used to find the right NOTIFY target.

-- 
Evan Hunt -- each@isc.org
Internet Systems Consortium, Inc.