Re: [DNSOP] Working Group Last Call draft-ietf-dnsop-resolver-priming

[神明達哉 <[e-mail]>]

At Wed, 17 Aug 2016 13:03:31 -0400,
Bob Harold <[e-mail]> wrote:

> > - Section 2
> >
> >    Therefore, it is important that resolvers be able to cope with
> >    change, even without relying upon configuration updates to be applied
> >    by their operator.
> >
> >   If we really want to make it work "even without relying upon
> >   configuration updates", we may need to consider some extreme cases
> >   where all of the ./NS data (and/or all of their glue AAAA/A records)
> >   change while a resolver keeps running for a very long period.  If
> >   this happens, once the cached priming data expires, even the next
> >   priming would fail, since at that point the resolver needs to use
> >   the configured data but none of the configured data is usable.  If
> >   we want to make it work even in such cases, we may have to encourage
> >   some specific techniques more strongly, e.g., query prefetch or
> >   auto-update the configured "root hint" with the result of priming
> >   query, etc.  Or, if this sentence doesn't intend to cover such
> >   extreme cases, it may probably have to be reworded to avoid
> >   misunderstanding.
> >
> I think we could clarify the sentence by adding some thing like "as long
> as at least one of the configured addresses (for each address type, IPv4
> and IPv6) responds with the correct list."  Even if all the IP's change, we
> just need one of the IP's to respond with the new list.

Yes, that's one way to address this point (if we want to address it).

--
JINMEI, Tatuya