<?xml version="1.0" encoding="utf-8" ?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns="http://purl.org/rss/1.0/">




    



<channel rdf:about="https://cis-india.org/a2k/front-page/search_rss">
  <title>Access To Knowledge (A2K)</title>
  <link>https://cis-india.org</link>
  
  <description>
    
            These are the search results for the query, showing results 2201 to 2215.
        
  </description>
  
  
  
  
  <image rdf:resource="https://cis-india.org/logo.png"/>

  <items>
    <rdf:Seq>
        
            <rdf:li rdf:resource="https://cis-india.org/internet-governance/blog/didp-request-20-is-presumptive-renewal-of-verisign2019s-contracts-a-good-thing"/>
        
        
            <rdf:li rdf:resource="https://cis-india.org/internet-governance/blog/didp-request-19-icann2019s-role-in-the-postponement-of-the-iana-transition"/>
        
        
            <rdf:li rdf:resource="https://cis-india.org/internet-governance/blog/didp-request-18-icann2019s-internal-website-will-stay-internal"/>
        
        
            <rdf:li rdf:resource="https://cis-india.org/internet-governance/blog/didp-request-17-how-icann-chooses-their-contractual-compliance-auditors"/>
        
        
            <rdf:li rdf:resource="https://cis-india.org/internet-governance/blog/didp-request-16-icann-has-no-documentation-on-registrars2019-201cabuse-contacts201d"/>
        
        
            <rdf:li rdf:resource="https://cis-india.org/internet-governance/blog/didp-request-15-what-is-going-on-between-verisign-and-icann"/>
        
        
            <rdf:li rdf:resource="https://cis-india.org/internet-governance/blog/didp-request-14-keeping-track-of-icann2019s-contracted-parties-registrars"/>
        
        
            <rdf:li rdf:resource="https://cis-india.org/internet-governance/blog/didp-request-13-keeping-track-of-icann2019s-contracted-parties-registries"/>
        
        
            <rdf:li rdf:resource="https://cis-india.org/internet-governance/blog/didp-request-12-revenues"/>
        
        
            <rdf:li rdf:resource="https://cis-india.org/internet-governance/blog/didp-request-11-netmundial-principles"/>
        
        
            <rdf:li rdf:resource="https://cis-india.org/internet-governance/blog/didp-request-10-icann-does-not-know-how-much-each-rir-contributes-to-its-budget"/>
        
        
            <rdf:li rdf:resource="https://cis-india.org/internet-governance/blog/didp-request-9-exactly-how-involved-is-icann-in-the-netmundial-initiative"/>
        
        
            <rdf:li rdf:resource="https://cis-india.org/internet-governance/blog/didp-34-on-granular-detail-on-icanns-budget-for-policy-development-process"/>
        
        
            <rdf:li rdf:resource="https://cis-india.org/internet-governance/blog/akriti-bopanna-april-4-2019-didp-33-on-icann-s-2012-gtld-round-auction-fund"/>
        
        
            <rdf:li rdf:resource="https://cis-india.org/internet-governance/blog/didp-31-on-icanns-fellowship-program"/>
        
    </rdf:Seq>
  </items>

</channel>


    <item rdf:about="https://cis-india.org/internet-governance/blog/didp-request-20-is-presumptive-renewal-of-verisign2019s-contracts-a-good-thing">
    <title>DIDP Request #20 - Is Presumptive Renewal of Verisign’s Contracts a Good Thing?</title>
    <link>https://cis-india.org/internet-governance/blog/didp-request-20-is-presumptive-renewal-of-verisign2019s-contracts-a-good-thing</link>
    <description>
        &lt;b&gt;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.&lt;/b&gt;
        &lt;p style="text-align: justify; "&gt;See the base registry agreement &lt;a class="external-link" href="https://newgtlds.icann.org/sites/default/files/agreements/agreement-approved-09jan14-en.htm"&gt;here&lt;/a&gt;.&lt;/p&gt;
&lt;hr style="text-align: justify; " /&gt;
&lt;p style="text-align: justify; "&gt;&lt;span id="docs-internal-guid-eb2fe452-396a-8d7f-0f0f-7f5c6e36a96a"&gt;In light of this, we filed a request asking ICANN for documents that discuss the rationale behind including the presumptive renewal clause. We also asked them for documents specific to the renewal of Verisign (.com and .net domains) and PIR (.org) contracts. &lt;span id="docs-internal-guid-eb2fe452-396a-c7c2-28df-9d7efc6a7e37"&gt;The request filed by Padmini Baruah can be found &lt;/span&gt;&lt;a href="https://www.icann.org/en/system/files/files/didp-20151130-2-cis-request-30nov15-en.pdf"&gt;&lt;span&gt;here&lt;/span&gt;&lt;/a&gt;&lt;span&gt;.&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;h3 style="text-align: justify; "&gt;&lt;span&gt;&lt;span&gt;What ICANN said&lt;/span&gt;&lt;/span&gt;&lt;/h3&gt;
&lt;p style="text-align: justify; "&gt;&lt;span&gt;&lt;span&gt;ICANN provided a surprisingly comprehensive response to our request. They provided documents in response to our request and stated the rationale that has been given for including a presumptive renewal clause. According to the response, &lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p dir="ltr" id="docs-internal-guid-eb2fe452-396b-5b12-4075-067c0188cd47" style="text-align: justify; "&gt;&lt;i&gt;&lt;span&gt;“Absent countervailing reasons, there is little public benefit, and some significant potential for disruption, in regular changes of a registry operator. In addition, a significant chance of losing the right to operate the registry after a short period creates adverse incentives to favor short term gain over long term investment.” &lt;/span&gt;&lt;/i&gt;&lt;/p&gt;
&lt;p dir="ltr" style="text-align: justify; "&gt;&lt;span&gt;ICANN explains that the contracts have been drawn such that they balance the concerns above with the ability to replace a registry that doesn’t serve the community as it is obliged to do. The response also offers links to various documents substantiating this rationale. &lt;/span&gt;&lt;/p&gt;
&lt;p dir="ltr" style="text-align: justify; "&gt;&lt;span&gt;We were provided an effective answer to our second question as well. ICANN’s response links us to various documents for the 2001, 2006 and 2012 renewals of Verisign’s contract for the .com domain. This includes a summary of the 2012 renewal, public comments for all three renewals and the proposed agreements. &lt;br /&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p dir="ltr" style="text-align: justify; "&gt;&lt;span&gt;For the .net domain, a presumptive renewal clause was not included in the 2001 Verisign contract which opened up the process to select an operator in 2005. ICANN chose to continue its relationship with Verisign and included the clause. The documents relevant to the 2011 renewal of the contracts have been provided. &lt;br /&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p dir="ltr" style="text-align: justify; "&gt;&lt;span&gt;After Verisign relinquished its rights over the .org domain in 2001, ICANN chose the Public Internet Society (PIR) to operate the domain.  While there was no presumptive renewal clause in 2002, documents relevant to the 2006 and 2013 renewals have been provided. &lt;br /&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p dir="ltr" style="text-align: justify; "&gt;&lt;span&gt;&lt;span id="docs-internal-guid-eb2fe452-396c-6d45-90fa-277d2dbd8c48"&gt;ICANN's response to our DIDP request may be found &lt;/span&gt;&lt;a href="https://www.icann.org/en/system/files/files/didp-20151130-2-cis-response-30dec15-en.pdf"&gt;&lt;span&gt;here&lt;/span&gt;&lt;/a&gt;&lt;span&gt;.&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
        &lt;p&gt;
        For more details visit &lt;a href='https://cis-india.org/internet-governance/blog/didp-request-20-is-presumptive-renewal-of-verisign2019s-contracts-a-good-thing'&gt;https://cis-india.org/internet-governance/blog/didp-request-20-is-presumptive-renewal-of-verisign2019s-contracts-a-good-thing&lt;/a&gt;
        &lt;/p&gt;
    </description>
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>asvatha</dc:creator>
    <dc:rights></dc:rights>

    
        <dc:subject>ICANN</dc:subject>
    
    
        <dc:subject>DIDP</dc:subject>
    
    
        <dc:subject>Internet Governance</dc:subject>
    

   <dc:date>2016-07-30T02:01:59Z</dc:date>
   <dc:type>Blog Entry</dc:type>
   </item>


    <item rdf:about="https://cis-india.org/internet-governance/blog/didp-request-19-icann2019s-role-in-the-postponement-of-the-iana-transition">
    <title>DIDP Request #19 - ICANN’s role in the Postponement of the IANA Transition</title>
    <link>https://cis-india.org/internet-governance/blog/didp-request-19-icann2019s-role-in-the-postponement-of-the-iana-transition</link>
    <description>
        &lt;b&gt;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.&lt;/b&gt;
        &lt;p style="text-align: justify; "&gt;&lt;a class="external-link" href="https://www.ntia.doc.gov/press-release/2014/ntia-announces-intent-transition-key-internet-domain-name-functions"&gt;See NTIA announcement here&lt;/a&gt;.&lt;/p&gt;
