April 2018 - Gnso-igo-ingo - lists.icann.org

Table of National Red Cross and Red Crescent Societies' names - Reconvened WG - Red Cross Society Names Protections
by Stephane Hankins April 30, 2018

April 30, 2018

Dear Berry, dear Thomas, Dear all, As agreed during our last telephone conference of 15 February, please find attached a copy of the completed Table of National Red Cross and Red Crescent Societies' names. This was prepared on the basis of the previously agreed criteria and conforms to the mock-up list we had submitted to the Reconvened Working Group earlier this year. Safe for exceptional cases where this was not manageable, the attached list was prepared in close coordination and consultation with the respective National Societies. Please note that, as previously discussed, some slight variations were introduced to the criteria where this was expressly requested and justified - e.g. in some rare cases, we included the words "red cross" or "red crescent" in the national language on their own (without the adjective indicating national affiliation) and thus, where the words "red cross" or "red crescent" constitute the commonly used name of the National Society (for instance, the words "Red Cross" in Swahili are included, as this is a name under which the Kenya Red Cross is commonly known and identified in Kenya: the words "Red Crescent" are included in Dari and in Pashto as this is the commonly used name of the Afghan Red Crescent in Afghanistan). In such instances, the English translation is inserted in the table in a yellow cell and is not proposed, as such, for protection/reservation. Please note that in a number of cases, certain translations of the names in national languages could not be included due to the fact that they do not exist (for instance, in the case of languages which do not make use of definite articles). In these cases, the concerned cells in official languages other than English were left blank. Thank you for any questions or querries that you would have on the attached table. With kind regards, Stéphane Stéphane J. Hankins Legal adviser Cooperation and Coordination within the Movement International Committee of the Red Cross Tel (Prof.):++41 22 730 24 19 ----- Forwarded by Stephane Hankins/DIR_GEN_MOUV_CHF/GVA/ICRC on 27.04.2018 15:55 ----- From: Mary Wong <mary.wong(a)icann.org> To: Stephane Hankins <shankins(a)icrc.org>, Berry Cobb Mail <mail(a)berrycobb.com> Cc: "gnso-igo-ingo(a)icann.org" <gnso-igo-ingo(a)icann.org> Date: 25.04.2018 16:09 Subject: Re: [Gnso-igo-ingo] Reconvened WG - Red Cross Society Names Protections - Update Dear Stephane and everyone, Depending on when the Working Group agrees on its recommendations that are to be published for public comment, that is when staff can go ahead and start the public comment period – and the timeline can be adjusted based on that date, if need be. However, please note that before the report is then submitted to the GNSO Council, the Working Group is obliged to review all public comments submitted (if any) and determine if any changes need to be made to its recommendations and/or report. Given that the deadline for documents for the Council’s consideration in Panama is 10 June, staff believes that it is highly unlikely that the final report can be submitted in time for the Council to consider it at its meeting in Panama. For your information, the document deadline for the Council’s July 2018 meeting is 9 July. We hope this is helpful. Thanks and cheers Mary From: Gnso-igo-ingo <gnso-igo-ingo-bounces(a)icann.org> on behalf of Stephane Hankins <shankins(a)icrc.org> Date: Wednesday, April 25, 2018 at 09:30 To: Berry Cobb Mail <mail(a)berrycobb.com> Cc: "gnso-igo-ingo(a)icann.org" <gnso-igo-ingo(a)icann.org> Subject: Re: [Gnso-igo-ingo] Reconvened WG - Red Cross Society Names Protections - Update Dear Berry, dear Thomas, Thank you for your message. Was the agreement not, during the last ConfCall, that the list of National Societies' names and the GNSO Working Group's draft Report and decision, would be released for public comment asap and then discussed at ICANN 62. I went back to the transcript of the last ConfCall, but some parts may be missing. It does quote Heather however as saying that "[i]n its recent meeting in Los Angeles, the GNSO Council undertook strategic planning for the year and raised the question as to whether this reconvened PDP could be wound up by mid-year". Would it not be better, subject to the confirmation of the list of National Red Cross and Red Crescent Societies' names by the WG at its upcoming 10 May session, to aim for the Report to be presented, and for the GNSO Council's determination to be made, end June in Panama? Thanks for your thoughts and kind regards, Stéphane Stéphane J. Hankins Legal adviser Cooperation and Coordination within the Movement International Committee of the Red Cross Tel (Prof.):++41 22 730 24 19 From: Heather Forrest <haforrestesq(a)gmail.com> To: Berry Cobb Mail <mail(a)berrycobb.com> Cc: gnso-igo-ingo(a)icann.org Date: 25.04.2018 14:38 Subject: Re: [Gnso-igo-ingo] Reconvened WG - Red Cross Society Names Protections - Update Sent by: "Gnso-igo-ingo" <gnso-igo-ingo-bounces(a)icann.org> Many thanks, Berry and Thomas, for your continued hard work here. I particularly appreciate the detailed timeline, and the efforts already expended to meet it. Best wishes, Heather Forrest On Tue, Apr 24, 2018 at 11:14 PM, <mail(a)berrycobb.com> wrote: Hi All, I wanted to provide you an update on the Reconvened WG effort regarding the protection of Red Cross National Society names. In consultation with the Red Cross representatives, they have provided an update that they are on target for the end of April to complete the definitive list of identifiers (193 orgs) to be considered for reservation protection. You will recall at our last session they provided examples of 12 National Societies where there was general agreement on the variations and the parameters that define those variations. In parallel, staff has started drafting the WG’s report that will outline the background of this issue, the WG’s deliberations, and proposed recommendations. The intent is to have both deliverables ready for review by the WG at our next meeting. Shortly, you will see a calendar invite for 10 May 2018 at 14:00 UTC for 90 minutes. At this session, we will first review the definitive list and deliberate on issues, if any. We will also review the draft report. The following is a proposed timeline to complete this effort. Staff and Thomas realize this will be a challenging time given the competition with GDPR efforts, but this group has committed to conclude at the end of June. As you will see, assuming the WG achieves consensus and no frictions with GDPR, this effort will may be behind schedule around mid-July. The WG can consider having a shorter comment period of 30 days given the reduced scope of this issue, but the WG should consider the balance of the 40 day rule versus delivering on time. We’re happy to have members thoughts on the mailing list in the meantime. Proposed timeline: · 10 May: WG Meeting · 18 May: Launch Public Comment proceeding for 40 days · 25 June: Start of ICANN61 – Staff has not planned on having a session at the meeting, at best an update to the Council · 27 June: Close of Public comment · 05 July: WG Meeting to review comments (don’t anticipate a ton of comments) · 13 July: Submit Report to Council Thank you for your time, and please submit your thoughts/comments on the mailing list. B Berry A. Cobb 720.839.5735 mail(a)berrycobb.com @berrycobb _______________________________________________ Gnso-igo-ingo mailing list Gnso-igo-ingo(a)icann.org https://mm.icann.org/mailman/listinfo/gnso-igo-ingo _______________________________________________ Gnso-igo-ingo mailing list Gnso-igo-ingo(a)icann.org https://mm.icann.org/mailman/listinfo/gnso-igo-ingo The ICRC - working to protect and assist people affected by armed conflict and other situations of violence. Find out more: www.icrc.org[icrc.org] This e-mail is intended for the named recipient(s) only. Its contents are confidential and may only be retained by the named recipient(s) and may only be copied or disclosed with the consent of the International Committee of the Red Cross (ICRC). If you are not an intended recipient please delete this e-mail and notify the sender. =============================================================================== The ICRC - working to protect and assist people affected by armed conflict and other situations of violence. Find out more: www.icrc.org This e-mail is intended for the named recipient(s) only. Its contents are confidential and may only be retained by the named recipient (s) and may only be copied or disclosed with the consent of the International Committee of the Red Cross (ICRC). If you are not an intended recipient please delete this e-mail and notify the sender. ===============================================================================

