Thanks Susan....I am just the messenger here....but you may want to make that point to the GAC. [cid:image001.png@01D95506.7402B700] Jeffrey J. Neuman Founder & CEO JJN Solutions, LLC p: +1.202.549.5079 E: jeff@jjnsolutions.com<mailto:jeff@jjnsolutions.com> http://jjnsolutions.com From: Susan Payne <susan.payne@comlaude.com> Sent: Sunday, March 12, 2023 5:15 PM To: Jeff Neuman <jeff@jjnsolutions.com>; council@gnso.icann.org Subject: RE: GAC/GNSO Council Talking Points/Questions - ICANN76 I don't believe that the proposed ethical waiver (as this is drafted) applies to any group but lawyers with specific ethical obligations, i.e. not consultants or third parties Jeff Susan Payne Head of Legal Policy Com Laude T +44 (0) 20 7421 8250 Ext 255 [cid:image002.png@01D95506.7402B700]<https://comlaude.com/> From: council <council-bounces@gnso.icann.org<mailto:council-bounces@gnso.icann.org>> On Behalf Of Jeff Neuman via council Sent: Sunday, March 12, 2023 5:09 PM To: council@gnso.icann.org<mailto:council@gnso.icann.org> Subject: [council] FW: GAC/GNSO Council Talking Points/Questions - ICANN76 To give the Council a little bit more information on the following AOB item from the GAC: * "Transparency in GNSO PDP regarding the companies and organizations being represented - role and current limitations of the SOI system This relates to the topic being discussed by the group discussing Statements of Interest and whether all consultants/lawyers/third parties must disclose who they represent when participating in a policy process. This was brought up in the CPH / GAC Bilateral and the GAC let the CPH know that they are putting this on the GNSO/GAC agenda. The GAC seems to agree with the CPH that full transparency and disclosure should be required and that there should be no exceptions. Please take this as the provision of information only. I take no position on this issue, but merely passing this on as the GNSO Liaison to the GAC. Sincerely, Jeff Neuman GNSO Liaison to the GAC [cid:image001.png@01D95506.7402B700] Jeffrey J. Neuman Founder & CEO JJN Solutions, LLC p: +1.202.549.5079 E: jeff@jjnsolutions.com<mailto:jeff@jjnsolutions.com> http://jjnsolutions.com<https://gbr01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjjnsolutions.com%2F&data=05%7C01%7Csusan.payne%40comlaude.com%7C7875f947f0b94ec3c12508db23467887%7C442149eed2004029b9b18f029e916b85%7C0%7C0%7C638142557801326694%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=bSTB6xdG9LdNmRCnU9AemY5hZwQi0Srd4R54RBo5Zqc%3D&reserved=0> From: council <council-bounces@gnso.icann.org<mailto:council-bounces@gnso.icann.org>> On Behalf Of Jeff Neuman via council Sent: Sunday, March 12, 2023 9:09 AM To: council@gnso.icann.org<mailto:council@gnso.icann.org> Subject: [council] FW: GAC/GNSO Council Talking Points/Questions - ICANN76 FYI, please find enclosed some updates to the GNSO/GAC Talking points from the GAC for your review. Sincerely, Jeff [cid:image001.png@01D95506.7402B700] Jeffrey J. Neuman Founder & CEO JJN Solutions, LLC p: +1.202.549.5079 E: jeff@jjnsolutions.com<mailto:jeff@jjnsolutions.com> http://jjnsolutions.com<https://gbr01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjjnsolutions.com%2F&data=05%7C01%7Csusan.payne%40comlaude.com%7C7875f947f0b94ec3c12508db23467887%7C442149eed2004029b9b18f029e916b85%7C0%7C0%7C638142557801326694%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=bSTB6xdG9LdNmRCnU9AemY5hZwQi0Srd4R54RBo5Zqc%3D&reserved=0> From: Benedetta Rossi <benedetta.rossi@icann.org<mailto:benedetta.rossi@icann.org>> Sent: Saturday, March 11, 2023 1:31 PM To: gnso-chairs@icann.org<mailto:gnso-chairs@icann.org> Cc: gac-leadership@icann.org<mailto:gac-leadership@icann.org>; Jeff Neuman <jeff@jjnsolutions.com<mailto:jeff@jjnsolutions.com>>; Jorge.Cancio@bakom.admin.ch<mailto:Jorge.Cancio@bakom.admin.ch> Subject: Update: GAC/GNSO Council Talking Points/Questions - ICANN76 Dear GNSO Council Leadership and GNSO Liaison to the GAC, Please find below an updated set of talking points/questions from the GAC, in preparation for the upcoming GAC bilateral with the GNSO Council taking place on Wednesday, 15 March 2023. One item was added under AOB, otherwise the talking points/questions are the same as those previously shared. Thank you, Kind regards, Benedetta -- Benedetta Rossi | GAC Advice and Policy Support, Senior Manager benedetta.rossi@icann.org<mailto:benedetta.rossi@icann.org> | +32.491.90.42.50 ICANN | Internet Corporation for Assigned Names and Numbers Talking Points/Questions GAC/GNSO Council Bilateral - ICANN76 - 15 March 2023 Subsequent Rounds of New gTLDs * GNSO Guidance Process (GGP) Applicant Support * What key indicators of success have emerged so far as part of the GNSO guidance process on applicant support? * SubPro Operational Design Assessment (ODA) - including options being considered by the Board and unresolved issues identified in the ODA * What is your current state of thinking regarding the intention of the Board to adopt some SubPro recommendations during ICANN 76, while deferring a small set of important ones to a later stage? * The GAC has taken note with interest of the Board's planned approach to handle the outputs from the GNSO on SubPro. We have especially taken note of the issues the Board is identifying as "pending" and subject to further dialogue with the GNSO Council. * In this regard, we would like to draw your attention to the GAC input to the Board consultation on the final recommendations of SubPro, which was filed on June 1st 2021. This GAC input includes GAC positions regarding many of the issues now identified as pending by the Board, inter alia: * RVC/PICs * Applicant support * GAC Consensus Advice and GAC Early Warnings * Community Applications * Auctions * The GAC would welcome being included in such forthcoming dialogues. * GAC/GNSO facilitated dialogue on closed generics * Should an agreement be reached and a PDP be considered, can GNSO processes accommodate delivering a PDP in a limited amount of time (i.e. prior to the next round of gTLD releases)? If so, given the varying viewpoints on the topic, how would GAC and ALAC be included in such a PDP in order to ensure that the communities allow them equivalent say as in the facilitated dialogue? DNS Abuse Mitigation * Can the GNSO Council share its views as to whether it considers the topic of domain name abuse mitigation to fall within the designated scope of permissible policy development efforts within ICANN's mandate under the bylaws ? * What does the GNSO Council think would be required to set the stage for a successful delivery of effective policy recommendations that address the harms caused by DNS Abuse? WHOIS Disclosure System * In the Kuala Lumpur Communiqué, the GAC noted the proposed WHOIS Disclosure System is a useful first step which would facilitate the collection of useful data, to possibly shed light on usage rates, timelines for response, and percentages of requests granted or denied. * Given the importance of gathering such data to inform building a more comprehensive system, how can participation of all registrars be achieved ? * Should policy development be considered, can GNSO processes accommodate a truly expedited very narrowly focused policy development process ? If that is the case what would such expedited delivery of policy recommendation require to be successful ? Accuracy of Registration Data Background: * In the Kuala Lumpur Communiqué, the GAC "having actively contributed to the work of the Registration Data Accuracy Scoping Team," reiterated "the importance of addressing efficiently and in a timely manner the issue of accuracy and reliability of domain name registration data". The GAC also took "good note of the recommendations of the Interim Report on Assignments #1 and #2 and encourages the Scoping Team to continue its work while ICANN awaits feedback from the relevant data protection authorities regarding its legal basis for processing data for the purposes of measuring accuracy" * The GAC is aware of the GNSO Council resolution of 17 november 2022 which paused the work of the Registration Data Accuracy Scoping Team, possibly for up to six months, and stated: "As part of its review of the formation and instructions to the Scoping Team, the Council will consider next steps for finding new leadership for this effort" Question * What is the status of the search for a new Chair of the Registration Data Accuracy Scoping Team ? IGO Protections and UDRP Review * The Board recently received a Staff summary of public comments on the EPDP on Specific Curative Rights Protections for International Governmental Organizations (IGOs) which stated that "[w]hile some commentators expressed support...a few commentators [notably the BC/ICA] noted specific concerns, including with the potential consequence for registrants should IGOs [not be required to] submit to a [court] jurisdiction." For purposes of any dialogue with the Board, is the Council aware that: * (a) that the Recommendations specifically state that a complaint "must also include a notice informing the respondent...of its right to challenge a UDRP [or URS] decision...by filing a claim in court"? * (b) the BC/ICA participated in the EPDP and the Recommendations received a Full Consensus designation? * Noting that there was Full Consensus for each of the 5 Recommendations of the EPDP on Specific Curative Rights Protections for International Governmental Organizations (IGOs), and assuming a Board vote to move ahead, how can the GAC support timely implementation of these Recommendations? Any other business * GAC Communiqué issues of importance to the GAC and GNSO Council response * The GAC would welcome an even more interactive exchange with the GNSO Council. Hence, any additional reactions from GNSO to the GAC Communique beyond the "advice section" would be welcome. Such reactions can be in writing but also may take the form of an intersessional dialogue if the matter warrants it. * Transparency in GNSO PDP regarding the companies and organizations being represented - role and current limitations of the SOI system ________________________________ The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the "Com Laude Group") does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28-30 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28-30 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28-30 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see www.comlaude.com<https://comlaude.com>
