23 November, 2010


From the recent IANA Committee minutes:

"Report on DNAME testing work item to be revived, and staff to discuss and to report to IC on status of work and identification of the department that will lead this work."

DNAME record analysis was first mentioned by the IANA at Riga in 2006 -- this was after Verisigns's "Proposal for DNAME Equivalence Mapping for TLD Strings" and after John Klensin's analysis:

"While there are many circumstances in which DNAME is not appropriate, or behaves in ways different from what users predict, it appears to be quite safe when used to define a reference within a single zone file and quite predictable when there are no records other than the DNAME associated with the DNAME's label."
It's nice to hear that the IANA is working on a project that may ultimately provide a solution to the quandary faced by the new gTLD Applicant Support WG.    

In related news, Michael Palage posting on Circleid has noticed (from the same set of minutes) the following:
Root Zone File Management and Implementation: The IC discussed challenges and unforeseen results arising from the automation of Root Zone Management, in relation to the automated use of ISO-3166 official short names in the Root Zone database and addresses.
Michael writes:  "Hopefully ICANN will be providing more detail into the "challenges and unforeseen results" in connection with the automation of the Root Zone Management as part of the new generic Top-Level Domain (gTLD) update. Clearly the automation of the Root Zone Management is a key cog in ICANN's new gTLD machinery if it hopes to add up to five hundred new TLDs to the root per year. However, this also raises legitimate questions into what other "challenges and unforeseen results" might arise in connection with the new gTLD process and whether an unlimited number of new gTLDs in the first round is the most prudent course of action."

No comments:

Post a Comment