You're right; I apologize for presuming that you'd be defending DNSSEC. I inferred it from "DNSSEC will make the Internet more secure", but ignored the "let's talk about what makes it controversial". I hope you can capture more than just the controversy about who deploys DNSSEC (the DHS or ICANN or the ISPs). I hope you can also manage to address: * The alienation that seems to exist between application developers, network operators, and the IETF standards bodies, which for example caused Apple to ship a multicast DNS implementation ("Bonjour") that leads the market and that the IETF openly competes with. * The insularity perceived in the IETF DNS standards groups, which ostracized Daniel J. Bernstein, author of one of the top 3 DNS implementations, and excluded his voice from the standards. * The faction of the IETF that believes that public consensus has failed, and that the way ahead is to have for-proft entities work with vendors to dictate standards. * The total lack of consensus among developers, security practitioners, standards groups, and vendors about what the Internet's security problems are and where they're best solved (a hint: most security people would tell you that the important problems are all inside Mozilla and Internet Explorer). I think this is a very cool subject to tackle on an Internet governance blog. I just want to make sure we don't hold out the IETF (or security people, for that matter) as "protagonists" in a challenge drama.