ICANN58 - Copenhagen

11 Mar 2017 to 16 Mar 2017
Copenhagen, Denmark


Event report/s:
Aida Mahmutovic

The Next Generation gTLD Registration Directory Service (RDS) to Replace WHOIS Policy Development Process Working Group was established with the aim to provide the Generic Names Supporting Organiza

The Next Generation gTLD Registration Directory Service (RDS) to Replace WHOIS Policy Development Process Working Group was established with the aim to provide the Generic Names Supporting Organization (GNSO) Council with policy recommendations regarding two main questions:

’What are the fundamental requirements for gTLD registration data? Is a new policy framework and next-generation RDS needed to address these requirements?’

The agenda of the session was qualified as ‘unique’, as it aimed to present 19 questions that were developed for Cannataci. It was underlined that questions were developed with the aim to understand more the importance of data protection and privacy requirements in the context of the domain name system.

Cannataci addressed the following questions raised by the chair, in more depth: ‘What do you mean when you say ICANN to specify the purpose of domain name? What criteria should be used to determine the legitimate purposes? What is the difference between primary and secondary purposes?’

It was stated by Cannataci that ICANN needs to consider sustainability. He invited ICANN to look into setting up a transversal group which deals with privacy and other human rights, such as freedom of expression. The group would be open to others to join the discussion, and would help ‘bounce off’ important questions. He emphasised that ‘the purpose of collecting data remains the key’. It is important that the collection of ‘specific personal data’ is one in line with a specific purpose, which can never be a general one: “Jurisprudence does not say ‘Just in case I need it’.”

Addressing the question of primary and secondary purpose for data collection, he stated that it is not up to the regulators to define secondary purpose, and that this needs to be carefully stipulated by the data controller when he/she defines the goal of looking for data. ‘When you talk about the secondary purpose, please be specific and don’t expect or let regulator do it., Cannataci said.

Another question was raised in relation to the Article 6.1. b) of the EU Data Protection Directive which provides that personal data may only be collected for specified, explicitly and legitimate purpose and not further processed in a way incompatible with those purposes, specified in Article 7 of the Directive.

‘Under what circumstances might the publication of domain name registration data elements that are personal be allowable?’ Cannataci addressed the question stating that ‘we need to start from knowing whyat all we want to publish anything. If you what to publish personal data, then there must be a reason for it. What is the public interest for publishing the information? Is it transparency, for example?”

He continued by stating that once data is easily associated with an identified or identifiable individual, then it becomes personal data. , such as in the case of domain name, it becomes a personal information. If data related to a domain nameis linked to someone who is identifiable,  then it becomes a personal data.He concluded by saying that the question ‘What is the purpose of publishing (personal) data?’ should be the main question.

As the time  allocated for the session ended, it was said that the 19 questions would be further fine-tuned, and, once answers are collected, the could be published on the group’s webpage, if the members find that useful. 

Krishna Kumar Rajamannar

The Non-Commercial Stakeholder Group (NCSG) started the session by demanding a response from the ICANN Board on how ICANN’s complaint process can be modified.

The Non-Commercial Stakeholder Group (NCSG) started the session by demanding a response from the ICANN Board on how ICANN’s complaint process can be modified. The NSCG feel that the current process should be made more accountable, allow enough time for registrants to respond to allegations, and create a safer environment for registrants who might be victims of harassment and abuse.

Mr Jamie Hedlund, SVP, Contractual Compliance & Consumer Safeguards at ICANN replied that within contractual compliance, the complaints of abuse are handled very seriously. He added that these complaints are addressed as soon as they are presented to them.  He further mentioned that the staff work closely with anyone who feels like there has been abuse against them, be it the registrants, registrars, or registries, and encouraged anyone who feels like they are the victims of abuse to bring those issues forward.

The Board replied that ICANN can only act within its mission and is not actually the place for solving issues on content and copyright. They added that the confusion over what ICANN’s role is adds friction, and encouraged communication between the concerned parties to solve the issues outside of ICANN to reach a solution.

The NSCG raised the issue of increasing transparency within ICANN to enhance community participation and understanding. The Board replied that transparency is a major priority and added that the Board's working group on trust, set up in Helsinki, is aimed at increasing the trust of the community. They added that they are exploring methods of engaging with the community, such as by explaining what that Board does to the community, and by reaching out to the community within their own ecosystem in order to address and explain the decision-making process.

The NCSG also raised the issue of Public Interest Commitments (PIC) in the new gTLD registry agreement, which they see as contradicting the consensus processes. Furthermore, they added that this overrides the many hours of volunteer effort, time, research drafting, editing and reviewing spent creating the agreement, and how this should be prevented from happening again, since it harms the multistakeholder model. The Board assured them that these valid concerns will be addressed based on the specifics of the issue.

On the issue of capacity building, the Board added that they are looking at ways to leverage both the Fellowship and the NextGen@ICANN programmes to support community building. They indicated that although this does not solve the immediate problems, efforts are in place to address the long term concerns regarding community development. 

Krishna Kumar Rajamannar

The session focussed on addressing the concerns of the Commercial Stakeholder Group of the Generic Names Supporting Organizations (GNSO).

The session focussed on addressing the concerns of the Commercial Stakeholder Group of the Generic Names Supporting Organizations (GNSO). The Internet Service Providers and Connectivity Providers (ISPCP) highlighted the lack of response to their letter on Digital Object Architecture  (DOA). The ISPCP then raised the issue of the overlapping of key sessions that place the community under work and time pressure. They added that there are many conflicts in the meetings leading to the community suffering from overwork. The ISPCP suggested conducting some of the sessions with a historical background at alternate settings, including increasing remote participation and cutting down on meetings with sparse participation.

The ISPCP pointed to the number of reviews that are scheduled and questioned the value of scheduling one review after another. They consider this to be very resource intensive with little result. They feel that this is not inclusive and leads to a very narrow line of comments from people who are affected.  The ICANN Board then extensively discussed the issue of DOA and the reply to the ISPCP. They promised that a reply to the letter will be sent soon. They also acknowledged that the community is being overworked and said that actions will be taken to address the issue.

The Business Constituency (BC) pointed to the lack of transparency in the staffing process and their proposed inputs on the new gTLD registries. The BC pointed out that with no substantive community inputs, the ICANN staff is playing the lead role in various process. They feel that this contradicts the ICANN Board's commitment to transparency, accountability and being neutral. The BC demanded assurance from the Board that the comments and perspective of the community will be respected. The BC also asked the Board and the staff to consult with the community before they get into negotiations. The Board replied that they have taken into account the comments on transparency and accountability, and that they are looking at ways to enhance the transparency mechanism and also request from the community to understand the fundamental purpose of the contractual documents.

The BC then raised the issue of the Open Data Initiative (ODI) and having access to the data. The Board replied saying that collecting data through the ODI costs time, money and resources and advised the BC to prioritise the data that they need and to be specific with their data requests. They added that they have enhanced the community's power by allowing the community to comment on and veto budget proposals. The BC expressed their appreciation for the outreach and awareness programme and the role played by ICANN.

To address the question on participation and diversity in the working groups, the Board said that they will support increasing the geographical diversity as a priority. The BC advised the Board to increase staff support for the community to address the issue of community burn-out. The BC further pointed out that there are instances where the community loses its morale and there is a need to keep the community energised in order to increase participation. 

Marília Maciel

The session was dedicated to the discussion of how to protect the acronyms of  International Governmental Organisations (IGOs).

The session was dedicated to the discussion of how to protect the acronyms of  International Governmental Organisations (IGOs). The discussion encompassed the following topics: a) which names or acronyms should be reserved; b) how to notify IGOs of the registration of a related name; c) the dispute resolution mechanism that could be used to resolve potentially competing legal processes; d) the appeal mechanism if the parties disagree with the results of that dispute resolution.

Mr Bruce Tonkin, ICANN Board, kickstarted the discussion by revising the narrow scope of ICANN’s mandate: to ensure the security and stability of the domain name system. He also listed some of the principles that guide the organisation, such as: the need to carry out its activities in conformity with the relevant principles of international law, international conventions and applicable local laws, while recognising that governments and public authorities are responsible for public policy and taking into account public policy advice. This should be done in a way that respects the multistakeholder decision-making process, ensuring that as many parties as possible are involved in assessing the global public interest.

