> -----Original Message----- > From: DNSOP [mailto:dnsop-boun...@ietf.org] On Behalf Of Evan Hunt > > On Tue, Mar 28, 2017 at 06:31:56PM -0000, John Levine wrote: > > What if such a server receives BULK by AXFR? By IXFR? > > I agree these scenarios in particular need to be specified. >
Hi Evan, Thanks for your comments. > > One possible solution would be an EDNS signal indicating whether or > not the secondary server implements BULK. If not, the primary would > have to expand the BULK data during transfer, same as BIND expands > $GENERATE. (I proposed a similar sort of EDNS signaling mechanism > in draft-hunt-note-rr-01 a few years back.) > I believe this would ultimately be less efficient than generating the records on the fly. Assuming a relatively small range, say an IPv4 /16. You would need to sweep through similar logic and load _every_single_answer_ into memory rather than just the ones which are asked for. I see no reason caching couldn't be used to hold the more commonly requested records in order to save on CPU. (apologies for double-neg) Additionally, the patterns could (and most likely should) be pre- parsed for simpler/ lower calorie processing. Thanks, John > > -- > Evan Hunt -- e...@isc.org > Internet Systems Consortium, Inc. > > _______________________________________________ > DNSOP mailing list > DNSOP@ietf.org > https://www.ietf.org/mailman/listinfo/dnsop > > -- THESE ARE THE DROIDS TO WHOM I REFER: This communication is the property of CenturyLink and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments. _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
