the fact that masataka's proposal seemed qualitatively better to me eleven years ago is moot. the reason dnssec isn't deployed yet has nothing to do with any such qualitative differences. we are where we are, and what we've got to do now is deploy what we've got now. the dnssec spec at present may be ugly but it is practicable, and there's a large body of expertise and running code and commercial products and interoperability testing behind it.
while i didn't enjoy watching masataka's proposal railroaded into the ditch and while it would have taken less time to get masataka's dnssec proposal deployable than it has taken to get to what we've got now, the silver lining for me was that i learned how to railroad my own proposals through IETF using the techniques i learned. RFC 2136, RFC 2671, and RFC 2845 all exist only because of the dirty tricks i learned by watching masataka's mistreatment. (had i known at the outset how IETF worked, i would have worked to prevent that mistreatment, but i was a n00b.) -- Paul Vixie -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. _______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