With regard to applicable laws, the Generic Name Supporting Organization (GNSO) policy development process (PDP) is taking into account the Paris Convention for the protection of industrial property, which has some specific provisions that relate to the names and abbreviations of intergovernmental organisations, preventing third parties from getting a trademark against these names. The Article 6ter is only applicable to trademarks and its purpose is to prohibit the registration and use of trademarks that are identical to or present certain similarity with the name or official signs of an IGO.

The current status of discussions is the following, when it comes to the reservation of names and acronyms:

  • Names: the ICANN Board has approved permanently withholding from registration at the second level.
  • Acronyms: the Board has approved interim protections for the acronyms in gTLDs. At this stage, the current prevailing view seems to be that acronyms have multiple uses, they are not owned by any one party and therefore it is not appropriate to reserve them in advance.

It is important to note, however, that both of these provisions do not protect names in gTLDs registered or top level names created prior to 2012. This means that there is no current protection for com, net, org, biz, info, name, moby, for example. One of the reasons that justify a policy development process is to make sure that the approach is applied to all gTLDs.

An additional complexity is that acronyms are not unique. For example, AU is the acronym for the African Union and that is also the country code for Australia. Many companies use AU as a designation to indicate their Australian operations.

The next topic of discussion was a mechanism that would let IGOs know when an undue registration happens. In this regard, suggestions were received from both the GNSO and the Governmental Advisory Committee (GAC). Both agree with the idea of a notification period, based on the experience of trademark protection, but the issue is how this notification should be done, to whom and for how long. The model of a 90-day 'Sunrise period’, proposed by the GNSO, was not accepted by the GAC because the opportunity for abusing a name may come at any time. For the GAC, a permanent notification mechanism should be preferable.

An adaptation of the 90-day period gained traction during the session and it was also suggested that ICANN could be a service provider for giving notification that an IGO name has gone into the DNS. This 90-day approach would allow use of the model of existing mechanisms and avoid re-opening a PDP. When it comes to potential dispute resolution mechanisms applying to IGO-related names, it was felt by some participants that it would be more pragmatic to give IGOs easier access to the existing improved system, unless there is a legal opinion that IGOs would need a separate system because of their immunity.

When it comes to appeals, the prevailing opinion seemed to be that ICANN’s curative rights processes are supplements to existing laws and that ICANN has no authority to compel registrants to submit to arbitration with no legal appeal. What would happen with regards to IGO’s immunity from national judicial process is an issue that deserves further discussion. 

Sorina Teleanu

The Governmental Advisory Committee (GAC) held several discussions throughout the week on issues related to new generic top-level domains (gTLDs). Governments explored several topics considered to be of high priority (e.g. community applications, geographic names, applicant support). They also engaged in exchanges with the New gTLD Subsequent Procedures Policy Development Process (PDP) Working Group (WG) (established within the framework of ICANN’s Generic Names Supporting Organization (GNSO) with the aim to determine whether any changes should be made to the new gTLD policy recommendations).

The GAC’s contribution to the New gTLD Subsequent PDP WG

The WG explained that it was collecting input on and exploring substantive issues, within the framework of four work tracks: overall process, support, and outreach; legal, regulatory, and contractual requirements; string contention objections and disputes; and Internationalised Domain Names and technical and operational issues. Several questions related to this issues have been prepared by the group, and the community will soon be invited to provide comments. Early input from the GAC will be welcome, and not necessarily in the shape of formal GAC advice (as elaborating such advice could be a rather lengthy process).

A question was raised as to whether previous GAC advice on new gTLD issues has been taken into account by the WG. In response, it was said that the WG has been considering GAC’s advice, but that, as it explores issues that have not been previously tackled by governments, additional input would be welcome. Several examples were given of issues on which GAC could provide feedback, such as applicant support, categories of new gTLDs, and community applications. These and other issues were discussed in more detail, as outlined below.

Outreach and applicant support

Governments expressed concerns regarding the fact that there were very few applications from developing countries during the 2012 round. Although entities from such countries could have applied for support, this opportunity was not extensively taken advantage of. The WG is paying careful consideration to this issue, looking at questions such as: How to make sure that more applicants are aware of and apply for support? What other issues should be improved when it comes to applicant support?

Geographic names

Another area of concern for governments is related to the use of geographic names as gTLDs. As there are several efforts within the ICANN community dedicated to exploring this issue (including, but not limited to the GAC and the PDP WG), a joint working session is planned for the upcoming Johannesburg ICANN meeting, in June 2017.

Categories of gTLDs

As part of its advice related to the 2012 round of new gTLD applications, the GAC requested that the categories of gTLDs be more clearly separated. The possibility of introducing new categories of gTLDs (in addition to, for example, the brand and community applications, more or less recognised as part of the 2012 round) is now being discussed by the WG, which is trying to determine the impact such a change would have on the application, evaluation, and contracting process. The group is also discussing whether, in case there are clearly defined categories of gTLDs, there should be any prioritisation for some of them. For example, as brand and geographic names are seen by some as among the most sustainable types of new gTLDs, should applications for such gTLDs be prioritised during the evaluation process?

Community TLDs

A presentation was delivered on a report commissioned by the Council of Europe (CoE) on the issue of community-based applications (CBAs). The report focuses on ICANN’s policies and procedures concerning CBAs, and CBA-related opportunities and challenges from a human rights perspective. One of the main findings of the report was that it is insufficiently clear on which public interest values are served by CBAs and which categories of individuals or groups should be regarded as communities. Several recommendations are included in the report, on issues such as: the definition of the term ‘community’; community objections (for gTLDs representing names of relevance for certain communities); community priority evaluation; accountability mechanisms; and other concepts for subsequent gTLD rounds (e.g. considering community applications first; inviting applications in staggered batches to better manage workflow; developing an entirely different community track which would include restrictions to ensure applicants are accountable to their communities and provide real benefit to them).

GAC members emphasised the need to further reflect on what kind of changes should be implemented for new application rounds, in order to make sure that the public interest will be achieved in the end. It was also mentioned that community and geographic TLDs could be the ones to be most relevant in the future.

The CoE explained that it did not expect the GAC to endorse the recommendations outlined in the report, but rather to suggest that these recommendations are considered in the context of the New gTLD Subsequent Procedures PDP.

Other issues raised during the discussions were related to:

  • Rights protection mechanisms (aimed at ensuring the protection of intellectual property rights when introducing new gTLDs). The results of the current review of existing mechanisms will feed into the subsequent rounds PDP.
  • Application fees. Lowering the fees related to applying for new gTLDs could represent an incentive for small and medium-sized enterprises to enter the TLD market. Although, during the 2012 round, there was a process for reducing the fees for some categories of applicants, this was not taken advantage of. The process will therefore need to be further analysed in order to determine how it can be improved.
  • Applications still not finalised. At the moment, some 90 new gTLD applicants have yet to finalise their application process, for various reasons. Should a new round of new gTLDs be launched nevertheless? On the one side, it was said that there is no need to stop a new round until these cases are finalised, and that the only measure that could be taken with regard to these applications is to make sure that no one else applies for the respective strings. On the other hand, it was outlined that these remaining applications are the problematic ones, and that maybe it would be wise to wait for their finalisation, and apply any lessons learnt to subsequent new gTLD rounds.

The GAC will continue to explore these and other issues, and to engage with the New gTLD Subsequent Procedures PDP.

Sorina Teleanu

Throughout the week, the Governmental Advisory Committee (GAC) held several discussions on issues related to the on-goin

Throughout the week, the Governmental Advisory Committee (GAC) held several discussions on issues related to the on-going work on enhancing the accountability of ICANN.

At the start of the discussions, the GAC Secretariat gave an overview of the current activities undertaken in the context of the Work Stream (WS2) of the Cross Community Working Group on ICANN Accountability (CCWG-Accountability). Priority areas for WS2 include: jurisdiction, human rights and international law, improving the accountability of ICANN supporting organisations (SOs) and advisory committees (ACs), transparency, and diversity. Although the group will not be able to keep the initial timeline for completing its work (June 2017), it will work on a proposal for a new timeline, to be presented to its chartering organisations.

Among the various priority areas for WS2, the complex work on jurisdiction issues looks into questions related to ICANN's jurisdiction, including how choice of jurisdiction and applicable laws for dispute settlement impact ICANN's accountability and the actual operation of policies. Some GAC members stressed that jurisdiction issues be tackled not only looking at what is already in place, but also keeping in mind situations that may arise in the future and would need to be addressed, in particular in relation to dispute settlement.

