<?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/search_rss">
  <title>Centre for Internet and Society</title>
  <link>https://cis-india.org</link>
  
  <description>
    
            These are the search results for the query, showing results 21 to 33.
        
  </description>
  
  
  
  
  <image rdf:resource="https://cis-india.org/logo.png"/>

  <items>
    <rdf:Seq>
        
            <rdf:li rdf:resource="https://cis-india.org/internet-governance/blog/cis-comments-supporting-the-dns-industry-in-underserved-regions"/>
        
        
            <rdf:li rdf:resource="https://cis-india.org/internet-governance/blog/didp-request-1-icanns-expenditures-on-travel-meetings"/>
        
        
            <rdf:li rdf:resource="https://cis-india.org/internet-governance/blog/didp-request-4-icann-and-the-netmundial-principles"/>
        
        
            <rdf:li rdf:resource="https://cis-india.org/internet-governance/blog/didp-request-6-revenues-from-gtld-auctions"/>
        
        
            <rdf:li rdf:resource="https://cis-india.org/a2k/blogs/dipp-response-to-cis-rti-improper-payment-february-2015"/>
        
        
            <rdf:li rdf:resource="https://cis-india.org/a2k/blogs/dipp-response-to-cis-first-rti-february-2015"/>
        
        
            <rdf:li rdf:resource="https://cis-india.org/a2k/blogs/dipp-response-to-cis-second-rti-request-february-2015"/>
        
        
            <rdf:li rdf:resource="https://cis-india.org/a2k/blogs/dipp-response-to-cis-third-rti-request-february-2015"/>
        
        
            <rdf:li rdf:resource="https://cis-india.org/a2k/blogs/national-ipr-policy-series-rti-requests-by-cis-to-dipp-dipp-responses"/>
        
        
            <rdf:li rdf:resource="https://cis-india.org/internet-governance/blog/icann49-public-forum-statement"/>
        
        
            <rdf:li rdf:resource="https://cis-india.org/internet-governance/blog/icann-work-stream-2-recommendations-on-accountability"/>
        
        
            <rdf:li rdf:resource="https://cis-india.org/internet-governance/blog/icann2019s-documentary-information-disclosure-policy-2013-i-didp-basics"/>
        
        
            <rdf:li rdf:resource="https://cis-india.org/accessibility/blog/report-gaad-2017"/>
        
    </rdf:Seq>
  </items>

</channel>


    <item rdf:about="https://cis-india.org/internet-governance/blog/cis-comments-supporting-the-dns-industry-in-underserved-regions">
    <title>Comments to ICANN Supporting the DNS Industry in Underserved Regions  </title>
    <link>https://cis-india.org/internet-governance/blog/cis-comments-supporting-the-dns-industry-in-underserved-regions</link>
    <description>
        &lt;b&gt;Towards exploring ideas and strategies to help promote the domain name industry in regions that have typically been underserved, ICANN published a call for public comments on May 14, 2014. In particular, ICANN sought comments related to existing barriers to Registrar Accreditation and operation and suggestions on how these challenges might be mitigated. CIS contributed to the comments on this report, which will be used to determine next steps to support the domain name industry in underserved regions.&lt;/b&gt;
        &lt;p style="text-align: justify; "&gt;&lt;b&gt; &lt;/b&gt;&lt;b&gt; &lt;/b&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;span&gt;Domain names and the DNS are used in virtually every aspect of the Internet, and without the DNS, the Internet as we know it, would not exist. The DNS root zone has economic value and  ICANN's contract with Verisign delineates the selling of domain names via only ICANN accredited registrars. By the indirect virtue of its control of the root, ICANN has the power and capacity to influence the decisions of entities involved in the management and operations of the DNS, including registrars.&lt;/span&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;b&gt;Too far, too many?&lt;/b&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;We acknowledge some of the efforts for improvements, in particular with reference to barriers to participation in DNS-related business in regions such as Africa and the Middle East, including the creation of a fellowship program, and increased availability of translated materials. However, despite these efforts, the gaps in the distribution of the DNS registrars and registries across the world has become an issue of heightened concern.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;This is particularly true, in light of the distribution of registrars and given that, of the 1124 ICANN-accredited registrars, North America has a total of 765 registrars. US and Canada together, have more than double the number of registrars than the rest of the world taken collectively. To put things further into perspective, of the total number of registrars 725 are from the United States alone, and 7 from the 54 countries of Africa.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;A barrier to ICANN's capacity building initiatives has been the lack of trust, given the general view that, ICANN focuses on policies that favour entrenched incumbents from richer countries. Without adequate representation from poorer countries, and adequate representation from the rest of the world's Internet population, there is no hope of changing these policies or establishing trust. The entire region of Latin America and the Caribbean, comprising of a population of 542.4 million internet users&lt;a href="file:///C:/Users/jyoti/Desktop/Comments%20on%20Supporting%20the%20DNS%20Industry%20in%20Underserved%20Regions.doc#_ftn1"&gt;[1]&lt;/a&gt; in 2012, has only 22 registrars spread across a total of 10 countries. In Europe, covering a population of 518.5 million internet users&lt;a href="file:///C:/Users/jyoti/Desktop/Comments%20on%20Supporting%20the%20DNS%20Industry%20in%20Underserved%20Regions.doc#_ftn2"&gt;[2]&lt;/a&gt;, are 158 registrars and 94 of those are spread across Germany, UK, France, Spain and Netherlands. The figures paint the most dismal picture with respect to South Asia, in particular India, where just 16 registrars cater to the population of internet users that is expected to reach 243 million by June 2014&lt;a href="file:///C:/Users/jyoti/Desktop/Comments%20on%20Supporting%20the%20DNS%20Industry%20in%20Underserved%20Regions.doc#_ftn3"&gt;[3]&lt;/a&gt;.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;While we welcome ICANN's research and outreach initiatives with regard to the DNS ecosystem in underserved regions, without the crucial first step of clarifying the metrics that constitute an underserved region, these efforts might not bear their intended impact. ICANN cannot hope to identify strategies towards bridging the gaps that exist in the DNS  ecosystem, without going beyond the current ICANN community, which, while nominally being 'multistakeholder' and open to all, grossly under-represents those parts of the world that aren't North America and Western Europe.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;The lack of registries in the developing world is another significant issue that needs to be highlighted and addressed. The top 5 gTLD registries are in the USA and it is important that users and the community feels that the fees being collected are equivalent compensation for the services they provide. As registries operate in captive markets that is allocated by ICANN, we invite ICANN to improve its financial accountability, by enabling its stakeholders to assess the finances collected on these registrations.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;b&gt;Multistakeholderism—community and consensus &lt;/b&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;As an organization that holds itself a champion of the bottom-up policy development process, and, as a private corporation fulfilling a public interest function, ICANN, is in a unique position to establish new norms of managing common resources. In theory and under ICANN’s extensive governance rules, the board is a legislative body that is only supposed to approve the consensus decisions of the community and the staff wield executive control. However in reality, both board and the staff have been criticised for decisions that are not backed by the community.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;The formal negotiations between ICANN and Registrar Stakeholder Group Negotiating Team (Registrar NT) over the new Registrar Accreditation Agreement (RAA), is an example of processes that have a multistakeholder approach but fail on values of deliberation and pluralistic decision making.&lt;a href="file:///C:/Users/jyoti/Desktop/Comments%20on%20Supporting%20the%20DNS%20Industry%20in%20Underserved%20Regions.doc#_ftn4"&gt;[4]&lt;/a&gt; ICANN staff insisted on including a "proposed Revocation (or "blow up") Clause that would have given them the ability to unilaterally terminate all registrar accreditations" and another proposal seeking to provide ICANN Board ability to unilaterally amend the RAA (identical to proposal inserted in the gTLD registry agreement - a clause met with strong opposition not only from the Registry Stakeholder Group but from the broader ICANN community).&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;Both proposals undermine the multistakeholder approach of the ICANN governance framework, as they seek more authority for the Board, rather than the community or protections for registrars and more importantly, registrants. The proposed amendments to the RAA were not issues raised by Law Enforcement, GAC or the GNSO but by the ICANN staff and received considerable pushback from the Registrar Stakeholder Group Negotiating Team (Registrar NT). The bottom-up policy making process at ICANN has also been questioned with reference to the ruling on vertical integration between registries and registrars, where the community could not even approach consensus.&lt;a href="file:///C:/Users/jyoti/Desktop/Comments%20on%20Supporting%20the%20DNS%20Industry%20in%20Underserved%20Regions.doc#_ftn5"&gt;[5]&lt;/a&gt; Concerns have also been raised about the extent of the power granted to special advisory bodies handpicked by the ICANN president, the inadequacy of existing accountability mechanisms for providing a meaningful and external check on Board decisions and the lack of representation of underserved regions on these special bodies. ICANN must evolve its accountability mechanisms, to go beyond the opportunity to provide comments on proposed policy, and extend to a role for stakeholders in decision making, which is presently a privilege reserved for staff rather than bottom-up consensus.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;ICANN was created as a consensus based organisation that would enable the Internet, its stakeholders and beneficiaries to move forward in the most streamlined, cohesive manner.&lt;a href="file:///C:/Users/jyoti/Desktop/Comments%20on%20Supporting%20the%20DNS%20Industry%20in%20Underserved%20Regions.doc#_ftn6"&gt;[6]&lt;/a&gt; Through its management of the DNS, ICANN is undertaking public governance duties, and it is crucial that it upholds the democratic values entrenched in the multistakeholder framework. Bottom up policy making extends beyond passive participation and has an impact on the direction of the policy. Presently, while anyone can comment on policy issues, only a few have a say in which comments are integrated towards outcomes and action. We would like to stress not just improving and introducing checks and balances within the ICANN ecosystem, but also, integrating accountability and transparency practices at all levels of decision making.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;b&gt;Bridging the gap&lt;/b&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;We welcome the Africa Strategy working group and the public community process that was initiated by ICANN towards building domain name business industry in Africa, and, we are sure there will be lessons that will applicable to many other underserved regions. In the context of this report CIS, wants to examine the existing criteria of the accreditation process. As ICANN's role evolves and its revenues grow across the DNS and the larger Internet landscape, it is important in our view, that ICANN review and evolve it's processes for accreditation and see if they are as relevant today, as they were when launched.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;The relationship between ICANN and every accredited registrar is governed by the individual RAA, which set out the obligations of both parties, and, we recommend simplifying and improving them. The RAA language is complex, technical and not relevant to all regions and presently, there are no online forms for the accreditation process. While ICANN's language will be English, the present framing has an American bias—we recommend—creating an online application process and simplifying the language keeping it contextual to the region. It would also be helpful, if ICANN invested in introducing some amount of standardization across forms, this would reduce the barrier of time and effort it takes to go through complex legal documents and contribute to the growth of DNS business.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;The existing accreditation process for registrars requires applicants to procure US$70,000 or more for the ICANN accreditation to become effective. The applicants are also required to obtain and maintain for the length of accreditation process, a commercial general liability insurance with a policy limit of US$500,000 or more. The working capital and the insurance are quite high and create a barrier to entrance of underserved regions in the DNS ecosystem.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;With lack of appropriate mechanisms registrars resort to using US companies for insurance, creating more foreign currency pressures on themselves. The commercial general liability insurance requirement for the registrars is not limited to their functioning as a registrar perhaps not the most appropriate option. &lt;span&gt;ICANN should, and must, increase efforts towards helping registrars find suitable insurance providers and scaling down the working capital. Solutions may lie in exploring variable fee structures adjusted against profits, and derived after considering factors such as cost of managing domain names and sub-domain names, expansion needs, ICANN obligations and services, financial capacities of LDCs and financial help pledged to disadvantaged groups or countries.&lt;/span&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;Presently, the start-up capital required is too high for developing countries, and this is reflected in the number of registries in these areas. Any efforts to improve the DNS ecosystem in underserved regions, must tackle this by scaling down the capital in proportion to the requirements of the region.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;Another potential issue that ICANN should consider, is that users getting sub-domain names from local registrars located in their own country, are usually taxed on the transaction, however, online registration through US registrars spares users from paying taxes in their country.&lt;a href="file:///C:/Users/jyoti/Desktop/Comments%20on%20Supporting%20the%20DNS%20Industry%20in%20Underserved%20Regions.doc#_ftn7"&gt;[7]&lt;/a&gt; This could create a reverse incentive for registering domain sub-names online from US registrars. ICANN should push forward on efforts to ensure that registrars are sustainable by providing incentives for registering in underserved regions and help towards maintain critical mass of the registrants. The Business Constituency (BC)—the voice of commercial Internet users within ICANN, could play a role in this and ICANN should endeavour to either, expand the BC function or create a separate constituency for the representation of  underserved regions.&lt;/p&gt;
&lt;hr size="1" style="text-align: justify; " width="33%" /&gt;
&lt;p style="text-align: justify; "&gt;&lt;a href="file:///C:/Users/jyoti/Desktop/Comments%20on%20Supporting%20the%20DNS%20Industry%20in%20Underserved%20Regions.doc#_ftnref1"&gt;[1]&lt;/a&gt; Internet Users and Population stats 2012. http://www.internetworldstats.com/stats2.htm&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;a href="file:///C:/Users/jyoti/Desktop/Comments%20on%20Supporting%20the%20DNS%20Industry%20in%20Underserved%20Regions.doc#_ftnref2"&gt;[2]&lt;/a&gt; Internet Users and Population stats 2012. http://www.internetworldstats.com/stats4.htm&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;a href="file:///C:/Users/jyoti/Desktop/Comments%20on%20Supporting%20the%20DNS%20Industry%20in%20Underserved%20Regions.doc#_ftnref3"&gt;[3]&lt;/a&gt; Times of India IAMAI Report. http://timesofindia.indiatimes.com/tech/tech-news/India-to-have-243-million-internet-users-by-June-2014-IAMAI/articleshow/29563698.cms&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;a href="file:///C:/Users/jyoti/Desktop/Comments%20on%20Supporting%20the%20DNS%20Industry%20in%20Underserved%20Regions.doc#_ftnref4"&gt;[4]&lt;/a&gt; Mar/07/2013 - Registrar Stakeholder Group Negotiating Team (Registrar NT) Statement Regarding ICANN RAA Negotiations.http://www.icannregistrars.org/calendar/announcements.php&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;a href="file:///C:/Users/jyoti/Desktop/Comments%20on%20Supporting%20the%20DNS%20Industry%20in%20Underserved%20Regions.doc#_ftnref5"&gt;[5]&lt;/a&gt; Kevin Murphy, Who runs the internet? An ICANN 49 primer. http://domainincite.com/16177-who-runs-the-internet-an-icann-49-primer&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;a href="file:///C:/Users/jyoti/Desktop/Comments%20on%20Supporting%20the%20DNS%20Industry%20in%20Underserved%20Regions.doc#_ftnref6"&gt;[6]&lt;/a&gt; Stephen Ryan, Governing Cyberspace: ICANN, a Controversial Internet Standards Body http://www.fed-soc.org/publications/detail/governing-cyberspace-icann-a-controversial-internet-standards-body&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;a href="file:///C:/Users/jyoti/Desktop/Comments%20on%20Supporting%20the%20DNS%20Industry%20in%20Underserved%20Regions.doc#_ftnref7"&gt;[7]&lt;/a&gt; Open Root-Financing LDCs in the WSIS process. See: http://www.open-root.eu/about-open-root/news/financing-ldcs-in-the-wsis-process&lt;/p&gt;
        &lt;p&gt;
        For more details visit &lt;a href='https://cis-india.org/internet-governance/blog/cis-comments-supporting-the-dns-industry-in-underserved-regions'&gt;https://cis-india.org/internet-governance/blog/cis-comments-supporting-the-dns-industry-in-underserved-regions&lt;/a&gt;
        &lt;/p&gt;
    </description>
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>jyoti</dc:creator>
    <dc:rights></dc:rights>

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

   <dc:date>2014-07-04T06:48:36Z</dc:date>
   <dc:type>Blog Entry</dc:type>
   </item>


    <item rdf:about="https://cis-india.org/internet-governance/blog/didp-request-1-icanns-expenditures-on-travel-meetings">
    <title>DIDP Request #1: ICANN's Expenditures on "Travel &amp; Meetings"</title>
    <link>https://cis-india.org/internet-governance/blog/didp-request-1-icanns-expenditures-on-travel-meetings</link>
    <description>
        &lt;b&gt;CIS sent ICANN a request under its Documentary Information Disclosure Policy, seeking details of expenditure by ICANN at its Meetings. CIS' request and ICANN's response are detailed below. &lt;/b&gt;
        &lt;h2 style="text-align: justify; "&gt;&lt;/h2&gt;