1 0

Reconvened WG - Red Cross Society Names Protections - Update
by mail＠berrycobb.com April 25, 2018

April 25, 2018

Hi All, I wanted to provide you an update on the Reconvened WG effort regarding the protection of Red Cross National Society names. In consultation with the Red Cross representatives, they have provided an update that they are on target for the end of April to complete the definitive list of identifiers (193 orgs) to be considered for reservation protection. You will recall at our last session they provided examples of 12 National Societies where there was general agreement on the variations and the parameters that define those variations. In parallel, staff has started drafting the WG's report that will outline the background of this issue, the WG's deliberations, and proposed recommendations. The intent is to have both deliverables ready for review by the WG at our next meeting. Shortly, you will see a calendar invite for 10 May 2018 at 14:00 UTC for 90 minutes. At this session, we will first review the definitive list and deliberate on issues, if any. We will also review the draft report. The following is a proposed timeline to complete this effort. Staff and Thomas realize this will be a challenging time given the competition with GDPR efforts, but this group has committed to conclude at the end of June. As you will see, assuming the WG achieves consensus and no frictions with GDPR, this effort will may be behind schedule around mid-July. The WG can consider having a shorter comment period of 30 days given the reduced scope of this issue, but the WG should consider the balance of the 40 day rule versus delivering on time. We're happy to have members thoughts on the mailing list in the meantime. Proposed timeline: . 10 May: WG Meeting . 18 May: Launch Public Comment proceeding for 40 days . 25 June: Start of ICANN61 - Staff has not planned on having a session at the meeting, at best an update to the Council . 27 June: Close of Public comment . 05 July: WG Meeting to review comments (don't anticipate a ton of comments) . 13 July: Submit Report to Council Thank you for your time, and please submit your thoughts/comments on the mailing list. B Berry A. Cobb 720.839.5735 mail(a)berrycobb.com @berrycobb