Discussions were held on possible GAC contributions to the various calls for input launched or about to be launched by the various CCWG sub-groups: a questionnaire on jurisdiction-related issues; a draft Framework of Interpretation to assist ICANN in applying relevant bylaws which require the organisation to respect internationally recognised human rights (draft to be soon finalised by the dedicated sub-group); a questionnaire for ACs/SOs, currently under development by the sub-group working on diversity; and draft recommendations for best practices in terms of ACs/SOs accountability (also under development within the dedicated group). While it would be important for individual GAC members to contribute to these calls, the group will also need to consider providing collective responses on issues such as diversity, human rights, and ACs/SOs accountability.

GAC also discussed issues related to the implementation of the new ICANN bylaws, which came into force after the transition of the IANA functions stewardship to the global Internet community. There are several issues to be addressed:

1. A new framework for how the Board is expected to respond to GAC advice

The bylaws define two levels of Board responses to GAC advice:

  • GAC advice (irrespective of whether it has been given with or without objections in the GAC). The advice shall be duly taken into account. If the Board acts in a manner that is not consistent with GAC advice, it had to inform the Committee and state the reasons for its decisions.
  • GAC consensus advice (full GAC consensus advice with no formal objections within the committee). Such advice may only be rejected by a vote of no less than 60% of the Board. In such a case, the Board and the GAC will try to find a mutually acceptable solution.

Governments held initial discussions on possible procedures to identify whether GAC advice is: based on a full consensus in the absence of formal objections (GAC consensus advice), or based on a broad agreement but with a small number of objections (GAC advice). Several approaches were presented, and they are to be further discussed by GAC intersessionally:

  • GAC consensus advice (full consensus, with no formal objections);
  • GAC advice/consensus advice (broad agreement, but with up to three formal objections);
  • GAC advice (broad agreement, but with a very small number of formal objections;
  • communication of range of views to the Board (more than 10 objections).

It was explained that, in the case of simple GAC advice, the committee has the possibility to define modalities for dealing with one or a very small number of objections, in order to prevent cases when one or a very small number of countries could block consensus. Several GAC members underlined the fact that GAC should simply continue to follow its operating principles and only adopt advice on the basis of consensus. There was, however, willingness to explore a possible mechanism to avoid a veto-blocking consensus within the committee.

2. GAC participation in the Empowered Community (EC)

The EC is a mechanism which allows the ICANN community (represented by its ACs and SOs) to hold ICANN accountable through a number of powers such as approving changes to fundamental bylaws and remove Board members. GAC is a decisional participant in the EC, and, in this context, it needs to address a number of issues:

  • Guiding principles for its participation in the EC. The proposal discussed by GAC members was for the committee to generally engage with issues that have direct or indirect public implications, and will participate in the early stages of the so-called ‘escalation process’ (steps towards the exercise of community powers) to assist resolution of the issue wherever feasible and appropriate.
  • Representation in the EC Administration (ECA), the collective entity of all decisional participants. The proposal is for the GAC Chair to represent the GAC in the ECA.
  • Engagement in the escalation process. The escalation process involves four stages: petition, conference call, community forum, and exercise of community power. With regard to the first three stages, it is proposed that the GAC either support or not oppose an issue moving forward. Involvement in the fourth stage would require a consensus GAC position. If consensus is not possible, GAC would abstain from any decision-making process in the EC.  

As discussions on these issues were only initial, governments will continue to explore them in the upcoming period.

The EC is about to be tested. In February, the Board adopted a decision to create a new committee for handling requests for reconsideration (appeals against ICANN decisions). This decision requires a change in the ICANN fundamental bylaws, which requires approval from the EC. It is expected that a part of the third stage in the escalation process (the community forum where decisional participants discuss the issue) will be held during ICANN 59 (June, Johannesburg). GAC members have agreed, in principle, to participate in the initial phases of the escalation process until the June meeting.

Sorina Teleanu

The joint meeting between the ICANN Board of Directors and the Governmental Advisory Committee (GAC) revolved around sev

The joint meeting between the ICANN Board of Directors and the Governmental Advisory Committee (GAC) revolved around several topics of particular interest for governments, including the use of two-letter country codes at second level (i.e. as domain names) in generic top-level domains (gTLDs).

In November 2016, the ICANN Board adopted a resolution authorising ICANN to allow new gTLD registry operators to allow the registration of domain names representing two-letter country codes, as long as the operators implement a set of required measures to avoid confusion with corresponding country codes. Such measures were described in a document released in December 2016 by ICANN’s Global Domains Division. Previous to this decision, GAC issued advice cautioning the Board that the release of two-letter country codes could create confusion among end-users in that they may interpret the domain names as being affiliated with a government or a country code TLD manager.

Many GAC members expressed concerns over the Board resolution, both in terms of process and substance, including:

  • The decision taken by the Board followed up on a policy development process that has been in place for a number of years, but rather dormant. It is unclear what determined the Board to take its decision at this specific point in time.
  • Following the Board resolution, it is no longer mandatory for gTLD registries to notify governments of the plans for their use of two-letter codes, nor are registries required to seek agreement of governments when releasing two-letter country codes at the second level. This is quite a significant change.
  • From a majority of GAC members, the Board decision represents a de facto rejection of GAC advice. While some of the countries do not have a problem with the decision per se, they still think that there have been flaws in the process. In addition, it would have been preferable for the Board to simply say that it has decided not to follow GAC advice.
  • There continue to be serious concerns among governments with regard to the potential for end-user confusion. Overall, the mitigation measures for avoiding confusion are either not working, or working in a way that is detrimental to governments. For example, one of these measures is for countries to register their country codes with new gTLD operators during the exclusive registration period. Some countries have tried to explore this option and found out that the costs would be bring undue financial burden.

The Board explained that it had examined the release of two-letter country codes in respect to ICANN’s mission, commitments, and shared values. In its view, the resolution is fully consistent with GAC advice. With regard to the possibility of confusion, there have been measures devised to mitigate such risks, and the Board finds them appropriate.

Moreover, it was said that countries do not own their country codes. These codes are designated at the top level on the basis of the ISO list for country codes. But at the second level there have already been registrations of domain names representing two-letter country codes in both legacy gTLDs and many ccTLDs. Some countries have underlined that it is not within the Board’s right or mandate to decide whether GAC members have rights over two character codes.

At the end of the discussions, the Board mentioned that it is willing to engage into discussions with GAC members that are uncomfortable with the decision, and discuss both the process and the substance, and why the Board thinks that it has acted in accordance with GAC advice. This does not mean that the decision will be renegotiated.

Other points touched on during the meeting were related to:

  • Confidentiality of GAC documents. For a long time, GAC thought that its internal communications were confidential, and that only sovereign governments had access to the content of such communication. Governments recently realised that, in certain circumstances, when someone challenges an ICANN decision and there is a legal procedure, documents need to be produced drawing on internal GAC communication. While being concerned about this issue, GAC is working  with ICANN on a solution.
  • New Board process for considering GAC advice. The ICANN Board is implementing a process allowing it to give more timely response to GAC advice. This will involve calls between GAC and the Board following the issuance of GAC advice. Questions will be prepared in advance of the calls, and there will be discussions aimed to assist the Board in fully and accurately understanding GAC advice before considering it.
  • Protection of names of intergovernmental organisations and of Red Cross/Red Crescent. On this issue, there has been conflicting GAC advice and Generic Names Supporting Organization (GNSO) recommendations (with the GAC asking for the protection of these names). The Board has facilitated discussions among the two groups on this issue. GAC expressed its appreciation for this kind of facilitation, and noted that it is looking forward to continue the discussion with a view to unlocking the situation. The Board mentioned that it is also important to find ways to avoid such blockage situations in the future.
  • Cross Community Working Group on ICANN Accountability (CCWG-Accountability) Work Stream (WS2). GAC and individual GAC members are seeking to actively participate in WS2, despite it being challenging to keep track of the multiple streams of work. The main topics of interest for governments include: the implementation of the ICANN bylaw changes resulting from the WS1, jurisdiction-related issues, diversity, and legitimacy.
Sorina Teleanu

The joint meeting between the Governmental Advisory

The joint meeting between the Governmental Advisory Committee (GAC) and the At-Large Advisory Committee (ALAC) was structured around five topics.

Update from GAC Working group on the protection of geographic names

The group focuses on how to improve the protection offered to geographic names in any future expansions of gTLDs. Currently, it discusses the elaboration of a set of best practices for new gTLDs in relation to geographic names. The main proposal is the development of a repository of terms, that would reveal stakes and interests of people, communities, or rights holders in particular names, at the beginning of the gTLD application process. This would allow potential applicants to find out about possible conflicts with regard to the strings they consider applying for. The proposal is to have the repository compiled by ICANN, while governments will input names. It could also benefit from lists of geographic names that are compiled by various international organisations.

The idea, still under discussion, has received both support and opposition. Some of the concerns include:

  • some strings have a multiple legitimate use and meaning;
  • there could be possible harm to free speech and legitimate commerce;
  • if the list is created, some governments may not be sending names to the database, as not all of them are aware of ICANN processes;
  • there is no established legal basis or accepted norm that would ensure predictability for new gTLD applicants.

The main argument in favour of such a repository is that it would help avoid future conflicts and litigations with regards to geographic names.

Community-based applications (CBAs) for new gTLDs

An overview was given of the Council of Europe (CoE) commissioned report on CBAs. The report analyses ICANN’s policies and procedures concerning CBAs, from a human rights perspective. The rationale for this report stems from the fact that CoE considers top-level domains as tools that enable people to communicate and access information; they are also important for the enjoyment of freedom of expression, assembly, and association, all of which should be enjoyed without discrimination. The report outlines a series of findings and recommendations, and the objective is to submit these recommendations for consideration in the context of the relevant policy development processes on new gTLD related issues.

For ALAC, it was disappointing to see that the process for CBAs has been set up as such a high bar that only few applicants could meet the requirements to qualify. For future rounds, it will be important to ensure that communities are actively supported to obtain gTLDs. It is possible that ALAC will support at least some of the recommendations in the CoE commissioned report.

GAC draft survey on underserved regions

Within the context of the GAC Underserved regions working group, a survey has been prepared with the aim to understand challenges and capacity needs of governments from under-served regions when it comes to participation in ICANN. The survey is also intended to help GAC respond directly and appropriately to such need, to increase the participation of under-served countries in GAC and broader ICANN processes. The survey is now targeted at GAC members, but the committee hopes that it will be expanded to the wider community, with support from ALAC and others.

ALAC and GAC have a shared goal when it comes to reaching out to underserved communities and trying to encourage and/or empower them to participate in ICANN processes. And synergies and forms of collaborations could be identified in this area.

At Large review

The At-Large community has undergone an organisational review process which resulted in a draft report outlining several recommendations. ALAC finds some of these recommendations easy to accept, while others are see not only be unacceptable, but dangerous to implement. Some recommendations are related to engagement, outreach, and the need to bring new people into At-large activities. ALAC noted that one challenge in outreach activities has always been related to being able to present ICANN in an understandable way, and that the community will try to identify new approaches.

During the discussions, concerns were raised over what some perceive as unsuccessful review processes within ICANN, mainly due to difficulty in finding external independent reviewers who can understand ICANN’s complexity.  One significant challenge when it comes to review processes is to achieve the right balance between an independent evaluator and an evaluator that understand what he/she is reviewing.

Cross Community Working Group on ICANN Accountability (CCWG-Accountability) Work Stream (WS2) - topics of joint interest

One topic of joint interest for both ALAC and GAC in WS 2 of CCWG is related to the issue of diversity within ICANN.

One concern expressed by ALAC was that there are still instances in which ICANN staff or even the Board considers that they do not have any obligations to parties other than the ones contributing money to ICANN. This is something the two committees could try to further explore, as they are both concerned about the public interest.

One comment made during the discussion was related to the 2012 round of new gTLD applications and the fact that the application and evaluation processes have demonstrated that the existing accountability mechanisms are not always working properly and can even be used for a purpose which is opposite to the one they were created for. As both ALAC and GAC are serving the public interest, the two committees could jointly look into such issues.

Marília Maciel

The New gTLD Program established auctions as a mechanism of last resort to resolve string contention.

The New gTLD Program established auctions as a mechanism of last resort to resolve string contention. Although most string contentions have been resolved through other means before reaching an auction conducted by ICANN's authorised auction service provider, significant funds have accrued as a result of several auctions.

These auction funds have been put aside by the ICANN Board, until there is a plan for the appropriate use of the funds. A drafting team composed of representatives of supporting organisations (SOs), advisory committees (ACs), and the Board was convened, and prepared the charter for the Cross-Community Working Group on new gTLD auction proceeds (CCWG), responsible to devise that plan.

The Chair, Mr Jonathan Robinson, started the meeting in Copenhagen with a recap of the CCWG charter provisions and the legal and fiduciary constraints that need to be observed by the WG. The charter has strong requirements with regards to avoiding potential conflicts of interests: statements of interest need to be filled by members, as well as declarations whether the members (or their organisations) plan to apply for funds. One of the main questions posed to the CCWG members was whether the group believes that ICANN or its constituencies should be able to apply for ICANN auction funds for the future.

There was also a recap of the goals and objectives of the group, as defined by the charter:

  • Developing a proposal for consideration by chartering organisations on a mechanism to be developed in order to allocate new gTLD auction proceeds.
  • Consider the scope of fund allocation under the necessary conditions to preserve ICANN’s tax status (Californian non-profit corporation).
  • The CCWG will not make decisions on who will receive the funds.

The focus of the group so far has been: a) to provide an assessment of CCWG members' skills and expertise, to identify the shortcomings on expertise that may require the supplement of external input; b) to identify topics that may require further briefings/information to ensure common understanding.