&lt;h2 style="text-align: justify; "&gt;&lt;/h2&gt;
&lt;h2 style="text-align: justify; "&gt;CIS' Request&lt;/h2&gt;
&lt;p style="text-align: justify; "&gt;&lt;span&gt;18 December 2014&lt;/span&gt;&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: center; "&gt;&lt;strong&gt;Sub: Request for itemized details of expenditure by ICANN at its Meetings&lt;/strong&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;We would like to thank Mr. Calvez and Mr. Gupta for providing information regarding ICANN’s domain name revenues for the fiscal year ending June 30, 2014.&lt;a href="#_ftn1"&gt;[1]&lt;/a&gt; We would like to request further information through the DIDP.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;In the Audited Financial Statements for the fiscal year ended June 30, 2014, the “statements of activities” provides Total Expenses (for ICANN and New gTLD) as USD 124,400,000.&lt;a href="#_ftn2"&gt;[2]&lt;/a&gt; For the fiscal year ended June 30, 2013, the Total Expenses (ICANN and New gTLD) noted is USD 150,362,000.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;According to the statement, this covers expenses for Personnel, Travel and meetings, Professional services and Administration. Quarterly Reports note that the head “Travel and meetings” includes community support requests.&lt;a href="#_ftn3"&gt;[3]&lt;/a&gt; In addition to these heads, Quarterly Reports include “Bad debt expenses” and “Depreciation expenses”. The manner of accounting for these is explained in &lt;span&gt;Note 2&lt;/span&gt; to the Notes to Financial Statements.&lt;a href="#_ftn4"&gt;[4]&lt;/a&gt; Note 2 explains that the expenses statement is prepared by “functional allocation of expenses” to identifiable programs or support services, or otherwise by methods determined by the management.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;For the purposes of our research into normative and practised transparency and accountability in Internet governance, we request, to begin with, &lt;i&gt;current and historical&lt;/i&gt; information regarding itemized, detailed expenses under the head “Travel and meetings”. We request this information from 1999 till 2014. We request that such information be categorized and sub-categorised as follows:&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;Total and Individual Expenses for each meeting (categorised by meeting and year):&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;span&gt;1. Total and individual expenses for ICANN staff (differentiated by department and name of each individual attending the event, including dates/duration of attendance);&lt;/span&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;-    Also broken down into each individual expense (flights, accommodation, per diem or separate local transport, food and other expenses).&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;-    Each ICANN staff member who attended the event to be named.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;2. &lt;span&gt;Total and individual expenses for members of ICANN Board (listed by each Board member and dates/duration of attendance);&lt;/span&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;-    Broken down into each individual expense (flights, accommodation, per diem or separate local transport, food and other expenses).&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;-    Each Board member to be named.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;span&gt;3. Total and individual expenses for members of ICANN constituencies (ALAC, ATRT, ccNSO, GAC, GNSO, etc.)&lt;/span&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;-    Broken down into each individual expense (flights, accommodation, per diem or separate local transport, food and other expenses).&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;-    Each attendee for whom ICANN covered expenses to be named.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;span&gt;4. Total and individual expenses for ICANN fellows&lt;/span&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;-    Broken down into each individual expense (flights, accommodation, per diem or separate local transport, food and other expenses).&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;-    Each attendee for whom ICANN covered expenses to be named, including their region and stakeholder affiliation.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;5. &lt;span&gt;Total and individual expenses incurred for any other ICANN affiliate or liaison (ISOC, IETF, IAB, etc.)&lt;/span&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;-    Broken down into each individual expense (flights, accommodation, per diem or separate local transport, food and other expenses).&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;-    Each attendee for whom ICANN covered expenses to be named, including their affiliation.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;6. &lt;span&gt;Total and individual expenses incurred for any other person, whether or not directly affiliated with ICANN&lt;/span&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;-    Broken down into each individual expense (flights, accommodation, per diem or separate local transport, food and other expenses).&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;-    Each attendee for whom ICANN covered expenses to be named, including their affiliation.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;span&gt;Please note that we request the above-detailed information for ICANN meetings, and also other meetings for which ICANN may provide financial support (for instance, CWG-Stewardship or CWG-Accountability). We request, as a preliminary matter, a list of &lt;/span&gt;&lt;i&gt;all meetings&lt;/i&gt;&lt;span&gt; to which ICANN provides and has, in the past, provided financial support (1999-2014).&lt;/span&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;We note that some information of this nature is available in the Travel Support Reports.&lt;a href="#_ftn5"&gt;[5]&lt;/a&gt; However, the Travel Support Reports are available only from 2008 (Cairo meeting), and are not available for ICANN48 to ICANN51. Further, the Travel Support Reports do not exhibit the level of granularity necessary for research and scrutiny. As explained above, we request granular information for all meetings.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;In our view, providing such information will not violate any individual or corporate rights of ICANN, its Staff, Board, Affiliates/Liaisons or any other individual. Public corporations and even private organisations performing public functions may be subjected to or accept an increased level of transparency and accountability. We believe this is of especial importance to ICANN, as it is involved in a process to enhance its accountability, intrinsically related to IANA Stewardship Transition. We expressed similar views in our initial comment to “Enhancing ICANN Accountability”.&lt;a href="#_ftn6"&gt;[6]&lt;/a&gt; Increased transparency from ICANN may also address accountability concerns present across stakeholder-groups both within and outside ICANN.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;We await your favorable response and the requested information within the prescribed time limit. Please do not hesitate to contact us should you require any clarifications.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;Thank you very much.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;span&gt;Warm regards,&lt;/span&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;Geetha Hariharan&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;Centre for Internet &amp;amp; Society&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;W: &lt;a href="http://cis-india.org"&gt;http://cis-india.org&lt;/a&gt;&lt;/p&gt;
&lt;p&gt; &lt;/p&gt;
&lt;h2&gt;ICANN's Response&lt;/h2&gt;
&lt;p&gt;ICANN responded to the above request for information within the stipulated time of 30 days. &lt;strong&gt;&lt;a href="https://www.icann.org/en/system/files/files/cis-response-17jan15-en.pdf"&gt;ICANN’s response is here&lt;/a&gt;&lt;/strong&gt;. A short summary of CIS's request and ICANN's response can be found &lt;a href="https://cis-india.org/internet-governance/blog/table-of-cis-didp-requests/at_download/file"&gt;&lt;strong&gt;in this table (Request S. no. 1)&lt;/strong&gt;&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt; &lt;/p&gt;
&lt;hr align="left" size="1" width="33%" /&gt;
&lt;p&gt;&lt;a href="#_ftnref1"&gt;[1]&lt;/a&gt; See &lt;i&gt;ICANN reveals hitherto undisclosed details of domain names revenues&lt;/i&gt;, &lt;a href="http://cis-india.org/internet-governance/blog/cis-receives-information-on-icanns-revenues-from-domain-names-fy-2014"&gt;http://cis-india.org/internet-governance/blog/cis-receives-information-on-icanns-revenues-from-domain-names-fy-2014&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;a href="#_ftnref2"&gt;[2]&lt;/a&gt; See &lt;i&gt;ICANN Financial Statements As of and For the years ended June 30, 2014 and 2013&lt;/i&gt;, pages 7, 19-20, &lt;a href="https://www.icann.org/en/system/files/files/financial-report-fye-30jun14-en.pdf"&gt;https://www.icann.org/en/system/files/files/financial-report-fye-30jun14-en.pdf&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;a href="#_ftnref3"&gt;[3]&lt;/a&gt; For instance, see &lt;i&gt;ICANN FY14 Financial Package: For the nine months ending March 2014&lt;/i&gt;, pages 2-5, &lt;a href="https://www.icann.org/en/system/files/files/package-fy14-31mar14-en.pdf"&gt;https://www.icann.org/en/system/files/files/package-fy14-31mar14-en.pdf&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;a href="#_ftnref4"&gt;[4]&lt;/a&gt; &lt;i&gt;Supra&lt;/i&gt; note 1, page 14.&lt;/p&gt;
&lt;p&gt;&lt;a href="#_ftnref5"&gt;[5]&lt;/a&gt; See Community Travel Support, &lt;a href="https://www.icann.org/resources/pages/travel-support-2012-02-25-en#reports"&gt;https://www.icann.org/resources/pages/travel-support-2012-02-25-en#reports&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;a href="#_ftnref6"&gt;[6]&lt;/a&gt; See CIS Comments on Enhancing ICANN Accountability, &lt;a href="http://cis-india.org/internet-governance/blog/cis-comments-enhancing-icann-accountability"&gt;http://cis-india.org/internet-governance/blog/cis-comments-enhancing-icann-accountability&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-1-icanns-expenditures-on-travel-meetings'&gt;https://cis-india.org/internet-governance/blog/didp-request-1-icanns-expenditures-on-travel-meetings&lt;/a&gt;
        &lt;/p&gt;
    </description>
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>geetha</dc:creator>
    <dc:rights></dc:rights>

    
        <dc:subject>ICANN</dc:subject>
    
    
        <dc:subject>DIDP</dc:subject>
    
    
        <dc:subject>Transparency</dc:subject>
    
    
        <dc:subject>Accountability</dc:subject>
    

   <dc:date>2015-03-05T08:00:36Z</dc:date>
   <dc:type>Blog Entry</dc:type>
   </item>


    <item rdf:about="https://cis-india.org/internet-governance/blog/didp-request-4-icann-and-the-netmundial-principles">
    <title>DIDP Request #4: ICANN and the NETmundial Principles</title>
    <link>https://cis-india.org/internet-governance/blog/didp-request-4-icann-and-the-netmundial-principles</link>
    <description>
        &lt;b&gt;CIS sent ICANN a request under its Documentary Information Disclosure Policy, seeking details of ICANN's implementation of the NETmundial Principles that it has endorsed widely and publicly. CIS' request and ICANN's response are detailed below.&lt;/b&gt;
        &lt;p style="text-align: justify; "&gt; &lt;/p&gt;
