GNSO Council resolution 21 October 2020
Dear all, Please find below the resolution from the GNSO Council at the meeting Part 1 on Wednesday 21 October 2020 which will be posted shortly on the GNSO resolutions<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_council_resolutions_2020&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=PDd_FX3f4MVgkEIi9GHvVoUhbecsvLhgsyXrxgtbL10DTBs0i1jYiBM_uTSDzgqG&m=ZSgASD1EuH-U7lIp4Tv5rZ7qbpaQd30Zx7zYM0-pUk0&s=fX9ASCG1j6_lmUZBaZPCSK8a5HGDv7G_X0ZM7ChsG_k&e=> page. Item 3: Consent Agenda 3.1 - Action Decision Radar<https://community.icann.org/download/attachments/40175174/program_management_tool_20200924.pdf?version=1&modificationDate=1599834261000&api=v2> - Next Steps for WHOIS Conflicts Procedure Implementation Advisory Group The GNSO Council has considered the proposed immediate actions and subsequent steps as outlined in the WHOIS Conflicts Procedure IAG (WHOIS IAG) Small Team’s proposal<http://mm.icann.org/pipermail/council/attachments/20201006/2a0c0c3e/SummaryofWHOISConflictsProcedureIAGSmallTeamProposal-0001.docx>. The proposal outlines recommended next steps to consider with respect to modifying the implementation of the WHOIS Conflicts Procedure, in light of public comments received and changes to data protection law that may have affected the implementation of the Procedure. Specifically, the GNSO Council requests: 1. ICANN org, in consultation with contracted parties, to draft a proposal for a modification to the existing Procedure based on its past experience with both the WHOIS Conflicts Procedure and the registrar data retention waiver process. In formulating the draft proposal, the GNSO Council recommends that ICANN org consider changes to data protection law that may have affected the previous implementation of this Procedure in light of the contractual requirements, e.g., the General Data Protection Regulation. For example, should the identification of a new trigger to activate the procedure be considered given potential financial penalties under GDPR? 2. Following receipt of the proposal from ICANN org, the GNSO Council will consider the proposal and assess next steps, including seeking input from the community, if appropriate, given the substance of the proposal. Following the GNSO Council’s consideration, the GNSO Council may choose to adopt the proposal. 3. If the GNSO Council does not deem the proposal appropriate: * the GNSO Council will recommend a small group of Council volunteers to review the WHOIS IAG draft charter<https://gnso.icann.org/sites/default/files/file/field-file-attach/draft-icann-procedure-whois-conflicts-iag-23jan18-en.pdf> and confirm it is still fit for purpose; and * Following confirmation of the Charter by the GNSO Council, the GNSO Council recommends launching the call for volunteers for the WHOIS IAG, taking into consideration the GNSO Council’s upcoming workload. For example, the call for volunteers may need to be postponed if no community bandwidth is available to immediately consider the issues. In the meantime, ICANN org, in conjunction with the EPDP Phase 1 IRT, will need to update relevant terminology pursuant to EPDP Phase 1, Rec. 27. 4. Should the GNSO Council consider the outcome developed from the WHOIS IAG unacceptable, the GNSO Council will consider initiating an EPDP to either change or repeal the Consensus Policy. 3.2 - Action Decision Radar<https://community.icann.org/download/attachments/40175174/program_management_tool_20200924.pdf?version=1&modificationDate=1599834261000&api=v2> - Per the rationale<https://gnso.icann.org/en/drafts/draft-epdp-idn-policy-2-11oct20-en> circulated on 11 October 2020, Council agrees to launch a call for volunteers for a small team to develop both a draft charter and an EPDP scoping document for the IDN Policy Track 2. 3.3 - Following the GNSO Council’s consideration of the proposed immediate actions and subsequent steps as outlined here<https://gnso.icann.org/sites/default/files/file/field-file-attach/epdp-2-priority-2-items-10sep20-en.pdf>, the GNSO Council directs: EPDP Phase 2a – Legal/natural and feasibility of unique contacts 1. The GNSO Policy Support Team communicate to the groups that have appointed members to the EPDP Team that the Council is expected to instruct the EPDP Team to further consider the topics of legal/natural and feasibility of unique contacts per the instructions above, as well as the expected timeframe, provided herein for reference, “[a]t the latest 3 months after reconvening, the Chair of the EPDP Team and GNSO Council Liaison to the EPDP will report back to the GNSO Council on the status of deliberations. Based on this report, which is expected to include an update on progress made and the expected likelihood of consensus recommendations, the GNSO Council will decide on next steps, which could include providing additional time for the EPDP to finalize its recommendations or termination of the EPDP if it is clear that no progress is being made or consensus is unlikely). Request groups to: * Commence process of confirming members availability and/or re- appointing members to work on these topics. Proposed deadline: 15 November. * Start developing proposals to address these topics, factoring in deliberations to date, that will allow the EPDP Team to kickstart deliberations on these topics when it reconvenes.” 2. The Council leadership to initiate an Expression of Interest Process to identify a new Chair. The EPDP Team shall recommence its deliberations upon selection and confirmation of a new Chair; however, should no suitable candidates be found or should the appointment process require significant time, Council leadership will inform the Council accordingly and recommend commencement of deliberations under the leadership of the GNSO Council liaison to the EPDP Team. Accuracy: 1. The GNSO Policy Support Team communicates to GNSO SG/Cs, as well as ICANN Advisory Committees that have expressed an interest in the topic of accuracy, the intent of the GNSO Council to launch a scoping team on this topic. Request groups to: * Start thinking about members that have relevant knowledge and expertise that should join this effort once the scoping team launches. * Start compiling relevant information and suggestions that would allow kickstarting the discussions on 1. and 2. once the scoping team is formed (see here<https://gnso.icann.org/sites/default/files/file/field-file-attach/epdp-2-priority-2-items-10sep20-en.pdf> for resources already identified). 2. Council leadership to request ICANN Org to develop a briefing document that outlines both (i) existing accuracy requirements and programs and (ii) the corresponding impact that GDPR has had on implementing / enforcing these requirements and programs. The document, once delivered, will be provided to the scoping team to inform its deliberations. 3. GNSO Council to consider in the context of the Council Action / Decision Radar, the appropriate starting time for this effort, factoring in other projects that are in the pipeline. 3.4 - Confirmation of the Recommendations Report<https://gnso.icann.org/sites/default/files/file/field-file-attach/draft-epdp-phase-2-report-08oct20-en.pdf> to the ICANN Board regarding adoption of recommendations 1-22 contained in the Final Report from the EPDP Temporary Specification for gTLD Registration Data – Phase 2. 3.5 - Appointment of the GNSO Liaison to the Governmental Advisory Committee (motion<https://community.icann.org/x/OgebC>) Vote results <https://gnso.icann.org/en/meetings/gnso-council-motion-recorder-21oct20-en.pdf> Thank you. Kind regards, Nathalie
Dear All, I would like to volunteer for the position of ccNSO Council Liaison. I spent the first few years of my involvement with the ICANN community following the activities of the ccNSO, where I maintained good relationships. Later as Chair of the GeoTLD.Group (an interest group of the RySG) I worked with many GeoTLD operators who are also ccTLD operators. I believe I will be able to transition after Philippe in that role seamlessly. This should not impede me from maintaining my activities as the Liaison to the IRT on Registration Data Policy. I look forward to fulfilling both roles in parallel. Kindly, Sebastien Ducos GoDaddy Registry | Senior Client Services Manager [signature_2051221899] +61449623491 Level 8, 10 Queens Road Melbourne, VIC, Australia 3004 sebastien@registry.godaddy<mailto:sebastien@registry.godaddy> www.linkedin.com/in/sebastienducos<https://www.linkedin.com/in/sebastienducos>
Dear Council, Thanks Seb for volunteering. Is there a description of the role of the GNSO Council Liaison to the ccNSO? I know the role of ccNSO Liaison to to the GNSO is an official role which is held by Marteen Simon (According to the Website)? Also, as the GNSO Council Liaison to the GAC is one that is appointed by the Standing Selection Committee, is the GNSO Liaison to the ccNSO also selected by the SSC? Finally, does the GNSO Liaison to the ccNSO have to be a Councilor? Sorry for what may seem like very elementary questions, but I couldnt find anything on this newer role and I want to be prepared to answer these questions should they arise from GAC members. Sincerely, Jeff Jeffrey J. Neuman Founder & CEO JJN Solutions, LLC Jeff@JJNSolutions.com +1.202.549.5079 Http://www.jjnsolutions.com ________________________________ From: council <council-bounces@gnso.icann.org> on behalf of Sebastien@registry.godaddy <Sebastien@registry.godaddy> Sent: Friday, October 23, 2020 11:11:09 AM To: council@gnso.icann.org <council@gnso.icann.org> Cc: gnso-secs@icann.org <gnso-secs@icann.org> Subject: [council] Liaison to the ccNSO Dear All, I would like to volunteer for the position of ccNSO Council Liaison. I spent the first few years of my involvement with the ICANN community following the activities of the ccNSO, where I maintained good relationships. Later as Chair of the GeoTLD.Group (an interest group of the RySG) I worked with many GeoTLD operators who are also ccTLD operators. I believe I will be able to transition after Philippe in that role seamlessly. This should not impede me from maintaining my activities as the Liaison to the IRT on Registration Data Policy. I look forward to fulfilling both roles in parallel. Kindly, Sebastien Ducos GoDaddy Registry | Senior Client Services Manager [signature_2051221899] +61449623491 Level 8, 10 Queens Road Melbourne, VIC, Australia 3004 sebastien@registry.godaddy<mailto:sebastien@registry.godaddy> www.linkedin.com/in/sebastienducos<https://www.linkedin.com/in/sebastienducos>
Hi Jeff, I found this to be useful: https://gnso.icann.org/sites/default/files/file/field-file-attach/gnso-liais... In answer to your questions, I read: * A liaison must be a member of the GNSO Council. * GNSO Council Liaison to the Country Code Names Supporting Organisation (ccNSO) The GNSO Council also appoints a liaison to the ccNSO. The role of the liaison is to follow the deliberations of the ccNSO and identify when there are issues or topics being discussed that are of mutual interest. Furthermore, the liaison is expected to be available to answer any questions or relay any queries the ccNSO may have for the GNSO Council. As such, the GNSO liaison to the ccNSO is expected to: * Participate in the meetings and activities of the ccNSO; * Be sufficiently informed of ongoing GNSO efforts to communicate and advocate the positions of the GNSO to the ccNSO on topics of mutual interest; * Report to the GNSO on current and upcoming activities of the ccNSO that may be of relevance to the ccNSO and broader ccTLD community; * Actively prepare for and participate in bilateral meetings between the GNSO and ccNSO Councils. * Report to the GNSO Council not less than once a month on the activities of the ccNSO. This can be done in writing to the Council mailing list and could include sharing meeting agenda’s and/or meeting outcomes. The liaison should seek specific direction from the GNSO Council on issues of mutual interest where GNSO Council input is required. I don’t see anything referring to the SSC here, but at the same time this is the fruit of a few minutes of search online. This is by no means exhaustive. Kindly, Sebastien Ducos GoDaddy Registry | Senior Client Services Manager [signature_1141741454] +61449623491 Level 8, 10 Queens Road Melbourne, VIC, Australia 3004 sebastien@registry.godaddy<mailto:sebastien@registry.godaddy> www.linkedin.com/in/sebastienducos<https://www.linkedin.com/in/sebastienducos> From: Jeff Neuman <jeff@jjnsolutions.com> Date: Saturday, 24 October 2020 at 4:48 pm To: Sebastien Ducos <Sebastien@registry.godaddy>, council@gnso.icann.org <council@gnso.icann.org> Cc: gnso-secs@icann.org <gnso-secs@icann.org> Subject: Re: Liaison to the ccNSO Notice: This email is from an external sender. Dear Council, Thanks Seb for volunteering. Is there a description of the role of the GNSO Council Liaison to the ccNSO? I know the role of ccNSO Liaison to to the GNSO is an official role which is held by Marteen Simon (According to the Website)? Also, as the GNSO Council Liaison to the GAC is one that is appointed by the Standing Selection Committee, is the GNSO Liaison to the ccNSO also selected by the SSC? Finally, does the GNSO Liaison to the ccNSO have to be a Councilor? Sorry for what may seem like very elementary questions, but I couldnt find anything on this newer role and I want to be prepared to answer these questions should they arise from GAC members. Sincerely, Jeff Jeffrey J. Neuman Founder & CEO JJN Solutions, LLC Jeff@JJNSolutions.com +1.202.549.5079 Http://www.jjnsolutions.com ________________________________ From: council <council-bounces@gnso.icann.org> on behalf of Sebastien@registry.godaddy <Sebastien@registry.godaddy> Sent: Friday, October 23, 2020 11:11:09 AM To: council@gnso.icann.org <council@gnso.icann.org> Cc: gnso-secs@icann.org <gnso-secs@icann.org> Subject: [council] Liaison to the ccNSO Dear All, I would like to volunteer for the position of ccNSO Council Liaison. I spent the first few years of my involvement with the ICANN community following the activities of the ccNSO, where I maintained good relationships. Later as Chair of the GeoTLD.Group (an interest group of the RySG) I worked with many GeoTLD operators who are also ccTLD operators. I believe I will be able to transition after Philippe in that role seamlessly. This should not impede me from maintaining my activities as the Liaison to the IRT on Registration Data Policy. I look forward to fulfilling both roles in parallel. Kindly, Sebastien Ducos GoDaddy Registry | Senior Client Services Manager [signature_2051221899] +61449623491 Level 8, 10 Queens Road Melbourne, VIC, Australia 3004 sebastien@registry.godaddy<mailto:sebastien@registry.godaddy> www.linkedin.com/in/sebastienducos<https://www.linkedin.com/in/sebastienducos>
Thanks Seb. This is exactly what I was looking for. Can someone confirm this is the final version as there are redlines. Best regards, JJN Solutions Jeffrey J Neuman (202) 549-5079 Jeff@jjnsolutions.com ________________________________ From: Sebastien@registry.godaddy <Sebastien@registry.godaddy> Sent: Saturday, October 24, 2020 1:05:18 PM To: Jeff Neuman <jeff@jjnsolutions.com>; council@gnso.icann.org <council@gnso.icann.org> Cc: gnso-secs@icann.org <gnso-secs@icann.org> Subject: Re: Liaison to the ccNSO Hi Jeff, I found this to be useful: https://gnso.icann.org/sites/default/files/file/field-file-attach/gnso-liais... In answer to your questions, I read: * A liaison must be a member of the GNSO Council. * GNSO Council Liaison to the Country Code Names Supporting Organisation (ccNSO) The GNSO Council also appoints a liaison to the ccNSO. The role of the liaison is to follow the deliberations of the ccNSO and identify when there are issues or topics being discussed that are of mutual interest. Furthermore, the liaison is expected to be available to answer any questions or relay any queries the ccNSO may have for the GNSO Council. As such, the GNSO liaison to the ccNSO is expected to: * Participate in the meetings and activities of the ccNSO; * Be sufficiently informed of ongoing GNSO efforts to communicate and advocate the positions of the GNSO to the ccNSO on topics of mutual interest; * Report to the GNSO on current and upcoming activities of the ccNSO that may be of relevance to the ccNSO and broader ccTLD community; * Actively prepare for and participate in bilateral meetings between the GNSO and ccNSO Councils. * Report to the GNSO Council not less than once a month on the activities of the ccNSO. This can be done in writing to the Council mailing list and could include sharing meeting agenda’s and/or meeting outcomes. The liaison should seek specific direction from the GNSO Council on issues of mutual interest where GNSO Council input is required. I don’t see anything referring to the SSC here, but at the same time this is the fruit of a few minutes of search online. This is by no means exhaustive. Kindly, Sebastien Ducos GoDaddy Registry | Senior Client Services Manager [signature_1141741454] +61449623491 Level 8, 10 Queens Road Melbourne, VIC, Australia 3004 sebastien@registry.godaddy<mailto:sebastien@registry.godaddy> www.linkedin.com/in/sebastienducos<https://www.linkedin.com/in/sebastienducos> From: Jeff Neuman <jeff@jjnsolutions.com> Date: Saturday, 24 October 2020 at 4:48 pm To: Sebastien Ducos <Sebastien@registry.godaddy>, council@gnso.icann.org <council@gnso.icann.org> Cc: gnso-secs@icann.org <gnso-secs@icann.org> Subject: Re: Liaison to the ccNSO Notice: This email is from an external sender. Dear Council, Thanks Seb for volunteering. Is there a description of the role of the GNSO Council Liaison to the ccNSO? I know the role of ccNSO Liaison to to the GNSO is an official role which is held by Marteen Simon (According to the Website)? Also, as the GNSO Council Liaison to the GAC is one that is appointed by the Standing Selection Committee, is the GNSO Liaison to the ccNSO also selected by the SSC? Finally, does the GNSO Liaison to the ccNSO have to be a Councilor? Sorry for what may seem like very elementary questions, but I couldnt find anything on this newer role and I want to be prepared to answer these questions should they arise from GAC members. Sincerely, Jeff Jeffrey J. Neuman Founder & CEO JJN Solutions, LLC Jeff@JJNSolutions.com +1.202.549.5079 Http://www.jjnsolutions.com ________________________________ From: council <council-bounces@gnso.icann.org> on behalf of Sebastien@registry.godaddy <Sebastien@registry.godaddy> Sent: Friday, October 23, 2020 11:11:09 AM To: council@gnso.icann.org <council@gnso.icann.org> Cc: gnso-secs@icann.org <gnso-secs@icann.org> Subject: [council] Liaison to the ccNSO Dear All, I would like to volunteer for the position of ccNSO Council Liaison. I spent the first few years of my involvement with the ICANN community following the activities of the ccNSO, where I maintained good relationships. Later as Chair of the GeoTLD.Group (an interest group of the RySG) I worked with many GeoTLD operators who are also ccTLD operators. I believe I will be able to transition after Philippe in that role seamlessly. This should not impede me from maintaining my activities as the Liaison to the IRT on Registration Data Policy. I look forward to fulfilling both roles in parallel. Kindly, Sebastien Ducos GoDaddy Registry | Senior Client Services Manager [signature_2051221899] +61449623491 Level 8, 10 Queens Road Melbourne, VIC, Australia 3004 sebastien@registry.godaddy<mailto:sebastien@registry.godaddy> www.linkedin.com/in/sebastienducos<https://www.linkedin.com/in/sebastienducos>
Hi Jeff, Here is a ink to the clean (current) version https://gnso.icann.org/sites/default/files/file/field-file-attach/gnso-liais... Thanks, Pam ------------------------------------------------------------------ Sender:Jeff Neuman <jeff@jjnsolutions.com> Sent At:2020 Oct. 25 (Sun.) 12:37 Recipient:Sebastien@registry.godaddy <Sebastien@registry.godaddy>; council@gnso.icann.org <council@gnso.icann.org> Cc:gnso-secs@icann.org <gnso-secs@icann.org> Subject:Re: [council] Liaison to the ccNSO Thanks Seb. This is exactly what I was looking for. Can someone confirm this is the final version as there are redlines. Best regards, JJN Solutions Jeffrey J Neuman (202) 549-5079 Jeff@jjnsolutions.com From: Sebastien@registry.godaddy <Sebastien@registry.godaddy> Sent: Saturday, October 24, 2020 1:05:18 PM To: Jeff Neuman <jeff@jjnsolutions.com>; council@gnso.icann.org <council@gnso.icann.org> Cc: gnso-secs@icann.org <gnso-secs@icann.org> Subject: Re: Liaison to the ccNSO Hi Jeff, I found this to be useful: https://gnso.icann.org/sites/default/files/file/field-file-attach/gnso-liais... In answer to your questions, I read: A liaison must be a member of the GNSO Council. GNSO Council Liaison to the Country Code Names Supporting Organisation (ccNSO) The GNSO Council also appoints a liaison to the ccNSO. The role of the liaison is to follow the deliberations of the ccNSO and identify when there are issues or topics being discussed that are of mutual interest. Furthermore, the liaison is expected to be available to answer any questions or relay any queries the ccNSO may have for the GNSO Council. As such, the GNSO liaison to the ccNSO is expected to: Participate in the meetings and activities of the ccNSO; Be sufficiently informed of ongoing GNSO efforts to communicate and advocate the positions of the GNSO to the ccNSO on topics of mutual interest; Report to the GNSO on current and upcoming activities of the ccNSO that may be of relevance to the ccNSO and broader ccTLD community; Actively prepare for and participate in bilateral meetings between the GNSO and ccNSO Councils. Report to the GNSO Council not less than once a month on the activities of the ccNSO. This can be done in writing to the Council mailing list and could include sharing meeting agenda’s and/or meeting outcomes. The liaison should seek specific direction from the GNSO Council on issues of mutual interest where GNSO Council input is required. I don’t see anything referring to the SSC here, but at the same time this is the fruit of a few minutes of search online. This is by no means exhaustive. Kindly, Sebastien Ducos GoDaddy Registry | Senior Client Services Manager [signature_1141741454] +61449623491 Level 8, 10 Queens Road Melbourne, VIC, Australia 3004 sebastien@registry.godaddy www.linkedin.com/in/sebastienducos From: Jeff Neuman <jeff@jjnsolutions.com> Date: Saturday, 24 October 2020 at 4:48 pm To: Sebastien Ducos <Sebastien@registry.godaddy>, council@gnso.icann.org <council@gnso.icann.org> Cc: gnso-secs@icann.org <gnso-secs@icann.org> Subject: Re: Liaison to the ccNSO Notice:This email is from an external sender. Dear Council, Thanks Seb for volunteering. Is there a description of the role of the GNSO Council Liaison to the ccNSO? I know the role of ccNSO Liaison to to the GNSO is an official role which is held by Marteen Simon (According to the Website)? Also, as the GNSO Council Liaison to the GAC is one that is appointed by the Standing Selection Committee, is the GNSO Liaison to the ccNSO also selected by the SSC? Finally, does the GNSO Liaison to the ccNSO have to be a Councilor? Sorry for what may seem like very elementary questions, but I couldnt find anything on this newer role and I want to be prepared to answer these questions should they arise from GAC members. Sincerely, Jeff Jeffrey J. Neuman Founder & CEO JJN Solutions, LLC Jeff@JJNSolutions.com +1.202.549.5079 Http://www.jjnsolutions.com From: council <council-bounces@gnso.icann.org> on behalf of Sebastien@registry.godaddy <Sebastien@registry.godaddy> Sent: Friday, October 23, 2020 11:11:09 AM To: council@gnso.icann.org <council@gnso.icann.org> Cc: gnso-secs@icann.org <gnso-secs@icann.org> Subject: [council] Liaison to the ccNSO Dear All, I would like to volunteer for the position of ccNSO Council Liaison. I spent the first few years of my involvement with the ICANN community following the activities of the ccNSO, where I maintained good relationships. Later as Chair of the GeoTLD.Group (an interest group of the RySG) I worked with many GeoTLD operators who are also ccTLD operators. I believe I will be able to transition after Philippe in that role seamlessly. This should not impede me from maintaining my activities as the Liaison to the IRT on Registration Data Policy. I look forward to fulfilling both roles in parallel. Kindly, Sebastien Ducos GoDaddy Registry | Senior Client Services Manager [signature_2051221899] +61449623491 Level 8, 10 Queens Road Melbourne, VIC, Australia 3004 sebastien@registry.godaddy www.linkedin.com/in/sebastienducos
Hi Jeff, SSC just makes a selection, the appointment is done by the GNSO Council. Maxim Alzoba On 25 Oct 2020, 04:37, at 04:37, Jeff Neuman <jeff@jjnsolutions.com> wrote:
Thanks Seb. This is exactly what I was looking for.
Can someone confirm this is the final version as there are redlines.
Best regards,
JJN Solutions Jeffrey J Neuman (202) 549-5079 Jeff@jjnsolutions.com ________________________________ From: Sebastien@registry.godaddy <Sebastien@registry.godaddy> Sent: Saturday, October 24, 2020 1:05:18 PM To: Jeff Neuman <jeff@jjnsolutions.com>; council@gnso.icann.org <council@gnso.icann.org> Cc: gnso-secs@icann.org <gnso-secs@icann.org> Subject: Re: Liaison to the ccNSO
Hi Jeff,
I found this to be useful: https://gnso.icann.org/sites/default/files/file/field-file-attach/gnso-liais...
In answer to your questions, I read:
* A liaison must be a member of the GNSO Council. * GNSO Council Liaison to the Country Code Names Supporting Organisation (ccNSO) The GNSO Council also appoints a liaison to the ccNSO. The role of the liaison is to follow the deliberations of the ccNSO and identify when there are issues or topics being discussed that are of mutual interest. Furthermore, the liaison is expected to be available to answer any questions or relay any queries the ccNSO may have for the GNSO Council. As such, the GNSO liaison to the ccNSO is expected to: * Participate in the meetings and activities of the ccNSO; * Be sufficiently informed of ongoing GNSO efforts to communicate and advocate the positions of the GNSO to the ccNSO on topics of mutual interest; * Report to the GNSO on current and upcoming activities of the ccNSO that may be of relevance to the ccNSO and broader ccTLD community; * Actively prepare for and participate in bilateral meetings between the GNSO and ccNSO Councils. * Report to the GNSO Council not less than once a month on the activities of the ccNSO. This can be done in writing to the Council mailing list and could include sharing meeting agenda’s and/or meeting outcomes. The liaison should seek specific direction from the GNSO Council on issues of mutual interest where GNSO Council input is required.
I don’t see anything referring to the SSC here, but at the same time this is the fruit of a few minutes of search online. This is by no means exhaustive.
Kindly,
Sebastien Ducos
GoDaddy Registry | Senior Client Services Manager
[signature_1141741454]
+61449623491
Level 8, 10 Queens Road
Melbourne, VIC, Australia
3004
sebastien@registry.godaddy<mailto:sebastien@registry.godaddy>
www.linkedin.com/in/sebastienducos<https://www.linkedin.com/in/sebastienducos>
From: Jeff Neuman <jeff@jjnsolutions.com> Date: Saturday, 24 October 2020 at 4:48 pm To: Sebastien Ducos <Sebastien@registry.godaddy>, council@gnso.icann.org <council@gnso.icann.org> Cc: gnso-secs@icann.org <gnso-secs@icann.org> Subject: Re: Liaison to the ccNSO
Notice: This email is from an external sender.
Dear Council,
Thanks Seb for volunteering.
Is there a description of the role of the GNSO Council Liaison to the ccNSO? I know the role of ccNSO Liaison to to the GNSO is an official role which is held by Marteen Simon (According to the Website)? Also, as the GNSO Council Liaison to the GAC is one that is appointed by the Standing Selection Committee, is the GNSO Liaison to the ccNSO also selected by the SSC? Finally, does the GNSO Liaison to the ccNSO have to be a Councilor?
Sorry for what may seem like very elementary questions, but I couldnt find anything on this newer role and I want to be prepared to answer these questions should they arise from GAC members.
Sincerely,
Jeff
Jeffrey J. Neuman
Founder & CEO
JJN Solutions, LLC
Jeff@JJNSolutions.com
+1.202.549.5079
Http://www.jjnsolutions.com
________________________________
From: council <council-bounces@gnso.icann.org> on behalf of Sebastien@registry.godaddy <Sebastien@registry.godaddy> Sent: Friday, October 23, 2020 11:11:09 AM To: council@gnso.icann.org <council@gnso.icann.org> Cc: gnso-secs@icann.org <gnso-secs@icann.org> Subject: [council] Liaison to the ccNSO
Dear All,
I would like to volunteer for the position of ccNSO Council Liaison.
I spent the first few years of my involvement with the ICANN community following the activities of the ccNSO, where I maintained good relationships. Later as Chair of the GeoTLD.Group (an interest group of the RySG) I worked with many GeoTLD operators who are also ccTLD operators.
I believe I will be able to transition after Philippe in that role seamlessly.
This should not impede me from maintaining my activities as the Liaison to the IRT on Registration Data Policy. I look forward to fulfilling both roles in parallel.
Kindly,
Sebastien Ducos
GoDaddy Registry | Senior Client Services Manager
[signature_2051221899]
+61449623491
Level 8, 10 Queens Road
Melbourne, VIC, Australia
3004
sebastien@registry.godaddy<mailto:sebastien@registry.godaddy>
www.linkedin.com/in/sebastienducos<https://www.linkedin.com/in/sebastienducos>
------------------------------------------------------------------------
_______________________________________________ council mailing list council@gnso.icann.org https://mm.icann.org/mailman/listinfo/council
_______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.
participants (5)
-
Jeff Neuman -
Maxim Alzoba -
Nathalie Peregrine -
Pamela Little -
Sebastien＠registry.godaddy