During the development of a work plan, the group reviewed the questions proposed by the charter to identify: Are any of them gating questions that need to be answered beforehand? Are any key questions missing? Is any external expertise required to address charter questions? The mapping out of a possible timeline.

Ms Samantha Eisner, Deputy General Counsel at ICANN, started her presentation by explaining that any funds that ICANN spends need to be within the remit of its mission. ICANN also proposed some guidelines and principles for consideration in the work of the group:

  • Consistency with ICANN’s mission as set out in bylaws.
  • Private benefit concerns. ICANN may only spend the funds for public benefit purpose, not direct to a private actor. The group needs to build in protection with regards to that.
  • Because of the US tax exemption status, the funds must not be used for political activity. They should not be used for lobbying activities, such as attempts to influence legislation.
  • Decisions have to be taken without a conflict of interest. ICANN is prohibited from benefiting insiders to ICANN, such as the staff or the Board. Community conflicts of interest should also be taken into account.
  • There are several ways in which the CCWG can help maintain the integrity of the process: transparent assessments of how the recommendations contribute to this integrity; considering the use of established mechanisms for disbursing the funds, as opposed to calling for development of untested modalities; recommendations that enhance transparency; etc.
  • Financial and fiduciary concerns. The Board and officers of ICANN hold fiduciary duties to the organisation to make sure that self-dealing does not occur and their private interests are not benefited through ICANN’s decision making and actions.

A letter from the ICANN Board also details some specific considerations for the group, mentioning certain mechanisms and principles that the Board would like to see considered:

  • Legal and fiduciary constraints of ICANN
  • Important items to the cost of operation of the CCWG:
    • The CCWG should run as a project with proper budget and schedule, based on a working plan.
    • Auction proceeds will remain curtained off until the next phase, when an approved plan for distribution is in place;
    • Once a system is set up for distribution, the cost of administering the distribution of the funds will naturally come out of the auction proceeds.
    • The CCWG must cast a wide net: the focus should be on general principles and objectives.
    • Conflicts of interest need to be carefully assessed.

The group conducted a survey as an initial assessment of the charter to determine whether some of the questions contained in the document should be considered fundamental, and whether external expertise may be needed to reply to some of the questions.

The next steps for the group are: a) review the letter from the Board in order to provide an equally substantive response; b) analyse the result of the survey and match it with the questions in the charter.

The deck of slides presented during the meeting and the full transcript of the session are available online. 

Marília Maciel

The session aimed to start a strategic dialogue on the importance of data and metrics in the context of ICANN, especially to enable: 1. evidence based policy making; 2.

The session aimed to start a strategic dialogue on the importance of data and metrics in the context of ICANN, especially to enable: 1. evidence based policy making; 2. organisational and community development; 3. a cleaner and safer DNS; 4. the development of new and better businesses; 5. enhancing public trust.

ICANN has already begun to work on some initiatives in this area with the gTLD Marketplace Health Index and the Identifier Technology Health Indicators. But so far there is no strategic thinking around data and the issue is not 'owned' at the most senior levels.

