Centre for Internet & Society

103 items matching your search terms.
Filter the results.
Item type



















New items since



Sort by relevance · date (newest first) · alphabetically
Blog Entry DIDP Request #17 - How ICANN Chooses their Contractual Compliance Auditors
by Asvatha Babu published Jul 29, 2016 — filed under: , ,
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.
Located in Internet Governance / Blog
Blog Entry DIDP Request #18 - ICANN’s Internal Website will Stay Internal
by Asvatha Babu published Jul 29, 2016 — filed under: , ,
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.
Located in Internet Governance / Blog
Blog Entry DIDP Request #19 - ICANN’s role in the Postponement of the IANA Transition
by Asvatha Babu published Jul 29, 2016 — filed under: , ,
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.
Located in Internet Governance / Blog
Blog Entry DIDP Request #20 - Is Presumptive Renewal of Verisign’s Contracts a Good Thing?
by Asvatha Babu published Jul 30, 2016 — filed under: , ,
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.
Located in Internet Governance / Blog
Blog Entry DIDP Request #21 - ICANN’s Relationship with the RIRs
by Asvatha Babu published Jul 30, 2016 — filed under: , ,
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.
Located in Internet Governance / Blog
Blog Entry DIDP Request #22 - Reconsideration Requests from Parties affected by ICANN Action
by Asvatha Babu published Jul 30, 2016 — filed under: , ,
According to ICANN by-laws, ICANN has the responsibility to answer to reconsideration requests filed by those directly affected by its actions.
Located in Internet Governance / Blog
Blog Entry DIDP Request #23 - ICANN does not Know how Diverse its Comment Section Is
by Asvatha Babu published Jul 30, 2016 — filed under: , ,
While researching ICANN and the IANA Stewardship Transition Coordination Group (ICG), we came across a diversity analysis report of a public comment section.
Located in Internet Governance / Blog
Blog Entry DIDP Request #25 - Curbing Sexual Harassment at ICANN
by Asvatha Babu published Jul 30, 2016 — filed under: , ,
Markus Kummer at Public Forum 2 mentioned that ICANN has standards of behavior regarding sexual harassment that are applicable for its staff.
Located in Internet Governance / Blog
Blog Entry DIDP Request #27 - On ICANN’s support to new gTLD Applicants
by Asvatha Babu published Jul 30, 2016 — filed under: , ,
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).
Located in Internet Governance / Blog
Blog Entry DIDP Request #28 - ICANN renews Verisign’s RZM Contract?
by Asvatha Babu published Jul 30, 2016 — filed under: , ,
Our request to ICANN was related to our (mistaken) assumption that Verisign and ICANN had signed an agreement for Root Zone Maintenance and had recently renewed it. In that context we had asked for information such as documents reflecting the decision making process, copy of the current RZM agreement, public comments and an audit report of Verisign’s RZM functions.
Located in Internet Governance / Blog