On Tue, Nov 14, 2017 at 09:16:43AM +1100, Mark Andrews wrote: > Remember the draft was designed to handle ALL record updates to the > parent zone after being approved by the registrar in a unified manner. > NS, DS, A, DNAME, AAAA, TXT, CNAME, etc. This isn’t restricted to DS > records.
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.) 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. -- Evan Hunt -- e...@isc.org Internet Systems Consortium, Inc. _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
