Naming and shaming is not the only mechanism for change, and it's not effective when things "work". Sunsetting and deprecating parts of protocols (like IQUERY or TYPE=ANY) is more important as it helps not only to keep the protocol concise, but also forces evolution of protocol implementations (or at least brings implementors back for discussions).
Marek On Wed, Jun 22, 2016 at 3:36 AM, Jim Reid <j...@rfc1035.com> wrote: > >> On 22 Jun 2016, at 11:13, Stephane Bortzmeyer <bortzme...@nic.fr> wrote: >> >> It is not "fun", it is the only way to have broken implementations >> (Akamai, djbdns) fixed. If we do not name them, they will continue >> forever. > > I doubt that will help Stephane. djbdns has been broken for ~20 years -- no > AXFR, no EDNS0, no TCP/53, no DNSSEC, no TSIG, etc, etc -- and likely to be > that way forever. DJB no longer supports or maintains the software, apart > from fixing security vulnerabilities IIUC. So the DNS is probably always > going to be stuck with that abandonware being in the state it was in at its > last "stable release" in 2001. > > The best we can hope from naming and shaming is to encourage people to keep > away from implementations that are broken and/or cause serious > interoperability issues. Whether that advice will get heard and acted on is > another matter of course. Darwinism will eventually take care of the poor DNS > deployment choices anyway. > > > _______________________________________________ > DNSOP mailing list > DNSOP@ietf.org > https://www.ietf.org/mailman/listinfo/dnsop _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
