Re: [DNSOP] opportunistic semi-authoritative caching (Re: DNSOP Call for Adoption - draft-tale-dnsop-serve-stale)

[Paul Vixie <[e-mail]>]

On Thursday, September 07, 2017 11:08:43 PM Joe Abley wrote:
> >>   Would you see the querying application informing you of intent via
> >> 
> >> option code saying "If I'm unable to talk to you once TTL expires, I may
> >> serve your last known good answer"?
> > 
> > i don't think so. if it was "may i serve your last good answer?" then yes.
> > but with it as "i may" and the ? outside the quotes as shown above, then
> > no.
> There's a recursive operator with whom Jared and tale may be familiar that
> some time ago had a feature called "pinning" whereby particular names that
> were known to be availability-sensitive (their non-availability caused
> great disturbance in the helpdesk) could be "pinned" -- that is, in the
> recursive server, they were configured never to expire from the cache. They
> could be refreshed, but they would not expire.

the domain name system is the world's first and only distributed, coherent, 
autonomous, reliable database. if someone decides, for the sake of their help 
desk, to use my data for longer than the TTL i signaled, that's an affront to 
both coherence and autonomy, and they should stop.

if they really need this, they should provide a method by which i can specify 
both a TTL and an Expiry, and i will consider publishing both values, and if i 
do, then they can use them the way i intend them. because as i said, autonomy. 
it's my data, and my TTL.

vixie