4 3

ADOBE CONNECT – WHAT NEXT? - ICANN Blog By Ash Rangan
by Nathalie Peregrine April 20, 2018

April 20, 2018

Dear all: Please take a look at this blog on Adobe Connect. And note the request: Before we make these changes, we want to hear from you. What do you think? Please submit your thoughts on this contemplated move before May 2nd here: RP-tool(a)icann.org<mailto:RP-tool@icann.org> Best regards, David https://www.icann.org/news/blog/adobe-connect-what-next[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_blo…> ADOBE CONNECT – WHAT NEXT? As you know, the ICANN organization took down its Adobe Connect service midway through the ICANN61 meeting in response to reported issues[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_blo…> with this service. Concurrently, we began to conduct our own forensic analysis of the reported incident and began working with our Adobe cloud service provider, CoSo Cloud LLC, and through them with Adobe to learn more. Shortly thereafter, we rolled out instances of Zoom and WebEx for the community to support remote participation (RP) and collaboration. Here's where we are now: The Forensics Investigation With respect to our forensics work, we received application logfiles from CoSo Cloud, going back for a period of one year. ICANN Engineering and Security teams have examined these application log files and the results of our investigation clearly show "fingerprints of incursion" by the researcher who reported the issue. We were unable to find any other indication that anyone else either identified or exploited this issue. Thanks to the person who found the bug again. Working closely with CoSo Cloud, we were able to recreate the reported issue, and understand the conditions required to trigger it. This information has been communicated to Adobe, and Adobe is working on a software fix to address the root cause of the issue. We have also been working with CoSo on options to re-enable Adobe Connect in the shorter term. We have determined there are two viable paths to accomplish this goal. They are: 1. Deploy a hardened configuration to eliminate "man-in-the-middle" exploitations by encrypting relevant traffic, or 2. Implement a programmatic fix from CoSo Cloud to substantially reduce the window during which the issue can be exploited. With respect to the first option, we attempted to hack the hardened configuration in a test environment last week, and were not able to do so over the course of 7 hours. Separately, CoSo Cloud and Adobe conducted similar tests and confirmed that this configuration is protected from exploitation of the issue. Community Feedback and Next Steps For the last three weeks, we have been gathering limited feedback regarding users' experiences with WebEx and Zoom. So far, we have input from about 200 people, including ICANN org meeting organizers and the ICANN community. Our analysis of this feedback indicates a desire to revert back to an Adobe Connect, providing the security of the service is ensured. Accordingly, we would like to propose the following plan to the broader community for consideration: 1. We would like to restore Adobe Connect services with both the new hardened configuration and the programmatic fix discussed above. Our intent would be to restore service by 3 May. This would allow us to use Adobe Connect during several upcoming events including the Board Workshop, the GDD Industry Summit, and ICANN62. 2. Once Adobe releases a new version of the software with a fix for this issue from their perspective, and provides assurance the update has been adequately tested, we will move toward that release of Adobe Connect in a prudent manner, with the help of CoSo Cloud. We believe that this approach will ensure the security of our content, and of our community interactions, while also enabling our community to use the collaboration tools of their choice. Before we make these changes, we want to hear from you. What do you think? Please submit your thoughts on this contemplated move before May 2nd here: RP-tool(a)icann.org<mailto:RP-tool@icann.org> Meanwhile, we will continue to offer WebEx and Zoom for RP and collaboration purposes. We will also continue to follow industry developments, including the research ALAC is doing on the RP and collaboration space, to ensure we are using secure and cost-effective tools that are appropriate for our needs. I look forward to your comments! David A. Olive Senior Vice President Policy Development Support Internet Corporation for Assigned Names and Numbers (ICANN)

