[dns-operations] DNS Flush Protocol

[Warren Kumari]

On Fri, Mar 27, 2015 at 2:40 PM, George Michaelson <ggm at apnic.net> wrote:
> I would agree that assumptions are a road to perdition.
>
> But the model of concentration of eyeballs through resolvers is not
> new. So, whilst I agree in *principle* I think it bears thinking
> about: do you actually really expect a disruptive (sea)change  here?
>
> I mean, I think its more likely we get a sea-change in the signed root
> outcomes, than less people use 8.8.8.8 and 4.4.4.4 personally. Or
> Comcast, given their centrality in current (and forseeable future)
> market share now they're getting the eyes behind TW. Or China's
> concentration of views behind 3-4 carriers.
>
> So yes. But then again.. Perhaps.. No.

This isn't really an architectural decision -- currently the way we
flush caches is someone posts a "OMG, I just did something dumb,
please can everyone flush their cache for $foo" on some set of mailing
lists... and then we all wander around asking how / why we should
trust that mail, some set of people actually flush, some don't read
them mail till 4 days later, some bemoan the fact that we still
haven't solved this problem, etc.

I was saying is that we don't really need to reach *every* recursive,
whatever we do manage to do will be better than the current position.

Sure, a fully awesome, all shining, all dancing cache flush solution
that can securely flush all caches everywhere would be best, but until
this comes along, something, anything really, is better than posting
on DNS-Operations....

W
[0}: I'm assuming everyone knows about:
https://developers.google.com/speed/public-dns/cache and
http://cachecheck.opendns.com/ ?


>
> On 27 March 2015 at 14:16, Paul Vixie <paul at redbarn.org> wrote:
>> see also:
>>
>> http://www.techrepublic.com/blog/data-center/opendns-and-neustars-real-time-directory-aim-to-speed-dns-update-times/
>> _______________________________________________
>> dns-operations mailing list
>> dns-operations at lists.dns-oarc.net
>> https://lists.dns-oarc.net/mailman/listinfo/dns-operations
>> dns-jobs mailing list
>> https://lists.dns-oarc.net/mailman/listinfo/dns-jobs
> _______________________________________________
> dns-operations mailing list
> dns-operations at lists.dns-oarc.net
> https://lists.dns-oarc.net/mailman/listinfo/dns-operations
> dns-jobs mailing list
> https://lists.dns-oarc.net/mailman/listinfo/dns-jobs



-- 
I don't think the execution is relevant when it was obviously a bad
idea in the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair
of pants.
   ---maf