First, I don't see why this draft exists in the IETF. How does this impact interoperability?
Further, this draft is hinting at a mixed signal. In an era where operators are rushing to deploy RRL because of what appears on the surface to be overly aggressive clients, the document is telling cache servers that they ought to be (slightly) overly aggressive. I get that this is *slightly* overly aggressive and that the use here is "benign" (chuckle if you want), but, well, 131 is still over the limit (of 130 kph). And intent is immaterial when I see a query thrown my way. Why is this important? I looked at one popular name, just to pick one for the sake of an email message (not a whitepaper). The TTL on an A record is 300 and my dig reported it took 19ms to get a response from an authoritative server. I.e., the domain wants to change the A frequently but also has a fast authoritative infrastructure. 19ms is less than one-half of one percent of one percent of 300, if I plug that into an "efficiency" I'm dividing: 300 / 300.019 = 99.993% I don't see the real-world benefit of this. On Jul 1, 2013, at 17:43, Warren Kumari wrote: > Hi there, > > We would like to draw your attention to a new draft. > If describes a simply optimization that, with minimal to no state, keeps > popular records in recursive server's caches. > > W > > Begin forwarded message: > >> From: [email protected] >> Subject: New Version Notification for draft-wkumari-dnsop-hammer-00.txt >> Date: July 1, 2013 5:40:44 PM EDT >> To: Roy Arends <[email protected]>, Suzanne Woolf <[email protected]>, Warren >> Kumari <[email protected]> >> >> >> A new version of I-D, draft-wkumari-dnsop-hammer-00.txt >> has been successfully submitted by Warren Kumari and posted to the >> IETF repository. >> >> Filename: draft-wkumari-dnsop-hammer >> Revision: 00 >> Title: Highly Automated Method for Maintaining Expiring >> Records >> Creation date: 2013-07-01 >> Group: Individual Submission >> Number of pages: 5 >> URL: >> http://www.ietf.org/internet-drafts/draft-wkumari-dnsop-hammer-00.txt >> Status: http://datatracker.ietf.org/doc/draft-wkumari-dnsop-hammer >> Htmlized: http://tools.ietf.org/html/draft-wkumari-dnsop-hammer-00 >> >> >> Abstract: >> This document describes a simple DNS cache optimization which keeps >> the most popular records in the DNS cache. >> >> > > No man is an island, But if you take a bunch of dead guys and tie them > together, they make a pretty good raft. > --Anon. > > > _______________________________________________ > DNSOP mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/dnsop -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Edward Lewis NeuStar You can leave a voice message at +1-571-434-5468 There are no answers - just tradeoffs, decisions, and responses.
_______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