The speakers agreed that requests for more and better data are being made from different parts of the organisation, in initiatives such as the gTLD Marketplace Health Index – which aims to measure market concentration in different sectors of the new gTLD market – and during the work of the Competition, Consumer Trust and Consumer Choice (CCT) Review Team. Thirty out of fifty recommendations made by the CCT Review Team are data-related.

Data is very important for evidence-based policy development at ICANN: it can help to identify problems, assess how serious they are, and prioritise them. It also allows for an assessment of the implementation – whether the policy was successful in solving the problem or not.

In spite of the importance of data, a large amount of it is not public. Some actors that operate within the ICANN framework own their databases and define how and by whom the information can be accessed.

Building data-driven businesses within the context of ICANN is important as well. Data can reveal important elements in the DNS market, such as market activity and potential slow-down, market growth, competition levels, deficit of innovation, and the perception of registrants. It can also provide market intelligence. For example: for a long time it was believed that registrants prefer shorter domain names, however, recent data suggests that individuals prefer longer and rather descriptive domains.

Data is also important for ICANN and its community to be able to tell their organisational story. There is little information, for example, on the number of jobs directly and indirectly created by the domain name industry, and the levels of community engagement. Initiatives put forth by other organisations, such as the Internet Measurement Project of the Internet Society, have successfully used data to tell a narrative. ICANN needs to use data to tell its story.

In order to bring data to the core of ICANN’s activities, some steps are necessary, such as: a) hiring a data specialist; b) adjusting community expectations when it comes to balancing privacy and openness; c) putting data governance frameworks in place.

With that in mind, ICANN recently launched an open data initiative. The project tasks ICANN staff with the mission of preparing ICANN to open data standards, to improve the way ICANN generates and collects data, and to devise a plan so that the collected data is made public over time.

Some challenges to achieving these goals within the context of ICANN are: a) data has been collected for a long time in different formats; b) there is no document planning framework, there are distributed curation and disperse formats; c) the initiative is not a priority in the budget; d) there is need to reconcile privacy and the possibility of personally identifying data with contractual obligations of the parties involved; e) re-publishing data acquired from third parties presents constraints.

The open data project will start with a pilot, with the following components: a) identify ICANN managed data; b) deploy the pilot project; c) determine a process for making data public; d) listen to the community for prioritisation hints. 

Marília Maciel

The session was organised by ICANN’s Global Domains Division (GDD) and aimed to provide updates on the progress of several gTLD-related reviews, their key milestones and next steps. 

The session was organised by ICANN’s Global Domains Division (GDD) and aimed to provide updates on the progress of several gTLD-related reviews, their key milestones and next steps. 

The Competition, Consumer Trust and Consumer Choice Review (CCT) was the first process to be discussed. This review aims to assess whether and to which extent the New gTLD Program has enhanced competition in the DNS market, affected consumer trust and increased consumer choice. In the course of their work, CCT members had the goal to be methodologically data-driven and support their conclusions on factual data. They also tried to identify the metrics that could be used to evaluate the implementation of their recommendations.

Some highlights from the conclusions of the report were presented:

  • Competition increased to a certain extent;
  • There was an increase in the number of disputes over domain names, which can be noticed by an increase in Universal Domain Dispute Resolution (UDRP) and Universal Rapid Suspension (URS) procedures;
  • Safeguards were successful to mitigate degradation of consumer trust, particularly trademark safeguards;
  • ICANN needs to be a better data collector, so future reviews can be more data-driven;
  • There was low participation from the global south in the first round. If the community decides that it is a priority to correct this issue, urgent measures need to be put in place.

CCT’s Initial Report is open for public comment from anyone interested until 27 April. A webinar is going to be organised, probably on 29 March, to present the main findings of the report.

The New gTLD Subsequent Procedures Working Group was the second new gTLD related process to be discussed. In December 2015, the Generic Names Supporting Organisation (GNSO) approved the creation of the working group on new gTLD subsequent procedures, with the aim of reviewing and improving, if necessary, the 2007 GNSO’s policy recommendations on the introduction of new gTLDs.

The WG clustered its substantive discussions in two areas: a discussion on overarching issues and a discussion based on working tracks.

The four WG’s working tracks encompass the most substantive work of the WG and are dedicated to the following topics:

  • Work track 1: Overall process, support for applicants and outreach
  • Work track 2: Legal and regulatory aspects and contractual obligations
  • Work track 3: String contention, objections and disputes
  • Work track 4: Internationalised domain names – technical and operational aspects.

Questions regarding each of the tracks have been developed and will be put up for public comment. Respondents can choose to answer only a few questions from the questionnaire.

The initial report from the new gTLD subsequent procedures working group is expected to be published at the end of 2017. Related policy development processes will feed into the work of this working group.

The Cross-Community Working Group on Use of Country/Territory Names as TLDs was the third process to the analysed. This CCWG was chartered by the Country Code Names Supporting Organisation (ccNSO) and the GNSO to: a) review the current status of representations of country and territory names, as they exist under current ICANN policies, guidelines and procedures; b) provide advice regarding the feasibility of developing a consistent and uniform definitional framework that could be applicable across the respective supporting organisations (SOs) and advisory committees (ACs).

The discussion in the CCWG started with two letter-codes as top-level domains. There was an agreement among participants in reserving two letters at the top level of the DNS exclusively for the country code top-level domains (ccTLDs). The rationale behind this was that ICANN should not be placed in the position of having to decide what is a country: if a new country is created, for example, corresponding two-letter TLDs should be available. The use of country and territory names at a second or other level is excluded from the scope of the CCWG.

When it comes to the reservation of three-letter TLDs, there was no consensus among CCWG participants. As a result, the WG did not make further progress on discussing country and territory names. The WG produced an initial report of its findings and recommendations which is available for public comment until 21 April.

The Working Group dedicated to the Review of All Rights Protection Mechanisms (RPMs) in All gTLDs was created by the GNSO to conduct a review of RPMs in two phases: Phase One will focus on a review of all the RPMs that were developed for the New gTLD Program, and Phase Two will focus on a review of the Uniform Dispute Resolution Policy (UDRP).

The review of the Post-Delegation Dispute-Resolution Policy (PDDRP), a mechanism through which trademark owners bring an action against DNS operators, has been concluded. The working group recommended, for example, that in some cases trademark holders should be able to come together and file a joint complaint against a registry. The review of the Trademark Clearinghouse (TMHC) is close to being completed. It was recommended that having more than one Clearinghouse operator would increase competition.

The working group is expected to wrap-up the review of the Clearinghouse in next few days and start the review of the Sunrise registration rights and Trademark claiming notice.

The Continuous data driven study on root stability (CDAR study) was the last new gTLD-related process to be analysed. The group focused on two main questions: Did the delegation degrade the security and stability of the root DNS system? Can any degradation occur in the future?

The draft CDAR report was published before ICANN 57 (Hyderabad). The study did not notice any degradation of the security and stability of the root as a result of the introduction of new gTLDs. 

Agustina Callegari

The session was the first meeting between the ICANN Board and the Customer Standing Committee (CSC) after the Internet Assigned Numbers Authority (IANA) stewardship transition.

Mr Byron Holland, member of the CSC appointed by the Country Code Names Supporting Organisation (ccNSO), started by explaining the main mission of the CSC according to its Charter. He highlighted that the CSC is responsible for monitoring the Public Technical Identifiers' (PTI) performance of the IANA naming function, against the service level expectations in the IANA Naming Function Contract. He also mentioned other responsibilities of the CSC such as participating in reporting, monitoring, conducting surveys, and informing the community about issues related to the performance of the IANA functions. According to him, this role has been assumed according to plan.

Holland explained in detail how the CSC does its work through monthly meetings, which usually take place in the middle of each month. At the meeting, CSC members receive and discuss the PTI report on 63 specific metrics, and decide on the CSC report. He also specified that the meetings are open, that records and proceedings are published on their website, and that the reports are sent to an extensive distribution list. For people who want to stay informed on this issue but do not have time to read a detailed report, he recommended the monthly report, which is only about a page long and gives an update of the IANA functions performance. 

Regarding the CSC reports, Holland explained that the CSC rates the overall performance of the PTI based on a number of Service Level Expectations (SLE) achieved excellent when all the expectations are achieved; satisfactory when not all are achieved – but there is no need for concern; and, needs improvement when actions are necessary. He added that the CSC also reports on metrics that the CSC is tracking closely, on how the SLEs could be adjusted, and on the numbers of complaints.

