On Jun 11, 2008, at 6:26 AM, Gervase Markham wrote: > It's not true that we won't work on any other solution. This is what > we > have now, and there have been no alternative proposals which (to my > mind) look like producing anything workable in the short term.
Putting the list in the DNS instead of in the browser isn't workable? Serious question. I think several proposals have been advanced here that /could/ work. Mine has the virtue of being completely under your control. The other one, where subdomains are called out in the zones of the domains that contain them, is not under your control, and wouldn't be a good interim solution, but sounds like a good long-term solution because it puts correctness in the hands of the people who suffer or benefit from it. So what I would personally like to see here is a staged transition. In the first stage, mozilla.org would set up a TLD list in its own DNS space, or in some new subdomain they register with good anycast replication so that no individual server has to bear the entire load. This list would be maintained by mozilla.org, using information from registries and domain owners, and also using your current ad-hoc system. But you'd also implement the system that was proposed here where the registries themselves can publish this information in their own domains. And over time, the hope would be that the number of TLDs you'd have to maintain in your list would slowly dwindle, to the point where it would become more of a quirks list than a registry of its own. This could work because the incentives are in the right direction - sites that have problems with your ad-hoc registry can either contact you or fix their own DNS, and fixing their own DNS may well be easier. I haven't heard you responding that either of these solutions wouldn't work, so I'm assuming they would, but perhaps I'm wrong. It also may be the case that for reasons of practicality you need to start with a list embedded in the browser; as long as you have a plan to make the transition to a list that's maintained more dynamically, and as long as you actually execute that plan, it seems to me that this is harmless. BTW, thanks for your reasoned responses to all these questions and accusations being thrown at you. You seem to have really elicited a lot of energetic response with your initial request, and I hope that something good will come of it. _______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