&lt;h3 style="text-align: justify; "&gt;CIS Request&lt;/h3&gt;
&lt;p style="text-align: justify; "&gt;&lt;span&gt;27 December 2014&lt;/span&gt;&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: center; "&gt;&lt;strong&gt;Sub: Details of implementation by and within ICANN of the NETmundial Outcome Document (April ‘14)&lt;/strong&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;span&gt; &lt;/span&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;We express our appreciation at ICANN’s prompt acknowledgement of our previous DIDP request, and await the information. We would, in the meanwhile, request information regarding ICANN’s internal measures to implement the NETmundial Outcome Document.&lt;a href="#_ftn1"&gt;[1]&lt;/a&gt;&lt;span&gt; &lt;/span&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;In a post titled &lt;i&gt;Turning Talk Into Action After NETmundial,&lt;/i&gt;&lt;a href="#_ftn2"&gt;[2]&lt;/a&gt; Mr. Chehade emphasized the imperative to carry forward the NETmundial principles to fruition. In nearly every public statement, Mr. Chehade and other ICANN representatives have spoken in praise and support of NETmundial and its Outcome Document.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;But in the absence of binding value to them, self-regulation and organizational initiatives pave the way to adopt them. There must be concrete action to implement the Principles. In this regard, we request information about mechanisms or any other changes afoot within ICANN, implemented internally in recognition of the NETmundial Principles.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;At the IGF in Istanbul, when CIS’ Sunil Abraham raised this query,&lt;a href="#_ftn3"&gt;[3]&lt;/a&gt; Mr. Chehade responded that mechanisms ought to and will be undertaken jointly and in collaboration with other organisations. However, institutional improvements are intra-organisational as well, and require changes &lt;i&gt;within &lt;/i&gt;ICANN. An example would be the suggestions to strengthen the IGF, increase its term, and provide financial support (some of which are being achieved, though ICANN’s financial contribution to IGFSA is incongruous in comparison to its financial involvement in the NETmundial Initiative).&lt;span&gt; &lt;/span&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;From ICANN, we have seen consistent championing of the controversial NETmundial Initiative,&lt;a href="#_ftn4"&gt;[4]&lt;/a&gt; and contribution to the IGF Support Association.&lt;a href="#_ftn5"&gt;[5]&lt;/a&gt; There are also mechanisms instituted for IANA Stewardship Transition and Enhancing ICANN Accountability,&lt;a href="#_ftn6"&gt;[6]&lt;/a&gt; as responses to the NTIA’s announcement to not renew the IANA functions contract and related concerns of accountability.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;In addition to the above, we would like to know what ICANN has done to implement the NETmundial Principles, internally and proactively.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;We hope that our request will be processed within the stipulated time period of 30 days. Do let us know if you require any clarifications on 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;/p&gt;
&lt;p style="text-align: justify; "&gt;Geetha Hariharan&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;Centre for Internet &amp;amp; Society&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;W: &lt;a href="http://cis-india.org"&gt;http://cis-india.org&lt;/a&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt; &lt;/p&gt;
&lt;h3 style="text-align: justify; "&gt;ICANN Response&lt;/h3&gt;
&lt;p style="text-align: justify; "&gt;ICANN's response to the above request disappointingly linked to the very same blogpost we note in our request, &lt;i&gt;Turning Talk Into Action After NETmundial&lt;/i&gt;. Following this, ICANN points us to their involvement in the NETmundial Initiative. On the question of internal implementation, ICANN's response is defensive, to say the least. "ICANN is not the home for the implementation of the NETmundial Principles", they say. In any event, ICANN defends that it already implements the NETmundial Principles in its functioning, a response that comes as a surprise to us. "&lt;span&gt;Many of the NETmundial Principles are high-level statements that permeate through the &lt;/span&gt;&lt;span&gt;work of any entity – particularly a multistakeholder entity like ICANN – that is interested &lt;/span&gt;&lt;span&gt;in the upholding of the inclusive, multistakeholder process within the Internet governance &lt;/span&gt;&lt;span&gt;framework", notes ICANN's response. Needless to say, ICANN's response falls short of responding to our queries. &lt;/span&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;span&gt;Finally, ICANN notes that our request is beyond the scope of the DIDP, as it does not relate to ICANN's operational activities. Notwithstanding that our query does in fact seek ICANN's operationalisation of the NETmundial Principles, we are now confused as to where to go to seek this information from ICANN. If the DIDP is not the effective transparency tool it is aimed to be, who in ICANN can provide answers to these questions?&lt;/span&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;span&gt;ICANN's response may be &lt;a href="https://www.icann.org/en/system/files/files/cis-netmundial-response-27jan15-en.pdf"&gt;&lt;strong&gt;found here&lt;/strong&gt;&lt;/a&gt;. A short summary of our request and ICANN's response may be found &lt;a href="https://cis-india.org/internet-governance/blog/table-of-cis-didp-requests/at_download/file"&gt;&lt;strong&gt;in this table (Request S. no. 4)&lt;/strong&gt;&lt;/a&gt;.&lt;/span&gt;&lt;/p&gt;
&lt;hr size="1" style="text-align: justify; " width="33%" /&gt;
&lt;p style="text-align: justify; "&gt;&lt;a href="#_ftnref1"&gt;[1]&lt;/a&gt; See &lt;i&gt;NETmundial Multi-stakeholder Statement&lt;/i&gt;, &lt;a href="http://netmundial.br/wp-content/uploads/2014/04/NETmundial-Multistakeholder-Document.pdf"&gt;http://netmundial.br/wp-content/uploads/2014/04/NETmundial-Multistakeholder-Document.pdf&lt;/a&gt;. &lt;i&gt; &lt;/i&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;a href="#_ftnref2"&gt;[2]&lt;/a&gt; See Chehade, &lt;i&gt;Turning Talk Into Action After NETmundial&lt;/i&gt;, &lt;a href="http://blog.icann.org/2014/05/turning-talk-into-action-after-netmundial/"&gt;http://blog.icann.org/2014/05/turning-talk-into-action-after-netmundial/&lt;/a&gt;.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;a href="#_ftnref3"&gt;[3]&lt;/a&gt; See &lt;i&gt;ICANN Open Forum&lt;/i&gt;, 9&lt;sup&gt;th&lt;/sup&gt; IGF 2014 (Istanbul, Turkey), &lt;a href="https://www.youtube.com/watch?v=Cio31nsqK_A"&gt;https://www.youtube.com/watch?v=Cio31nsqK_A&lt;/a&gt;.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;a href="#_ftnref4"&gt;[4]&lt;/a&gt; See McCarthy, &lt;i&gt;I’m Begging You To Join&lt;/i&gt;, The Register (12 December 2014), &lt;a href="http://www.theregister.co.uk/2014/12/12/im_begging_you_to_join_netmundial_initiative_gets_desperate/"&gt;http://www.theregister.co.uk/2014/12/12/im_begging_you_to_join_netmundial_initiative_gets_desperate/&lt;/a&gt;.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;a href="#_ftnref5"&gt;[5]&lt;/a&gt; See &lt;i&gt;ICANN Donates $50k to Internet Governance Forum Support Association&lt;/i&gt;, &lt;a href="https://www.icann.org/resources/press-material/release-2014-12-18-en"&gt;https://www.icann.org/resources/press-material/release-2014-12-18-en&lt;/a&gt;.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;a href="#_ftnref6"&gt;[6]&lt;/a&gt; See &lt;i&gt;NTIA IANA Functions’ Stewardship Transition &amp;amp; Enhancing ICANN Accountability Processes&lt;/i&gt;, &lt;a href="https://www.icann.org/stewardship-accountability"&gt;https://www.icann.org/stewardship-accountability&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-4-icann-and-the-netmundial-principles'&gt;https://cis-india.org/internet-governance/blog/didp-request-4-icann-and-the-netmundial-principles&lt;/a&gt;
        &lt;/p&gt;
    </description>
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>geetha</dc:creator>
    <dc:rights></dc:rights>

    
        <dc:subject>ICANN</dc:subject>
    
    
        <dc:subject>DIDP</dc:subject>
    
    
        <dc:subject>Transparency</dc:subject>
    
    
        <dc:subject>Accountability</dc:subject>
    

   <dc:date>2015-03-05T08:28:44Z</dc:date>
   <dc:type>Blog Entry</dc:type>
   </item>


    <item rdf:about="https://cis-india.org/internet-governance/blog/didp-request-6-revenues-from-gtld-auctions">
    <title>DIDP Request #6: Revenues from gTLD auctions</title>
    <link>https://cis-india.org/internet-governance/blog/didp-request-6-revenues-from-gtld-auctions</link>
    <description>
        &lt;b&gt;CIS sent ICANN a request under its Documentary Information Disclosure Policy, seeking information regarding revenues received from gTLD auctions. CIS' request and ICANN's response are detailed below.&lt;/b&gt;
        &lt;p style="text-align: justify; "&gt; &lt;/p&gt;
&lt;h2 style="text-align: justify; "&gt;CIS Request&lt;/h2&gt;
&lt;p style="text-align: justify; "&gt;&lt;span&gt;12 January 2015&lt;/span&gt;&lt;span&gt; &lt;/span&gt;&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: center; "&gt;&lt;strong&gt;Sub: Revenues from gTLD auctions&lt;/strong&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;span&gt; &lt;/span&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;It is our understanding that an auction for a Generic Top Level Domain (gTLD) is used as a last-resort mechanism in order to resolve string contention, i.e., when there are groups of applications for same or confusingly similar new gTLDs. As of now, the ICANN website only furnishes information of the winning applicant and the winning price, as regards each new gTLD auction.&lt;a href="#_ftn1"&gt;[1]&lt;/a&gt; We have observed that information regarding the bids from all other applicants is not available. The revenue information provided to us&lt;a href="#_ftn2"&gt;[2]&lt;/a&gt; does not include revenues from new gTLDs.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;In this regard, we request you to provide us with the following information:&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;(i)    How many gTLDs have been sold &lt;i&gt;via&lt;/i&gt; the auction process, since its inception?&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;(ii)   What were the starting and winning bids in the ICANN auctions conducted?&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;(iii) What revenue has ICANN received from the gTLD auctions, since the first ICANN auction was conducted? Please also provide information about the winner (name, corporate information provided to/ available with ICANN).&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;(iv) How are proceeds from the gTLD auction process utilized?&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;span&gt;We believe that this information will give us a framework for understanding the gTLD auction process within ICANN. Furthermore, it will assist us in understanding the manner and purpose for which the proceeds from the auctioning process are utilized, in the broader structure of ICANN transparency and accountability.&lt;/span&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;We hope that our request will be processed within the stipulated time period of 30 days. Do let us know if you require any clarifications on our queries.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;Warm regards,&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;Lakshmi Venkataraman,&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;IV Year, NALSAR University of Law, Hyderabad,&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;i&gt;for &lt;/i&gt;Centre for Internet &amp;amp; Society&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;W: &lt;a href="http://cis-india.org"&gt;http://cis-india.org&lt;/a&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt; &lt;/p&gt;
&lt;h2 style="text-align: justify; "&gt;ICANN Response&lt;/h2&gt;
&lt;p style="text-align: justify; "&gt;ICANN's response to the above query is positive. ICANN states that all information surrounding the auctions is available on the New gTLDs microsite, and on the Auctions page: &lt;span&gt;http://newgtlds.icann.org/en/applicants/auctions. The current status of &lt;/span&gt;&lt;span&gt;auction proceeds and costs are available at &lt;/span&gt;&lt;span&gt;http://newgtlds.icann.org/en/applicants/auctions/proceeds,&lt;/span&gt;&lt;span&gt; and auction results are at &lt;/span&gt;&lt;span&gt;https://gtldresult.icann.org/application-result/applicationstatus/auctionresults. The utilization of proceeds from the auctions is yet to be decided by the ICANN Board:&lt;/span&gt;&lt;span&gt; “[auction] proceeds will be reserved and earmarked until the Board determines a plan for the appropriate use of the funds through consultation with the community. Auction proceeds are net of any Auction costs. Auction costs may include initial set-up costs, auction management fees, and escrow fees.”&lt;/span&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;span style="text-align: justify; "&gt;ICANN's response to our DIDP request may be &lt;a href="https://www.icann.org/en/system/files/files/cis-response-09feb15-en.pdf"&gt;&lt;strong&gt;found here&lt;/strong&gt;&lt;/a&gt;.&lt;/span&gt;&lt;span style="text-align: justify; "&gt; A short summary of our request and ICANN's response may be found &lt;/span&gt;&lt;a href="http://cis-india.org/internet-governance/blog/table-of-cis-didp-requests/at_download/file" style="text-align: justify; "&gt;&lt;strong&gt;in this table (Request S. no. 6)&lt;/strong&gt;&lt;/a&gt;&lt;span style="text-align: justify; "&gt;.&lt;/span&gt;&lt;/p&gt;
&lt;hr size="1" style="text-align: justify; " width="33%" /&gt;
&lt;p style="text-align: justify; "&gt;&lt;a href="#_ftnref1"&gt;[1]&lt;/a&gt; See &lt;i&gt;Auction Results&lt;/i&gt;, &lt;a href="https://gtldresult.icann.org/application-result/applicationstatus/auctionresults"&gt;https://gtldresult.icann.org/application-result/applicationstatus/auctionresults&lt;/a&gt;.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;a href="#_ftnref2"&gt;[2]&lt;/a&gt; See &lt;i&gt;ICANN reveals hitherto undisclosed details of domain names revenues&lt;/i&gt;, &lt;a href="http://cis-india.org/internet-governance/blog/cis-receives-information-on-icanns-revenues-from-domain-names-fy-2014"&gt;http://cis-india.org/internet-governance/blog/cis-receives-information-on-icanns-revenues-from-domain-names-fy-2014&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-6-revenues-from-gtld-auctions'&gt;https://cis-india.org/internet-governance/blog/didp-request-6-revenues-from-gtld-auctions&lt;/a&gt;
        &lt;/p&gt;
    </description>
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>geetha</dc:creator>
    <dc:rights></dc:rights>

    
        <dc:subject>ICANN</dc:subject>
    
    
        <dc:subject>DIDP</dc:subject>
    
    
        <dc:subject>Transparency</dc:subject>
    
    
        <dc:subject>Accountability</dc:subject>
    

   <dc:date>2015-03-10T10:59:37Z</dc:date>
   <dc:type>Blog Entry</dc:type>
   </item>


    <item rdf:about="https://cis-india.org/a2k/blogs/dipp-response-to-cis-rti-improper-payment-february-2015">
    <title>DIPP RESPONSE TO CIS RTI - IMPROPER PAYMENT - FEBRUARY, 2015</title>
    <link>https://cis-india.org/a2k/blogs/dipp-response-to-cis-rti-improper-payment-february-2015</link>
    <description>
        &lt;b&gt;&lt;/b&gt;
        
        &lt;p&gt;
        For more details visit &lt;a href='https://cis-india.org/a2k/blogs/dipp-response-to-cis-rti-improper-payment-february-2015'&gt;https://cis-india.org/a2k/blogs/dipp-response-to-cis-rti-improper-payment-february-2015&lt;/a&gt;
        &lt;/p&gt;
    </description>
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>nehaa</dc:creator>
    <dc:rights></dc:rights>

    
        <dc:subject>Government Information</dc:subject>
    
    
        <dc:subject>Access to Knowledge</dc:subject>
    
    
        <dc:subject>Intellectual Property Rights</dc:subject>
    
    
        <dc:subject>Accountability</dc:subject>
    
    
        <dc:subject>NATIONAL IPR POLICY</dc:subject>
    
    
        <dc:subject>IPR THINK TANK</dc:subject>
    

   <dc:date>2015-04-14T17:35:58Z</dc:date>
   <dc:type>File</dc:type>
   </item>


    <item rdf:about="https://cis-india.org/a2k/blogs/dipp-response-to-cis-first-rti-february-2015">
    <title>DIPP RESPONSE TO CIS (FIRST) RTI - FEBRUARY, 2015</title>
    <link>https://cis-india.org/a2k/blogs/dipp-response-to-cis-first-rti-february-2015</link>
    <description>
        &lt;b&gt;&lt;/b&gt;
        
        &lt;p&gt;
        For more details visit &lt;a href='https://cis-india.org/a2k/blogs/dipp-response-to-cis-first-rti-february-2015'&gt;https://cis-india.org/a2k/blogs/dipp-response-to-cis-first-rti-february-2015&lt;/a&gt;
        &lt;/p&gt;
    </description>
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>nehaa</dc:creator>
    <dc:rights></dc:rights>

    
        <dc:subject>Government Information</dc:subject>
    
    
        <dc:subject>Access to Knowledge</dc:subject>
    
    
        <dc:subject>DIPP</dc:subject>
    
    
        <dc:subject>Intellectual Property Rights</dc:subject>
    
    
        <dc:subject>Accountability</dc:subject>
    
    
        <dc:subject>NATIONAL IPR POLICY</dc:subject>
    
    
        <dc:subject>IPR THINK TANK</dc:subject>
    

   <dc:date>2015-04-14T17:42:43Z</dc:date>
   <dc:type>File</dc:type>
   </item>


    <item rdf:about="https://cis-india.org/a2k/blogs/dipp-response-to-cis-second-rti-request-february-2015">
    <title>DIPP RESPONSE TO CIS (SECOND) RTI REQUEST - FEBRUARY, 2015</title>
    <link>https://cis-india.org/a2k/blogs/dipp-response-to-cis-second-rti-request-february-2015</link>
    <description>
        &lt;b&gt;&lt;/b&gt;
        
        &lt;p&gt;
        For more details visit &lt;a href='https://cis-india.org/a2k/blogs/dipp-response-to-cis-second-rti-request-february-2015'&gt;https://cis-india.org/a2k/blogs/dipp-response-to-cis-second-rti-request-february-2015&lt;/a&gt;
        &lt;/p&gt;
    </description>
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>nehaa</dc:creator>
    <dc:rights></dc:rights>

    
        <dc:subject>Government Information</dc:subject>
    
    
        <dc:subject>Access to Knowledge</dc:subject>
    
    
        <dc:subject>DIPP</dc:subject>
    
    
        <dc:subject>Intellectual Property Rights</dc:subject>
    
    
        <dc:subject>Accountability</dc:subject>
    
    
        <dc:subject>NATIONAL IPR POLICY</dc:subject>
    
    
        <dc:subject>IPR THINK TANK</dc:subject>
    

   <dc:date>2015-04-14T17:58:50Z</dc:date>
   <dc:type>File</dc:type>
   </item>


    <item rdf:about="https://cis-india.org/a2k/blogs/dipp-response-to-cis-third-rti-request-february-2015">
    <title>DIPP RESPONSE TO CIS (THIRD) RTI REQUEST - FEBRUARY, 2015</title>
    <link>https://cis-india.org/a2k/blogs/dipp-response-to-cis-third-rti-request-february-2015</link>
    <description>
        &lt;b&gt;&lt;/b&gt;
        
        &lt;p&gt;
        For more details visit &lt;a href='https://cis-india.org/a2k/blogs/dipp-response-to-cis-third-rti-request-february-2015'&gt;https://cis-india.org/a2k/blogs/dipp-response-to-cis-third-rti-request-february-2015&lt;/a&gt;
        &lt;/p&gt;
    </description>
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>nehaa</dc:creator>
    <dc:rights></dc:rights>

    
        <dc:subject>Government Information</dc:subject>
    
    
        <dc:subject>Access to Knowledge</dc:subject>
    
    
        <dc:subject>DIPP</dc:subject>
    
    
        <dc:subject>Intellectual Property Rights</dc:subject>
    
    
        <dc:subject>Accountability</dc:subject>
    
    
        <dc:subject>NATIONAL IPR POLICY</dc:subject>
    
    
        <dc:subject>IPR THINK TANK</dc:subject>
    

   <dc:date>2015-04-14T18:16:52Z</dc:date>
   <dc:type>File</dc:type>
   </item>


    <item rdf:about="https://cis-india.org/a2k/blogs/national-ipr-policy-series-rti-requests-by-cis-to-dipp-dipp-responses">
    <title>National IPR Policy Series: RTI Requests by CIS to DIPP + DIPP Responses</title>
    <link>https://cis-india.org/a2k/blogs/national-ipr-policy-series-rti-requests-by-cis-to-dipp-dipp-responses</link>
    <description>
        &lt;b&gt;In earlier blog posts, we have discussed the development of India’s National IPR Policy (“the Policy”); comments by the Centre for Internet and Society (“CIS”) to the IPR Think Tank before the release of the first draft of the Policy and CIS’ comments to the IPR Think Tank in response to the first draft of the Policy. Continuing our National IPR Policy Series, this article documents our requests to the Department of Industrial Policy and Promotion (“DIPP” / “the Department”) under the Right to Information (“RTI”) Act, 2005 and the responses of the Department.&lt;/b&gt;
        &lt;p&gt;&lt;a href="https://cis-india.org/a2k/blogs/national-ipr-policy-series-dipp-response.pdf" class="external-link"&gt;View the PDF here&lt;/a&gt;.&lt;/p&gt;
