1) ICANN 61 GAC Communique:
2) ICANN61 Report via Tweets
#ICANN61 Welcome Ceremony, Cherine Chalaby: the #ICANN Board is committed to acting, at all times, in the collective interest of all stakeholders and not in the single interest of a single stakeholder.— Samantha Dickinson (@sgdickinson) March 12, 2018
#ICANN61 PublicForum 1, @icann_president: I have a lot of ideas, but I believe that as #ICANN CEO, the multistakeholder model isn’t something I should participate in. You, the community decide. I’m here to serve you.— Samantha Dickinson (@sgdickinson) March 12, 2018
#ICANN61 Public Forum, Cherine Chalaby: there’s no way to completely de-risk the KSK rollover. Things will always break when you have a KSK rollover. But sometimes the risk of *not* doing the rollover is higher than the risk of doing it.— Samantha Dickinson (@sgdickinson) March 15, 2018
#ICANN61 PublicForum 1, @JamilZahid: as chair of the NomCom, proposes that the currently non-voting, term-unlimited RSSAC and SSAC liaisons to the NomCom become full voting members of the NomCom and be term-limited.— Samantha Dickinson (@sgdickinson) March 12, 2018
GDPR / WHOIS:#ICANN61 Public Forum: the #metoo movement comes to #ICANN. A group of women from the community have documented experiences of harassment at ICANN meetings & will send the compilation to ICANN Board today (nobody called out by name in compilation).— Samantha Dickinson (@sgdickinson) March 15, 2018
#ICANN61 Cross-Community on #GDPR, Cathrin Bauer-Bulst of @EU_Commission: the accreditation system for accessing non-public Whois remains the biggest missing piece of the puzzle. We need a temporary solution to go live in May while we work towards a permanent solution.— Samantha Dickinson (@sgdickinson) March 12, 2018
#ICANN61 Cross-Community on #GDPR, @NickWenbanSmith: @Nominet hasn’t published email addresses for .uk domains for decades, and it’s not been a problem. There are 12 million .uk domains. Nominet only receives ~10 queries a month for non-public data on domains.— Samantha Dickinson (@sgdickinson) March 12, 2018
FY19 ICANN Budget:#ICANN61 Cross-Community on #GDPR, @NickWenbanSmith: a reform of the basic principle of blanket worldwide publication of registrant data, with no checks and balances, was well overdue.— Samantha Dickinson (@sgdickinson) March 12, 2018
#ICANN61 @icann_president: The draft FY19 budget is a starting point that we expect the community to criticise. And we will take your criticisms into account. Ultimately, it’s the community that makes the final decisions about #ICANN’s budget.— Samantha Dickinson (@sgdickinson) March 12, 2018
#ICANN61 Welcome Ceremony, Cherine Chalaby: #ICANN Board will consider ALL comments made to the public comment period on the draft FY19 budget.— Samantha Dickinson (@sgdickinson) March 12, 2018
#ICANN61 Public Forum, Cherine Chalaby: #ICANN's funding levelling off doesn’t mean we should panic or worry. The question is how we can be effective in our spending. We need to strike a balance between fiscal responsibility & the ability for community to participate effectively.— Samantha Dickinson (@sgdickinson) March 15, 2018
CCWG-Accountability WS2 jurisdiction report:#ICANN61 GAC: Peru insists Communique not only document no. of GAC members present in San Juan but also total no. of GAC members, to show how participation is dropping & to send a message to the budget process about need for (more) funding for travel assistance.— Samantha Dickinson (@sgdickinson) March 14, 2018
#ICANN61 GAC, France: report of CCWG-Accountability’s Sub-Group on Jurisdiction took some viewpoints into consideration more than others. Feel the recommendations have not taken all positions into account. Therefore France also couldn’t approve the Jurisdiction recommendations.— Samantha Dickinson (@sgdickinson) March 11, 2018
New gTLD .AMAZON:#ICANN61 GAC, Argentina & Portugal: like Brazil, also see the lack of anything addressing #ICANN’s jurisdiction in California as problematic, so also objected formally to the recommendations of the CCWG-Accountability’s Sub-Group on Jurisdiction.— Samantha Dickinson (@sgdickinson) March 11, 2018
GAC vs ICANN Board re 2-letter country codes at second level:#ICANN61 GAC, Brazil: after discussions at #ICANN60 on .amazon #newgTLD, Amazon sent a revised proposal to the govts concerned about their application. The govts r discussing it, haven’t yet reached conclusion, meet again on 27 March, with report planned by mid-April at latest.— Samantha Dickinson (@sgdickinson) March 10, 2018
#ICANN61 GAC, Brazil: Board’s 2016 decision to allow 2-letter registrations at 2nd level was a major change to previously existing way 2-letter country codes were managed at 2nd level. Board has not responded to procedural or substantive issues that GAC has raised about this.— Samantha Dickinson (@sgdickinson) March 10, 2018
#ICANN61 GAC: Portugal, Argentina, China and France support Brazil’s intervention expressing dissatisfaction— Samantha Dickinson (@sgdickinson) March 10, 2018
with the way the #ICANN Board handled their decision to allow 2-letter registrations in 2nd level domains.
#ICANN61 GAC, Singapore: supports Brazil’s intervention about the lack of due process regarding Board’s decision on 2-letter codes at 2nd level. Need to address this or similar incident could happen again.— Samantha Dickinson (@sgdickinson) March 10, 2018
See also on Domain Mondo: News Review: ICANN61 March 10-15, San Juan, Puerto Rico (video of Public Forums, Board Meeting, ICANN Org Executive Team, and session on GDPR)#ICANN61 GAC, Belgium: the Board’s decision to allow 2-letter registrations at the 2nd level has set a precedent - it set aside an established, agreed, procedure and has reduced trust in ICANN process.— Samantha Dickinson (@sgdickinson) March 10, 2018
