[Gnso-ssc] [Ext] Follow up from January 7 Call

[Jothan Frakes]

Hi all-

This was discussed in the RrSG meeting today and there may be another EOI
round requested; the challenge in more robust volunteer quantity seems to
be a perfect storm of holidays + volunteer fatigue + pandemic + gap of
awareness of what the task of IRP is (ie it was called selecting people to
select people to select people).

There is another discussion happening between contracted CPH about
approaching the GNSO for second EOI on it.

-Jothan

Jothan Frakes
Tel: +1.206-355-0230



On Mon, Jan 11, 2021 at 1:36 PM Craig Schwartz via Gnso-ssc <
gnso-ssc at icann.org> wrote:

> Hi Emily,
>
> A quick note to circle back on this. Should another EOI be opened, I think
> the questionnaire needs to mirror what is in Section 3.1 of the Terms of
> Reference.
>
> Thanks,
> Craig
>
>
> *--*
> Craig Schwartz
> Managing Director
> fTLD Registry Services | .BANK & .INSURANCE
> Mobile: +1 202 236 1154
> www.fTLD.com
>
>
>
>
>
> On Thu, Jan 7, 2021 at 1:05 PM Craig Schwartz <craig at ftld.com> wrote:
>
>> Hi Emily,
>>
>> Thanks for this. Given the importance of this opportunity and the limited
>> number of EOIs that have been received, I support seeking input from the
>> SG/C Chairs. I have reached out to the RySG Chair on this, but haven't
>> heard back yet.
>>
>> Craig
>>
>>
>> *--*
>> Craig Schwartz
>> Managing Director
>> fTLD Registry Services | .BANK & .INSURANCE
>> Mobile: +1 202 236 1154
>> www.fTLD.com
>>
>>
>>
>>
>>
>> On Thu, Jan 7, 2021 at 10:21 AM Emily Barabas <emily.barabas at icann.org>
>> wrote:
>>
>>> Dear Craig,
>>>
>>>
>>>
>>> Thank you for the question. It is ultimately the SG/C Chairs that will
>>> decide whether a subsequent EOI process will be opened. However, if the SSC
>>> would like to provide input on the matter, staff can share this with the
>>> SG/C Chairs. SSC members are welcome to share on list whether they think
>>> the SSC should provide input to the SG/C Chairs.
>>>
>>>
>>>
>>> Kind regards,
>>>
>>> Emily
>>>
>>>
>>>
>>> *From: *Craig Schwartz <craig at ftld.com>
>>> *Date: *Thursday, 7 January 2021 at 15:01
>>> *To: *"gnso-ssc at icann.org" <gnso-ssc at icann.org>
>>> *Cc: *Emily Barabas <emily.barabas at icann.org>, Carlton Samuels <
>>> carlton.samuels at gmail.com>
>>> *Subject: *[Ext] Follow up from January 7 Call
>>>
>>>
>>>
>>> As I had an unexpected family medical matter to attend to this morning,
>>> it compromised my ability to fully participate in the call. I tried to type
>>> in the chat when I could.
>>>
>>>
>>>
>>> The only matter for me that isn't clear with respect to next steps is
>>> whether or not a subsequent EOI for the CRG will be discussed/conducted to
>>> potentially fill the second slot available to the GSNO. Would appreciate
>>> hearing from ICANN staff on this.
>>>
>>>
>>>
>>> Thank you,
>>>
>>> Craig
>>>
>>> *--*
>>>
>>> Craig Schwartz
>>>
>>> Managing Director
>>>
>>> fTLD Registry Services | .BANK & .INSURANCE
>>>
>>> Mobile: +1 202 236 1154
>>>
>>> www.fTLD.com [ftld.com]
>>> <https://urldefense.com/v3/__http:/www.fTLD.com__;!!PtGJab4!uyMV3aWykNf-DoXq1QGPxjHxt_KXW3DeRirHU6apmYM31dW42PqxSZGaumiXOcw6N-6AwXPxdw$>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
> Gnso-ssc mailing list
> Gnso-ssc at icann.org
> https://mm.icann.org/mailman/listinfo/gnso-ssc
> _______________________________________________
> 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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-ssc/attachments/20210111/5336c7e2/attachment-0001.html>