&lt;hr /&gt;
&lt;h3&gt;Details of RTI Requests Filed by CIS&lt;/h3&gt;
&lt;p style="text-align: justify; "&gt;In February, 2015, &lt;a href="http://cis-india.org/a2k/blogs/rti-requests-dipp-details-on-constitution-and-working-of-ipr-think-tank"&gt;CIS had filed three RTI requests&lt;/a&gt; with the DIPP. &lt;a href="https://cis-india.org/a2k/blogs/cis-rti-request-to-dipp-number-1-february-2015/view"&gt;The first request&lt;/a&gt; was four-pronged, seeking information related to &lt;i&gt;first,&lt;/i&gt; the process followed by the Department in the creation of the IPR Think Tank; &lt;i&gt;second, &lt;/i&gt;details and documents of a meeting held to constitute the Think Tank; &lt;i&gt;third, &lt;/i&gt;details and documents of all/multiple meetings held to constitute the Think Tank; &lt;i&gt;fourth&lt;/i&gt;, details of a directive/directives received from any other Government Ministry/authority directing the constitution of the Think Tank and &lt;i&gt;fifth,&lt;/i&gt; the process of shortlisting the members of the Think Tank by the DIPP.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;a href="https://cis-india.org/a2k/blogs/cis-rti-request-to-dipp-number-2-february-2015/view"&gt;In our second RTI request,&lt;/a&gt; &lt;i&gt;first,&lt;/i&gt; we requested details of the process followed by the Think Tank in the formulation of the Policy; &lt;i&gt;second, &lt;/i&gt;we requested all documents relating to a meeting held for the formulation of the Policy; &lt;i&gt;third, &lt;/i&gt;we requested all documents held for multiple meetings for the creation of the Policy and &lt;i&gt;fourth,&lt;/i&gt; we requisitioned all suggestions and comments received by the Think Tank from stakeholders &lt;b&gt;before&lt;/b&gt; the release of the Policy, that is, those suggestions/comments received in November, 2014.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;In our &lt;a href="https://cis-india.org/a2k/blogs/cis-request-to-dipp-3.pdf" class="external-link"&gt;third RTI request&lt;/a&gt;, also filed on also filed in February, 2015, we had asked the DIPP to indicate all suggestions and comments received by the IPR Think Tank from different stakeholders in response to the first draft of the National IPR Policy (to have been submitted on or before January 30, 2015 &lt;a href="http://dipp.nic.in/English/acts_rules/Press_Release/pressRelease_IPR_Policy_30December2014.pdf"&gt;as per DIPP’s Public Notice&lt;/a&gt;).&lt;/p&gt;
&lt;h3 style="text-align: justify; "&gt;Responses by DIPP to CIS' RTI Requests&lt;/h3&gt;
&lt;p style="text-align: justify; "&gt;The DIPP replied to our three RTI requests in multiple stages. At first, &lt;a href="https://cis-india.org/a2k/blogs/dipp-response-improper-payment.pdf" class="external-link"&gt;in a letter dated 12 February, 2015&lt;/a&gt;, we were directed to resubmit our application , seemingly because we hadn’t addressed the Postal Money Order to the correct authority, and were directed to do the same. Funnily enough, we received three other responses – one for each of our RTI requests (the first of these is not dated; the second one is dated 19 February, 2015 and then revised to 26 February, 2015; and the third is also dated 26 February, 2015).&lt;/p&gt;
&lt;h3 style="text-align: justify; "&gt;The First Response: On the Constitution of the Think Tank&lt;/h3&gt;
&lt;p style="text-align: justify; "&gt;In the &lt;a href="https://cis-india.org/a2k/blogs/dipp-response-1.pdf" class="external-link"&gt;first of their responses&lt;/a&gt; to these requests, the Department has grouped our queries into five questions and provided a point-wise response to these questions, as under:&lt;/p&gt;
&lt;ul&gt;
&lt;li style="text-align: justify; "&gt;&lt;b&gt;Please indicate in detail the process followed by the Department of Industrial Policy and Promotion for the constitution for an IPR Think Tank to draft the National Intellectual Property Rights Policy under Public Notice No. 10 (22)/2013 –IPR-III dated November 13, 2014 (sic).&lt;/b&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p style="text-align: justify; "&gt;In its response the Department notes that it convened an &lt;i&gt;interactive meeting on IPR issues&lt;/i&gt; which was chaired by the Minister for Commerce and Industry (Independent Charge), i.e., Ms. Nirmala Sitharaman. As per the Department’s response, this meeting was held on 22 September, 2014 (&lt;b&gt;“the Meeting”&lt;/b&gt;) and was aimed at discussing &lt;i&gt;issues related to IPRs, including finalization of the Terms of Reference for IPR Think-Tank proposed to be established &lt;/i&gt;(sic.) The Department also notes that &lt;i&gt;representatives from various Ministries/Departments, Member of various Expert Committees constituted by the Department, besides IP experts and other Legal Practitioners&lt;/i&gt; (sic) were invited to the meeting. The Department then states that the composition of the Think Tank was decided &lt;i&gt;on the basis of the discussions held in the department after the said interactive Meeting&lt;/i&gt; (sic).&lt;/p&gt;
&lt;ul&gt;
&lt;li style="text-align: justify; "&gt;&lt;b&gt;If there was a meeting held to decide on the same, please include all necessary documents including the minutes of the meeting, records, documents, memos, e-mails, opinion, advices, press releases, circulars, orders etc in which the constitution of the aforesaid mentioned IPR Think Tank was decided (sic).&lt;/b&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p style="text-align: justify; "&gt;The Department has attached the Minutes of the Meeting held on 22 September, 2014 (&lt;b&gt;“the Minutes”&lt;/b&gt;) and states that there were no documents or papers that were circulated at this meeting and that the participants were asked to present their views on various IP issues at this meeting.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;span&gt;Excerpts from the Minutes&lt;/span&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;The Secretary of the Department (Shri Amitabh Kant) refers to a (then) recent announcement made by the Minister of State for Commerce and Industry (&lt;b&gt;“the Minister”&lt;/b&gt;) on the formulation of the National IPR Policy and the establishment of an IPR Think Tank and states that the meeting had been convened to &lt;i&gt;discuss on various IPR issues with IP experts and legal practitioners so that it would provide essential inputs to the policy needs of the department&lt;/i&gt; (sic). The Minutes report that Mr. Kant further stated that the objective of the department was to have &lt;i&gt;a world class IP system&lt;/i&gt; and that this included a comprehensive National IPR Policy and &lt;i&gt;which takes care of various issues like IP creation, protection, administration and capacity building &lt;/i&gt;(sic). He is also reported to have said that such a stakeholder interaction was important for the government to seek inputs.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;The Minister is reported to have said that the purpose of the meeting was to constitute an IP Think Tank that would &lt;i&gt;regularly provide inputs to all IP policy needs of this department as well as advice government in disparate legal aspects (sic). &lt;/i&gt;The Minutes also report her to have said that the department would finalize an IP policy within ninety days of the Meeting, based on the inputs of the participants.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;According to the Minutes, various issues emerged from the discussion. &lt;i&gt;Inter alia, &lt;/i&gt;these include  &lt;i&gt;first,&lt;/i&gt; that the proposal to constitute the Think Tank was a welcome measure, along the lines of similar initiatives taken by Australia, South Kora, the United Kingdom and the United States of America; &lt;i&gt;second, &lt;/i&gt;that in order to remove misconceptions held by &lt;i&gt;foreign stakeholders&lt;/i&gt; about IP enforcement in India, there was a need to highlight judgments of Indian courts that were favorable to &lt;i&gt;foreign stakeholders and MNCs&lt;/i&gt;; &lt;i&gt;third, &lt;/i&gt;that the national policies on telecom, manufacturing and IP ought to be integrated; &lt;i&gt;fourth&lt;/i&gt;, that the focus of the Policy should be &lt;b&gt;&lt;i&gt;increase in creation of IP including commercialization of IP and strengthening human capital and IP management&lt;/i&gt;&lt;/b&gt; and &lt;i&gt;fifth&lt;/i&gt;, that empirical studies should be conducted to examine the feasibility of Utility Models protection, that there was a need to revise the law on Geographical Indications and that the Policy should include protection for traditional knowledge and guidelines for publicly funded research.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;The Minister is then said to have identified six major areas during the discussion, including &lt;i&gt;IP institution, legislation, implementation, public awareness, international aspects and barriers in IP growth&lt;/i&gt; as areas to be covered under the Policy.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;span&gt;Who attended the Meeting?&lt;/span&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;Attached with the Minutes was also a list of participants who attended the Meeting. Out of the thirty six attendees, &lt;i&gt;I have not been able to locate a single individual or organization representing civil society&lt;/i&gt;. Participants include representatives from various government departments and ministries, including &lt;i&gt;inter alia,&lt;/i&gt; the DIPP, the Department of Commerce, the Ministry of External Affairs, the Ministry of Information and Broadcasting, the Copyright Division from the Department of Higher Education of the Ministry of Human Resources Development, the Office of the Controller General of Patents, Designs and Trademarks and the Ministry of Culture. The Meeting was also attended by representatives of corporations and industry associations, including FICCI, CII and Cadila Pharmaceuticals; in addition to representatives from law firms including Luthra and Luthra, K&amp;amp;S Partners and Inventure IP and academics including, &lt;i&gt;inter alia,&lt;/i&gt; faculty from the Asian School of Business, Trivandrum, Indian Law Institute, Delhi, Tezpur University, Assam, National Law University, Delhi, NALSAR University of Law, Hyderabad, the Indian Institute of Technology, Madras and the National Law School of India University, Bangalore.&lt;/p&gt;
&lt;ul&gt;
&lt;li style="text-align: justify; "&gt;&lt;b&gt;If there were multiple meetings held for the same please provide all necessary documents including the minutes of all such meetings, records, documents, memos, e-mails, opinions, advices, press releases, circulars, orders etc. for all such meetings held (sic).&lt;/b&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p style="text-align: justify; "&gt;The Department answered, “No”; which I’m taking to mean that there weren’t other meetings held for the formulation of the Think Tank or the Policy. This is interesting, because the Minutes (referred to earlier) speak of another inter-ministerial meeting &lt;i&gt;including IP experts and legal practitioners&lt;/i&gt; slated to be held around the 10&lt;sup&gt;th&lt;/sup&gt; of October, 2014, to discuss the framework of the Policy.&lt;/p&gt;
&lt;ul style="text-align: justify; "&gt;
&lt;li&gt;&lt;b&gt;If a directive or directives were received by the Department of Industrial Policy and Promotion from any other government body to constitute such a think tank, please provide a copy of such a directive received by the DIPP from any Government authority, to constitute such a Think Tank (sic).&lt;/b&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p style="text-align: justify; "&gt;The Department answered, “No”; which I’m taking to mean that there was no communication received by the Department to constitute this Think Tank.&lt;/p&gt;
&lt;ul style="text-align: justify; "&gt;
&lt;li&gt;&lt;b&gt;Please indicate in detail the process of shortlisting the members of the IPR Think Tank by the Department of Industrial Policy and Promotion or any other body that was responsible for the same (sic).&lt;/b&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p style="text-align: justify; "&gt;The Department replied that the answer to this was the same as that to the first question.&lt;/p&gt;
&lt;h3 style="text-align: justify; "&gt;The Second Response: The Drafting of the Policy&lt;/h3&gt;
&lt;p&gt;The &lt;a href="https://cis-india.org/a2k/blogs/dipp-response-2.pdf/" class="external-link"&gt;second of the Department's responses&lt;/a&gt; to our requests came in the form of separate responses to each of our four questions, as under:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;b&gt;Please indicate in detail the process followed by the IPR Think Tank constituted by the Department of Industrial Policy and Promotion via Public Notice No. 10 (22)/2013-IPR-III dated November 13, 2014 while framing the first draft of the National IPR Policy dated Dec. 19, 2014 (sic).&lt;/b&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p style="text-align: justify; "&gt;The Department stated that the IPR Think Tank conducted its meetings independently without any interference from the Department. The Department then stated that the Think Tank had received comments from stakeholders via a dedicated email id and &lt;i&gt;conducted the interactive meeting with stakeholders while framing the draft on the National IPR Policy.&lt;/i&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li style="text-align: justify; "&gt;&lt;b&gt;If there was a meeting held to decide on the same, please include all necessary documents including the minutes of the meeting, records, documents, memos, e-mails, opinion, advices, press releases, circulars, orders, suggestions etc. related to drafting of such National IPR Policy Think Tank chaired by Justice Prabha Sridevan (sic). &lt;/b&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p style="text-align: justify; "&gt;The Department replied that since the IPR Think Tank had decided &lt;i&gt;its process by themselves&lt;/i&gt; (sic), the Department&lt;i&gt; do not have the minutes of the meeting etc. conducted by the IPR Think Tank &lt;/i&gt;(sic). It attached with its reply a copy of the press releases announcing the composition of the Think Tank and asking stakeholders to submit comments to the first draft of the Policy.&lt;/p&gt;
&lt;ul&gt;
&lt;li style="text-align: justify; "&gt;&lt;b&gt;If there were multiple meetings held for the same, please provide all necessary documents including the minutes of all such meetings, records, documents, memos, e-mails, opinions, advices, press releases, circulars, order suggestions etc. for all such meetings held (sic).&lt;/b&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The Department replied that the response to this was the same as that to the earlier question above.&lt;/p&gt;
&lt;ul&gt;
&lt;li style="text-align: justify; "&gt;&lt;b&gt;Please provide all the suggestions and comments received by the IPR Think Tank from stakeholders after the DIPP issued Public Notice No. 10/22/2013-IPR-III dated 13.11.2014 asking for suggestions and comments on or before November 30, 2014 (sic).&lt;/b&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The Department replied that the comments and suggestions were received by the Think Tank directly and that therefore, the Department was &lt;i&gt;not in a position to provide the same.&lt;/i&gt;&lt;/p&gt;
&lt;h3&gt;The&lt;i&gt; &lt;/i&gt;Third Response: Stakeholder Comments&lt;/h3&gt;
&lt;p&gt;In its &lt;a href="https://cis-india.org/a2k/blogs/dipp-response-3.pdf" class="external-link"&gt;third and final response&lt;/a&gt; to our requests, the DIPP replied to our query as under:&lt;/p&gt;
&lt;ul&gt;
&lt;li style="text-align: justify; "&gt;&lt;b&gt;Please indicate all the suggestions and comments received by the IPR Think Tank by different stakeholders on or before January 30, 2015 on its first draft of the National Intellectual Property Policy submitted by the IPR Think Tank on December 19, 2014.&lt;/b&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The Department said that &lt;i&gt;the suggestions and comments on the draft on National IPR Policy have been received by the IPR Think Tank directly. As such this Department is not in a position to provide the same (sic.).&lt;/i&gt;&lt;/p&gt;
&lt;h3&gt;Observation on the DIPP's Responses&lt;/h3&gt;
&lt;p&gt;&lt;i&gt;Prima facie, &lt;/i&gt;the responses by the Department are rather curious, leading to a range of oddities and unanswered questions.&lt;/p&gt;
&lt;h3&gt;Who Will Watch the IPR Think Tank&lt;/h3&gt;
&lt;p style="text-align: justify; "&gt;In its response to our first RTI request, the Department quite clearly stated that it decided the composition of the IPR Think Tank based on discussions in a meeting that it convened, which was also chaired by the Minister of State for Commerce and Industry, the parent ministry of the DIPP. In the same response, the Department also stated that it had not received any directive from any other ministry/government department directing the constitution of the IPR Think Tank, leading to the conclusion that this decision was taken by the DIPP/the Ministry of Commerce and Industry itself. Subsequently however, the Department justified its refusal to furnish us with documents leading to the development of the first draft of the National IPR Policy (contained in our second RTI request) by stating that the IPR Think Tank conducted its business without any interference from the Department, and that the Department did not have access to any of the submissions made to the IPR Think Tank or any of the internal minutes of the meetings etc. that were a part of the process of drafting the IPR Policy.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;Various press releases by the DIPP have stated that it has constituted the IPR Think Tank, and that the purpose of the IPR Think Tank &lt;a href="http://dipp.nic.in/English/acts_rules/Press_Release/ipr_PressRelease_24October2014.pdf"&gt;would be to advise the Department on IPR issues.&lt;/a&gt; Visibly, the Department intends for the IPR Think Tank to play an active role in shaping India’s IP law and policy, including suggesting amendments to laws wherever necessary. It is concerning therefore that on the question of accountability of the IPR Think Tank, the DIPP remains silent. It may be argued perhaps, that the IPR Think Tank constitutes a ‘public authority’ under Section 2(h)(d) of the &lt;a href="http://righttoinformation.gov.in/rti-act.pdf"&gt;Right to Information Act, 2005&lt;/a&gt; (&lt;b&gt;“RTI Act”&lt;/b&gt;). In that case, the IPR Think Tank would have to fulfill, &lt;i&gt;inter alia,&lt;/i&gt; all of the obligations under Section 4 of the RTI Act as well as designate a Public Information Officer. Alternatively, given that the IPR Think Tank has been constituted by the DIPP and performs functions for the DIPP, the Public Information Officer of the DIPP would have to furnish &lt;span&gt;all&lt;/span&gt; relevant information under the RTI Act (including the information that we sought in our requests, which was not provided to us).&lt;/p&gt;
&lt;h3 style="text-align: justify; "&gt;Who are the Stakeholders&lt;/h3&gt;
&lt;p style="text-align: justify; "&gt;Even a preliminary look at the list of participants at the Meeting (based on which the Department constituted the IPR Think Tank) reveals that not all stakeholders have been adequately represented. I haven’t been able to spot any representation from civil society and other organizations that might be interested in a more balanced intellectual property framework that is not rights-heavy. The following chart (based on a total sample size of 36 participants, as stated in the list of participants provided to us by the DIPP) will help put things in perspective.&lt;/p&gt;
&lt;table class="listing"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;th&gt;&lt;img src="https://cis-india.org/home-images/Meeting.png" alt="Meeting" class="image-inline" title="Meeting" /&gt;&lt;/th&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;h3 style="text-align: justify; "&gt;What Could've Been Done?&lt;/h3&gt;
&lt;p style="text-align: justify; "&gt;Setting aside arguments on its necessity, let us for the moment assume that this drafting of the National IPR Policy is an exercise that needed to have been undertaken. We must now examine what might possibly be the best way to go about this.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;In 2014, the World Intellectual Property Organization (&lt;b&gt;“WIPO”&lt;/b&gt;) (based on whose approach the Policy seems to have been based- at least in part), produced a detailed &lt;a href="http://www.wipo.int/edocs/pubdocs/en/intproperty/958/wipo_pub_958_1.pdf"&gt;Methodology for the Development of National Intellectual Property Strategies&lt;/a&gt;, outlining a detailed eight step process before a National IP Policy was implemented in a Member State. While this approach is one to be followed by the WIPO and might not be entirely suited to India’s drafting exercise, specific sections on the national consultation process as well as the drafting and implementation of national intellectual property strategies might prove to be a decent starting point.&lt;/p&gt;
&lt;p&gt;(More on this in an upcoming article).d&lt;/p&gt;
&lt;h3&gt;Where Do We Go From Here?&lt;/h3&gt;
&lt;p style="text-align: justify; "&gt;The DIPP’s responses have left me with more questions, probably the subject of more RTI requests. Is the IPR Think Tank a public authority for the purposes of the Right to Information Act, 2005? To whom should questions of informational accountability of the IPR Think Tank be addressed, if there is no information available on the IPR Think Tank, and the DIPP claims to have no access to it? Do we need to re-examine the draft National IPR Policy given that there has been inadequate representation of all stakeholders? What were the suggestions made by different stakeholders, and (how) have these been reflected in the first draft of the Policy? Was there an evaluation exercise conducted before the first draft of the Policy was released in order to better inform the formulation of the Policy?&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;We will be looking at these and other questions as they arise, and sending some of these to the DIPP in the form of RTI requests. (Watch the blog for more).&lt;/p&gt;
        &lt;p&gt;
        For more details visit &lt;a href='https://cis-india.org/a2k/blogs/national-ipr-policy-series-rti-requests-by-cis-to-dipp-dipp-responses'&gt;https://cis-india.org/a2k/blogs/national-ipr-policy-series-rti-requests-by-cis-to-dipp-dipp-responses&lt;/a&gt;
        &lt;/p&gt;
    </description>
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>nehaa</dc:creator>
    <dc:rights></dc:rights>

    
        <dc:subject>Access to Knowledge</dc:subject>
    
    
        <dc:subject>Pervasive Technologies</dc:subject>
    
    
        <dc:subject>DIPP</dc:subject>
    
    
        <dc:subject>RTI</dc:subject>
    
    
        <dc:subject>National IPR Policy</dc:subject>
    
    
        <dc:subject>Accountability</dc:subject>
    
    
        <dc:subject>Featured</dc:subject>
    
    
        <dc:subject>IPR Think Tank</dc:subject>
    
    
        <dc:subject>Homepage</dc:subject>
    

   <dc:date>2015-04-26T08:47:00Z</dc:date>
   <dc:type>Blog Entry</dc:type>
   </item>


    <item rdf:about="https://cis-india.org/internet-governance/blog/icann49-public-forum-statement">
    <title>CIS Statement at ICANN 49's Public Forum</title>
    <link>https://cis-india.org/internet-governance/blog/icann49-public-forum-statement</link>
    <description>
        &lt;b&gt;This was a statement made by Pranesh Prakash at the ICANN 49 meeting (on March 27, 2014), arguing that ICANN's bias towards the North America and Western Europe result in a lack of legitimacy, and hoping that the IANA transition process provides an opportunity to address this.&lt;/b&gt;
        &lt;p&gt;Good afternoon. My name is Pranesh Prakash, and I'm with the Yale Information Society Project and the Centre for Internet and Society.&lt;/p&gt;
