Subject: Re: [DNSOP] Perl related question on BULK RR

From: "Woodworth, John R" <[email-masked]>
Date: Mon, 3 Apr 2017 22:08:53 +0000

> -----Original Message-----
> From: Woodworth, John R
>
> > -----Original Message-----
> > From: DNSOP [mailto:[email-masked]] On Behalf Of Tony Finch
> ...
> >
> > So my question is, how does the BULK rewriting system interact
> > with DNS loops? Is there a CPU-eating tarpit in there?
> >
>

Hi Tony,

Thanks again for your question.

According to RFC1034, protection should already be in place for all
compliant nameserver implementations.

    ... domain software should not fail when presented with CNAME
    chains or loops; CNAME chains should be followed and CNAME loops
    signalled as an error.

Although this does not specifically call out other RR types, it does
set precedence for following chains and avoiding loops.

I've run through a number of thought exercises and believe this
should still be the case with BULK RRs.

Having said this, I believe your point to be valid and our draft
as well as any implementations would benefit from explicit guidance
for loop avoidance specific to processing BULK RRs.  This should
provide greater consistency across implementations and help avoid
any confusion and error prone logic.

I've also been meaning to flesh out the section regarding sanity
checks while reading BULK RRs into memory (from file or wire).
This could help with avoiding a particular type of loop.

I will work to get these changes added into our draft.

Thanks,
John

>
> > Tony.
> > --
> > f.anthony.n.finch  <[email-masked]>  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
> > [email-masked]
> > 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.