&lt;hr /&gt;
&lt;p style="text-align: justify; "&gt;In August 2015, NTIA announced that it would not be technically possible to meet this deadline and extended it by a year. NTIA stated,&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;span id="docs-internal-guid-816516c5-3775-475c-1f2f-cfde97e46a00"&gt;“&lt;i&gt;Accordingly, in May we asked the groups developing the transition documents how long it would take to finish and implement their proposals. After factoring in time for public comment, U.S. Government evaluation and implementation of the proposals, the community estimated it could take until at least September 2016 to &lt;a class="external-link" href="https://www.ntia.doc.gov/blog/2015/update-iana-transition"&gt;complete this process&lt;/a&gt;&lt;/i&gt;.”&lt;/span&gt;&lt;/p&gt;
&lt;p dir="ltr" id="docs-internal-guid-816516c5-3780-2a3c-fb9f-381a3585fb5b" style="text-align: justify; "&gt;&lt;span&gt;&lt;span id="docs-internal-guid-816516c5-377f-e490-8578-5857613384b7"&gt;In our DIDP request, we asked ICANN for all documents that it had submitted to NTIA that were relevant to the IANA transition and its postponement from the date of the initial announcement— March 14, 2015 to the date of the announcement of extension — August 17, 2015. We specifically requested the documents requested by NTIA in May 2015 as referenced by &lt;/span&gt;&lt;a href="https://www.ntia.doc.gov/blog/2015/update-iana-transition"&gt;&lt;span&gt;this&lt;/span&gt;&lt;/a&gt;&lt;span&gt; blogpost. &lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p dir="ltr" style="text-align: justify; "&gt;&lt;span&gt;The request filed by Padmini Baruah can be found &lt;/span&gt;&lt;a href="https://www.icann.org/en/system/files/files/didp-20151130-1-cis-request-30nov15-en.pdf"&gt;&lt;span&gt;here&lt;/span&gt;&lt;/a&gt;&lt;span&gt;. &lt;/span&gt;&lt;/p&gt;
&lt;h3 style="text-align: justify; "&gt;&lt;span&gt;What ICANN said&lt;/span&gt;&lt;/h3&gt;
&lt;p style="text-align: justify; "&gt;&lt;span&gt;ICANN’s response terms our request as “broadly worded” and assumes that our request is only related to documents about the extension of the deadline. It was not. &lt;br /&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;span&gt;After NTIA’s announcement in 2014, ICANN launched a multi-stakeholder process and discussion at ICANN 49 in Singapore to facilitate the transition. The organizational structure of this process has been mapped out according to the different IANA functions that are being transitioned. Accordingly, we have the:&lt;/span&gt;&lt;/p&gt;
&lt;ul style="text-align: justify; "&gt;
&lt;li&gt;&lt;span&gt;IANA Stewardship Transition Coordination Group (ICG)&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;Cross Community Working Group (CWG-Stewardship)&lt;/li&gt;
&lt;li&gt;Consolidated RIR IANA Stewardship Proposal Team (CRISP TEAM)&lt;/li&gt;
&lt;li&gt;IANAPLAN Working Group (IANAPLAN WG)&lt;/li&gt;
&lt;li&gt;Cross-Community Working&lt;/li&gt;
&lt;li&gt;Group (CCWG-Accountability) &lt;/li&gt;
&lt;/ul&gt;
&lt;p style="text-align: justify; "&gt;In addressing our request, ICANN references this multi-stakeholder community overseeing the transition. According to the response document, the ICG, CWG-Stewardship, CRISP Team, IANAPLAN WG and the CCWG-Accountability submitted responses directly to the NTIA leaving the ICANN with no documents responsive to our request.&lt;/p&gt;
&lt;p dir="ltr" id="docs-internal-guid-816516c5-3782-ddb4-6000-3aee1459369a" style="text-align: justify; "&gt;&lt;span&gt;ICANN's response to our DIDP request may be found &lt;/span&gt;&lt;a href="https://www.icann.org/en/system/files/files/didp-20151130-1-cis-response-30dec15-en.pdf"&gt;&lt;span&gt;here&lt;/span&gt;&lt;/a&gt;&lt;span&gt;. &lt;/span&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt; &lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;span&gt;&lt;br /&gt;&lt;/span&gt;&lt;/p&gt;
        &lt;p&gt;
        For more details visit &lt;a href='https://cis-india.org/internet-governance/blog/didp-request-19-icann2019s-role-in-the-postponement-of-the-iana-transition'&gt;https://cis-india.org/internet-governance/blog/didp-request-19-icann2019s-role-in-the-postponement-of-the-iana-transition&lt;/a&gt;
        &lt;/p&gt;
    </description>
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>asvatha</dc:creator>
    <dc:rights></dc:rights>

    
        <dc:subject>ICANN</dc:subject>
    
    
        <dc:subject>DIDP</dc:subject>
    
    
        <dc:subject>Internet Governance</dc:subject>
    

   <dc:date>2016-07-29T16:37:04Z</dc:date>
   <dc:type>Blog Entry</dc:type>
   </item>


    <item rdf:about="https://cis-india.org/internet-governance/blog/didp-request-18-icann2019s-internal-website-will-stay-internal">
    <title>DIDP Request #18 - ICANN’s Internal Website will Stay Internal</title>
    <link>https://cis-india.org/internet-governance/blog/didp-request-18-icann2019s-internal-website-will-stay-internal</link>
    <description>
        &lt;b&gt;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.&lt;/b&gt;
        &lt;p style="text-align: justify; "&gt;&lt;span id="docs-internal-guid-6ae20cf4-3723-9313-1ca4-571610febfac"&gt;The request filed by Padmini Baruah can be found &lt;/span&gt;&lt;a href="https://www.icann.org/en/system/files/files/didp-request-20150901-6-01sep15-en.pdf"&gt;&lt;span&gt;here&lt;/span&gt;&lt;/a&gt;&lt;span&gt;. To no one’s surprise, not only did ICANN not have this document in “ICANN's possession, custody, or control,” even if it did it would be subject to &lt;a class="external-link" href="https://www.icann.org/resources/pages/didp-2012-02-25-en"&gt;DIDP conditions for non-disclosure&lt;/a&gt;.&lt;/span&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;span&gt;&lt;span id="docs-internal-guid-6ae20cf4-3724-8d54-05ca-866fe5bc62b5"&gt;ICANN's response to our DIDP request may be found &lt;/span&gt;&lt;a href="https://www.icann.org/en/system/files/files/didp-response-20150901-6-cis-wiki-01oct15-en.pdf"&gt;&lt;span&gt;here&lt;/span&gt;&lt;/a&gt;&lt;span&gt;.&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
        &lt;p&gt;
        For more details visit &lt;a href='https://cis-india.org/internet-governance/blog/didp-request-18-icann2019s-internal-website-will-stay-internal'&gt;https://cis-india.org/internet-governance/blog/didp-request-18-icann2019s-internal-website-will-stay-internal&lt;/a&gt;
        &lt;/p&gt;
    </description>
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>asvatha</dc:creator>
    <dc:rights></dc:rights>

    
        <dc:subject>ICANN</dc:subject>
    
    
        <dc:subject>DIDP</dc:subject>
    
    
        <dc:subject>Internet Governance</dc:subject>
    

   <dc:date>2016-07-29T14:53:50Z</dc:date>
   <dc:type>Blog Entry</dc:type>
   </item>


    <item rdf:about="https://cis-india.org/internet-governance/blog/didp-request-17-how-icann-chooses-their-contractual-compliance-auditors">
    <title>DIDP Request #17 - How ICANN Chooses their Contractual Compliance Auditors </title>
    <link>https://cis-india.org/internet-governance/blog/didp-request-17-how-icann-chooses-their-contractual-compliance-auditors</link>
    <description>
        &lt;b&gt;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.&lt;/b&gt;
        &lt;p style="text-align: justify; "&gt;&lt;span id="docs-internal-guid-88ef1d6f-3472-3cd6-bf11-e5bb7d2ea6a9"&gt;It is clear to us at CIS that the people in charge of these compliance audits perform an important function at ICANN. To that effect, we requested information on the 24 individuals mentioned by Mr Chehadi as well as the third party auditors who perform this powerful watchdog function. More specifically, we requested documents calling for appointments of the auditors and copies of their contracts with ICANN.&lt;/span&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;span&gt;&lt;span id="docs-internal-guid-88ef1d6f-3472-5ef2-432a-dbb3e446057d"&gt;The request filed by Padmini Baruah can be found &lt;/span&gt;&lt;a href="https://www.icann.org/en/system/files/files/didp-request-20150901-5-01sep15-en.pdf"&gt;&lt;span&gt;here&lt;/span&gt;&lt;/a&gt;&lt;span&gt;.&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;h3 style="text-align: justify; "&gt;&lt;span&gt;&lt;span&gt;What ICANN said&lt;/span&gt;&lt;/span&gt;&lt;/h3&gt;
&lt;p dir="ltr" id="docs-internal-guid-88ef1d6f-3472-81e4-8a58-7815de9e725d" style="text-align: justify; "&gt;&lt;span&gt;In their response to the first part of our question, ICANN linked us to a webpage containing the names and titles of all employees working on contractual compliance. This page contains 26 names including the Contractual Compliance Risk and Audit Manager: &lt;/span&gt;&lt;a href="https://www.icann.org/resources/pages/about-2014-10-10-en"&gt;&lt;span&gt;https://www.icann.org/resources/pages/about-2014-10-10-en&lt;/span&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p dir="ltr" id="docs-internal-guid-88ef1d6f-3472-cda1-dd73-6b12b9aa1fc5" style="text-align: justify; "&gt;&lt;span&gt;ICANN also described the process of selecting KPMG as their third party auditor in detail. A pre-selection process shortlists 5 companies  that fit the following criteria: knowledge of ICANN, global presence, size, expertise and reputation. Then, ICANN issues a targeted Request For Proposal (RFP) to these companies asking them for their audit proposals. After a question and answer session, a proposal analysis and rating the scorecards, a “cross-functional steering committee” decided to go with KPMG. While the process has been discussed transparently, our questions remain unanswered.&lt;/span&gt;&lt;/p&gt;
&lt;p dir="ltr" id="docs-internal-guid-88ef1d6f-3473-0cee-aa58-9889a6de22eb" style="text-align: justify; "&gt;&lt;span&gt;The RFP would qualify as the document requested by us in the second part of the question (i.e.)  a “document that calls for appointments to the post of the contractual compliance auditor.” Unfortunately, ICANN has not published the RFP citing the DIDP Conditions for Non-disclosure. However, the timeline for the RFP and other details have been posted &lt;/span&gt;&lt;a href="https://www.icann.org/resources/pages/governance/rfps-en"&gt;&lt;span&gt;here&lt;/span&gt;&lt;/a&gt;&lt;span&gt; after our DIDP request. In addition, the contract between  KPMG and ICANN has also not been published. &lt;/span&gt;&lt;/p&gt;
&lt;p dir="ltr" id="docs-internal-guid-88ef1d6f-3473-2c8e-1679-7191963f7ad9" style="text-align: justify; "&gt;&lt;span&gt;ICANN's response to our DIDP request may be found &lt;/span&gt;&lt;a href="https://www.icann.org/en/system/files/files/didp-response-20150901-5-cis-auditor-appt-01oct15-en.pdf"&gt;&lt;span&gt;here&lt;/span&gt;&lt;/a&gt;&lt;span&gt;. &lt;/span&gt;&lt;/p&gt;
        &lt;p&gt;
        For more details visit &lt;a href='https://cis-india.org/internet-governance/blog/didp-request-17-how-icann-chooses-their-contractual-compliance-auditors'&gt;https://cis-india.org/internet-governance/blog/didp-request-17-how-icann-chooses-their-contractual-compliance-auditors&lt;/a&gt;
        &lt;/p&gt;
    </description>
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>asvatha</dc:creator>
    <dc:rights></dc:rights>

    
        <dc:subject>ICANN</dc:subject>
    
    
        <dc:subject>DIDP</dc:subject>
    
    
        <dc:subject>Internet Governance</dc:subject>
    

   <dc:date>2016-07-29T02:20:59Z</dc:date>
   <dc:type>Blog Entry</dc:type>
   </item>


    <item rdf:about="https://cis-india.org/internet-governance/blog/didp-request-16-icann-has-no-documentation-on-registrars2019-201cabuse-contacts201d">
    <title>DIDP Request #16 - ICANN has no Documentation on Registrars’ “Abuse Contacts”</title>
    <link>https://cis-india.org/internet-governance/blog/didp-request-16-icann-has-no-documentation-on-registrars2019-201cabuse-contacts201d</link>
    <description>
        &lt;b&gt;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.&lt;/b&gt;
        &lt;p style="text-align: justify; "&gt;We wrote to ICANN requesting information on these abuse complaints received by registrars over the last year. We specifically wanted reports of illegal activity on the internet submitted to these abuse contacts as well as details on actions taken by registrars in response to these complaints.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;span id="docs-internal-guid-9b05b54d-3465-1c5e-3830-7af0d8e37b19"&gt;The request filed by Padmini Baruah can be found &lt;/span&gt;&lt;a href="https://www.icann.org/en/system/files/files/didp-request-20150901-4-01sep15-en.pdf"&gt;&lt;span&gt;here&lt;/span&gt;&lt;/a&gt;&lt;span&gt;.&lt;/span&gt;&lt;/p&gt;
