[council] Liaison to the ccNSO

[Maxim Alzoba]

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 at 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 at jjnsolutions.com
>________________________________
>From: Sebastien at registry.godaddy <Sebastien at registry.godaddy>
>Sent: Saturday, October 24, 2020 1:05:18 PM
>To: Jeff Neuman <jeff at jjnsolutions.com>; council at gnso.icann.org
><council at gnso.icann.org>
>Cc: gnso-secs at icann.org <gnso-secs at 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-liaison-wg-21feb18-en.pdf
>
>
>
>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 at registry.godaddy<mailto:sebastien at registry.godaddy>
>
>www.linkedin.com/in/sebastienducos<https://www.linkedin.com/in/sebastienducos>
>
>
>
>
>
>From: Jeff Neuman <jeff at jjnsolutions.com>
>Date: Saturday, 24 October 2020 at 4:48 pm
>To: Sebastien Ducos <Sebastien at registry.godaddy>,
>council at gnso.icann.org <council at gnso.icann.org>
>Cc: gnso-secs at icann.org <gnso-secs at 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 at JJNSolutions.com
>
>+1.202.549.5079
>
>Http://www.jjnsolutions.com
>
>
>
>
>
>________________________________
>
>From: council <council-bounces at gnso.icann.org> on behalf of
>Sebastien at registry.godaddy <Sebastien at registry.godaddy>
>Sent: Friday, October 23, 2020 11:11:09 AM
>To: council at gnso.icann.org <council at gnso.icann.org>
>Cc: gnso-secs at icann.org <gnso-secs at 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 at registry.godaddy<mailto:sebastien at registry.godaddy>
>
>www.linkedin.com/in/sebastienducos<https://www.linkedin.com/in/sebastienducos>
>
>
>
>
>------------------------------------------------------------------------
>
>_______________________________________________
>council mailing list
>council at 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.