> -----Original Message----- > From: DNSOP [mailto:dnsop-boun...@ietf.org] On Behalf Of Tony Finch > > Woodworth, John R <john.woodwo...@centurylink.com> wrote: > > > Apologies but I did not hear the full question regarding BULK RR's and > > the perl like back-references. If you could please repeat the > > question we would be happy to comment. > > I didn't ask the question, but based on a quick look at the draft I > think there might be a fun problem. > > Frequently, when you have string rewriting with substitution and > iteration, you have a Turing-complete esoteric programming system. > > NAPTR very cunningly avoids this trap (IIRC) by constraining the > rewrites to be on a strictly monotonically reducing suffix of the > input. > > BULK does not itself have built-in iteration like NAPTR, but because > it synthesizes records it interacts with the DNS's existing resolver > loops: > chasing delegations, and chasing CNAMEs and DNAMEs. Note that CNAMEs > and DNAMEs are also chased within authoritative servers. > > So my question is, how does the BULK rewriting system interact with > DNS loops? Is there a CPU-eating tarpit in there? > Hi Tony,
Thank you for the excellent question. I will need to run through some logic exercises to attempt to create this scenario and if successful work out a solution. Thanks, John > > Tony. > -- > f.anthony.n.finch <d...@dotat.at> http://dotat.at/ - I xn--zr8h > punycode South Utsire: Northwesterly 4 or 5 backing southwesterly > 3 or 4. Slight or moderate. Fog patches, drizzle. Moderate or good, > occasionally very poor. > > _______________________________________________ > 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
