[NCSG-PC] Fwd: [gnso-chairs] GNSO/GAC dialogue on closed generics: selection of GNSO participants
Kathy Kleiman
Kathy at KathyKleiman.com
Mon Sep 12 17:40:49 EEST 2022
Great Tomslin, and tx you!
Please pass my name along - with a special request for the first meeting
(or informal meeting) of this group on Wednesday or Thursday of the
ICANN meeting!
Best, Kathy
On 9/12/2022 4:25 AM, Tomslin Samme-Nlar wrote:
> Hi Kathy,
>
> My bad. I misunderstood the request. I am happy with the proposal of
> an unofficial alternate.
>
> Warmly,
> Tomslin
>
> On Sat, 10 Sept 2022, 00:47 Kathy Kleiman, <Kathy at kathykleiman.com> wrote:
>
> Hi Tomslin and All,
>
> Tx for your support and your response. I should note that my
> request below is not for an "official alternate," but an
> "/unofficial alternate/*" *and I'm glad Stephanie supports. ALAC
> is already planning to do so, and it is a very wise thing for us
> to do as well. I'm afraid I must insist.
>
> ICANN in these small groups can be all consuming and many people
> who participate on these teams are paid fulltime to do so (as I
> was when I was Director of Policy for .ORG). Our IPC friend, when
> they appoint Paul McGrady, will certainly be paid for his
> participation - and he does work for Amazon.
>
> Like ALAC, we are really the only true volunteers in this
> process. Accordingly, we cannot drop everything and abandon the
> work that we do to put bread on our tables. We also can't go
> crazy trying to make meetings that may conflict with requirements
> of our jobs and families. Unfair requirements is why NCSG and
> NCUC over the years has not participated in many roles of
> leadership and involvement across ICANN.
>
> So the only thing that makes sense is reasonable backup- an
> /unofficial/ alternate. It may not be part of the official rules,
> but it is a "reasonable accommodation" for parents and mothers and
> "reasonable accommodation" is a legal term of art in the US - for
> making sure that everyone can participate regardless of circumstances.
>
> ALAC will be taking these approach - an informal alternate.
> Together (and this is not your job or Manju's), we can make the
> sound argument that true volunteers need informal alternates to
> cover meetings the main representative simply can't make - and
> meetings too important to miss (which is any of them). ICANN
> needs its "watchers" in place...
>
> For my peace of mind, as I start a busy book tour (we launched on
> Wednesday in NYC at the engineering school of Cooper Union!), we
> will need this unofficial alternate. It is the right thing to do
> for NCSG and good precedent for days to come.
>
> Best, Kathy
>
> On 9/7/2022 4:54 PM, Tomslin Samme-Nlar wrote:
>> Hi Kathy,
>>
>> Thanks for volunteering. Really appreciate it because with the
>> short window and skills required, it would have been very
>> difficult to get a volunteer. So, thank you!
>>
>> Regarding your recommendation that we appoint an official
>> alternate, I am afraid that is not possible as stipulated on the
>> candidate guidance document I attached to my previous email. And
>> more we are now also past the negotiation phase in the Council.
>> The guidance document is now the rule book for appointing
>> members. What we could do is to pull you out as member in the
>> event that you can't attend and appoint George instead.
>>
>> Please let us know and apologies that Manju and I were unable to
>> secure an official alternate for NCSG during the drafting and
>> discussion of the text.
>>
>> Warmly,
>> Tomslin
>>
>> On Thu, 8 Sept 2022, 00:01 Kathy Kleiman,
>> <Kathy at kathykleiman.com> wrote:
>>
>> Hi Tomslin and All,
>>
>> I would like to recommend that I be appointed with George
>> Sadowsky as an unofficial alternate. George as you know as an
>> ICANN Board member for many years. But few know that before
>> that he was a founding member of NCUC (NCSG would not be
>> created for about decade after). In 1999, George was with
>> New York University as IT director and joined us in founding
>> NCUC and attending early meetings. We were his initial link
>> to ICANN!
>>
>> He has now applied to join NCSG. Some Board members leave
>> ICANN forever, but those who remain, tend to go back to the
>> groups they came from. I hope we will approve his membership.
>> And then I hope we can allow him to work with me on the
>> Closed Generics issues. He is an expert on this issue from
>> his time on the Board and knows how difficult and complicated
>> it is. He helped make sure we heard from noncommercial
>> organizations around the world before passing the first ban
>> on Closed Generics. Later, when the Subsequent Procedures
>> Working Group was looking closely at this issue, George (at
>> my invitation) joined the Working Group to again share the
>> complexities and potential problems of Closed Generics from
>> his perspective (which include his more recent experience
>> with many United Nations organizations).
>>
>> While technically the job is supposed to be for one person,
>> it is too big for one volunteer (note: some attorneys will be
>> paid by their clients and law firms to participate fully in
>> this new group and there is a reason for that). ALAC plans to
>> appoint a primary person and a backup person if the primary
>> person cannot attend a meeting or discussion. Since I will be
>> on book tour with my new book about the ENIAC Programmers,
>> */Proving Ground, /*I think it would be good idea for us to
>> have a similar arrangement. We don't want to miss a single
>> Closed Generic meeting!
>>
>> Best and tx,
>>
>> Kathy
>>
>> On 9/6/2022 8:41 AM, Tomslin Samme-Nlar wrote:
>>> FYI, PC.
>>>
>>> I am still waiting on guidance from Bruna but I just wanted
>>> to bring to your attention this statement in the meantime "
>>> /*This group would ideally have a first informal meeting
>>> during ICANN 75, so we would appreciate if you would let us
>>> know the name of your representative ideally by September
>>> 19^th */."
>>> It means we have only 2 weeks to name a representative for
>>> this. I don't think it'll be a problem since Kathy Kleinman
>>> had indicated interest already and was granted funding to KL
>>> based on that interest but I thought I'd flag the urgency to
>>> the whole committee.
>>>
>>> Warmly,
>>> Tomslin
>>> @LinkedIn: https://www.linkedin.com/in/tomslin/
>>>
>>>
>>> ---------- Forwarded message ---------
>>> From: *philippe.fouquart--- via Gnso-chairs*
>>> <gnso-chairs at icann.org>
>>> Date: Fri, 2 Sept 2022 at 22:01
>>> Subject: [gnso-chairs] GNSO/GAC dialogue on closed generics:
>>> selection of GNSO participants
>>> To: mason.cole at appdetex.com <mason.cole at appdetex.com>,
>>> wolf-ulrich.knoben at t-online.de
>>> <wolf-ulrich.knoben at t-online.de>, lschulman at inta.org
>>> <lschulman at inta.org>, bruna.mrtns at gmail.com
>>> <bruna.mrtns at gmail.com>, plommer at gmail.com
>>> <plommer at gmail.com>, benakin at gmail.com <benakin at gmail.com>,
>>> aheineman at godaddy.com <aheineman at godaddy.com>,
>>> sdemetriou at verisign.com <sdemetriou at verisign.com>,
>>> chair at rysg.info <chair at rysg.info>, secretariat at rysg.info
>>> <secretariat at rysg.info>, secretariat at icannregistrars.org
>>> <secretariat at icannregistrars.org>
>>> Cc: gnso-secs at icann.org <gnso-secs at icann.org>,
>>> gnso-chairs at icann.org <gnso-chairs at icann.org>, council at gnso
>>> icann. org <council at gnso.icann.org>
>>>
>>>
>>> Dear SG/C leaders,
>>>
>>> Hope this email finds you all well.
>>>
>>> As you know, following an invitation from the Board, the
>>> GNSO and the GAC will enter into a dialogue to “formulate a
>>> workable framework to identify and handle closed generic
>>> applications for the immediate next round of new gTLDs”, and
>>> in this dialogue we will be joined by ALAC.
>>>
>>> Council leadership would like to invite each Stakeholder
>>> Group to select a representative for this dialogue. This
>>> group is would ideally have a first informal meeting during
>>> ICANN 75, so we would appreciate if you would let us know
>>> the name of your representative ideally by September 19^th .
>>>
>>> The attached document provides the guidance for this
>>> appointment.
>>>
>>> I would finally like to draw your attention to the spirit of
>>> involvement in this effort:
>>>
>>> * the framework discussion will focus on options other
>>> than the two endpoint positions (i.e. no closed generics
>>> at all; closed generics without restrictions) as per the
>>> Board’s Proposed Parameters for Dialogue
>>> * the participants will "contribute as independent
>>> individuals, bringing their individual experiences and
>>> expertise, and not serve as representatives of their
>>> respective community organization(s). The participants
>>> must commit to focusing on successfully developing a
>>> framework for closed generics, even if the end product
>>> is inconsistent with the goals or priorities of the
>>> participant or the participant's SO/AC/SG/C.” (Council
>>> small team report)
>>>
>>> Looking forward to hearing from you, and wishing you all
>>> safe travels to KL.
>>>
>>> Best regards,
>>>
>>> Philippe
>>>
>>> Board/GNSO correspondence:
>>>
>>> * 6 Mar 2022 Letter from Maarten Botterman to Manal Ismail
>>> and Philippe Fouquart
>>> <https://www.icann.org/en/system/files/correspondence/botterman-to-ismail-fouquart-06mar22-en.pdf> –
>>> including the framing paper
>>> * 27 April 2022 Letter from Philippe Fouquart to Maarten
>>> Botterman
>>> <https://www.icann.org/en/system/files/correspondence/fouquart-to-botterman-27apr22-en.pdf>
>>> * 19 May 2022 Letter from Maarten Botterman to Philippe
>>> Fouquart
>>> <https://www.icann.org/en/system/files/correspondence/botterman-to-fouquart-19may22-en.pdf>
>>> * 29 Jun 2022 Letter from Philippe Fouquart to Maarten
>>> Botterman and Manal Ismail
>>> <https://www.icann.org/en/system/files/correspondence/fouquart-to-botterman-ismail-29jun22-en.pdf>
>>> * 25 Jul 2022 Letter from Maarten Botterman to Philippe
>>> Fouquart and Manal Ismail
>>> <https://www.icann.org/en/system/files/correspondence/botterman-to-fouquart-ismail-25jul22-en.pdf>
>>>
>>> Council small team report:
>>> https://gnso.icann.org/sites/default/files/policy/2022/draft/draft-closed-generics-small-team-report-24jun22-en.pdf
>>>
>>>
>>> _________________________________________________________________________________________________________________________
>>>
>>> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
>>> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
>>> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
>>> Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
>>>
>>> This message and its attachments may contain confidential or privileged information that may be protected by law;
>>> they should not be distributed, used or copied without authorisation.
>>> If you have received this email in error, please notify the sender and delete this message and its attachments.
>>> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
>>> Thank you.
>>> _______________________________________________
>>> Gnso-chairs mailing list
>>> Gnso-chairs at icann.org
>>> https://mm.icann.org/mailman/listinfo/gnso-chairs
>>> _______________________________________________
>>> 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.
>>>
>>> _______________________________________________
>>> NCSG-PC mailing list
>>> NCSG-PC at lists.ncsg.is
>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>> _______________________________________________
>> NCSG-PC mailing list
>> NCSG-PC at lists.ncsg.is
>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20220912/7bc606de/attachment.htm>
More information about the NCSG-PC
mailing list