[Info] GNSO Council resolutions 26 April 2018

[Rafik Dammak]

Hi,

The main highlight with regard to agenda is the discussion about the impact
of GDPR in term of policy as it is possible that board activates an interim
policy. Such option was never used before and if it is enacted, the GNSO
has to create a replacing consensus policy within 1 year. So we discussed
this and thinking what we should do from council standpoint as it is the
policy manager.
One concern is that a normal PDP process takes more time than 1 year and
therefore we may have to explore option like expediated PDP (EPDP) which
was never used before.
All these remain speculation and guessing till board makes a decision on
the matter. Things would be clearer in coming days. what we can say "to be
continued".

Best,

Rafik





Le sam. 28 avr. 2018 à 00:18, Rafik Dammak <rafik.dammak at gmail.com> a
écrit :

> Hi Dorothy,
>
> Thanks for the comment.
> Do you mean the remembrance motion or the whole agenda? In term of
> highlights, it is not easy to summarize his achievements and hard
> to give justice to what he did. As GNSO chair he oversaw the council
> management several policies in time where the focus was mainly on new gTLD
> program (no talk about IANA stewardship transition!)
> and where more cooperation with other supporting organizations and
> advisory committees on different activities like IDNs got shape and
> predated what will be later called cross-community working groups. I may be
> biased as I was in council at that time.
>
> With regard to agenda, we just get the list of motions approved
> including consent agenda. The rest of agenda included discussion topics and
> updates mostly. The summary should be shared later in coming days.
>
> Best,
>
> Rafik
>
> Le sam. 28 avr. 2018 à 00:03, dorothy g <dgdorothydg at gmail.com> a écrit :
>
>> Still so sad about Stephane.  I looked through the full text. There is a
>> lot that was covered. Any other areas you would wish to highlight?
>>
>> best
>>
>> On Fri, Apr 27, 2018 at 2:48 PM, Rafik Dammak <rafik.dammak at gmail.com>
>> wrote:
>>
>>> hi all,
>>>
>>> please find the resolutions approved by the GNSO Council in yesterday
>>> conference call.
>>> feel free to ask me any question or clarification.
>>>
>>> Best Regards,
>>>
>>> Rafik Dammak
>>>
>>> NCSG Policy Committee Chair
>>>
>>> ---------- Forwarded message ---------
>>>
>>> Dear all,
>>>
>>>
>>>
>>> Please find below the resolutions from the GNSO Council at its meeting
>>> on Thursday, 26 April 2018.  They have been posted on the GNSO website
>>> here: https://gnso.icann.org/en/council/resolutions
>>>
>>>
>>>
>>>
>>>
>>> Thank you,
>>>
>>>
>>>
>>> Nathalie
>>>
>>>
>>>
>>> *CONSENT AGENDA*
>>>
>>>
>>>
>>>    - *Adoption of the GNSO Review of GAC Communiqué for submission to
>>>    the ICANN Board *
>>>
>>> Whereas,
>>>
>>> 1.      1. The Governmental Advisory Committee advises the ICANN Board
>>> on issues of public policy, and especially where there may be an
>>> interaction between ICANN's activities or policies and national laws or
>>> international agreements. It usually does so as part of a Communiqué, which
>>> is published towards the end of every ICANN meeting.
>>>
>>> 2.      2. The GNSO is responsible for developing and recommending to
>>> the ICANN Board substantive policies relating to generic top-level domains.
>>>
>>> 3.      3. The GNSO has expressed a desire to provide feedback to the
>>> ICANN Board on issues in the GAC Communiqué as these relate to generic
>>> top-level domains to inform the ICANN Board as well as the broader
>>> community of past, present or future gTLD policy activities that may
>>> directly or indirectly relate to advice provided by the GAC.
>>>
>>> 4.      4.  The GNSO hopes that the input provided through its review
>>> of the GAC Communiqué will further enhance the co-ordination and promote
>>> the sharing of information on gTLD related policy activities between the
>>> GAC, Board and the GNSO.
>>>
>>> Resolved,
>>>
>>> 1.      1. The GNSO Council adopts the GNSO Review of the San Juan GAC
>>> Communiqué (see
>>> https://gac.icann.org/contentMigrated/icann61-gac-communique) and
>>> requests that the GNSO Council Chair communicate the GNSO Review of the San
>>> Juan GAC Communiqué to the ICANN Board.
>>>
>>> 2.      2. The GNSO Council requests that the GNSO Chair also informs
>>> the GAC Chair of the communication between the GNSO Council and the ICANN
>>> Board.
>>>
>>>    - *The GNSO Council agrees that ICANN org should continue to treat
>>>    the Community gTLD Change Request process as a matter of implementation.*
>>>
>>> Vote results
>>> <https://gnso.icann.org/en/meetings/gnso-council-motion-recorder-26apr18-en.pdf>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>  *In Memory of Stéphane Van Gelder - motion updated with friendly
>>> amendments proposed by Rafik Dammak & Donna Austin*
>>>
>>> Submitted by: Rafik Dammak
>>>
>>> Seconded by: the GNSO Council
>>>
>>>
>>>
>>> Whereas:
>>>
>>>
>>>
>>> 1.Stéphane Van Gelder first entered the domain name business in the late
>>> 1990s when he founded Indom, a registrar in France, which later become part
>>> of the GroupNBT based in the United Kingdom. It was while Stéphane was
>>> General manager of INDOM that he was elected to the GNSO Council by the
>>> Registrar Stakeholder Group.
>>>
>>> 2. Stéphane served on the GNSO Council from 2008 through 2012, as an
>>> elected representative of the Registrars Constituency.
>>>
>>> 3. Stéphane served as Vice Chair of the GNSO Council in 2010 and was
>>> elected and served two consecutive terms as Chair of the GNSO Council in
>>> 2011 and 2012.
>>>
>>> 4. As Chair of the GNSO Council, Stéphane was an impartial and neutral
>>> facilitator on all issues. For Stéphane, remaining neutral was key to
>>> ensuring collective dialogue.
>>>
>>> 5. Stéphane made significant contributions to ICANN and was a strong and
>>> respected community leader. During his tenure as GNSO Chair, Stéphane
>>> oversaw and shepherded the:
>>>
>>>
>>>
>>> a. completion of an extensive update of the GNSO's operating procedures;
>>>
>>>
>>>
>>> b. establishment of the DNS Security & Stability Analysis working group
>>> jointly with the ALAC, ccNSO and NRO;
>>>
>>>
>>>
>>> c. completion of the Fast Flux, Post-Expiration Domain Name Recovery and
>>> Inter-Registrar Transfer Policy (IRTP) Part B Policy Development Processes
>>> (PDPs) and the joint ccNSO-GNSO Internationalized Domain Name working group;
>>>
>>>
>>>
>>> d. launch of the IRTP Part C, Thick WHOIS and Locking of Domain Names
>>> subject to Uniform Dispute Resolution Policy Proceedings PDPs; and (e)
>>> continuing work on WHOIS studies, registration abuse policies, and multiple
>>> other GNSO projects.
>>>
>>>
>>>
>>> e. the completion of the Applicant Guidebook for the 2012 New gTLD
>>> Program and the launch of the Program.
>>>
>>>
>>>
>>> f. Stéphane was a well-respected and much liked member of not only the
>>> GNSO, but of the broader ICANN Community. He was admired for his passion,
>>> his fairness, his ability to find the best in people and his true gift for
>>> uniting people.
>>>
>>>
>>>
>>> g. Stéphane’s passing is a great loss to the many people in the ICANN
>>> community that had the pleasure to work and interact with him, and for his
>>> many friends at ICANN the loss is significant.
>>>
>>>
>>>
>>> Resolved:
>>>
>>>
>>>
>>> 1.The GNSO Council wishes to recognize the significant contribution
>>> Stéphane made to the GNSO Council during his tenure and his notable
>>> achievements during this time.
>>>
>>> 2. Stéphane’s genuine passion, energy and commitment to the Internet and
>>> all that it brought to the world was second to none and we will miss him
>>> dearly.
>>>
>>> 3. On behalf of the current and previous GNSO Councils, we offer our
>>> deepest and heartfelt sympathies to his family and friends at this most
>>> difficult time.
>>>
>>>
>>>
>>> Vote results
>>> <https://gnso.icann.org/en/meetings/gnso-council-motion-recorder-26apr18-en.pdf>
>>>
>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-discuss/attachments/20180427/729f66bb/attachment.htm>