Holland also listed the CSC activities since October 2016:

  • Reviewed four PTI reports and issued four monthly CSC reports.
  • Discussed the PTIs/IANA department's 2016 customer survey
  • Started a discussion about PTI related complaints and processes from the survey
  • Developed internal procedures
  • Agreed on the short-term priorities
  • Approved the dashboard that the PTI has put up
  • Launched the CSC website

To summarise, Holland said that the PTI performance has been very good with only some minor metrics missed and no consumer service impact or operational problems. He also said that the CEO of ICANN has initiated a dialogue with the CSC chair, and that the ICANN community needs to plan for reviews.

After that, the floor was opened to questions and comments from Board members and from the audience. Mr Steve Crocker, Chair of the ICANN Boad, referred to the importance of understanding whether the 63 specific metrics are relevant. Mr Göran Marby, ICANN CEO and President, briefly explained the importance of the meeting between the two external Board Members of the PTI and himself as a way of formalising the context between the organisations. Among other questions, Mr Khaled Koubaa, ICANN Board member, asked about the review of the effectiveness of the CSC (to begin by October 2018) and whether a process has been put in place by ccNSO and the Generic Names Supporting Organization (GNSO) to work on this review. Holland responded that no work has been undertaken within ccNSO in this regard, but that actions are to be expected. 

Agustina Callegari

The Internet Governance Public Session focused on the following topics: the work of ICANN's Cross Community Working Group on Internet Governance (CCWG-IG); the main Internet governance issues for 2

The Internet Governance Public Session focused on the following topics: the work of ICANN's Cross Community Working Group on Internet Governance (CCWG-IG); the main Internet governance issues for 2017 and the primary outcomes on the IG front in 2016; and, the IG priorities for the CCWG-IG and ICANN, taking into account the new global political agenda.

The session was moderated by Mr Olivier Crepin-Leblond, Chair of the European At-Large Organisation (EURALO) at ICANN, who, after introducing the items on the agenda, talked about the work that the CCWG-IG has done. The main objective of the CCWG-IG is to coordinate, facilitate, and increase the participation of the ICANN community in discussions and processes pertaining to Internet governance. He talked about the new Charter draft. He said that since it has only recently been submitted, there has so far not been any feedback from the chartering organisations, i.e the Country Code Names Supporting Organization (ccNSO), Generic Names Supporting Organization (GNSO), and At-Large Advisory Committee (ALAC).

Ms Marilyn Cade, Principal and CEO of mCADE, ICT Strategies, highlighted the different aspects of the CCWG-IG work, as well as the importance of continuing to consider emerging issues that could affect ICANN´s mission. She also remarked that the WG is open to new participants, both active members and observers, and she invited those present at the session to join.

Crepin-Leblond continued the discussion with the Charter review process, and provided information on where to find documents such as member lists, previous call records, and next calls and events on the CCWG-IG webpage. He also mentioned the work and efforts of the members to keep the group updated on a variety of issues that are part of the Internet governance ecosystem.

Ambassador Benedicto Fonseca mentioned the WSIS+10 review process and talked about the Working Group on Enhanced Cooperation (WGEC). He reminded the audience that the WGEC comes from the Tunis Agenda, but that there are different interpretations of the concept. However, he stressed that despite the different interpretations, there has been an increase in co-operation on different levels, but that there are still improvements to be made. Regarding the work of the WGEC, he said that the second meeting took place on 26-27 January 2017 in Geneva, and that the third one will be held on 3-5 May 2017 at the same venue. He also remarked that there will be remote participation.

Cade added that the annual WSIS Forum is important for ICANN, as it is a great opportunity for the ICANN Board Members, the CEO, and high-level staff be in contact with the ministries of different countries.

Mr Nigel Hickson, Vice President, Global Stakeholder Engagement at ICANN, spoke about the two International Telecommunication Regulations (ITRs) – one from 1988 and another from 2012 – at the International Telecommunication Union (ITU). He explained that problems arise when a country applies both. In addition, he said that the next World Telecommunication Development Conference (WTDC) will take place from 9 to 20 October 2017 in Buenos Aires.

Mr Jorge Cancio, Senior Legal Adviser to the Swiss Government, talked about the twelfth annual meeting of the Internet Governance Forum (IGF) which will be held in Geneva on 18–21 December 2017, and invited the community to submit workshop proposal for this year's agenda.

Mr Markus Kummer, ICANN Board member, mentioned that the IGF is funded by voluntary contributions and that ICANN makes contributions to this trust fund. He also said that the IGF is a good place for recruiting new  ICANN community members.

For the last topic on the agenda, Ms Tatiana Tropina, Senior Researcher at the Max Planck Institute for Foreign and International Criminal Law, and member of the Executive Committee of the Non Commercial Users Constituency (NCUC), highlighted issues related to Internet governance that are important for ICANN, such as cybersecurity. She stressed that ICANN does not need to get involved in all these matters, but it should be aware of the developments and how they could impact the multistakeholder model. She remarked that the ICANN community have proved that the model works. 

Amrita Choudhury

The public forum is a platform where the community can pose the ICANN Board members questions, either in person or remotely. Two such fora were organised during ICANN58.

Topics which dominated the public fora include: ICANN's jurisdiction, the next round of applications for generic top-level domains (gTLDs), delays in the process of reviewing the 2012 round of new gTLDs, diversity, ICANN's engagement, transparency, data security and privacy, and the ICANN Board's priorities.

In regards to ICANN's jurisdiction, Mr Steve Crocker, Chair of the ICANN Board, confirmed that ICANN would remain based in the USA and that the sub-group working on ICANN's jurisdiction (in the framework of Work Stream 2 of the Cross Community Working Group on ICANN Accountability – CCWG-Accountability) would be discussing ways to handle issues, should they arise in the future.

Language diversity was highlighted by several community members, and it was suggested that there should be interpretation services at the meetings in the local host language. ICANN community members were encouraged to join the CCWG Accountability sub-group on diversity, to enhance the discussions.

Issues such as the ICANN's engagement, particularly in underserved regions, such as small islands, and the broadening of participation, especially of the next generation, were raised by several participants. The importance of measuring the engagement of participants in ICANN, especially in the subsequent meetings, was highlighted by one community member. Responding to a question on ICANN's initiatives  to increase the engagement of the next generation, Mr Ram Mohan, ICANN Board member, shared examples of a hackathon event (Hack2Build) that took place during ICANN57, while Ms Rinalia Abdul Rahim, ICANN Board member, explained how the DotAsia pilot lead to the formation of the NextGen programme. On the question of how to increase engagement in underserved areas and strengthen ICANN's long term engagement plans, Mr Göran Marby, ICANN President and CEO, said that ICANN would base their plans for improving regional support on what they learn. Creating greater awareness and the continued engagement of ICANN was emphasised by participants.

On the issue of privacy and security of data, the need for stricter rules concerning the handling of private data in the context of Whois services was one of the issues raised byparticipants. Ms Becky Burr, ICANN Board member, said that while there is an ongoing discussion on the way in which Whois data is made available and its legitimate use, personal data, including Whois data, can only be processed for legitimate purposes.

ICANN’s continued engagement with Data Protection Authorities (DPAs), and the setting up a data protection or privacy officer, especially to comply with the European data protection regulations, were some of the recommendations made by participants during the public fora. Burr said that the engagements with DPAs would continue and that while ICANN is going through the compliance check-list, the ICANN community is also actively looking at the developments.

A lack of clarity with regard to the next round of gTLDs was addressed by several community members. However, no timeline for the next round of gTLDs was shared by the Board members. On issues related to specific marketing and awareness raising activities in relation to a subsequent round of gTLDs, Mr Akram Atallah, Director of the Global Domains Division at ICANN, said that such activities would be undertaken if the community so decides.

In response to the dissatisfaction that was expressed by some with regard to a Board resolution allowing the registration of two character codes as second level domain names in the new gTLDs, Crocker stated that the matter continues to be under discussion, due to its sensitive and contentious nature. Furthermore, Mr Thomas Schneider, Chair of the Governmental Advisory Committee (GAC) noted that the issue has been of great concern for a large number of GAC members, and that these governments hope they can work together with new gTLD registries and try to find a solution acceptable to all parties.

Addressing the concerns raised about possible unfair competition arising between registrars in Europe and other regions owing to ICANN's plan to designate one domain name data escrow provider at subsidy, Atallah said that after this initiative is implemented in Europe, other regions would be considered as well.

