Gervase, On Jun 9, 2008, at 9:34 AM, Gervase Markham wrote: >> I'm curious: have you consulted with the various TLD-related >> organizations (e.g., ccNSO, gNSO, CENTR, APTLD, AfTLD, LACTLD, >> etc.) on >> how to solve this problem? > > No. What do you think they'd say that hasn't been said in this thread > already?
You're talking about essentially creating a registry of their registry policies and distributing it statically via your product. I would imagine they might be interested and might even have some useful input to provide. Some might even think it rude (even Microsoftian :-)) not to ask. But perhaps I've been at layer 9 too long. Just to be clear, my understanding of the situation is that you are proposing to ask that every TLD who has a zone in which the public can register to notify you of that fact so that you can distribute and use a list of these registries within your product, relying on Mozilla's update/upgrade functionality to update and maintain this list. Explicit in this proposal is that the registries notify you every time they add a new 'public registry' or change the status of an existing 'public registry'. Failure to update a registry could have negative impact on customers of the TLD due to, for example, being unable to set cookies. Is this an accurate summary? Regards, -drc P.S. If you do send your message to the technical contacts for all the TLDs, expect quite a few bounces. It seems keeping whois data up to date is a challenge for many TLD admins. Having a bit of experience dealing with the various TLD administrators, this might be seen as cautionary towards what you're proposing to do. P.P.S. Before anyone asks, IANA policies disallow IANA from initiating a change and require all changes to be confirmed by the TLD admins -- IANA could harass people to update their info, but the TLD AC and TC must take action for a change to occur. This turns out to be quite a stumbling block. _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
