On Thu, Feb 14, 2019 at 04:05:22PM -0800, Paul Vixie wrote:
> nope. because it did not prototype any partial replication. i'm not
> going to mirror COM because i need it to reach FARSIGHTSECURITY.COM.

I didn't say anybody's going to mirror COM, I said I suspect zone
mirroring will find applications other than pre-caching the root.
The fact that it isn't a complete solution to the problem space you're
interested in at the moment doesn't mean it was useless. That wasn't a major
motivation for the work anyway, I don't believe -- my recollection is that
it was mainly about reducing garbage traffic, with latency reduction for
some resolvers a happy side-effect.

Keeping cache data warm and available during network partitions is a
largely solved problem; we have prefetch/hammer, we have serve-stale.
(Also apparently we have whatever generates all that zombie DNS traffic
Geoff discovered back in 2016, but I'd rather avoid perpetuating that
mistake, which seems *quite* perpetual enough as it is.)

Keeping cache data coherent is less solved: we don't have the trusted
invalidation piece you mentioned. I agree that might be a useful line of
inquiry.  I guess that's the point you were trying to make; I didn't get
it immediately because you started off discussing the shortcomings of an
RFC that doesn't seem particularly directly related.  So let's get
specific about the problem and discuss requirements for a solution.

-- 
Evan Hunt -- e...@isc.org
Internet Systems Consortium, Inc.

_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop

Reply via email to