On the questions regarding status and delay of the independent review related to the Community Priority Evaluation (CPE) and the independent review process, the Board commented that the review process was ongoing and that they will be able to respond based on the outcome of the review.

Two participants raised questions regarding the complaint mechanism process at ICANN.  Marby stated that going forward, complaints would be managed by a complaints officer. Mr John Jeffrey, General Counsel, elaborated on the role of the complaints officer and the ombudsman, and said that the process of filing a complaint has yet to be decided on.

On the question related to the priorities of the Board for this year, Mr Cherine Chalaby, ICANN Board member, explained that the Board would be working on three 'clusters'. These include various priorities, among which: improving the Board relationship with the community, with points such as transparency of the Board, increased engagement, increased diversity, and efficient use of volunteers; improving the efficiency and effectiveness of the Board; improving financial stability; enhance the effectiveness of review processes; supporting the ICANN CEO through the creation of an environment where the CEO succeeds; progressing on community public policy issues; progressing on technical issues; and supporting the Nominating Committee (NomCom).

Questions were raised related to transparency in ICANN's selection process of the location for ICANN meetings, the existence of closed sessions, and the expenditure report on travel support to community members to attend various meetings. There was also a request for staff to ensure appropriate planning for the ICANN59 joint session between the GAC, the Generic Names Supporting Organization (GNSO) and the Country Code Names Supporting Organization (ccNSO), on geographic names (i.e. avoiding conflicts with other important sessions). It was observed that there were no sessions on the Public Technical Identifiers during ICANN58.

The involvement of Board members in Policy Development Processes (PDP) was also raised, and it was clarified that, while there is no rule prohibiting Board members to participate in such processes, this has not traditionally been done. The Board was also asked whether it is aware of the various upcoming Internet governance events and activities, and Mr Markus Kummer, ICANN Board Member, confirmed the Board's awareness by talking about their working group on Internet governance. Apart from ICANN taking part in various events, he reaffirmed ICANN's continued support of the Internet Governance Forum (IGF), including regional and national IGFs.

Finally, ICANN was applauded for its statement about US Executive Order 13769, titled Protecting the Nation from Foreign Terrorist Entry into the United States, its fellowship programme, and the criteria being developed for choosing arbitrators for the Independent Review Panel.

Agustina Callegari

The ICANN58 opening ceremony took place 18 years after ICANN held its first meeting.

The ICANN58 opening ceremony took place 18 years after ICANN held its first meeting. Mr Jean-Jacques Sahel, Vice President, Europe (Global Stakeholder Engagement) at ICANN, started the meeting off by presenting the speakers.

The first speaker was Dr Steve Crocker, Chair of the ICANN Board of Directors, who shared some interesting facts about Denmark, such as it being one of the most connected countries in the world: Danish people are largely accessing the Internet through mobile devices linked to the nation's 100% 4G cellular systems, which last year facilitated a 97% Internet penetration rate.

Crocker introduced the key topic of the ceremony: transparency. He said that the ICANN Board is increasing its transparency and that they are engaged in a pilot programme to a consider opening some of their sessions. He also mentioned that the organisation's direction is clear and that their top priorities are to continue strengthening their technical orientation and the security of the domain name system (DNS). Crocker finished off by highlighting the work of the community towards this aim and he emphasised that empathy and mutual respect should be the basis of all discussions.

Ms Mette Bock, Danish Minister for Culture, talked about the use and importance of the Internet for Danish people. She said that the country is in the top ten of the UN ICT development index and that Danish people are the most advanced Internet Users in the European Union. She underlined the key and critical role that ICANN plays in coordinating and developing the DNS. She further remarked on the importance of new accountability mechanisms within ICANN. Bock thanked the community for their work during the IANA stewardship transition process.

Sahel then gave the floor to Prof. Henrik Udsen, Chair of the Danish Internet Forum (DIFO) & DK Hostmaster, who noted that the multistakeholder model is a vital component in creating a robust solution to many challenges that we currently face, both at a national and international level. An example is the fight against Internet crime, in which the DNS plays an important role.

The next speaker was Mr Göran Marby, President and CEO of ICANN, who started off by highlighting the power of the Internet in giving opportunities to people who would otherwise have none. However, he highlighted that users' needs are changing and that we need to take these needs into account. He went on to share some of the actions that ICANN is taking in order to be more transparent. One of them is the recent creation of the Complaints Office as an additional way for the ICANN organisation to be accountable for and transparent about its performance. Marby explained that it will work with ICANN's various internal complaints processes to assist improvements and collect data about complaints received across the organisation.

The last speaker was Mr David Conrad, ICANN Senior Vice President & Chief Technology Officer, who announced that on 11 October 2017, ICANN will be changing the root zone key signing key (KSK). Before this happens, DNS operators who have enabled DNS Security Extensions (DNSSEC) validation must update their configurations. To assist operators, ICANN has launched a testbed for them to determine the readiness to support the KSK rollover.

At the end of the ceremony, participants were treated to a special performance by the Tivoli Youth Guard.

Agustina Callegari

The Governmental Advisory Committee (GAC) met with the Country Code Name Supporting Organisation (ccNSO) to discuss a variety of topics such as various policy development processes (PDP); the retirement of country code top-level domains (ccTLDs); the delegation, revocation and retirement of ccTLDs; as well as an update by the Cross Community Working Group (CWG) on the use of country and territory names as TLDs (CWG-UCTN).

Ms Katrina Sataki, Chair of the ccNSO, opened the meeting and introduced Mr Nigel Roberts, ccNSO Councillor, who talked about the ccNSO PDP to address the lack of policy with respect to the retirement of ccTLDs and the introduction of a review mechanism on issues pertaining to the delegation, transfer, revocation and retirement of ccTLDs.

During ICANN57, in November 2016, the ccNSO Council resolved to appoint a drafting team to develop a charter and delineate the issues pertaining to the review mechanism and retirement of ccTLDs. To that end, a working group to address this issue will be presented to the ccNSO and the Council will be asked to formally start the PDP.

Mr Bart Boswinkel, Sr Director, ccNSO Policy Development Support, ICANN, shared three questions from the ccNSO Council on this process:

  1. Whether or not the ccNSO Council should initiate a PDP to develop a process to review this issue?
  2. Should it be one or two PDPs?
  3. Should this process be done in the format of a Task Force or a Working Group or another mechanism?

Several questions were addressed and three recommendations made. The first one was that the PDP process needs be started for both the review and the retirement of ccTLDs. It was also recommended to have one Working Group at this stage and that this way of organising could be more effective than a Task Force, as the community has more experience with them.

Boswinkel pointed out the next steps, which will involve:

  • the Council's decision on initiating this PDP
  • the publication of an issue report seeking public comments
  • a call for volunteers for the working group, both for the appointments made by the Council and for participants from other supporting organisations (SO) and advisory committees (AC)
  • formally ask the GAC for their opinion.

He also remarked that the work is expected to be completed by January 2019, as there will be several rounds of public consultation.

Ms Annabeth Lange, Chair of the CWG-UCTN, gave an update about the work that the group has been doing. She noted that the mandate of this WG was limited to codes and names based on ISO3166, and that its aim is to review the existing policies and find a common framework that all stakeholders could agree on.

The group has been working on developing its Interim Paper for public comment, including the consensus views to date, the issues faced, and the conviction of the group that a harmonised framework is not feasible. She talked about the current status of the CCWG as the group has finalised its discussion on 2-letter codes, but there are still deliberation about 3-letter codes. She made a call to action for the present to read the report and give input.

Lange also referred to the tentative recommendations that this CCWG has made. The main one was to close the CCWG with the end of its current mandate, but to continue working on the issue in another format. In order to do so, there is a need of consolidation efforts. In addition, she mentioned the next steps to take on the matter such as a webinar on 25 April, to discuss geographical names as a whole, and a face to face meeting during ICANN59.

After the presentation, some of the GAC members made comments and asked questions. The GAC Vice Chair from Argentina, Ms Olga Cavalli, spoke about the work that is being done at the GAC Working Group to Examine the Protection of Geographic Names in Any Future Expansion of gTLDs, and she brought attention to the importance of merging their work with this CCWG. Cavalli also stressed that the GAC WG is undergoing an analysis of what happened/will happen with the names that are not on any of the lists. 

Sorina Teleanu

The New gTLD Subsequent Procedures Policy Development Process (PDP) Working Group, established within the framework of I