&lt;h3 style="text-align: justify; "&gt;&lt;span&gt;What ICANN said&lt;/span&gt;&lt;/h3&gt;
&lt;p style="text-align: justify; "&gt;&lt;span&gt;Our request to ICANN very specifically dealt with reported illegal activities. However, in their response, ICANN first broadened it to abuse complaints and then failed to give a narrowed down list of even those complaints.&lt;/span&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;span&gt;In their response, ICANN indicated that they do not store records of complaints made to the abuse contact. This is stored by the registrars and is available to ICANN only upon request. However, since ICANN is only obliged to publish documents it already has in its possession, we did not receive an answer to our first question. &lt;/span&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;span&gt;&lt;span id="docs-internal-guid-9b05b54d-3467-44df-1aed-bbe876d6dc71"&gt;As for the second item, ICANN gave a familiarly vague answer, linking us to the&lt;/span&gt;&lt;a href="https://www.icann.org/compliance/notices"&gt;&lt;span&gt; Contractual Compliance Complaints&lt;/span&gt;&lt;/a&gt;&lt;span&gt; page with a list of all the breach notices that have been issued by ICANN to registrars. A breach notice is relevant to our request only if it is in response to an abuse complaint, and the abuse complaint specifically deals with illegal activity. Even discounting that, this is not a comprehensive list when you take into account that a breach notice is published only “if a &lt;/span&gt;&lt;span&gt;formal contractual compliance enforcement process has been initiated &lt;/span&gt;&lt;span&gt;relating to an abuse complaint and resulted in a breach.”&lt;a href="#ftn1"&gt;[1] &lt;/a&gt;What about the rest of the complaints received by the registrar?&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;span&gt;&lt;span&gt;In addition, ICANN refused to publish any communication or documentation of ICANN requesting reports of illegal activity under the DIDP non-disclosure conditions. &lt;br /&gt;&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;span&gt;&lt;span&gt;&lt;span id="docs-internal-guid-9b05b54d-3469-bdb4-1603-805eb7dc6a97"&gt;ICANN's response to our DIDP request may be found &lt;/span&gt;&lt;a href="https://www.icann.org/en/system/files/files/didp-response-20150901-4-cis-abuse-complaints-01oct15-en.pdf"&gt;&lt;span&gt;here&lt;/span&gt;&lt;/a&gt;&lt;span&gt;.&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;hr /&gt;
&lt;p dir="ltr" id="docs-internal-guid-9b05b54d-346a-e343-097c-9bedf6f32f17"&gt;&lt;a name="ftn1"&gt;[1] &lt;/a&gt;&lt;span&gt;See ICANN response here (Pg 4): https://www.icann.org/en/system/files/files/didp-response-20150901-4-cis-abuse-complaints-01oct15-en.pdf&lt;/span&gt;&lt;/p&gt;
        &lt;p&gt;
        For more details visit &lt;a href='https://cis-india.org/internet-governance/blog/didp-request-16-icann-has-no-documentation-on-registrars2019-201cabuse-contacts201d'&gt;https://cis-india.org/internet-governance/blog/didp-request-16-icann-has-no-documentation-on-registrars2019-201cabuse-contacts201d&lt;/a&gt;
        &lt;/p&gt;
    </description>
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>asvatha</dc:creator>
    <dc:rights></dc:rights>

    
        <dc:subject>ICANN</dc:subject>
    
    
        <dc:subject>DIDP</dc:subject>
    
    
        <dc:subject>Internet Governance</dc:subject>
    

   <dc:date>2016-07-29T02:11:52Z</dc:date>
   <dc:type>Blog Entry</dc:type>
   </item>


    <item rdf:about="https://cis-india.org/internet-governance/blog/didp-request-15-what-is-going-on-between-verisign-and-icann">
    <title>DIDP Request #15: What is going on between Verisign and ICANN?</title>
    <link>https://cis-india.org/internet-governance/blog/didp-request-15-what-is-going-on-between-verisign-and-icann</link>
    <description>
        &lt;b&gt;During a hearing of the House Committee on Energy and Commerce on “Internet Governance Progress After ICANN 53,” President and CEO of ICANN - Mr Fadi Chehade indicated that ICANN follows up with registries and registrars on receipt of any complaint against them about violations of their contract with ICANN.&lt;/b&gt;
        &lt;p style="text-align: justify; "&gt;At CIS, we believe that any exchange of dialogue or any outcome from ICANN acting on these complaints needs to be in the public domain. Thus, our 15th DIDP request to ICANN were for documents pertinent to Verisign’s contractual compliance and actions taken by ICANN stemming from any discrepancies of Verisign’s compliance with its ICANN contract.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;span id="docs-internal-guid-f679a3d5-345d-67c5-6d95-690f07d56d1f"&gt;The DIDP request filed by Padmini Baruah can be found &lt;/span&gt;&lt;a href="https://www.icann.org/en/system/files/files/didp-request-20150901-3-01sep15-en.pdf"&gt;&lt;span&gt;here&lt;/span&gt;&lt;/a&gt;&lt;span&gt;.&lt;/span&gt;&lt;/p&gt;
&lt;h3 style="text-align: justify; "&gt;&lt;span&gt;What ICANN said&lt;/span&gt;&lt;/h3&gt;
&lt;p style="text-align: justify; "&gt;&lt;span&gt;After sorting through a response designed to obfuscate information, it was clear that ICANN was not going to provide any of the details we requested. As mentioned in their previous responses, individual audit reports and the names of the registries associated with discrepancies are confidential under the DIDP Defined Conditions of Nondisclosure. Nevertheless, some details from the response are worth mentioning.&lt;/span&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;span&gt;According to the response, “As identified in Appendix B of the 2012 Contractual Compliance Year One Audit Program Report, the following TLDs were selected for auditing: DotAsia Organisation Limited (.ASIA), Telnic Limited (.TEL), Public Interest Registry (.ORG), Verisign (.NET), Afilias (.INFO), and Employ Media LLC (.JOBS).” The response goes on to state that out of these 6 registries that were selected, only 5 chose to participate in the audit, the identies of which are once again confidential. &lt;/span&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;span&gt;However, on further examination, it can be seen that Verisign (.NET) was chosen to participate in  the audit the year after as well. Therefore, it’s clear that 2013 was the year Verisign was audited. Unfortunately, that was pretty much all that was relevant to our request in ICANN’s response.&lt;/span&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;span&gt;Once again, ICANN was able to use the DIDP Defined Conditions of Nondisclosure, especially the following conditions to allow itself the ability not to answer the public: &lt;br /&gt;&lt;/span&gt;&lt;/p&gt;
&lt;ul style="text-align: justify; "&gt;
&lt;li&gt;&lt;span&gt;Information exchanged, prepared for, or derived from the deliberative and decision-making process between ICANN, its constituents, and/or other entities with which ICANN cooperates that, if disclosed, would or would be likely to compromise the integrity of the deliberative and decision-making process between and among ICANN, its constituents, and/or other entities with which ICANN cooperates by inhibiting the candid exchange of ideas and communications.&lt;/span&gt;&lt;span&gt; &lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;Information provided to ICANN by a party that, if disclosed, would or would be likely to materially prejudice the commercial interests, financial interests, and/or competitive position of such party or was provided to ICANN pursuant to a nondisclosure agreement or nondisclosure provision within an agreement.&lt;/span&gt;&lt;span&gt; &lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;Confidential business information and/or internal policies and procedures.&lt;a href="#ftn1"&gt;[1]&lt;/a&gt;&lt;/span&gt;&lt;span&gt; &lt;br /&gt;&lt;/span&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p style="text-align: justify; "&gt;&lt;span id="docs-internal-guid-f679a3d5-345f-fcdf-ba09-26b6f74477d8"&gt;ICANN’s response to our request can be found &lt;/span&gt;&lt;a href="https://www.icann.org/en/system/files/files/didp-response-20150901-3-cis-contractual-violations-verisign-01oct15-en.pdf"&gt;&lt;span&gt;here&lt;/span&gt;&lt;/a&gt;&lt;span&gt;.&lt;/span&gt;&lt;/p&gt;
&lt;hr style="text-align: justify; " /&gt;
&lt;p style="text-align: justify; "&gt;&lt;a name="ftn1"&gt;[1] &lt;/a&gt;&lt;span id="docs-internal-guid-f679a3d5-3461-1364-7277-525329280407"&gt;See DIDP https://www.icann.org/resources/pages/didp-2012-02-25-en&lt;/span&gt;&lt;/p&gt;
        &lt;p&gt;
        For more details visit &lt;a href='https://cis-india.org/internet-governance/blog/didp-request-15-what-is-going-on-between-verisign-and-icann'&gt;https://cis-india.org/internet-governance/blog/didp-request-15-what-is-going-on-between-verisign-and-icann&lt;/a&gt;
        &lt;/p&gt;
    </description>
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>asvatha</dc:creator>
    <dc:rights></dc:rights>

    
        <dc:subject>ICANN</dc:subject>
    
    
        <dc:subject>DIDP</dc:subject>
    
    
        <dc:subject>Internet Governance</dc:subject>
    

   <dc:date>2016-07-29T02:01:06Z</dc:date>
   <dc:type>Blog Entry</dc:type>
   </item>


    <item rdf:about="https://cis-india.org/internet-governance/blog/didp-request-14-keeping-track-of-icann2019s-contracted-parties-registrars">
    <title>DIDP Request #14: Keeping track of ICANN’s contracted parties: Registrars</title>
    <link>https://cis-india.org/internet-governance/blog/didp-request-14-keeping-track-of-icann2019s-contracted-parties-registrars</link>
    <description>
        &lt;b&gt;In September 2016, we filed two separate DIDP requests regarding ICANN’s Contractual Compliance Goals.&lt;/b&gt;
        &lt;p&gt;&lt;span id="docs-internal-guid-bf51bf89-322e-256d-7606-417c64dfd392"&gt;The first one which we have written about here,&lt;/span&gt;&lt;a href="#ftn1"&gt;[1] &lt;/a&gt;was regarding ICANN contracts with registries while the second one about registrars is briefed below. In our second request, we specifically asked for the following information:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Copies of the registrar contractual compliance audit reports for all the audits carried out as well as external audit reports from the last year (2014-2015).&lt;/li&gt;
