On Oct 2, 2012, at 5:27 PM, Warren Kumari wrote: > More seriously though, this is yet another chicken-and-egg problem…
Agreed. > In this particular case I think that the easiest / fastest way to get better > deployment is to convince the browser manufactures to include support for > DANE -- this will incentivize[0] folk to deploy records… Indeed, but as you yourself noted in an earlier thread: >> Something that would be very helpful for getting this deployed / implemented >> in browsers is number of folk (and more importantly, organizations) stating >> that they are planning on / would do DANE if the browsers supported it >> natively. Of course, even more helpful would be folk actually publishing >> TLSA records :-P >> >> The browser vendors all have limited cycles, and many many things to >> implement -- showing that this is something that users (and not just >> security weenie users) want and plan to use helps to prioritize developer >> time. So the best way to get the attention of the browser manufacturers is to get *other* people talking about DANE and requesting DANE from the browser manufacturers. Which speaks to the need for a broader outreach to people who might be consumers/users of the DANE protocol. > [0]: Whoohoo, "incentivize" ! Ah, the joys of the English language "evolving"... :-) Dan -- Dan York [email protected] http://www.danyork.me/ skype:danyork Phone: +1-802-735-1624 Twitter - http://twitter.com/danyork
_______________________________________________ dane mailing list [email protected] https://www.ietf.org/mailman/listinfo/dane