The New gTLD Subsequent Procedures Policy Development Process (PDP) Working Group, established within the framework of ICANN’s Generic Names Supporting Organization (GNSO) held an open meeting in the context of ICANN58, with the aim of advancing its work. As mentioned in its charter, the group is tasked with determining whether any changes should be made to the new generic top-level domains (gTLD) policy recommendations.

In the introductory part of the meeting, it was explained that the group had initially discussed broader issues such as: Should there be a new round of applications for new gTLDs? If so, should the categories of TLDs described in the 2012 Applicant Guidebook (AGB) be maintained, or should new categories be defined? Should there be rounds of applications, or should ICANN adopt a first-come-first-served principle? Currently, the group is focusing on more substantive issues, within the framework of four Work Tracks (WT). These are: (1) overall process, support, and outreach; (2) legal, regulatory, and contractual requirements; (3) string contention objections and disputes; and (4) Internationalised Domain Names and technical and operational.

The meeting continued with general introductions to the WTs, and further, more focused, discussions on a few of the issues covered within these tracks.

WT 1: Overall process, support, and outreach

This track looks into issues such as support and outreach regarding applications for new gTLD, communication (e.g. between ICANN and applicants), fees, and application queuing. Up until now, the sub-group mostly discussed issues related to fees (e.g. whether there should be different types of fees for different types of applications, and what areas should be emphasised when it comes to applicant support), and the possibility of introducing a pre-approval accreditation programme for registry service providers (RSPs).

During the discussions, concerns were raised with regards to the clarity of the new gTLD application process, and references were made to the fact that, during the 2012 round, there were several changes made in the process, after the release of the AGB. Many applicants found those changes as impacting the applications throughout the process. For future rounds, the amount of such ‘late implementation clarifications’ should be reduced, to bring more clarity and predictability into the process.

WT2: Legal, regulatory, and contractual requirements

The second track deals with issues related to the new gTLD registry agreement (whether there should be a template agreement for all types of gTLDs, or different templates for different types of gTLDs), mechanisms for rights protection at the second level – for domain names registered in new gTLDs, reserved names (whether the current policy for reserved names should change), registrant protection, ‘closed generics’, registry/registrar separation, and the global public interest.

On the issue of ‘closed generics’, the question is whether an entity could apply for a generic string, and restrict the registration of domain names to itself and its affiliates. The ICANN Board prohibited closed generics in the 2012 applications round (based on advice from the Governmental Advisory Committee), but the question remains open for possible future rounds. There have been voices both in favour of and against maintaining this prohibition, and comments were made on the need to actually define what a generic term is, and what the difference between generic and specific terms is.

On the issue of reserved names, there seems to be a preference among the group to largely maintain the existing policy regarding reserved names at the second level. Discussions were held on the advantages and disadvantages of producing a more or less definite list of reserved names, for registries to be able to use as reference and have more clarity on what is expected from them (as the current AGB only describes the categories of names that should be reserved).

WT3: String contention objections and disputes

This track looks into aspects related to: objections to new gTLD applications (e.g. on morality and public order grounds, legal rights objections, confusing similarity, etc.) and related costs and outcomes, string similarity in new gTLD applications, community applications (the overall approach to community-based applications, and how community priority evaluation worked), accountability mechanisms.

One of the issues raised during discussions on community-based applications (applications for gTLDs representing certain communities) was the possibility of introducing an ‘expression of interest’ period, during which entities would express their interest in applying for a certain string, and a timeframe would be made available for competing community-based applications to be submitted for some of the strings. A possible introduction of priority rounds for community-based applications was also discussed.

On the issue of string similarity, debates focused on the singulars – plurals cases (i.e. applications for two gTLDs that represent the singular and plural versions of the same word). Some mentioned that TLDs should be seen as public goods, and, as such, used in the public interest. As the public could be confused by singulars – plurals gTLDs, there should be a rule saying that such gTLDs should be prohibited. Others have argued that more attention needs to be paid to the fact that the plural version of an English word, for example, might have a different meaning in another language. It was also said that, instead of introducing a prohibition per se, emphasis should be put on education and awareness-raising among end-users.

WT4: Internationalised Domain Names (IDNs) and technical & operational

The sub-group focusing on this track discusses issues such as: IDNs, universal acceptance, applicant evaluation (e.g. the technical and financial evaluation of the applications), name collisions, and security and stability.

Discussions focused on new gTLD applicant evaluations. During the 2012 round, applicants were subject to background checks on criminal, financial, and cybersquatting grounds. As none of the applications failed these checks, two main questions were raised: Should such evaluations be eliminated for future rounds? Or should the requirements rather be enhanced?

The group will continue addressing these and other issues, and plans to issue a call for comments on a number of questions related to the four tracks of work in the upcoming period. A draft version of this call is available. The group intends to publish an initial report for public comment by the end of the year.

The ICANN58 meeting will take place on 11-16 March 2017, in Copenhagen, Denmark.

The meeting will give ICANN supporting organisations and advisory committees the opportunity to have face-to-face discussions on various issues pertaining to ICANN's activity. A detailed schedule will be made available on the meeting website.

ICANN meetings in brief

  • ICANN meetings are held three times each year in different regions of the globe to enable attendees from around the world to participate in person. One meeting each year is also the organisation's annual general meeting, during which new Board members take their seats. 
  • ICANN meetings are free and officially run five days (Monday to Friday). There are also a few pre-meeting workshops and working sessions when the volunteer members of our supporting organizations and advisory committees initiate their work. 
  • ICANN meetings offer the best opportunity for face-to-face discussions and airing of opinions among knowledgeable people dedicated to the continued stable and secure operation of the Internet. 
  • ICANN meetings offer a variety of sessions such as workshops, open forums, and working meetings on the development and implementation of Internet policies. 
  • Remote participation is possible while the meetings are going on. ICANN offers several tools such as streaming live audio and video, chatrooms, and online question boxes. 
  • Detailed logistics and information about each meeting venue, registration, and remote participation can be found at the dedicated website created for each meeting. 
  • ICANN’s Fellowship programme supports attendance at ICANN meetings by selected individuals from stakeholder groups around the world.

Where and when do ICANN meetings take place? 

ICANN meetings are held three times a year in different regions, with the Board typically choosing the actual location at least a year out from the meeting. The list of regions and countries of past and upcoming ICANN meetings is available at http://meetings.icann.org/calendar.

What happens between meetings? 

In the period between meetings, the supporting organisations (SOs) and advisory committees (ACs) work closely with ICANN staff to make progress on the work agreed to during the most recent meeting. The results are then posted for public comment on the ICANN website to allow anyone in the Internet community to become acquainted with the latest developments and offer opinions on them. ICANN’s advisory committees also prepare reports to inform you about these issues and their potential impact on the Internet. A summary and analysis of all the comments is prepared and relevant documents are revised accordingly in time for your further review at the next meeting.

What topics are discussed? 

A broad range of Internet-related topics are discussed at each meeting. The agenda is ever changing and as dynamic as the Internet itself, but typically they cover contractual issues with the retail and wholesale arms of the Domain Name System, ways to respond to illegal or abusive use of the Internet’s naming systems, internal restructuring, and new initiatives for increasing competition on the Internet.

What is an ICANN meeting and what happens? 

ICANN meetings provide the opportunity for an internationally diverse group of individuals and organisations to come together and discuss and develop policies for the Internet‘s naming systems. The organisation’s staff of around 100 runs the meetings and coordinates with its volunteer SOs and ACs. The SOs and ACs are represented by governments, managers of Domain Name System elements (registries, registrars, ISPs), technical, business and intellectual property communities, academia, Internet users, and so on. ICANN’s Board, which is international in nature, ultimately weighs and makes the final decisions about Internet policies and processes.

One committee, the Governmental Advisory Committee or GAC, is made up of representatives from governments and governmental entities. Currently numbering over 130 members, they come together at each meeting to provide a unique regulatory, legal, linguistic, and cultural perspective on the issues being discussed during the meeting.

ICANN’s international meetings have been a staple of ICANN’s multi-stakeholder bottom-up consensus-building model since its formation in 1998. At the annual general meeting, one of each year’s three meetings, participants have the opportunity to meet newly seated members of the Board of Directors and thank outgoing Board members for their service.


The GIP Digital Watch observatory is provided by



and members of the GIP Steering Committee


GIP Digital Watch is operated by

Scroll to Top