&lt;li&gt;A generic template of the notice served by ICANN before conducting such an audit.&lt;/li&gt;
&lt;li&gt;A list of the registrars to whom such notices were served in the last year.&lt;/li&gt;
&lt;li&gt;An account of the expenditure incurred by ICANN in carrying out the audit process.&lt;/li&gt;
&lt;li&gt;A list of the registrars that did not respond to the notice within a reasonable period of time.&lt;/li&gt;
&lt;li&gt;Reports of the site visits conducted by ICANN to ascertain compliance.&lt;/li&gt;
&lt;li&gt;Documents which identify the registrars who had committed material discrepancies in the terms of the contract.&lt;/li&gt;
&lt;li&gt;Documents pertaining to the actions taken in the event that there was found to be some form of contractual non-compliance.&lt;/li&gt;
&lt;li&gt;A copy of the registrar self-assessment form which is to be submitted to ICANN. &lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;The DIDP request filed by Padmini Baruah can be viewed here.&lt;/p&gt;
&lt;h3&gt;What ICANN said&lt;/h3&gt;
&lt;p&gt;&lt;span id="docs-internal-guid-bf51bf89-3234-6693-c084-c898ecb92ff6"&gt;Information pertinent to item 1 and 3 can be found in the 2014 Contractual Compliance Annual Report here:https://&lt;/span&gt;&lt;a href="http://www.icann.org/en/system/files/files/annual-2014-13feb15-en.pdf"&gt;&lt;span&gt;www.icann.org/en/system/files/files/annual-2014-13feb15-en.pdf&lt;/span&gt;&lt;/a&gt;&lt;span&gt;. While this report contains detailed information regarding the audit, individual audit reports are subject to the DIDP Defined Conditions for Nondisclosure.&lt;/span&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;span&gt;&lt;span id="docs-internal-guid-bf51bf89-3234-d617-f932-ee71027bdaf6"&gt;ICANN provided a link to all the communication templates used during the audit process, including the notice served by ICANN prior to conducting audits. (Item 2) It can be found here:&lt;/span&gt;&lt;a href="https://www.icann.org/en/system/files/files/audit-communication-template-04dec15-en.pdf"&gt;&lt;span&gt; &lt;/span&gt;&lt;span&gt;https://www.icann.org/en/system/files/files/audit-communication-template-04dec15-en.pdf&lt;/span&gt;&lt;/a&gt;&lt;span&gt;. As mentioned in an earlier blog post, ICANN set aside USD 0.6 million for the Three Year Audit plan.&lt;a href="#ftn2"&gt;[2] &lt;/a&gt;(item 4)&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;span&gt;&lt;span&gt;According to the Audit FAQ on ICANN website,&lt;a href="#ftn3"&gt;[3]&lt;/a&gt; &lt;span id="docs-internal-guid-bf51bf89-323a-156a-af6f-d315baa30ccd"&gt;“If a contracted party reaches the enforcement phase per process, ICANN will issue a notice of breach in which the outstanding issues are noted. The response links us to the ICANN webpage where these breach notices are listed:&lt;/span&gt;&lt;a href="https://www.icann.org/compliance/notices#notices-2014"&gt;&lt;span&gt; &lt;/span&gt;&lt;span&gt;https://www.icann.org/compliance/notices#notices-2014&lt;/span&gt;&lt;/a&gt;&lt;span&gt;. (Item 5) According to the link, 61 registrars received breach notices in 2014; a full explanation has been provided for each notice. (Item 7 and 8) Since no site visits were conducted, ICANN does not possess any document regarding this.&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;span&gt;&lt;span&gt;&lt;span&gt;&lt;span&gt;According to the ICANN website, “The 2013 Registrar Accreditation Agreement (RAA) requires ICANN-accredited registrars to complete an annual self-assessment and provide ICANN with a compliance certification by 20 January.”&lt;a href="#ftn4"&gt;[4] &lt;/a&gt;&lt;span id="docs-internal-guid-bf51bf89-3244-56d6-a94a-37347d37616b"&gt;The form for the same can be found here: &lt;/span&gt;&lt;a href="https://www.icann.org/resources/pages/approved-with-specs-2013-09-17-en#compliance"&gt;&lt;span&gt;https://www.icann.org/resources/pages/approved-with-specs-2013-09-17-en#compliance&lt;/span&gt;&lt;/a&gt;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;span&gt;&lt;span&gt;&lt;span&gt;&lt;span&gt;&lt;span&gt;&lt;span id="docs-internal-guid-bf51bf89-3244-91f8-830f-b40c5a82d02a"&gt;ICANN’s response to our request can be found &lt;/span&gt;&lt;a href="https://www.icann.org/en/system/files/files/didp-response-20150901-1-response-20150901-2-cis-ry-rr-audits-01oct15-en.pdf"&gt;&lt;span&gt;here&lt;/span&gt;&lt;/a&gt;&lt;span&gt;.&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;hr /&gt;
&lt;p&gt;&lt;a name="ftn1"&gt;[1] &lt;/a&gt;&lt;span id="docs-internal-guid-bf51bf89-3258-80b4-c7aa-aea9801aceac"&gt;To be linked to the first post&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;a name="ftn2"&gt;[2] &lt;/a&gt;&lt;span id="docs-internal-guid-bf51bf89-3258-28cd-a693-d1605b22ce9e"&gt;See FY15 budget (pg72): &lt;/span&gt;&lt;a href="https://www.icann.org/en/system/files/files/adopted-opplan-budget-fy15-01dec14-en.pdf"&gt;&lt;span&gt;https://www.icann.org/en/system/files/files/adopted-opplan-budget-fy15-01dec14-en.pdf&lt;/span&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a name="ftn3"&gt;[3] &lt;/a&gt;&lt;span id="docs-internal-guid-bf51bf89-3257-ded2-6793-607c741261a7"&gt;See Audit FAQ: https://www.icann.org/resources/pages/faqs-2012-10-31-en&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;a name="ftn4"&gt;[4] &lt;/a&gt;See CEO certification: https://www.icann.org/resources/pages/ceo-certification-2014-01-29-en&lt;/p&gt;
        &lt;p&gt;
        For more details visit &lt;a href='https://cis-india.org/internet-governance/blog/didp-request-14-keeping-track-of-icann2019s-contracted-parties-registrars'&gt;https://cis-india.org/internet-governance/blog/didp-request-14-keeping-track-of-icann2019s-contracted-parties-registrars&lt;/a&gt;
        &lt;/p&gt;
    </description>
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>asvatha</dc:creator>
    <dc:rights></dc:rights>

    
        <dc:subject>ICANN</dc:subject>
    
    
        <dc:subject>DIDP</dc:subject>
    
    
        <dc:subject>Internet Governance</dc:subject>
    

   <dc:date>2016-07-28T16:34:27Z</dc:date>
   <dc:type>Blog Entry</dc:type>
   </item>


    <item rdf:about="https://cis-india.org/internet-governance/blog/didp-request-13-keeping-track-of-icann2019s-contracted-parties-registries">
    <title>DIDP Request #13: Keeping track of ICANN’s contracted parties: Registries</title>
    <link>https://cis-india.org/internet-governance/blog/didp-request-13-keeping-track-of-icann2019s-contracted-parties-registries</link>
    <description>
        &lt;b&gt;On multiple occasions, Fadi Chehade, then President and CEO of ICANN has emphasized the importance of conducting audits (internal and external) to ensure compliance of ICANN’s contracted parties. At a US congressional hearing, he spoke about the contract monitoring function of ICANN. &lt;/b&gt;
        &lt;p style="text-align: justify; "&gt;In September 2015, we filed two separate DIDP requests regarding ICANN’s Contractual Compliance Goals. The first one, briefed below, is regarding the contracts with registries and the second one is regarding ICANN contracts with registrars. This post contains some additional background information on the Contractual Compliance Goals at ICANN. In our first request, we specifically asked for the following information:&lt;/p&gt;