&lt;p&gt;I am extremely concerned about the accountability of ICANN to the global community.  Due to various decisions made by the US government relating to ICANN's birth, ICANN has had a troubled history with legitimacy.  While it has managed to gain and retain the confidence of the technical community, it still lacks political legitimacy due to its history.  The NTIA's decision has presented us an opportunity to correct this.&lt;/p&gt;
&lt;p&gt;However, ICANN can't hope to do so without going beyond the current ICANN community, which while nominally being 'multistakeholder' and open to all, grossly under-represents those parts of the world that aren't North America and Western Europe.&lt;/p&gt;
&lt;p&gt;Of the 1010 ICANN-accredited registrars, 624 are from the United States, and 7 from the 54 countries of Africa.  In a session yesterday, a large number of the policies that favour entrenched incumbents from richer countries were discussed.  But without adequate representation from poorer countries, and adequate representation from the rest of the world's Internet population, there is no hope of changing these policies.&lt;/p&gt;
&lt;p&gt;This is true not just of the business sector, but of all the 'stakeholders' that are part of global Internet policymaking, whether they follow the ICANN multistakeholder model or another.  A look at the boardmembers of the Internet Architecture Board, for instance, would reveal how skewed the technical community can be, whether in terms of geographic or gender diversity.&lt;/p&gt;
&lt;p&gt;Without greater diversity within the global Internet policymaking communities, there is no hope of equity, respect for human rights -- civil, political, cultural, social and economic --, and democratic funtioning, no matter how 'open' the processes seem to be, and no hope of ICANN accountability either.&lt;/p&gt;
        &lt;p&gt;
        For more details visit &lt;a href='https://cis-india.org/internet-governance/blog/icann49-public-forum-statement'&gt;https://cis-india.org/internet-governance/blog/icann49-public-forum-statement&lt;/a&gt;
        &lt;/p&gt;
    </description>
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>pranesh</dc:creator>
    <dc:rights></dc:rights>

    
        <dc:subject>IANA</dc:subject>
    
    
        <dc:subject>IG4all</dc:subject>
    
    
        <dc:subject>Internet Governance</dc:subject>
    
    
        <dc:subject>Accountability</dc:subject>
    
    
        <dc:subject>ICANN</dc:subject>
    
    
        <dc:subject>North vs South</dc:subject>
    

   <dc:date>2014-06-04T05:31:44Z</dc:date>
   <dc:type>Blog Entry</dc:type>
   </item>


    <item rdf:about="https://cis-india.org/internet-governance/blog/icann-work-stream-2-recommendations-on-accountability">
    <title>ICANN Workstream 2 Recommendations on Accountability</title>
    <link>https://cis-india.org/internet-governance/blog/icann-work-stream-2-recommendations-on-accountability</link>
    <description>
        &lt;b&gt;One of the most significant initiatives to improve the accountability of the Internet Corporation of Assigned Names and Numbers (ICANN) commenced in 2014, when the Cross Community Working Group on Accountability was created. Its role was to develop a set of proposed enhancements to ICANN’s accountability to the global Internet community. This resulted in the first Work Stream (WS1) recommendations, which were eventually approved and incorporated into the bylaws of ICANN in 2016. These included a provision expressing the need for a second WS since the first one, done on a tight deadline,did not cover all the requisite issues. Instead WS1 only focused on issues that were needed to complete the Internet Assigned Numbers Authority(IANA) transition. &lt;/b&gt;
        &lt;p style="text-align: justify; "&gt;At the ICANN meeting in March of 2017 in Finland, the second Work Stream (WS2) was launched. The Cross Community Working Group submitted their final report at the end of June 2018 and the purpose of this blog is to look at the main recommendations given and the steps ahead to its implementation.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;The new Workstream was structured into the following 8 independent sub groups as per the topics laid down in the WS1 final report, each headed by a Rapporteur:&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;1. Diversity&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;2.  Guidelines for Standards of Conduct Presumed to be in Good Faith Associated   with Exercising Removal of Individual ICANN Board  Directors. (Guidelines for Good Faith)&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;3. Human Rights Framework of Interpretation (HR-FOI)&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;4. Jurisdiction&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;5. Office of the Ombuds&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;6. Supporting Organization/ Advisory Committee Accountability&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;7. Staff Accountability&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;8. ICANN Transparency&lt;/p&gt;
