by Tina Dam on November 12, 2008
One of the main IDN related topics from the just-finished ICANN meeting in Cairo that I think deserves some additional attention was:
Why Compliance with IDN technical requirements are a necessity on a global scale
Overall compliance with technical standards are important for TLD registry operators in order to keep their TLD stable and secure and in that way function and work well for their consumers and communities. Per ICANN Bylaws, interoperability of the Internet is a core value, which requires that technical standards are complied with. In some instances failure to comply with technical standards will only affects the corresponding TLD in isolation and does not interfere with other TLDs - when moving to the topic of IDN TLDs however this fact changes very quickly.
by Stacy Burnette on October 31, 2008
Whois has been a complex issue within ICANN, and continues to receive attention at the policy level. While this important policy work goes on, ICANN still has the clear responsibility to enforce existing Whois provisions in the Registrar Accreditation Agreement (RAA), and to better understand the real world status of Whois accuracy and Whois related services (e.g. privacy and proxy registration services).
So, what is ICANN doing for Whois compliance? Here is a recent survey of activities:
by Kieren McCarthy on April 3, 2007
The following is the discussion held over RegisterFly at the ICANN Board meeting on Friday 31 March 2007.
RegisterFly was also the topic of discussion for an hour at the end of the Public Forum on Monday 26 March 2007. The public forum’s full transcript is available here.
Note: Although transcript output is largely accurate, in some [...]
by Stacy Burnette on March 24, 2007
ICANN’s updated Contractual Compliance program (http://www.icann.org/compliance/), which includes ICANN’s Contractual Compliance philosophy, vision and operating plan, has been published to provide clear, transparent information regarding contractual compliance.
ICANN thanks the community for its participation and contribution to date to the Contractual Compliance Program and the community is encouraged to provide comments regarding this document.