&lt;ol style="text-align: justify; "&gt;
&lt;li&gt;Copies of the registry contractual compliance audit reports for all the audits carried out as well as external audit reports from the last year (2014-2015).&lt;/li&gt;
&lt;li&gt;A generic template of the notice served by ICANN before conducting such an audit. &lt;/li&gt;
&lt;li&gt;A list of the registries to whom such notices were served in the last year. &lt;/li&gt;
&lt;li&gt;An account of the expenditure incurred by ICANN in carrying out the audit process. &lt;/li&gt;
&lt;li&gt;A list of the registries that did not respond to the notice within a reasonable period of time. &lt;/li&gt;
&lt;li&gt;Reports of the site visits conducted by ICANN to ascertain compliance.&lt;/li&gt;
&lt;li&gt;Documents which identifies the registry operators who had committed material discrepancies in the terms of the contract. &lt;/li&gt;
&lt;li&gt;Documents pertaining to the actions taken in the event that there was found to be some form of contractual non-compliance. &lt;/li&gt;
&lt;/ol&gt;
&lt;p style="text-align: justify; "&gt;&lt;span id="docs-internal-guid-36e025c6-3214-1f40-f34c-66e56df641b6"&gt;The DIDP request filed by Padmini Baruah can be viewed &lt;/span&gt;&lt;a href="https://www.icann.org/en/system/files/files/didp-request-20150901-1-01sep15-en.pdf"&gt;&lt;span&gt;here&lt;/span&gt;&lt;/a&gt;&lt;span&gt;.&lt;/span&gt;&lt;/p&gt;
&lt;h3 style="text-align: justify; "&gt;&lt;span&gt;What ICANN said&lt;/span&gt;&lt;/h3&gt;
&lt;p style="text-align: justify; "&gt;&lt;span&gt;ICANN’s Contractual Compliance Goal is to ensure that all the parties that ICANN has entered into a contract with complies with the stipulations of the contract. This is done in several ways, including Contractual Compliance complaints and Audits.&lt;a href="#ftn1"&gt;[1]&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p dir="ltr" id="docs-internal-guid-36e025c6-3223-35f4-9e89-5d38d93e81e3" style="text-align: justify; "&gt;&lt;span&gt;In 2012, ICANN initiated the Three Year Audit plan where one-third of registries were selected each year for an audit. In 2014, the third set of registries were audited. In response to Item 1,  information about the audit for 2014 can be found here: &lt;/span&gt;&lt;a href="https://www.icann.org/en/system/files/files/contractual-compliance-ra-audit-report-2014-03feb15-en.pdf"&gt;&lt;span&gt;https://www.icann.org/en/system/files/files/contractual-compliance-ra-audit-report-2014-03feb15-en.pdf&lt;/span&gt;&lt;/a&gt;&lt;span&gt;. At this link, we can also find the list of registries that went through the audit process in 2014 (item 3). Monthly updates on overall contractual compliance can be found here:&lt;/span&gt;&lt;a href="https://www.icann.org/resources/pages/update-2013-03-15-en"&gt;&lt;span&gt; &lt;/span&gt;&lt;span&gt;https://www.icann.org/resources/pages/update-2013-03-15-en&lt;/span&gt;&lt;/a&gt;&lt;span&gt;. &lt;/span&gt;&lt;/p&gt;
&lt;p dir="ltr" id="docs-internal-guid-36e025c6-3223-80b1-a31b-01ccfb91f71d" style="text-align: justify; "&gt;&lt;span&gt;ICANN linked us to all the communication templates used during the audit process, including the notice served by ICANN prior to conducting audits. (Item 2) It can be found here: &lt;/span&gt;&lt;a href="https://www.icann.org/en/system/files/files/audit-communication-template-04dec15-en.pdf"&gt;&lt;span&gt;https://www.icann.org/en/system/files/files/audit-communication-template-04dec15-en.pdf &lt;/span&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p dir="ltr" style="text-align: justify; "&gt;&lt;span&gt;&lt;span id="docs-internal-guid-36e025c6-3223-c0d0-b744-b06fc20af7d3"&gt;In the operating plan and budget for FY15, ICANN sets aside USD 0.2 million for the New Registry Agreement Audit and USD 0.6 million for the Three Year Audit plan.&lt;a href="#ftn2"&gt;[2]&lt;/a&gt;&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p dir="ltr" style="text-align: justify; "&gt;&lt;span&gt;&lt;span&gt;Other documents to answer this question such as invoices from the external auditing firm are subject to non-disclosure under DIDP policies. Since all registries responded in a timely manner and no site visits were conducted, there are no documents to answer items 5 and 6. &lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p dir="ltr" style="text-align: justify; "&gt;&lt;span&gt;&lt;span&gt;The audit report linked above contains information on deficiencies identified during the audit. ICANN states that registries addressed these deficiencies during the remediation process. However, there is a caveat to this discussion. The names of the registries that are associated with these discrepancies remains confidential, subject to the DIDP Defined Conditions for Nondisclosure. (Item 7) ICANN goes on to state that it is not required to confirm if the registries have taken appropriate action and thus does not have any documents in response to item 8. While ICANN’s audit process seems thorough, does this last statement indicate a lack of enforcement mechanisms on ICANN’s part?  &lt;br /&gt;&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p dir="ltr" id="docs-internal-guid-36e025c6-3225-cbec-186e-0694f7918168" style="text-align: justify; "&gt;&lt;span&gt;ICANN’s response to our request can be found &lt;/span&gt;&lt;a href="https://www.icann.org/en/system/files/files/didp-response-20150901-1-response-20150901-2-cis-ry-rr-audits-01oct15-en.pdf"&gt;&lt;span&gt;here&lt;/span&gt;&lt;/a&gt;&lt;span&gt;.&lt;/span&gt;&lt;/p&gt;
&lt;hr style="text-align: justify; " /&gt;
&lt;p style="text-align: justify; "&gt;&lt;a name="ftn1"&gt;[1]. &lt;/a&gt;&lt;span id="docs-internal-guid-36e025c6-3227-7c19-f04b-6258c3ad1fbc"&gt;See Contractual Compliance website: https://www.icann.org/resources/pages/compliance-2012-02-25-en&lt;/span&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;a name="ftn2"&gt;[2]. &lt;/a&gt;&lt;span id="docs-internal-guid-36e025c6-3228-1009-f91a-30ea4972689f"&gt;See FY15 budget (pg72): &lt;/span&gt;&lt;a href="https://www.icann.org/en/system/files/files/adopted-opplan-budget-fy15-01dec14-en.pdf"&gt;&lt;span&gt;https://www.icann.org/en/system/files/files/adopted-opplan-budget-fy15-01dec14-en.pdf&lt;/span&gt;&lt;/a&gt;&lt;/p&gt;
        &lt;p&gt;
        For more details visit &lt;a href='https://cis-india.org/internet-governance/blog/didp-request-13-keeping-track-of-icann2019s-contracted-parties-registries'&gt;https://cis-india.org/internet-governance/blog/didp-request-13-keeping-track-of-icann2019s-contracted-parties-registries&lt;/a&gt;
        &lt;/p&gt;
    </description>
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>asvatha</dc:creator>
    <dc:rights></dc:rights>

    
        <dc:subject>ICANN</dc:subject>
    
    
        <dc:subject>DIDP</dc:subject>
    
    
        <dc:subject>Internet Governance</dc:subject>
    

   <dc:date>2016-07-28T15:40:01Z</dc:date>
   <dc:type>Blog Entry</dc:type>
   </item>


    <item rdf:about="https://cis-india.org/internet-governance/blog/didp-request-12-revenues">
    <title>DIDP Request #12: Revenues</title>
    <link>https://cis-india.org/internet-governance/blog/didp-request-12-revenues</link>
    <description>
        &lt;b&gt;The Centre for Internet &amp; Society (CIS) sought information from ICANN on their revenue streams by sending them a second request under their Documentary Information Disclosure Policy. This request and their response have been described in this blog post.&lt;/b&gt;
        &lt;h2 style="text-align: justify; "&gt;CIS Request&lt;/h2&gt;
&lt;p style="text-align: justify; "&gt;22 July 2015&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;To:&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;Mr. Cherine Chalaby, Chair, Finance Committee of the Board&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;Mr. Xavier Calvez, Chief Financial Officer&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;Mr. Samiran Gupta, ICANN India&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;All other members of Staff involved in accounting and financial tasks&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;span&gt;Sub: Raw data with respect to granular income/revenue statements of ICANN from 1999-2011&lt;/span&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;We  would  like  to  thank  ICAN  for  their  prompt  response  to  our  earlier  requests.  We appreciate that the granular Revenue Details  for FY14  have been  posted online.&lt;a href="#fn1" name="fr1"&gt;[1]&lt;/a&gt; We also appreciate that a similar  document  has  been  posted  for  FY13.&lt;a href="#fn2" name="fr2"&gt;[2] &lt;/a&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;And  we  hope  that  one  for  FY12  would  be  posted soon, as noted by you in your Response to our Request No. 20141222-1.&lt;a href="#fn3" name="fr3"&gt;[3] &lt;/a&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;As also noted by you in the same request, similar reports cannot be prepared for FY99 to  FY11 since “[i]t would be extremely time consuming and overly burdensome to cull through the raw data in order to compile the reports for the prior years”.&lt;a href="#fn4" name="fr4"&gt;[4] &lt;/a&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;Additionally, it was also mentioned that the “relevant information is available in other public available documents”.&lt;a href="#fn5" name="fr5"&gt;[5]&lt;/a&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;Hence, we  would like to request  for the raw  data for years FY99 to FY11, for our research on accountability  and  transparency  mechanisms  in  Internet  governance,  specifically  of  ICANN. Additionally,  we  would  also  like  to  request  for  the links  to  such  public  documents where the information is available.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;We look forward to the receipt of this information within the stipulated period of 30 days. Please feel free to contact us in the event of any doubts regarding our queries. &lt;br /&gt;Thank you very much. &lt;br /&gt;Warm regards, &lt;br /&gt;Aditya Garg,  &lt;br /&gt;I Year, National Law University, Delhi &lt;br /&gt;For Centre for Internet &amp;amp; Society &lt;br /&gt;W: http://cis-india.org&lt;/p&gt;
&lt;h2 style="text-align: justify; "&gt;ICANN Response&lt;/h2&gt;
&lt;p style="text-align: justify; "&gt;ICANN referred to our earlier DIDP request (see &lt;a href="https://www.icann.org/resources/pages/20141222-1-2015-01-22-en"&gt;here&lt;/a&gt;) where we had sought for a detailed report of their granular income and revenue statements from 1999-2014. They refused to disclose the data on grounds that it would be ‘time consuming’ and ‘overly burdensome’, which is a ground for refusal as per their exceptions to disclosure.&lt;/p&gt;
&lt;p&gt;Our request may be found &lt;a href="https://www.icann.org/en/system/files/files/didp-request-20150722-2-redacted-22jul15-en.pdf"&gt;here&lt;/a&gt;, and their response is linked to &lt;a href="https://www.icann.org/en/system/files/files/didp-response-20150722-2-21aug15-en.pdf"&gt;here&lt;/a&gt;.&lt;/p&gt;
&lt;hr /&gt;
&lt;p&gt;[&lt;a href="#fr1" name="fn1"&gt;1&lt;/a&gt;]. See &lt;i&gt;FY14 Revenue Detail By Source&lt;/i&gt;, https://www.icann.org/en/system/files/files/fy2014-revenue-source-01may15-en.pdf.&lt;/p&gt;
&lt;p&gt;[&lt;a href="#fr2" name="fn2"&gt;2&lt;/a&gt;]. See FY13 Revenue Detail By Source, https://www.icann.org/en/system/files/files/fy2013-revenue-source-01may15-en.pdf&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;[&lt;a href="#fr3" name="fn3"&gt;3&lt;/a&gt;]. See &lt;i&gt;Response to Documentary Information Disclosure Policy Request No. 20141222-1&lt;/i&gt;, https://www.icann.org/en/system/files/files/cis-response-21jan15-en.pdf.&lt;/p&gt;
&lt;p&gt;[&lt;a href="#fr4" name="fn4"&gt;4&lt;/a&gt;]. &lt;i&gt;Id&lt;/i&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;[&lt;a href="#fr5" name="fn5"&gt;5&lt;/a&gt;]. See &lt;i&gt;Response to Documentary Information Disclosure Policy Request No. 20141222-1&lt;/i&gt;, https://www.icann.org/en/system/files/files/cis-response-21jan15-en.pdf.&lt;/p&gt;
        &lt;p&gt;
        For more details visit &lt;a href='https://cis-india.org/internet-governance/blog/didp-request-12-revenues'&gt;https://cis-india.org/internet-governance/blog/didp-request-12-revenues&lt;/a&gt;
        &lt;/p&gt;
    </description>
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>Aditya Garg</dc:creator>
    <dc:rights></dc:rights>

    
        <dc:subject>ICANN</dc:subject>
    
    
        <dc:subject>Internet Governance</dc:subject>
    

   <dc:date>2015-09-14T15:32:37Z</dc:date>
   <dc:type>Blog Entry</dc:type>
   </item>


    <item rdf:about="https://cis-india.org/internet-governance/blog/didp-request-11-netmundial-principles">
    <title>DIDP Request #11: NETmundial Principles</title>
    <link>https://cis-india.org/internet-governance/blog/didp-request-11-netmundial-principles</link>
    <description>
        &lt;b&gt;The Centre for Internet &amp; Society (CIS) followed up on the implementation of the NETmundial Principles that ICANN has been endorsing by sending them a second request under their Documentary Information Disclosure Policy. This request and their response have been described in this blog post. &lt;/b&gt;
        &lt;p style="text-align: justify; "&gt;22 July 2015&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;To:&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;Mr. Fadi Chehade, CEO and President&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;Mr. Steve Crocker, Chairman of the Board&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;Mr. Cherine Chalaby, Chair, Finance Committee of the Board&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;Mr. Xavier Calvez, Chief Financial Officer&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;span&gt;Sub: Details of documents within ICANN regarding implementation of NETmundial Principles and documents modified within ICANN as a result of the same&lt;/span&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;It  is  our  understanding  that  ICANN  is  one  of  the founding  members  of  the  NETmundial Initiative. And hence, it has been credited in the public forum for championing the Initiative.&lt;a href="#fn1" name="fr1"&gt;[1] &lt;/a&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;Mr.  Fadi  Chehade,  CEO  and  President  of  ICANN,  has  maintained  that  it  is  time  for  the  global community to act and implement the Principles set forth in the initiative.&lt;a href="#fn2" name="fr2"&gt;[2]&lt;/a&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;ICANN itself, in response to one of our earlier requests, has acknowledged that "NETmundial Principles are high-level statements that permeate through the work of any entity –particularly a multistakeholder entity like ICANN."&lt;a href="#fn3" name="fr3"&gt;[3] &lt;/a&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;We,  therefore,  request  for  all  existing  documents  within  ICANN  which  represent  its  efforts  to implement  the  NETmundial  Principles  within  its  working.  Additionally, we would  also  want  to request  for  all  the  documents  which  were  modified  as  the  result  of  ICANN’s support of the NETmundial Initiave, highlighting the modification so made.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;We look forward to the receipt of this information within the stipulated period of 30 days. Please feel free to contact us in the event of any doubts regarding our queries.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;Thank you very much.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;Warm regards,&lt;br /&gt;Aditya Garg,&lt;br /&gt;1st Year, National Law University, Delhi for Centre for Internet &amp;amp; Society&lt;/p&gt;