&lt;p&gt; &lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;b&gt;1. &lt;/b&gt;&lt;b&gt;&lt;span&gt;DIVERSITY Recommendations &lt;/span&gt;&lt;/b&gt;&lt;b&gt; &lt;/b&gt;&lt;/p&gt;
&lt;p&gt;The sub-group on Diversity suggested ways by which ICANN can define, measure, report, support and promote diversity. They proposed  7 key factors to guide all diversity considerations: Language, Gender, Age, Physical Disability, Diverse skills, Geographical representation and stakeholder group. Each charting organization within ICANN is asked to undertake an exercise whereby they publish their diversity obligations on their website, for each level of employment including leadership either under their own charter or ICANN Bylaws. This should be followed by a diversity assessment of their existing structures and consequently used to formulate their diversity objectives/criteria and steps on how to achieve the same along with the timeline to do so. These diversity assessments should be conducted annually and at the very least, every 3 years.  ICANN staff has been tasked with developing a mechanism for dealing with complaints arising out of diversity and related issues. Eventually, it is envisioned that ICANN will create a Diversity section on their website where an Annual Diversity Report will be published. All information regarding Diversity should also be published in their Annual Report.&lt;/p&gt;
&lt;p&gt;The recommendations leave much upto the organization without establishing specific recruitment policies for equal opportunities. In their 7 parameters, race was left out as a criteria for diversity. The criteria of ‘diverse skills’ is also ambiguous; and within stakeholder group, it would have been more useful to highlight the priority for diversity of opinions within the same stakeholder group. So for example, to have two civil society organizations (CSOs) advocating for contrasting stances as opposed to having many CSO’s supporting one stance. However, these steps should be a good starting point to improve the diversity of an organization which in our earlier research we have found to be &lt;a href="https://cis-india.org/internet-governance/blog/global-multistakeholder-community-neither-global-nor-multistakeholder"&gt;neither global nor multistakeholder&lt;/a&gt;. In fact, our &lt;a href="https://cis-india.org/internet-governance/blog/icann-diversity-analysis"&gt;recent diversity analysis &lt;/a&gt;has shown concerns such as the vast number of the end users participating and as an extension, influencing ICANN work are male. The mailing list where the majority of discussions take place are dominated by individuals from industry bodies. This coupled with the relative minority presence of the other stakeholders, especially geographically (14.7% participation from Asian countries), creates an environment where concerns emanating from other sections of the society could be overshadowed. Moreover, when we have questioned ICANN’s existing diversity of employees based on their race and citizenship, they &lt;a href="https://cis-india.org/internet-governance/blog/didp-31-diversity-of-employees-at-icann"&gt;did not give us&lt;/a&gt; the figures citing either lack of information or confidentiality.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;b&gt;2. &lt;/b&gt;&lt;b&gt;&lt;span&gt;HUMAN RIGHTS FRAMEWORK OF INTERPRETATION (HR-FOI)&lt;/span&gt;&lt;/b&gt;&lt;b&gt; &lt;/b&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;A Framework of Interpretation was developed by the WS2 for ICANN Bylaws relating to Human Rights which clarified that Human Rights are not a Commitment for the organization but is a Core Value. The former being an obligation while the latter are &lt;i&gt;“&lt;span&gt;not necessarily intended to apply consistently and comprehensively to ICANN’s activities&lt;/span&gt;&lt;/i&gt;&lt;span&gt;”.&lt;/span&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;To summarize the FOI, if the applicable law i.e. the law practiced in the jurisdiction where ICANN is operating, does not mandate certain human rights then they do not raise issues under the core value.  As such, there can be no enforcement of human rights obligations by ICANN or any other party against any other party. Thus, contingent on the seat of the operations the law can vary though by in large ICANN recognizes and can be guided by significant internationally respected human rights such as those enumerated in the Universal Declaration of Human Rights. The United Nations Guiding Principles for Business and Human Rights was recognized as useful in the process of applying the core value in operations since it discusses corporate responsibility to respect human rights. Building on this, Human Right Impact Assessments (HRIA) with respect to ICANN policy development processes are currently being formulated by the Cross Community Working Group on Human Rights. Complementing this, ICANN is also undertaking an internal HRIA of the organization’s operations. It is important to remember that the international human rights instruments that are relevant here are those required by the applicable law.&lt;/p&gt;
&lt;p&gt;Apart from its legal responsibility to uphold the HR laws of an area, the framework is worded negatively in that it says ICANN should in general avoid violating human rights. It is also said that they should take into account HR when making policies but these fall short from saying that HR considerations should be given prominent weightage and since there are many core values, at any point one of the others can be used to sidestep human rights. One core value in particular says that ICANN should duly consider the public policy advice of governments and other authorities when arriving at a decision. Thus, if governments want to promote a decision to further national interests at the expense of citizen’s human rights then that would be very much possible within this FOI.&lt;/p&gt;
&lt;p&gt;&lt;b&gt;3. &lt;/b&gt;&lt;b&gt;&lt;span&gt;JURISDICTION&lt;/span&gt;&lt;/b&gt;&lt;b&gt; &lt;/b&gt;&lt;/p&gt;
&lt;p&gt;A highly contentious issue in WS2 was that of Jurisdiction, and the recommendations formed to tackle it were quite disappointing. Despite initial discussion by the group on ICANN’s location, they did not address the elephant in the room in their report. Even after the transition, ICANN’s new by-laws state that it is subject to California Law since it was incorporated there. This is partly the fault of the first Workstream because when enumerating the issues for WS2 with respect to jurisdiction, they left it ambiguous by stating: :&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;i&gt;“At this point in the CCWG Accountability’s work, the main issues that need within Work Stream 2 relate to the influence that ICANN ́s existing jurisdiction may have on the actual operation of policies and accountability mechanisms. This refers primarily to the process for the settlement of disputes within ICANN, involving the choice of jurisdiction and of the applicable laws, &lt;b&gt;&lt;span&gt;but not necessarily the location where ICANN is incorporated.”&lt;/span&gt;&lt;/b&gt;&lt;/i&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;Jurisdiction can often play a significant role in the laws that ICANN will have to abide by in terms of financial reporting, consumer protection, competition and labour laws, legal challenges to ICANN’s actions and finally, in resolving contractual disputes. In its present state, the operations of ICANN could, if such a situation arises, see interference from US authorities by way of legislature, tribunals, enforcement agencies and regulatory bodies.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;CIS has, in the past, discussed the concept of “&lt;a href="https://cis-india.org/internet-governance/blog/jurisdiction-the-taboo-topic-at-icann"&gt;jurisdictional resilience”&lt;/a&gt;, which calls for:&lt;/p&gt;
&lt;ul type="disc"&gt;
&lt;li&gt;Legal      immunity for core technical operators of Internet functions (as opposed to      policymaking venues) from legal sanctions or orders from the state in      which they are legally situated.&lt;/li&gt;
&lt;li&gt;Division      of core Internet operators among multiple jurisdictions&lt;/li&gt;
&lt;li&gt;Jurisdictional      division of policymaking functions from technical implementation functions&lt;/li&gt;
&lt;/ul&gt;
&lt;p style="text-align: justify; "&gt;Proposing to change ICANN’s seat of headquarters or at the very least, suggest ways for ICANN to gain partial immunity for its policy development processes under the US law would have gone a long way in making ICANN truly a global body. It would have also ensured that as an organization, ICANN would have been equally accountable to all its stakeholders as opposed to now, where by virtue of its incorporation, it has higher legal and possible political, obligations to the United States. This was (initially?) expressed by Brazil who dissented from the majority conclusions of the sub-group and drafted their own minority report, which was supported by countries like Russia.  They were unhappy that all countries are still not at an equal footing in the participation of management of Internet resources, which goes against the fundamentals of the multi-stakeholder system approach.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;Recommendations:&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;The recommendations passed were in two categories:&lt;/p&gt;
&lt;ol type="1"&gt;
&lt;li style="text-align: justify; "&gt;Office of Foreign Asset Control (OFAC)&lt;/li&gt;
&lt;/ol&gt;
&lt;p style="text-align: justify; "&gt;OFAC is an office of the US Treasury administering and enforcing economic and trade sanctions based on the American foreign policy and national security objectives. It is pertinent because, for ICANN to enter into a Registration Accreditation Agreement (RAA) with an applicant from a sanctioned country, it will need an OFAC license. What happens right now is that ICANN is under no obligation to request for this license and in either case, OFAC can refuse to provide it.  The sub group recommended that the terms of the RAA be modified so that ICANN is required to apply for and put their best efforts in securing the license if the applicant is qualified to be a registrar and not individually subject to sanctions. While the licensing process is underway they should also be helpful and transparent, and maintain on-going communication with the applicant. The same recommendation was made for applicants to the new gTLD program, from sanctioned countries. Other general licenses are needed from OFAC for certain ICANN transactions and hence it was proposed that ICANN pursue the same.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;2. Choice of law and Choice of Venue Provisions in ICANN Agreements&lt;/p&gt;
&lt;p&gt;In ICANN’S Registry Agreements (RA) and Registration Accreditation Agreement (RAA) the absence of a choice of law provision means that the governing law of these contracts is undetermined until later decided by a judge or arbitrator or an agreement between the parties. It was collectively seen that increased freedom of choice for the parties in the agreement could help in customizing the agreements and make it easier for registries and such to contractually engage with ICANN. Out of various options, the group decided that a Menu approach would be best whereby a host of options(decided by ICANN) can be provided and the party in case choose the most appropriate from them such as the jurisdiction of their incorporation.In RAs, the choice of venue was pre determined as Los Angeles, California but the group recommended that instead of imposing this choice on the party it would be better to offer a list of possible venues for arbitration. The registry can then choose amongst these options when entering into the contract.  There were other issues discussed which did not reach fruition due to lack of unanimity such as discussions on immunity of ICANN from US jurisdiction.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;b&gt;4. &lt;/b&gt;&lt;b&gt;&lt;span&gt;OFFICE OF THE OMBUDS&lt;/span&gt;&lt;/b&gt;&lt;b&gt; &lt;/b&gt;&lt;/p&gt;
&lt;p&gt;Subsequent to the external evaluation of the ICANN Office of the Ombuds (IOO), there were a couple of recommendations to strengthen the office. They were divided into procedural aspects that the office should carry out to improve their complaint mechanism such as differentiating between categories of complaints and explaining how each type would be handled with. The issues that would not invoke actions from the IOO should also be established clearly and if and where these could be transferred to any other channel. The response from all the relevant parties of ICANN to a formal request or report from the IOO should take place within 90 days, and 120 at the maximum if an explanation for the same can be provided. An internal timeline will be defined by the office for handling of complaints and document a report on these every quarter or annually. A recommendation for the IOO to be formally trained in mediation and have such experience within its ranks was further given. Reiterating the importance of diversity, even this sub group emphasized on the IOO bearing a diverse group in terms of gender and other parameters. This ensures that a complainant has a choice in who to approach in the office making them more comfortable. To enhance the independence of the Ombuds, their employment contract should have a 5 year fixed term which only allows for one extension of maximum 3 years. An Ombuds Advisory Panel is to be constituted by ICANN comprising five members to act as advisers, supporters and counsel for the IOO with at least 2 members having Ombudsman experience and the remaining possessing extensive ICANN experience. They would be responsible for selecting the new Ombuds and conducting the IOO’s evaluation every 5 years amongst others. Lastly, the IOO should proactively document their work by publishing reports on activity, collecting and publicizing statistics, user satisfaction information a well any improvements to the process.&lt;/p&gt;
&lt;p&gt;These proposals still do not address the opacity of how the Office of the Ombuds resolve these cases since it does not call for; a) a compilation of all the cases that have been decided by the office in the history of the organization b) the details of the parties that are involved if the parties have allowed that to be revealed and if not at the very least, the non sensitive data such as their nationality and stakeholder affiliation and c) a description of the proceedings of the case and who won in each of them. When CIS &lt;a href="https://cis-india.org/internet-governance/blog/didp-request-5-the-ombudsman-and-icanns-misleading-response-to-our-request-1"&gt;asked&lt;/a&gt; for the above in 2015, the information was denied on ground of confidentiality. Yet, it is vital to know these details since the Ombuds hear complaints against the Board, Staff and other constituent bodies and by not reporting on this, ICANN is rendering the process much less accountable and transparent. This conflict resolution process and its efficacy is even more essential in a multi-stakeholder environment so as to give parties the faith to engage in the process, knowing that the redressal mechanisms are strong. It is also problematic that sexual harassments complaints are dealt by the Ombuds and that ICANN does not have a specific Anti-Sexual Harassment Committee. The committee should be neutral and approachable and while it is useful for the Office of the Ombuds to be trained in sexual harassment cases, it is by no means a comprehensive and ideal approach to deal with complaints of this nature. Despite ICANN facing a sexual harassment claim i&lt;a href="https://cis-india.org/internet-governance/blog/cis-statement-on-sexual-harrasment-at-icann55"&gt;n 2016&lt;/a&gt;, the recommendations do not specifically address the approach the Ombuds should take in tackling sexual harassment.&lt;/p&gt;
&lt;p&gt; &lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;b&gt;5. &lt;/b&gt;&lt;b&gt;&lt;span&gt;SUPPORTING ORGANIZATION/ ADVISORY COMMITTEE ACCOUNTABILITY&lt;/span&gt;&lt;/b&gt;&lt;b&gt; &lt;/b&gt;&lt;/p&gt;
&lt;p&gt;The sub group presented the outcomes under the main heads of Accountability, Transparency, Participation, Outreach and Updates to policies and procedures. They suggested these as good practices that can be followed by the organizations and did not recommend that implementation of the same be required. The accountability aspect had suggestions of better documentation of procedures and decision-making.  Proposals of listing members of such organizations publicly, making their meetings open to public observation including minutes and transcripts along with disclosing their correspondence with ICANN were aimed at making these entities more transparent. In the same vein, rules of membership and eligibility criteria, the process of application and a process of appeal should be well defined. Newsletters should be published by the SO/AC to help non-members understand the benefit and the process of becoming a member. Policies were asked to be reviewed at regular intervals and these internal reviews should not extend beyond a year.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;b&gt;6. &lt;/b&gt;&lt;b&gt;&lt;span&gt;STAFF ACCOUNTABILITY&lt;/span&gt;&lt;/b&gt;&lt;b&gt; &lt;/b&gt;&lt;/p&gt;
&lt;p&gt;Improving the ICANN staff’s Accountability was the job of a different group who assessed it at the service delivery, departmental or organizational level not at an individual or personnel level. They did this by analysing the roles and responsibilities of the Board, staff and community members and the nexus between them. Their observations culminated in the understanding that ICANN needs to take steps such as make visible their performance management system and process, their vision for the departmental goals and how they tie in to the organization’s strategic goals and objectives. They note that several new mechanisms have already been established yet have not been used enough to ascertain their efficacy and thus, propose a regular information acquisition mechanism. Most importantly, they have asked ICANN to standardize and publish guidelines for suitable timeframes for acknowledging and responding to requests from the community.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt; &lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;b&gt;7. &lt;/b&gt;&lt;b&gt;&lt;span&gt;ICANN TRANSPARENCY&lt;/span&gt;&lt;/b&gt;&lt;b&gt; &lt;/b&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;The last group of the WS2 was one specifically looking at the transparency of the organization.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;i&gt;a.   &lt;span&gt;The Documentary Information Disclosure Policy (DIDP)&lt;/span&gt;&lt;/i&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;Currently the DIDP process only applies to ICANN’s “operational activities”, it was recommended to delete this caveat to cover a wider breadth of the organization’s activities. As CIS has experienced, request for information is often met with an answer that such information is not documented and to remedy the same, a documentation policy was proposed where if significant elements of a decision making process are taking place orally then the participants will be required to document the substance of the conversation. Many a times DIDP requests are refused because one aspect of the information sought is subject to confidentiality. hus one of the changes is to introduce a severability clause so that in such cases, information can still be disclosed with the sensitive aspect redacted or severed. In scenarios of redaction, the rationale should be provided citing one of the given DIDP exceptions along with the process for appeal. ICANN’s contracts should be under the purview of the DIDP except when subject to a non-disclosure agreement and further, the burden is on the other party to convince ICANN that it has a legitimate commercial reason for requested the NDA. No longer would any information pertaining to the security and stability of the Internet be outside the ambit of the DIDP but only if it is harmful to the security and stability. Finally, ICANN should review the DIDP every five years to see how it can be improved.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;i&gt;b.   &lt;span&gt;Documenting and Reporting on ICANN’s Interactions with the Government&lt;/span&gt;&lt;/i&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;In a prominent step towards being more transparent with their expenditure and lobbying, the group recommended that ICANN begins disclosing publicly on at least an annual basis, sums of $20,000 per year devoted to “political activities” both in the US and abroad. All expenditures should be done on an itemized basis by ICANN for both outside contractors and internal personnel along with the identities of the persons engaging in such activities and the type of engagement used for such activities amongst others.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;i&gt;cc.  &lt;span&gt;Transparency of Board Deliberations&lt;/span&gt;&lt;/i&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;i&gt; &lt;/i&gt;The bylaws were recommended to be revised so that material may be removed from the minutes of the Board if subject to a DIDP exception. The exception for deliberative processes should not apply to any factual information, technical report or reports on the performance or effectiveness of a particular body or strategy. When any information is removed from the minutes of the Board meeting, they should be disclosed after a particular period of time as and when the window of harm has passed.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;i&gt;d.     &lt;span&gt;ICANN’s Anonymous Hotline (Whistle-blower Protection)&lt;/span&gt;&lt;/i&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;To begin with, ICANN was recommended to devise a way such that when anyone searches their website for the term “whistle-blower”, it should redirect to their Hotline policy since people are unlikely to be aware that in ICANN parlance it is referred to as the Hotline policy.  Instead of only “serious crimes” that are currently reported, all issues and concerns that violate local laws should be. Complaints should not be classified as ‘urgent’ and ‘non-urgent’ but all reports should be a priority and receive a formal acknowledgment within 48 hours at the maximum. ICANN should make it clear that any retaliation against the reporter will be taken and investigated as seriously as the original alleged wrongdoing. Employees should be provided with data about the use of the Hotline, including the types of incidents reported. Few member of this group came out with a Minority Statement expressing their disapproval with one particular aspect of the recommendations that they felt was not developed enough, the one pertaining to ICANN’s attorney-client privilege. The recommendation did not delve into specifics but merely stated that ICANN should expand transparency in their legal processes including clarifying how attorney-client privilege is invoked. The dissidents thought ICANN should go farther and enumerate principles where the privilege would be waived in the interests of transparency and account for voluntary disclosure as well.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;The transparency recommendations did not focus on the financial reporting aspects of ICANN which &lt;a href="https://cis-india.org/internet-governance/blog/analysis-of-icann-financials-from-2012-2016"&gt;we have found ambiguities&lt;/a&gt; with before. Some examples are; the Registries and Registrars are the main sources of revenue though there is ambiguity as to the classifications provided by ICANN such as the difference between RYG and RYN. The mode of contribution of sponsors isn’t clear either so we do not know if this was done through travel, money, media partnerships etc. Several entities have been listed from different places in different years, sometimes depending on the role they have played such as whether they are a sponsor or registry. Moreover, the Regional Internet Registries are clubbed under one heading and as a consequence it is not possible to determine individual RIR     contribution like how much did APNIC pay for the Asia and Pacific region. Thus, there is a lot more scope for ICANN to be transparent which goes beyond the proposals in the report.&lt;/p&gt;
&lt;p&gt; &lt;/p&gt;
&lt;p&gt;It is worth noting that whereas the mandate of the WS1 included the implementation of the recommendations, this is not the case for WS2 and thus, by creating a report itself the mission of the group is concluded. This difference can be attributed to the fact that during the first WS, there was a need to see it through since the IANA transition would not happen otherwise. The change in circumstances and the corresponding lack of urgency render the process less powerful, the second time round. The final recommendations are now being discussed in the relevant charting organizations within ICANN such as the Government Advisory Council (GAC) and subsequent to their approval,, it will be sent to the Board who will decide to adopt them or not. If adopted, ICANN and its sub organizations will have to see how they can implement these recommendations. The co-chairs of the group will be the point of reference for the chartering organizations and an implementation oversight team has been formed, consisting of the Rapporteurs of the sub teams and the co-chairs. A Feasibility Assessment Report will be made public in due time which will describe the resources that would take to implement the recommendations. Since it would be a huge undertaking for ICANN to implement the above, the compliance process is expected to take a few years. .&lt;/p&gt;
&lt;p style="text-align: justify; "&gt; &lt;/p&gt;
&lt;p&gt;The link to report can be found&lt;a href="https://community.icann.org/display/WEIA/WS2+-+Enhancing+ICANN+Accountability+Home?preview=/59640761/88575033/FULL%20WS2%20REPORT%20WITH%20ANNEXES.pdf"&gt; here.&lt;/a&gt;&lt;/p&gt;

        &lt;p&gt;
        For more details visit &lt;a href='https://cis-india.org/internet-governance/blog/icann-work-stream-2-recommendations-on-accountability'&gt;https://cis-india.org/internet-governance/blog/icann-work-stream-2-recommendations-on-accountability&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:subject>Accountability</dc:subject>
    

   <dc:date>2018-11-23T14:56:20Z</dc:date>
   <dc:type>Blog Entry</dc:type>
   </item>


    <item rdf:about="https://cis-india.org/internet-governance/blog/icann2019s-documentary-information-disclosure-policy-2013-i-didp-basics">
    <title>ICANN’s Documentary Information Disclosure Policy – I: DIDP Basics</title>
    <link>https://cis-india.org/internet-governance/blog/icann2019s-documentary-information-disclosure-policy-2013-i-didp-basics</link>
    <description>
        &lt;b&gt;In a series of blogposts, Vinayak Mithal analyses ICANN's reactive transparency mechanism, comparing it with freedom of information best practices. In this post, he describes the DIDP and its relevance for the Internet community.&lt;/b&gt;
        &lt;p style="text-align: justify; "&gt;The Internet Corporation for Assigned Names and Numbers (“ICANN”) is a non-profit corporation incorporated in the state of California and vested with the responsibility of managing the DNS root, generic and country-code Top Level Domain name system, allocation of IP addresses and assignment of protocol identifiers. As an internationally organized corporation with its own multi-stakeholder community of Advisory Groups and Supporting Organisations, ICANN is a large and intricately woven governance structure. Necessarily, ICANN undertakes through its Bye-laws that “&lt;i&gt;in performing its functions ICANN shall remain accountable to the Internet community through mechanisms that enhance ICANN’s effectiveness&lt;/i&gt;”. While many of its documents, such as its Annual Reports, financial statements and minutes of Board meetings, are public, ICANN has instituted the Documentary Information Disclosure Policy (“DIDP”), which like the RTI in India, is a mechanism through which public is granted access to documents with ICANN which are not otherwise available publicly. It is this policy – the DIDP – that I propose to study.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;In a series of blogposts, I propose to introduce the DIDP to unfamiliar ears, and to analyse it against certain freedom of information best practices. Further, I will analyse ICANN’s responsiveness to DIDP requests to test the effectiveness of the policy. However, before I undertake such analysis, it is first good to know what the DIDP is, and how it is crucial to ICANN’s present and future accountability.&lt;/p&gt;