1 0

FW: [Gnso-next-gen-rds-lead] FW: URGENT REQUEST - Community Input re Accreditation Model Draft
by Terri Agnew April 2, 2018

April 2, 2018

FYI From: Brian Winterfeldt <Brian(a)Winterfeldt.law <mailto:Brian@Winterfeldt.law> > Date: Monday, April 2, 2018 at 15:07 To: "so-ac-sg-cleaders(a)icann.org <mailto:so-ac-sg-cleaders@icann.org> " <so-ac-sg-cleaders(a)icann.org <mailto:so-ac-sg-cleaders@icann.org> > Cc: "internet(a)winterfeldt.law <mailto:internet@winterfeldt.law> " <internet(a)winterfeldt.law <mailto:internet@winterfeldt.law> > Subject: RE: URGENT REQUEST - Community Input re Accreditation Model Draft Dear ICANN Community Leadership Colleagues: I write to follow up on my prior communication below to provide you with a formal invitation from the IPC and the BC to participate in a community-wide discussion regarding the proposed accreditation and access model for non-public WHOIS data, which was first circulated to the community during ICANN 61. The discussion will take place via ICANN-supported remote participation and/or audio bridge this Friday April 6, 2018 from 1400-1600 UTC. Please find the formal invitation attached with the pertinent participation details. Please distribute the invitation to your respective stakeholders and encourage broad distribution to encourage as much participation as possible in the discussion. Of course, please continue to channel written comments on the accreditation model proposal to <mailto:3amcomments@gmail.com> 3amcomments(a)gmail.com, with a copy to <mailto:internet@winterfeldt.law> internet(a)winterfeldt.law. Thank you very much for your assistance and engagement with respect to this ongoing effort. Best regards, Brian _____ <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.winterfeldt.law_&d =DwMFAg&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DJ69mAe-idEhpAMF1nu2 x6c2w3xl7xb5cjS_7sB4h6Y&m=2B8W8Arbme-D4u-B_TRTbN1ysc44yNrgdHI9xYiXehQ&s=XWpe sj5trpbb65DYwAD6KtjhoswZ8rGSMTTB7LZrTRc&e=> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.winterfeldt.law_&d =DwMFAg&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DJ69mAe-idEhpAMF1nu2 x6c2w3xl7xb5cjS_7sB4h6Y&m=2B8W8Arbme-D4u-B_TRTbN1ysc44yNrgdHI9xYiXehQ&s=XWpe sj5trpbb65DYwAD6KtjhoswZ8rGSMTTB7LZrTRc&e=> [winterfeldt.law] Brian J. Winterfeldt Principal Winterfeldt IP Group <x-apple-data-detectors://12/1> 1200 17 <x-apple-data-detectors://12/1> th <x-apple-data-detectors://12/1> St NW, <x-apple-data-detectors://12/1> Ste 501 <x-apple-data-detectors://12/1> Washington, DC 20036 <mailto:brian@winterfeldt.law> brian(a)winterfeldt.law +1 202 903 4422 From: Brian Winterfeldt Sent: Thursday, March 29, 2018 7:24 PM To: <mailto:so-ac-sg-cleaders@icann.org> so-ac-sg-cleaders(a)icann.org Cc: <mailto:internet@winterfeldt.law> internet(a)winterfeldt.law Subject: URGENT REQUEST - Community Input re Accreditation Model Draft Importance: High Dear ICANN Community Leadership Colleagues: As a follow-up to my statement on behalf of the IPC during Public Forum II at ICANN 61 in Puerto Rico with Steve DelBianco (from the BC), I am writing to again request your stakeholders' input and collaboration on the proposed Accreditation Model for access to non-public WHOIS data (Version 1.3). Our sincere hope is that this model will be implemented alongside the ICANN-developed Proposed Interim Model for GDPR Compliance. The Accreditation Model can be found here: <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ipconstituency.org_ assets_docs_WHOIS-2520Access-2520Accreditation-2520Process-25201.3-255b1-255 d.pdf&d=DwMFAg&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DJ69mAe-idEhp AMF1nu2x6c2w3xl7xb5cjS_7sB4h6Y&m=2B8W8Arbme-D4u-B_TRTbN1ysc44yNrgdHI9xYiXehQ &s=ZVAEQxooXzT86rLVPfHTxmzU0WSDnjHfiAcifwTNcmk&e=> http://www.ipconstituency.org/assets/docs/WHOIS%20Access%20Accreditation%20P rocess%201.3[1].pdf[ipconstituency.org]. We welcome any questions or feedback on the proposed Accreditation Model, put forward as a strawman to facilitate broader community-wide efforts to develop an accreditation system proposal. We had hoped to convene a community-wide call swiftly after ICANN 61, but the absence of Adobe Connect has made facilitating community discussion and input difficult. However, with the stop-gap solutions being put into place, we hope to convene a call to discuss Accreditation Model development within the next week or so. Developing an Accreditation Model for access to non-public WHOIS data is a critical yet-to-be-developed element of the interim GDPR compliance model, and as Goran noted in his letter to DPAs, the community has achieved consensus that something must be finalized and implemented to assure the appropriate functioning of a gated/tiered/layered access WHOIS system. Again, we hope that the Accreditation Model proposal we are sharing can act as a starting point for the community to make quick progress in this respect. Please send any input on this matter to <mailto:3amcomments@gmail.com> 3amcomments(a)gmail.com as soon as possible, with a copy to <mailto:internet@winterfeldt.law> internet(a)winterfeldt.law. This will help us make sure all the input provided is received and appropriately captured. Again, we hope to convene a community call to facilitate continued discussion on this issue next week, so we would love to receive your feedback ideally before the community session! Thank you for your input and timely engagement in this vital aspect of our ongoing work around GDPR and WHOIS! Best regards, Brian _____ <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.winterfeldt.law_&d =DwMFAg&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DJ69mAe-idEhpAMF1nu2 x6c2w3xl7xb5cjS_7sB4h6Y&m=2B8W8Arbme-D4u-B_TRTbN1ysc44yNrgdHI9xYiXehQ&s=XWpe sj5trpbb65DYwAD6KtjhoswZ8rGSMTTB7LZrTRc&e=> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.winterfeldt.law_&d =DwMFAg&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DJ69mAe-idEhpAMF1nu2 x6c2w3xl7xb5cjS_7sB4h6Y&m=2B8W8Arbme-D4u-B_TRTbN1ysc44yNrgdHI9xYiXehQ&s=XWpe sj5trpbb65DYwAD6KtjhoswZ8rGSMTTB7LZrTRc&e=> [winterfeldt.law] Brian J. Winterfeldt Principal Winterfeldt IP Group <x-apple-data-detectors://12/1> 1200 17 <x-apple-data-detectors://12/1> th <x-apple-data-detectors://12/1> St NW, <x-apple-data-detectors://12/1> Ste 501 <x-apple-data-detectors://12/1> Washington, DC 20036 <mailto:brian@winterfeldt.law> brian(a)winterfeldt.law +1 202 903 4422

1 0