&lt;h2 style="text-align: justify; "&gt;ICANN Response&lt;/h2&gt;
&lt;p style="text-align: justify; "&gt;ICANN in their response pointed to an earlier DIDP request that we had sent in, and they replied along the same lines. They brought to our attention that ICANN was not responsible for the implementation of the NETMundial Principles, despite it being one of the founding members of the Initiative. They reiterated their earlier statement of ICANN not being the “…&lt;i&gt;home for implementation of the NETmundial Principles or the evolution of multistakeholder participation in Internet governance.&lt;/i&gt;”  They have failed to provide us with documentary proof of the implementation of these principles, and have only pointed to statements which indicate a potential prospective adoption of said the initiative &lt;a href="#fn4" name="fr4"&gt;[4]; &lt;/a&gt;the responses have been near identical to those for the earlier DIDP request, which you can find &lt;a href="https://www.icann.org/en/system/files/files/cis-netmundial-response-27jan15-en.pdf"&gt;here&lt;/a&gt;.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;Further, ICANN claims that the information we seek falls within the scope of the exceptions to disclosure they lay down, as it is not within their operational activities, an explanation that fails to satisfy us. As always, they have used the wide scope of their non-disclosure policy to avoid providing us with the requisite information.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;The request can be found &lt;a href="https://www.icann.org/en/system/files/files/didp-request-20150722-1-redacted-22jul15-en.pdf"&gt;here&lt;/a&gt;, and ICANN’s response has been linked &lt;a href="https://www.icann.org/en/system/files/files/didp-response-20150722-1-21aug15-en.pdf"&gt;here&lt;/a&gt;.&lt;/p&gt;
&lt;hr style="text-align: justify; " /&gt;
&lt;p style="text-align: justify; "&gt;[&lt;a href="#fr1" name="fn1"&gt;1&lt;/a&gt;]. See McCarthy, I’m Begging You To Join, The Register (12 December 2014), http://www.theregister.co.uk/2014/12/12/im_begging_you_to_join_netmundial_initiative_gets_desperate/&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;[&lt;a href="#fr2" name="fn2"&gt;2&lt;/a&gt;]. See NETmundial Initiative Goes Live, Gobal Internet Community Invited to Participate (Press Release), https://www.netmundial.org/press-release-1&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;[&lt;a href="#fr3" name="fn3"&gt;3&lt;/a&gt;]. See Response to Documentary Information Disclosure Policy Request No. 20141228-1-NETmundial, https://www.icann.org/en/system/files/files/cis-netmundial-response-27jan15-en.pdf&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;[&lt;a href="#fr4" name="fn4"&gt;4&lt;/a&gt;]. Such as Objective 4.3 of their Strategic Five Year Plan. “&lt;i&gt;Demonstrate leadership by implementing best practices in multistakeholder mechanisms within the distributed Internet governance ecosystem while encouraging all stakeholders to implement the principles endorsed at NETmundial&lt;/i&gt;” at https://www.icann.org/en/system/files/files/strategic-plan-2016-2020-10oct14-en.pdf&lt;/p&gt;
        &lt;p&gt;
        For more details visit &lt;a href='https://cis-india.org/internet-governance/blog/didp-request-11-netmundial-principles'&gt;https://cis-india.org/internet-governance/blog/didp-request-11-netmundial-principles&lt;/a&gt;
        &lt;/p&gt;
    </description>
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>Aditya Garg</dc:creator>
    <dc:rights></dc:rights>

    
        <dc:subject>ICANN</dc:subject>
    
    
        <dc:subject>Internet Governance</dc:subject>
    

   <dc:date>2015-09-14T15:08:40Z</dc:date>
   <dc:type>Blog Entry</dc:type>
   </item>


    <item rdf:about="https://cis-india.org/internet-governance/blog/didp-request-10-icann-does-not-know-how-much-each-rir-contributes-to-its-budget">
    <title>DIDP Request #10 - ICANN does not know how much each RIR contributes to its Budget</title>
    <link>https://cis-india.org/internet-governance/blog/didp-request-10-icann-does-not-know-how-much-each-rir-contributes-to-its-budget</link>
    <description>
        &lt;b&gt;In an effort to understand the relationship between the Regional Internet Registries (RIRs) and ICANN, we requested current and historical information on the contract fees paid by the five RIRs (AfriNIC, ARIN, APNIC, LACNIC and RIPE NCC) to ICANN annually.&lt;/b&gt;
        &lt;p style="text-align: justify; "&gt;We acknowledged that the independently audited financial reports on ICANN’s website list the total amount from all RIRs as a lump sum.&lt;a href="#ftn1"&gt;[1] &lt;/a&gt;However, we specifically sought a breakdown of these fees detailing contributions made by each RIR from 1999 to 2014. Not only will this information help understand the RIR-ICANN relationship, it will also be relevant to the IANA transition.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;The request filed by Protyush Choudhury can be found &lt;a class="external-link" href="https://www.icann.org/en/system/files/files/cis-request-06feb15-en.pdf"&gt;here&lt;/a&gt;.&lt;/p&gt;
