Posts
DIDP Request #27 - On ICANN’s support to new gTLD Applicants
- July 30, 2016
In order to promote access to the New gTLD Program in developing regions, ICANN set up the New gTLD Applicant Support Program (Program) which seeks to facilitate cooperation between gTLD applicants from developing countries and those willing and able to support them financially (and in kind).
Read more →DIDP Request #25 - Curbing Sexual Harassment at ICANN
- July 30, 2016
Markus Kummer at Public Forum 2 mentioned that ICANN has standards of behavior regarding sexual harassment that are applicable for its staff.
Read more →DIDP Request #23 - ICANN does not Know how Diverse its Comment Section Is
- July 30, 2016
While researching ICANN and the IANA Stewardship Transition Coordination Group (ICG), we came across a diversity analysis report of a public comment section.
Read more →DIDP Request #22 - Reconsideration Requests from Parties affected by ICANN Action
- July 30, 2016
According to ICANN by-laws, ICANN has the responsibility to answer to reconsideration requests filed by those directly affected by its actions.
Read more →DIDP Request #21 - ICANN’s Relationship with the RIRs
- July 30, 2016
At CIS, we wanted a clearer understanding of ICANN’s relationship with the 5 internet registries. The large amount contributed by the RIRs to ICANN’s funding lead us to question the nature of this relationship as well as the payment. We wrote to ICANN asking them for these details.
Read more →DIDP Request #20 - Is Presumptive Renewal of Verisign’s Contracts a Good Thing?
- July 30, 2016
ICANN’s contract agreements with different registries contain a presumptive renewal clause. Unless they voluntarily give up their rights or there is a material breach by the registry operator, their contract with ICANN will be automatically renewed.
Read more →DIDP Request #19 - ICANN’s role in the Postponement of the IANA Transition
- July 29, 2016
In March 2014, the National Telecommunications and Information Agency (NTIA) of the United States government announced plans to shift the Internet Assigned Names and Numbers (IANA) functions from ICANN to the global multistakeholder community. The initial deadline set for this was September 2015.
Read more →DIDP Request #18 - ICANN’s Internal Website will Stay Internal
- July 29, 2016
ICANN maintains an internal website accessible to staff and employees. We requested ICANN to provide us with a document with the contents of that website in the interest of transparency and accountability.
Read more →DIDP Request #17 - How ICANN Chooses their Contractual Compliance Auditors
- July 29, 2016
At a congressional hearing on internet governance and progress, then President of ICANN Fadi Chehadi indicated that the number of people working on compliance audits grew substantially—from 6 to 24 (we misquoted it as 25)— in the span of a few years.
Read more →DIDP Request #16 - ICANN has no Documentation on Registrars’ “Abuse Contacts”
- July 29, 2016
Registrars on contract with ICANN are required to maintain an “abuse contact” - a 24/7 dedicated phone line and e-mail address to receive reports of abuse regarding the registered names sponsored by the registrar.
Read more →