<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On Oct 21, 2013, at 11:54, Keith Mitchell wrote:</div><blockquote type="cite"><div><br></div><div>Then ISC/BIND response to Kaminsky in 2008 was to burn perhaps 50% of<br>the company's product-wide development and support resources over that<br>year to co-ordinating, fixing, disclosing, patching, releasing and<br>evangelizing the solution to the problem. While at the time it felt to<br>us like great public benefit work was being done for the community, even<br>by the end of that year it was becoming clear it was not a particularly<br>great business decision.<br></div></blockquote></div><div><br></div>Over the weekend there was a CENTR Technical Workshop (the day before RIPE 67 and in the same location) where a panel was held on the recent DNS vulnerabilities as reported at DNS-OARC 7 days earlier. One of the thoughts that emerged (IMHO) was to set priorities like this: design-away the theoretic/academic described vulnerabilities, reserving trench-warfare techniques to battle attacks we "learn from packet captures." Given limited resources, that is how I'd spend them.<div><br></div><div>So, yes, I believe this - in retrospect (referring to Keith's report) a lot of resources were burned to stem an attack that never really materialized. Possibly because of the fix, but we will never know.<br><div><br></div><div>Oddly, during the CENTR meeting and during the RIPE DNS WG meeting that followed, the quote "in the long run we are all dead" [0] was uttered independently (different speakers) to mean that "it's fine to design into the future, but we need to eat now." Under that banner, RRL serves an important purpose by staving off the apocalypse, even if (and I do mean if) it's benefit is temporary.</div><div><br></div><div>This assumes that there is someone "designing away" vulnerabilities into the future, which I fear is a bad assumption currently. Most delivered techniques are triage with anything requiring major architectural rework considered to be "too far off into the future" to even being. I don't think DNSSEC would stand a chance starting from scratch today, given how avenues of innovation have changed.</div><div><br></div><div>[0] <a href="http://en.wikipedia.org/wiki/In_the_long_run_we_are_all_dead#Macroeconomic_usages">http://en.wikipedia.org/wiki/In_the_long_run_we_are_all_dead#Macroeconomic_usages</a></div><div><br><div>
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=<span></span>-=-=-=-<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>Edward Lewis <span></span> <br>NeuStar <span></span> You can leave a voice message at +1-571-434-5468<br><br>There are no answers - just tradeoffs, decisions, and responses.</div></div></div></span></span>
</div>
<br></div></div></body></html>