&lt;h3 style="text-align: justify; "&gt;What ICANN said&lt;/h3&gt;
&lt;p style="text-align: justify; "&gt;According to ICANN’s response to our request, the five RIRs (AfriNIC, ARIN, APNIC, LACNIC and RIPE NCC) make a voluntary annual contribution to ICANN’s budget through the Number Resource Organization (NRO). &lt;a href="#ftn2"&gt;[2] &lt;/a&gt; Since Financial Year 2000, this contribution has been made to ICANN as an aggregate amount without the kind of breakdown requested by us with the exception of FY03, FY04 and FY05. The breakdown of the contribution for those years is as below:&lt;/p&gt;
&lt;ul style="text-align: justify; "&gt;
&lt;li&gt;FY03: APNIC - $129,400; ARIN - $159,345; RIPE - $206,255&lt;/li&gt;
&lt;li&gt;FY04: APNIC - $160,500; ARIN - $144,450; RIPE - $224,700; LACNIC - $5,350&lt;/li&gt;
&lt;li&gt;FY05: APNIC - $220,976; ARIN - $218,507; RIPE - $358,086; LACNIC - $25,431&lt;/li&gt;
&lt;/ul&gt;
&lt;p style="text-align: justify; "&gt;The response links back to the independent financial reports mentioned by us in the request. &lt;span id="docs-internal-guid-ca5a7bda-2a44-cdfd-627f-3534a44a9ae4"&gt;These reports can be found on the ICANN website &lt;/span&gt;&lt;a href="https://www.icann.org/resources/pages/governance/current-en"&gt;&lt;span&gt;here&lt;/span&gt;&lt;/a&gt;&lt;span&gt;.&lt;/span&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;span&gt;On closer examination of the audit reports of FY03, 04 and 05, it is clear that the information provided in their response is either incomplete or incorrect. According to KPMG’s audit report of FY03, the total contribution from Address Registries is US$535,000. The breakdown in the response adds up only to $494,600. The response does not account for the extra $40,400. If only APNIC, ARIN and RIPE contributed to ICANN in 2003, where did the other $40,400 come from? Moreover, why is it listed as an Address Registry Fee in the audit report if it was a voluntary contribution?&lt;/span&gt;&lt;a href="#ftn3"&gt;[3]&lt;/a&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;The “Address Registry Fees” in the audit reports for FY04 and FY05 match the amounts in the response: $535,000 and $823,00 respectively. &lt;span id="docs-internal-guid-ca5a7bda-2a48-4c9a-4b9e-1793f74078dd"&gt;ICANN's response to our DIDP request may be found &lt;/span&gt;&lt;a href="https://www.icann.org/en/system/files/files/cis-response-08mar15-en.pdf"&gt;&lt;span&gt;here&lt;/span&gt;&lt;/a&gt;&lt;span&gt;.&lt;/span&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;span&gt;For the reader’s reference, the audit reports for FY00 - FY14 are linked below:&lt;/span&gt;&lt;/p&gt;
&lt;ul style="text-align: justify; "&gt;
&lt;li&gt;&lt;span&gt;FY00: &lt;/span&gt;&lt;a href="https://www.icann.org/resources/unthemed-pages/financial-report-fye-2000-06-30-en"&gt;&lt;span&gt;https://www.icann.org/resources/unthemed-pages/financial-report-fye-2000-06-30-en &lt;/span&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;FY01: &lt;/span&gt;&lt;a href="https://www.icann.org/resources/unthemed-pages/financial-report-fye-2001-06-30-en"&gt;&lt;span&gt;https://www.icann.org/resources/unthemed-pages/financial-report-fye-2001-06-30-en&lt;/span&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;FY02:&lt;/span&gt;&lt;a href="https://www.icann.org/resources/unthemed-pages/financial-report-fye-2002-06-30-en"&gt;&lt;span&gt; &lt;/span&gt;&lt;span&gt;https://www.icann.org/resources/unthemed-pages/financial-report-fye-2002-06-30-en&lt;/span&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;FY03: &lt;/span&gt;&lt;a href="https://www.icann.org/en/system/files/files/financial-report-fye-30jun03-en.pdf"&gt;&lt;span&gt;https://www.icann.org/en/system/files/files/financial-report-fye-30jun03-en.pdf&lt;/span&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;FY04: &lt;/span&gt;&lt;a href="https://www.icann.org/en/system/files/files/financial-report-fye-30jun04-en.pdf"&gt;&lt;span&gt;https://www.icann.org/en/system/files/files/financial-report-fye-30jun04-en.pdf&lt;/span&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;FY05: &lt;/span&gt;&lt;a href="https://www.icann.org/en/system/files/files/financial-report-fye-30jun05-en.pdf"&gt;&lt;span&gt;https://www.icann.org/en/system/files/files/financial-report-fye-30jun05-en.pdf&lt;/span&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;FY06: &lt;/span&gt;&lt;a href="https://www.icann.org/en/system/files/files/financial-report-fye-30jun06-en.pdf"&gt;&lt;span&gt;https://www.icann.org/en/system/files/files/financial-report-fye-30jun06-en.pdf&lt;/span&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;FY07: &lt;/span&gt;&lt;a href="https://www.icann.org/en/system/files/files/financial-report-fye-30jun07-en.pdf"&gt;&lt;span&gt;https://www.icann.org/en/system/files/files/financial-report-fye-30jun07-en.pdf&lt;/span&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;FY08: &lt;/span&gt;&lt;a href="https://www.icann.org/en/system/files/files/financial-report-fye-30jun07-en.pdf"&gt;&lt;span&gt;https://www.icann.org/en/system/files/files/financial-report-fye-30jun08-en.pdf&lt;/span&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;FY09: &lt;/span&gt;&lt;a href="https://www.icann.org/en/system/files/files/financial-report-fye-30jun09-en.pdf"&gt;&lt;span&gt;https://www.icann.org/en/system/files/files/financial-report-fye-30jun09-en.pdf&lt;/span&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;FY10:&lt;/span&gt;&lt;a href="https://www.icann.org/en/system/files/files/financial-report-fye-30jun10-en.pdf"&gt;&lt;span&gt; https://www.icann.org/en/system/files/files/financial-report-fye-30jun10-en.pdf&lt;/span&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;FY11: &lt;/span&gt;&lt;a href="https://www.icann.org/en/system/files/files/financial-report-fye-30jun11-en.pdf"&gt;&lt;span&gt;https://www.icann.org/en/system/files/files/financial-report-fye-30jun11-en.pdf&lt;/span&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;FY12: &lt;/span&gt;&lt;a href="https://www.icann.org/en/system/files/files/financial-report-fye-30jun12-en.pdf"&gt;&lt;span&gt;https://www.icann.org/en/system/files/files/financial-report-fye-30jun12-en.pdf&lt;/span&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;FY13:&lt;/span&gt;&lt;a href="https://www.icann.org/en/system/files/files/financial-report-fye-30jun13-en.pdf"&gt;&lt;span&gt; https://www.icann.org/en/system/files/files/financial-report-fye-30jun13-en.pdf&lt;/span&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt; &lt;span&gt;FY14: &lt;/span&gt;&lt;a href="https://www.icann.org/en/system/files/files/financial-report-fye-30jun14-en.pdf"&gt;&lt;span&gt;https://www.icann.org/en/system/files/files/financial-report-fye-30jun14-en.pdf&lt;/span&gt;&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;hr style="text-align: justify; " /&gt;
&lt;p style="text-align: justify; "&gt;&lt;a name="ftn1"&gt;[1] &lt;/a&gt;&lt;span id="docs-internal-guid-ca5a7bda-2a4b-7429-43b1-6785f6f611ea"&gt;See audited financial reports: &lt;/span&gt;&lt;a href="https://www.icann.org/resources/pages/governance/current-en"&gt;&lt;span&gt;https://www.icann.org/resources/pages/governance/current-en&lt;/span&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;a name="ftn2"&gt;[2] &lt;/a&gt;&lt;span id="docs-internal-guid-ca5a7bda-2a4b-2ee6-07b6-012828ea134f"&gt;See letter from NRO to ICANN:&lt;/span&gt;&lt;a href="https://www.icann.org/en/system/files/files/akplogan-to-twomey-23mar09-en.pdf"&gt;&lt;span&gt; &lt;/span&gt;&lt;span&gt;https://www.icann.org/en/system/files/files/akplogan-to-twomey-23mar09-en.pdf&lt;/span&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p dir="ltr" id="docs-internal-guid-ca5a7bda-2a4a-bcc8-755d-d325f935f7e4" style="text-align: justify; "&gt;&lt;a name="ftn3"&gt;[3]. &lt;/a&gt;&lt;span&gt;See report for FY03 (pg 4): &lt;/span&gt;&lt;a href="https://www.icann.org/en/system/files/files/financial-report-fye-30jun03-en.pdf"&gt;&lt;span&gt;https://www.icann.org/en/system/files/files/financial-report-fye-30jun03-en.pdf&lt;/span&gt;&lt;/a&gt;&lt;span&gt; &lt;/span&gt;&lt;/p&gt;
        &lt;p&gt;
        For more details visit &lt;a href='https://cis-india.org/internet-governance/blog/didp-request-10-icann-does-not-know-how-much-each-rir-contributes-to-its-budget'&gt;https://cis-india.org/internet-governance/blog/didp-request-10-icann-does-not-know-how-much-each-rir-contributes-to-its-budget&lt;/a&gt;
        &lt;/p&gt;
    </description>
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>asvatha</dc:creator>
    <dc:rights></dc:rights>

    
        <dc:subject>ICANN</dc:subject>
    
    
        <dc:subject>DIDP</dc:subject>
    
    
        <dc:subject>Internet Governance</dc:subject>
    

   <dc:date>2016-07-27T14:57:00Z</dc:date>
   <dc:type>Blog Entry</dc:type>
   </item>


    <item rdf:about="https://cis-india.org/internet-governance/blog/didp-request-9-exactly-how-involved-is-icann-in-the-netmundial-initiative">
    <title>DIDP Request #9 - Exactly how involved is ICANN in the NETmundial Initiative?</title>
    <link>https://cis-india.org/internet-governance/blog/didp-request-9-exactly-how-involved-is-icann-in-the-netmundial-initiative</link>
    <description>
        &lt;b&gt;The importance and relevance of knowing ICANN’s involvement in the NETmundial Initiative cannot be overstated.&lt;/b&gt;
        &lt;p style="text-align: justify; "&gt;It was reported recently that ICANN contributed US$200,000 to the Initiative.&lt;a href="#ftn1"&gt;[1] &lt;/a&gt;Following this report, we requested the details of all expenses incurred by ICANN for NMI till date. This includes formal contributions to NMI as well as costs incurred towards travel and accommodation of ICANN board and staff to meetings relevant to the NMI discussion.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;Apart from these financial details, we also requested information regarding the number of staff working on NMI from ICANN and the hours clocked by them for the same. We further specified that we would like this information to gauge ICANN’s involvement beyond its technical mandate. &lt;span id="docs-internal-guid-fb3cc834-2cf9-6ca2-744a-a463d372cec8"&gt;The request filed by &lt;/span&gt;&lt;span&gt;Geetha Hariharan&lt;/span&gt;&lt;span&gt; can be found &lt;/span&gt;&lt;a href="https://www.icann.org/en/system/files/files/cis-request-13jan15-en.pdf"&gt;&lt;span&gt;here&lt;/span&gt;&lt;/a&gt;&lt;span&gt;.&lt;/span&gt;&lt;/p&gt;