&lt;h3&gt;&lt;strong&gt;What is the DIDP?&lt;/strong&gt;&lt;/h3&gt;
&lt;p style="text-align: justify; "&gt;One of the core values of the organization as enshrined under Article I Section 4.10 of the Bye-laws note that “in performing its functions ICANN shall remain accountable to the Internet community through mechanisms that enhance ICANN’s effectiveness”. Further, Article III of the ICANN Bye-laws, which sets out the transparency standard required to be maintained by the organization in the preliminary, states - “ICANN and its constituent bodies shall operate to the maximum extent feasible in an open and transparent manner and consistent with procedures designed to ensure fairness”.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;Accordingly, ICANN is under an obligation to maintain a publicly accessible website with information relating to its Board meetings, pending policy matters, agendas, budget, annual audit report and other related matters. It is also required to maintain on its website, information about the availability of accountability mechanisms, including reconsideration, independent review, and Ombudsman activities, as well as information about the outcome of specific requests and complaints invoking these mechanisms.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;Pursuant to Article III of the ICANN Bye-laws for Transparency, ICANN also adopted the DIDP for disclosure of publicly unavailable documents and publish them over the Internet. This becomes essential in order to safeguard the effectiveness of its international multi-stakeholder operating model and its accountability towards the Internet community. Thereby, upon request made by members of the public, ICANN undertakes to furnish documents that are in possession, custody or control of ICANN and which are not otherwise publicly available, provided it does not fall under any of the defined conditions for non-disclosure. Such information can be requested via an email to &lt;a href="mailto:didp@icann.org"&gt;didp@icann.org&lt;/a&gt;.&lt;/p&gt;
&lt;h3&gt;&lt;strong&gt;Procedure&lt;/strong&gt;&lt;/h3&gt;
&lt;ul style="text-align: justify; "&gt;
&lt;li&gt;Upon the receipt of a DIDP request, it is reviewed by the ICANN staff.&lt;/li&gt;
&lt;li&gt;Relevant documents are identified and interview of the appropriate staff members is conducted.&lt;/li&gt;
&lt;li&gt;The documents so identified are then assessed whether they come under the ambit of the conditions for non-disclosure. 
&lt;ul&gt;
&lt;li&gt;Yes - A review is conducted as to whether, under the particular circumstances, the public interest in disclosing the documentary information outweighs the harm that may be caused by such disclosure. &lt;/li&gt;
&lt;li&gt;Documents which are considered as responsive and appropriate for public disclosure are posted on the ICANN website.&lt;/li&gt;
&lt;li&gt;In case of request of documents whose publication is appropriate but premature at the time of response then the same is indicated in the response and upon publication thereafter, is notified to the requester.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3&gt;&lt;strong&gt;Time Period and Publication &lt;/strong&gt;&lt;/h3&gt;
&lt;p style="text-align: justify; "&gt;The response to the DIDP request is prepared by the staff and is made available to the requestor within a period of 30 days of receipt of request via email. The Request and the Response is also posted on the DIDP page &lt;a href="http://www.icann.org/en/about/transparency"&gt;http://www.icann.org/en/about/transparency&lt;/a&gt; in accordance with the posting guidelines set forth at &lt;a href="http://www.icann.org/en/about/transparency/didp"&gt;http://www.icann.org/en/about/transparency/didp&lt;/a&gt;.&lt;/p&gt;
&lt;h3&gt;&lt;strong&gt;Conditions for Non-Disclosure&lt;/strong&gt;&lt;/h3&gt;
&lt;p style="text-align: justify; "&gt;There are certain circumstances under which ICANN may refuse to provide the documents requested by the public. The conditions so identified by ICANN have been categorized under 12 heads and includes internal information, third-party contracts, non-disclosure agreements, drafts of all reports, documents, etc., confidential business information, trade secrets, information protected under attorney-client privilege or any other such privilege,  information which relates to the security and stability of the internet, etc.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;Moreover, ICANN may refuse to provide information which is not designated under the specified conditions for non-disclosure if in its opinion the harm in disclosing the information outweighs the public interest in disclosing the information. Further, requests for information already available publicly and to create or compile summaries of any documented information may be declined by ICANN.&lt;/p&gt;
&lt;h3&gt;&lt;strong&gt;Grievance Redressal Mechanism &lt;/strong&gt;&lt;/h3&gt;
&lt;p style="text-align: justify; "&gt;In certain circumstances the requestor might be aggrieved by the response received and so he has a right to appeal any decision of denial of information by ICANN through the Reconsideration Request procedure or the Independent Review procedure established under Section 2 and 3 of Article IV of the ICANN Bye-laws respectively. The application for review is made to the Board which has designated a Board Governance Committee for such reconsideration. The Independent Review is done by an independent third-party of Board actions, which are allegedly inconsistent with the Articles of Incorporation or Bye-laws of ICANN.&lt;/p&gt;
&lt;h3&gt;&lt;strong&gt;Why does the DIDP matter?&lt;/strong&gt;&lt;/h3&gt;
&lt;p style="text-align: justify; "&gt;The breadth of ICANN’s work and its intimate relationship to the continued functioning of the Internet must be appreciated before our analysis of the DIDP can be of help. ICANN manages registration and operations of generic and country-code Top Level Domains (TLD) in the world. This is a TLD:&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;&lt;img src="https://cis-india.org/internet-governance/blog/TLD.jpg/@@images/1bb21859-d1aa-41c6-b5e0-4041ae099f54.jpeg" alt="TLD" class="image-inline" title="TLD" /&gt;&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;(&lt;i&gt;Source&lt;/i&gt;: &lt;a class="external-link" href="http://geovoices.geonetric.com/wp-content/uploads/2013/11/parts_of_a_domain_name.jpg"&gt;here&lt;/a&gt;)&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;Operation of many gTLDs, such as .com, .biz or .info, is under contract with ICANN and an entity to which such operation is delegated. For instance, Verisign operates the .com Registry. Any organization that wishes to allow others to register new domain names under a gTLD (sub-domains such as ‘benefithealth’ in the above example) must apply to ICANN to be an ICANN-accredited Registrar. GoDaddy, for instance, is one such ICANN-accredited Registrar. Someone like you or me, who wants to  get our own website – say, vinayak.com – buys from GoDaddy, which has a contract with ICANN under which it pays periodic sums for registration and renewal of individual domain names. When I buy from an ICANN-accredited Registrar, the Registrar informs the Registry Operator (say, Verisign), who then adds the new domain name (vinayak.com) to its registry list, and then it can be accessed on the Internet.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;ICANN’s reach doesn’t stop here, technically. To add a new gTLD, an entity has to apply to ICANN, after which the gTLD has to be added to the root file of the Internet. The root file, which has the list of all TLDs (or all ‘legitimate’ TLDs, some would say), is amended by Verisign under its tripartite contract with the US Government and ICANN, after which Verisign updates the file in its ‘A’ &lt;a href="http://root-servers.org/"&gt;root server&lt;/a&gt;. The other 12 root servers use the same root file as the Verisign root server. Effectively, this means that &lt;i&gt;only &lt;/i&gt;ICANN-approved TLDs (and all sub-domains such as ‘benefithealth’ or ‘vinayak’) are available across the Internet, on a global scale. Or at least, ICANN-approved TLDs have the most and widest reach. ICANN similarly manages country-code TLDs, such as .in for India, .pk for Pakistan or .uk for the United Kingdom.&lt;/p&gt;
&lt;p style="text-align: justify; "&gt;All of this leads us to wonder whether the extent of ICANN’s voluntary and reactive transparency is sufficient for an organization of such scale and impact on the Internet, perhaps as much impact as the governments do. In the next post, I will analyse the DIDP’s conditions for non-disclosure of information with certain freedom of information best practices.&lt;/p&gt;
&lt;hr style="text-align: justify; " /&gt;
&lt;p style="text-align: justify; "&gt;&lt;i&gt;Vinayak Mithal is a final year student at the Rajiv Gandhi National University of Law, Punjab. His interests lie in Internet governance and other aspects of tech law, which he hopes to explore during his internship at CIS and beyond. He may be reached at vinayakmithal@gmail.com.&lt;/i&gt;&lt;/p&gt;
        &lt;p&gt;
        For more details visit &lt;a href='https://cis-india.org/internet-governance/blog/icann2019s-documentary-information-disclosure-policy-2013-i-didp-basics'&gt;https://cis-india.org/internet-governance/blog/icann2019s-documentary-information-disclosure-policy-2013-i-didp-basics&lt;/a&gt;
        &lt;/p&gt;
    </description>
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>Vinayak Mithal</dc:creator>
    <dc:rights></dc:rights>

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

   <dc:date>2014-07-01T13:01:34Z</dc:date>
   <dc:type>Blog Entry</dc:type>
   </item>


    <item rdf:about="https://cis-india.org/accessibility/blog/report-gaad-2017">
    <title>Report of the Global Accessibility Awareness Day 2017 </title>
    <link>https://cis-india.org/accessibility/blog/report-gaad-2017</link>
    <description>
        &lt;b&gt;Aditya Tejas attended the Global Accessibility Awareness Day event organized at NIMHANS Convention Centre in Bengaluru. The event had multiple panels and presentations, including a talk on coding for accessibility, a panel on why accessibility is necessary and how India is lagging behind in implementing it, and a presentation on how accessibility principles are integrated into the product life cycle at Cisco.&lt;/b&gt;
        