&lt;h3 style="text-align: justify; "&gt;&lt;span&gt;What ICANN said&lt;/span&gt;&lt;/h3&gt;
&lt;p style="text-align: justify; "&gt;&lt;span&gt;In its response, ICANN separated the questions in the request into two categories: a) Expenses incurred by ICANN towards the NETmundial Initiative and b) Other resources (personnel and hours) allocated to the Initiative by ICANN. The first category in the request includes: formal contribution to the NETmundial Initiative; travel costs of ICANN board and staff; and costs of maintenance of other sponsored parties. The second includes the number of staff involved in the NETmundial Initiative from ICANN and the number of hours spent working on it.&lt;/span&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;span&gt;To answer both, the response directs us to the Memorandum of Collaboration (MOC)&lt;a href="#ftn2"&gt;[2]&lt;/a&gt;&lt;span id="docs-internal-guid-fb3cc834-2cff-6122-a30e-e27cf1377dd2"&gt;signed by the Brazilian Internet Steering Committee (&lt;/span&gt;&lt;a href="http://cgi.br"&gt;&lt;span&gt;CGI.br&lt;/span&gt;&lt;/a&gt;&lt;span&gt;), ICANN and the World Economic Forum (WEF) to set up the NETmundial Initiative according to the outcome document from the initial NETmundial meeting in Sao Paulo, Brazil. &lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;span&gt;&lt;span&gt;Some of the important takeaways from the MOC that are relevant to our request are the following:&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;ul style="text-align: justify; "&gt;
&lt;li&gt;&lt;span&gt;&lt;span&gt;Each party to the MOC agrees to pay $201,667 towards operational expenses on signature of the agreement.&lt;/span&gt;&lt;/span&gt;&lt;span&gt;&lt;span&gt; &lt;/span&gt;&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;&lt;span&gt;Total anticipated cost of the NETmundial Initiative is $605,000 (also mentioned in the response).&lt;/span&gt;&lt;/span&gt;&lt;span&gt;&lt;span&gt; &lt;/span&gt;&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;&lt;span&gt;Each party will assign 1 staff member to the NETmundial Initiative secretariat during the inaugural period to smoothen the process. This staff member will commit at least 50% of their time towards Secretariat work.&lt;/span&gt;&lt;/span&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p style="text-align: justify; "&gt;&lt;span&gt;&lt;span&gt;This information is important but it does not provide a comprehensive answer to our query. It does not, for example, answer if ICANN contributed anything more than the $201,667 the MOC specifies. It also does not tell us if ICANN allotted any staff apart from the designated secretariat member to work on NETmundial Initiative.&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;span&gt;&lt;span&gt;Further, the response states that ICANN does not keep track of costs according to the number of hours or the topic but rather according to strategic objectives. Since ICANN is not required to create a document that does not already exist to answer a DIDP enquiry,&lt;a href="#ftn3"&gt;[3] &lt;/a&gt;we have no way of knowing the specific amount of  time or money spent on the NETmundial Initiative by ICANN. The response instead directs us to the financial presentation at ICANN50 where the costs of attending the NETmundial Meeting at Sao Paulo is detailed. While this is interesting (ICANN spent $1.5 million)&lt;a href="#ftn4"&gt;[4] &lt;/a&gt;&lt;/span&gt;&lt;/span&gt;it is not a satisfactory answer to our question.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;ICANN justifies its lack of direct answers by expressing that not only is the request “overbroad", it is also “subject to the following DIDP Condition of Nondisclosure: Information requests: (i) which are not reasonable; (ii) which are excessive or overly burdensome; and (iii) complying with which is not feasible.”&lt;a href="#ftn5"&gt;[5] &lt;/a&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;span id="docs-internal-guid-fb3cc834-2d0e-b79e-fcb8-784e3a998046"&gt;ICANN's response to our DIDP request may be found &lt;/span&gt;&lt;a href="https://www.icann.org/en/system/files/files/cis-response-12feb15-en.pdf"&gt;&lt;span&gt;here&lt;/span&gt;&lt;/a&gt;&lt;span&gt;.&lt;/span&gt;&lt;/p&gt;
&lt;hr style="text-align: justify; " /&gt;
&lt;p style="text-align: justify; "&gt;&lt;a name="ftn1"&gt;[1] &lt;/a&gt;&lt;span id="docs-internal-guid-fb3cc834-2d0d-0c56-8105-394e1c8d2cac"&gt;See McCarthy, &lt;/span&gt;&lt;span&gt;‘I’m Begging You To Join’ – ICANN’s NETmundial Initiative gets desperate&lt;/span&gt;&lt;span&gt;, THE REGISTER (12 December 2014), &lt;/span&gt;&lt;span&gt;http://www.theregister.co.uk/2014/12/12/im begging you to join netmundial initiative gets d esperate/&lt;/span&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;a name="ftn2"&gt;[2] &lt;/a&gt;See MOC: https://www.netmundial.org/sites/default/files/MOC-%20CGI.br,%20ICANN%20&amp;amp;%20WEF.pdf&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;a name="ftn3"&gt;[3] &lt;/a&gt;&lt;span id="docs-internal-guid-fb3cc834-2d0b-01ff-7d33-5afd3d4e7aec"&gt;See Disclosure Policy: https://www.icann.org/resources/pages/didp-2012-02-25-en&lt;/span&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;a name="ftn4"&gt;[4] &lt;/a&gt;See ICANN50 Finance Presentation (Pg 4): https://london50.icann.org/en/schedule/thu-finance/presentation-finance-26jun14-en&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;a name="ftn5"&gt;[5] &lt;/a&gt;See ICANN conditions for non-disclosure: https://www.icann.org/resources/pages/didp-2012-02-25-en&lt;/p&gt;
        &lt;p&gt;
        For more details visit &lt;a href='https://cis-india.org/internet-governance/blog/didp-request-9-exactly-how-involved-is-icann-in-the-netmundial-initiative'&gt;https://cis-india.org/internet-governance/blog/didp-request-9-exactly-how-involved-is-icann-in-the-netmundial-initiative&lt;/a&gt;
        &lt;/p&gt;
    </description>
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>asvatha</dc:creator>
    <dc:rights></dc:rights>

    
        <dc:subject>ICANN</dc:subject>
    
    
        <dc:subject>DIDP</dc:subject>
    
    
        <dc:subject>Internet Governance</dc:subject>
    

   <dc:date>2016-07-27T15:53:22Z</dc:date>
   <dc:type>Blog Entry</dc:type>
   </item>


    <item rdf:about="https://cis-india.org/internet-governance/blog/didp-34-on-granular-detail-on-icanns-budget-for-policy-development-process">
    <title>DIDP #34 On granular detail on ICANN's budget for policy development process </title>
    <link>https://cis-india.org/internet-governance/blog/didp-34-on-granular-detail-on-icanns-budget-for-policy-development-process</link>
    <description>
        &lt;b&gt;ICANN has Advisory Committees which help guide the policy recommendations that the ICANN community develops while its Supporting Organizations are charged with developing policy recommendations for a particular aspect of ICANN's operations. Supporting Organizations are composed of volunteers from the community. ICANN publishes a combined budget for all these bodies under the head of policy development and CIS inquired about the financial resources allocated to each of them specifically. &lt;/b&gt;
        &lt;p style="text-align: justify; "&gt;The ICANN budgets are published for public comment yet the  community does not have supporting documents to illustrate how the  numbers were estimated or the rationale for allocation of the resources.  There is a lack of transparency when it comes to the internal budgeting.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;This DIDP is concerned with the policy development budget which, as  Stephanie Perrin of the Non-Commercial Stakeholder Group pointed out,  was merely 5% of ICANN’s total budget, a number significantly low for a  policy making organization. Thus, the information we request is a  detailed breakdown for the budgets for every Advisory Council as well as  Supporting Organizations for the previous fiscal year. You can find the  &lt;a class="external-link" href="http://cis-india.org/internet-governance/files/didp-on-budget/"&gt;attached request here&lt;/a&gt;.&lt;/p&gt;
        &lt;p&gt;
        For more details visit &lt;a href='https://cis-india.org/internet-governance/blog/didp-34-on-granular-detail-on-icanns-budget-for-policy-development-process'&gt;https://cis-india.org/internet-governance/blog/didp-34-on-granular-detail-on-icanns-budget-for-policy-development-process&lt;/a&gt;
        &lt;/p&gt;
    </description>
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>akriti</dc:creator>
    <dc:rights></dc:rights>

    
        <dc:subject>ICANN</dc:subject>
    
    
        <dc:subject>DIDP</dc:subject>
    
    
        <dc:subject>Internet Governance</dc:subject>
    

   <dc:date>2019-07-06T01:23:55Z</dc:date>
   <dc:type>Blog Entry</dc:type>
   </item>


    <item rdf:about="https://cis-india.org/internet-governance/blog/akriti-bopanna-april-4-2019-didp-33-on-icann-s-2012-gtld-round-auction-fund">
    <title>DIDP #33 On ICANN's 2012 gTLD round auction fund </title>
    <link>https://cis-india.org/internet-governance/blog/akriti-bopanna-april-4-2019-didp-33-on-icann-s-2012-gtld-round-auction-fund</link>
    <description>
        &lt;b&gt;This DIDP was filed to inquire about the state of the funds ICANN received from the last gTLD auctions.
&lt;/b&gt;
        &lt;p style="text-align: justify; "&gt;In 2012, after years of deliberation ICANN opened the application  round for new top level domains and saw over 1930 applications. Since  October 2013, delegation of these extensions commenced with it still  going on. However, 7 years since the round was open there has been no  consensus on how to utilize the funds obtained from the auctions. ICANN  until its last meeting was debating on the legal mechanisms/ entities to  be created who will decide on the disbursement of these funds. There is  no clear information on how those funds have been maintained over the  years or its treatments in terms of whether they have been set aside or  invested etc. Thus, our DIDP questions ICANN on the status of these  funds and can be &lt;a class="external-link" href="http://cis-india.org/internet-governance/files/didp-33"&gt;found here&lt;/a&gt;.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;span&gt;The response         to the DIDP received on 24th April, 2019 states that that even         though the request asked for information,         rather than documentation, our question was answered.         Reiterating that the DIDP mechanism         was&lt;/span&gt;&lt;span&gt; developed         to provide documentation rather than information.&lt;/span&gt;&lt;span&gt; &lt;/span&gt;&lt;span&gt;It stated         that on 25 October 2018, Resolution 2018.10.25.23 was passed         that compels the         President and CEO to allocate $36 million to the Reserve Fund.         The gTLD auction         proceeds were allocated to separate investment accounts, and the         interest         accruing from the proceedings was in accordance with the new         gTLD Investment         Policy.&lt;/span&gt;&lt;/p&gt;
        &lt;p&gt;
        For more details visit &lt;a href='https://cis-india.org/internet-governance/blog/akriti-bopanna-april-4-2019-didp-33-on-icann-s-2012-gtld-round-auction-fund'&gt;https://cis-india.org/internet-governance/blog/akriti-bopanna-april-4-2019-didp-33-on-icann-s-2012-gtld-round-auction-fund&lt;/a&gt;
        &lt;/p&gt;
    </description>
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>akriti</dc:creator>
    <dc:rights></dc:rights>

    
        <dc:subject>Freedom of Speech and Expression</dc:subject>
    
    
        <dc:subject>ICANN</dc:subject>
    
    
        <dc:subject>Internet Governance</dc:subject>
    

   <dc:date>2019-07-09T15:51:47Z</dc:date>
   <dc:type>Blog Entry</dc:type>
   </item>


    <item rdf:about="https://cis-india.org/internet-governance/blog/didp-31-on-icanns-fellowship-program">
    <title>DIDP #32 On ICANN's Fellowship Program </title>
    <link>https://cis-india.org/internet-governance/blog/didp-31-on-icanns-fellowship-program</link>
    <description>
        &lt;b&gt;In furtherance of its capacity building functions, ICANN selects Fellows for every public meeting. These are individuals from underserved and underrepresented communities who are trained to become active participants in the ICANN community.&lt;/b&gt;
        
&lt;p style="text-align: justify;"&gt;These fellows are assigned a mentor and receive training on ICANN's various areas of engagement. They are also given travel assistance to attend the meeting. While the process and selection criteria is detailed on their website, CIS had some questions as to the execution of these.&lt;/p&gt;
&lt;p style="text-align: justify;"&gt;Our DIDP questioned the following aspects:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Has any individual received the ICANN Fellowship more than the stated maximum limit of 3 times?&lt;/li&gt;
&lt;li&gt;If so, whose decision and what was the justification given for awarding it the 4th time and any other times after that?&lt;/li&gt;
&lt;li&gt;What countries did any such individuals belong to?&lt;/li&gt;
&lt;li&gt;How many times has the limit of 3 been breached while giving fellowships?&lt;/li&gt;
&lt;li&gt;What recording mechanisms are being used to ensure that awarding of these fellowships is kept track of, stored and updated? Are these public or privately made available anywhere? &lt;/li&gt;&lt;/ol&gt;
&lt;div&gt;You can &lt;a class="external-link" href="http://cis-india.org/internet-governance/files/fellowship-didp"&gt;access the request here&lt;/a&gt;.&lt;/div&gt;

        &lt;p&gt;
        For more details visit &lt;a href='https://cis-india.org/internet-governance/blog/didp-31-on-icanns-fellowship-program'&gt;https://cis-india.org/internet-governance/blog/didp-31-on-icanns-fellowship-program&lt;/a&gt;
        &lt;/p&gt;
    </description>
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>akriti</dc:creator>
    <dc:rights></dc:rights>

    
        <dc:subject>ICANN</dc:subject>
    
    
        <dc:subject>Internet Governance</dc:subject>
    

   <dc:date>2018-11-12T15:58:30Z</dc:date>
   <dc:type>Blog Entry</dc:type>
   </item>




</rdf:RDF>