&lt;p&gt;&lt;strong&gt;Logo of Shuttleworth Foundation below: &lt;/strong&gt;&lt;/p&gt;
&lt;p style="text-align: center;"&gt;&lt;img src="https://cis-india.org/home-images/ShuttleworthFunded.jpg/@@images/a7ad882b-1f69-4576-a25a-bffe5f942c79.jpeg" alt="null" class="image-inline" title="Shuttleworth" /&gt;&lt;/p&gt;
&lt;hr /&gt;
&lt;p style="text-align: justify;"&gt;Global Accessibility Awareness Day is celebrated across the world on May 3 every year. The objective of the event is to get everyone talking, thinking and learning about digital access/inclusion and people with different disabilities.&lt;/p&gt;
&lt;p style="text-align: justify;"&gt;This year the Global Accessibility Awareness Day 2017 (GAAD 2017) organized by Prakat Solutions and co-hosted by CIS and Mitra Jyoti, was held on May 18 at NIMHANS Convention Centre in Bengaluru. The event was designed to raise awareness around digital accessibility issues for persons with disabilities. The Shuttleworth Foundation also supported this event. Approximately 250 people were in attendance. The URL for the event is &lt;a href="http://gaad.in/"&gt;here&lt;/a&gt;. A detailed agenda can be found &lt;a href="http://gaad.in/Agenda.html"&gt;here&lt;/a&gt;. Video recordings of the event will be made available shortly.&lt;/p&gt;
&lt;p style="text-align: justify;"&gt;The event ran from 2:30-7:30 PM and featured various discussions and events, including dance ceremonies, skits, and talks by various figures.&lt;/p&gt;
&lt;p style="text-align: justify;"&gt;The first event was an extended presentation on coding for accessibility by Nawaz Khan of PayPal, in which he discussed how developers can integrate accessibility principles into their software from the design phase, and how persons with disabilities can productively make their issues known to developers. He encouraged developers to adopt international standards such as WAI-ARIA, and also encouraged developers to use accessible open source libraries and testing tools. He took questions about standards for other types of disabilities beyond visual impairment, joining the global conversation around accessibility standards, and accessibility design for mobile platforms.&lt;/p&gt;
&lt;p style="text-align: justify;"&gt;The main event was a panel on the awareness of accessibility issues in India and how they could be improved, both in the public and private spheres. In attendance were Abhik Biswas of Prakat Solutions, Pranay Gadodia of Deutsche Bank HR, Shalini Subramaniam of PayPal, Balachandra Shetty of Intuit, Sandeep Sabat of ZingUp Life, Kameshwari from Wipro, Mahabala Shetty from NIC, and Srinivasu from Informatica. The panel was moderated by Giri Prakash of Hindu Business Line. They discussed issues including how to promote a stronger government response to accessibility issues, initiatives that can be taken from the private or civil society sector in order to address accessibility issues, the lack of awareness around accessibility in the Indian context, and the responsibilities that developers have to make accessible apps and products. Shalini from PayPal talked about the potential for government initiatives such as Make in India could be used to further the availability of accessible consumer products and services in India.&lt;/p&gt;
&lt;p style="text-align: justify;"&gt;The second speaker, Kameshwari Visarapu from Wipro, talked about how persons with disabilities need to make their voices heard in society. She stressed that, while the laws are already in place, people do not demand their rights. Without this, the government and any community, even those with the necessary power, would not be able to make the changes. Mahabala Shetty from NIC pointed out that NIC is responsible for developing and updating various government websites. He said he understood that the inaccessibility of government websites and services is a serious problem, and pledged to make sure that all websites would be made accessible in the coming months.&lt;/p&gt;
&lt;p style="text-align: justify;"&gt;The fifth speaker was Sandeep Sabat of ZingUp Life, also a health tech company, which seeks to help people with issues not just around physical health, but also emotional, mental and spiritual health. He drew a comparison with the beginning of the mobile revolution, when people would say that web on mobile is a small, niche space, which eventually gave way to the idea of mobile-first design. Extending this analogy, he said that design must now be accessibility-first, in order to ensure that it becomes part of the culture of product development.&lt;/p&gt;
&lt;p style="text-align: justify;"&gt;The sixth speaker at the event was Balachandra Shetty from Intuit. He pointed out that design principles needed to make a product accessible and making that product easy to use for the general public are the same, and that improving the user experience for 20% of the population effectively improves it for everyone.&lt;/p&gt;
&lt;p style="text-align: justify;"&gt;The seventh speaker was Pranay Gadodia from Deutsche Bank HR, who argued that accessibility was important not just for persons with disabilities, but for everyone. He gave the example of ramps on public entrances, which make access easier for everyone. He demonstrated the use of a screen reader and tried to order food through Swiggy. When he found that the app was inaccessible, he pointed out that they had just lost a customer.&lt;/p&gt;
&lt;p style="text-align: justify;"&gt;The eighth speaker, Srinivasu from Informatica, talked about his work in the accessibility space for various NGOs and companies. He argued that inaccessibility was never built into a product by design, and that any problems were the result of ignorance. He also said that accessibility work was the only career with two major benefits – that of creating an immediate impact among the community and being the kind of work that not only takes advantage of a business opportunity but also directly benefits consumers.&lt;/p&gt;
&lt;p style="text-align: justify;"&gt;The ninth speaker, Abhik Biswas, said that he believes that accessibility is a nonissue, because if everyone wrote good code and followed best practices, all products would be accessible anyway. He said this was not always the case with software tools. He gave the example of work that Prakat did with a provider of legal software. In large corporate lawsuits, parties would usually share terabytes of data with each other, and legal e-discovery software is used to discover patterns for evidence. An inaccessible document would be useless to such software so, of course accessibility isn’t an issue only for a certain set of people. If you’re in the innovation space and trying to solve problems, he stressed, then accessibility is an issue.&lt;/p&gt;
&lt;p style="text-align: justify;"&gt;The moderator then raised the issue of the lack of progress for persons with disabilities in the past five years. He asked what progress has been made in the legal area, and whether there are any solutions that users can come up with themselves rather than waiting for government action. Shalini pointed out the inaccessibility of the Swiggy app, and added that there are automated accessibility checkers for apps, both Apple and Android. She demonstrated this for the audience.&lt;/p&gt;
&lt;p style="text-align: justify;"&gt;Kameshwari said that part of the problem is that a single person may not be able or willing to make much noise. There are a lot of communities that have been formed on a corporate/state/national level, but collectively making noise is important for major changes. One process that her own company tried was creating a repository of pre-tested accessible components, which has two advantages; the developer can pick the component from a standardized repository, and the component would have been pre-tested for accessibility and responsiveness. This is another possible solution – which people collectively come up with standardized repositories of accessible components.&lt;/p&gt;
&lt;p style="text-align: justify;"&gt;She then gave the example of an accessible garden in Kerala, where persons with disabilities could visit and touch different types of plants in a guided experience to help them identify and understand them. When talking about inclusivity, she asked, why create a separate garden? Integrate these features into all gardens instead, she suggested.&lt;/p&gt;
&lt;p style="text-align: justify;"&gt;The third speaker said that the government drains enthusiasm from people, and insisted that it could only play the role of a facilitator. The need is to inspire the necessary passion in people to carry forward the issues themselves.&lt;/p&gt;
&lt;p style="text-align: justify;"&gt;Sandeep said that the intent is already there, but the government was not capable of doing it alone. The social fabric of the country needs to change, along with the attitude of the society. To that end, they suggested making accessibility a non-issue, and looking for opportunities to integrate it into society at large. Instead of thinking of it through a usability standpoint, consider how to improve the overall user experience of a product through the lens of a user with disabilities.&lt;/p&gt;
&lt;p style="text-align: justify;"&gt;Balachandra pointed out that while love is a strong emotion, fear too is very powerful. The laws in the Commonwealth are much stricter than those in the US, he pointed out, and yet apps built in those countries are far more accessible than those in Indonesia, India etc. So, he suggested that if a product proved to be inaccessible to a certain segment of the population, the employees responsible could face down the CEO, and fear would drive them to make their products accessible. In addition, he called for stricter laws and a possible amendment of the IT Act, drawing upon laws in the Commonwealth and France. Disability discrimination in the US carries a high penalty, and suggested that similar laws would enforce accessibility in local products.&lt;/p&gt;
&lt;p style="text-align: justify;"&gt;The moderator asked Pranay: is it possible for app developers or mobile platform providers to make accessibility mandatory for apps that are publicly released? He answered that as a tech developer he might not be the right person to answer that, however, he know that the iOS framework is much more stringent than Android in this regard. He called on users with disabilities to call out inaccessible design wherever they saw it, in order to inform developers and to create a healthy competition to make companies disability-inclusive. He also pointed out that many corporations hold events or draft policy for persons with disabilities without involving them in the decision-making process, and that this needed to change.&lt;/p&gt;
&lt;p style="text-align: justify;"&gt;Srinivasu stressed that the job of making government services accessible fell on the developers within the government, who are in-house, or the vendors, who work for NIC. There are two things the government can do, he said; when asking for a vendor, they could refuse those who make inaccessible products, thus making accessibility a requirement for procurement.&lt;/p&gt;
&lt;p style="text-align: justify;"&gt;The second is to raise accessibility issues at the level of education. He gave the example of several apps like TaxiForSure and Cleartrip, all of which responded to accessibility issues raised by their users. He stressed that any user could give feedback, and not just those with disabilities, and that raising awareness is a duty for everyone. He asked the audience to share the event on WhatsApp, and to type with their non-dominant hand, as a simple way of understanding disability. The other exercise he called on the audience to do is to write a post about the event on Facebook or their blogs using only the keyboard, without touching their mouse. In this way, he drew attention to thinking about accessibility whenever one uses a website or software.&lt;/p&gt;
&lt;p style="text-align: justify;"&gt;Abhik took the opportunity to add one more dimension, an area of concern for app developers in India in particular – that of linguistic accessibility. Most apps, he pointed out, are being developed in English only, and most government apps have the additional burden of considering vernacular languages, while NVDA only supports 10-12. The government can’t solve this problem by making multilingual websites, as developers also need to contribute to projects like NVDA in order to build support for other languages. Accessibility, he stressed, wasn’t anyone’s problem, but everyone’s problem.&lt;/p&gt;
&lt;p style="text-align: justify;"&gt;After this, Shekhar Naik, former captain of the Indian blind cricket team, talked about his life story. He mentioned that there are over 5c0k blind cricketers in the country. He talked about his passion for cricket, how it brought him to where he was today, and thanked the government for its increased recognition and felicitation of persons with disabilities.&lt;/p&gt;
&lt;p style="text-align: justify;"&gt;After that, the owner of Pothole Raja, Pratap Bhimasena Rao, spoke about the importance of the accessibility of built environments such as roads. He pointed out that 25% of vehicular accidents cause a disability, and stressed the need to address these issues to promote not just accessibility, but prevent disability.&lt;/p&gt;
&lt;p style="text-align: justify;"&gt;After this, Amit Balakrishna Joshi from the state government gave a brief overview of the Karnataka government’s accessibility and e-governance initiatives. He spoke about the Karnataka Mobile One app, an initiative to consolidate and digitize several state government services. As the world’s largest Mobile One platform, it would integrate about 40 departments, with the objective of bringing equality in service delivery across socioeconomic, linguistic and literacy divides.&lt;/p&gt;
&lt;p style="text-align: justify;"&gt;At 7:00, Sean Murphy from Cisco gave a talk on universal design principles. He discussed how universal design is important to maximize market access, ensuring that a company reaches 100% of its market. In Cisco, accessibility is integrated into the product lifecycle right from the design phase to testing to rollout.&lt;/p&gt;
&lt;p style="text-align: justify;"&gt;He also discussed regulatory standards such as Section 508 in the US, which he stressed were critical to securing industry-wide accessibility. The event ended at 7:30 p.m.&lt;br /&gt;&lt;br /&gt;&lt;/p&gt;
&lt;p style="text-align: justify;"&gt;&lt;strong&gt;Images:&lt;/strong&gt;&lt;/p&gt;
&lt;p style="text-align: justify;"&gt;&lt;img src="https://cis-india.org/copy_of_SRID6275.JPG/image_preview" alt="GAAD lamplighting" class="image-inline image-inline" title="GAAD lamplighting" /&gt;&lt;/p&gt;
&lt;p style="text-align: justify;"&gt;&lt;strong&gt;Participants light the lamp to commemorate the start of GAAD 2017.&lt;/strong&gt;&lt;/p&gt;
&lt;p style="text-align: justify;"&gt;&lt;strong&gt;&lt;br /&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p style="text-align: justify;"&gt;&lt;strong&gt;&lt;img src="https://cis-india.org/copy_of_SRID6299.JPG/image_preview" alt="GAAD Abhik Biswas" class="image-inline image-inline" title="GAAD Abhik Biswas" /&gt;&lt;br /&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p style="text-align: justify;"&gt;&lt;strong&gt;Prakat Solutions co-founder Abhik Biswas speaks at GAAD 2017.&lt;/strong&gt;&lt;/p&gt;
&lt;p style="text-align: justify;"&gt;&lt;strong&gt;&lt;img src="https://cis-india.org/SRID6557.JPG/image_preview" alt="GAAD 2017 panel" class="image-inline image-inline" title="GAAD 2017 panel" /&gt;&lt;br /&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p style="text-align: justify;"&gt;&lt;strong&gt;Panelists discuss accessibility challenges in India.&lt;/strong&gt;&lt;/p&gt;

        &lt;p&gt;
        For more details visit &lt;a href='https://cis-india.org/accessibility/blog/report-gaad-2017'&gt;https://cis-india.org/accessibility/blog/report-gaad-2017&lt;/a&gt;
        &lt;/p&gt;
    </description>
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>nirmita</dc:creator>
    <dc:rights></dc:rights>

    
        <dc:subject>Accountability</dc:subject>
    

   <dc:date>2017-06-19T15:07:28Z</dc:date>
   <dc:type>Blog Entry</dc:type>
   </item>




</rdf:RDF>
