[NCSG-PC] Fwd: [council] REQUEST FOR INPUT and the EPDP Team input in response to GNSO Council's request

[Rafik Dammak]

Hi all,

This is request to send input to council about phase 1 recommendations
board vote. I added the ncsg epdp list in cc to reach our reps to EPDP team
and asking them for guidance. We also need to add any procedural concerns.
GNSO council will discuss the topic with board at Marrakech meeting.

Best,

Rafik


---------- Forwarded message ---------
From: Drazek, Keith via council <council at gnso.icann.org>
Date: Wed, Jun 12, 2019, 23:14
Subject: [council] REQUEST FOR INPUT and the EPDP Team input in response to
GNSO Council's request
To: council at gnso.icann.org <council at gnso.icann.org>
Cc: gnso-secs at icann.org <gnso-secs at icann.org>


Hi all,



As requested, the EPDP Team submitted its input (attached) on the Phase 1
recommendations to the GNSO Council in advance of our interaction with the
ICANN Board in Marrakech.



If your respective SGs and Cs have any further input to the Council, please
send it to the Council list by this Friday so we can plan accordingly.



Our interaction with the Board in Marrakech will be the beginning of our
dialogue on this matter.



Regards,

Keith



*From:* Janis Karklins <karklinsj at gmail.com>
*Sent:* Sunday, June 09, 2019 4:23 PM
*To:* Drazek, Keith <kdrazek at verisign.com>
*Cc:* gnso-epdp-team at icann.org; gnso-epdp-lead at icann.org
*Subject:* [EXTERNAL] EPDP Team input in response to GNSO Council's request



Dear Keith,



Following the request of the GNSO Council for the EPDP Team to identify any
questions, comments or concerns to be shared with the ICANN Board in
relation to their action on the EPDP Phase 1 Recommendations, 3 groups
provided their feedback (see Annex A) which the EPDP Team discussed during
its meeting on 6 June 2019. Although there was not sufficient time to
formalize and agree on an EPDP Team response, the team felt it important to
share the different perspectives with you to help inform the Council’s
preparation for the consultation process with the ICANN Board. My take-away
from the discussion was that:



·         In relation to purpose 2, there is general understanding for why
the Board decided to not adopt this purpose and the EPDP Team confirms that
it considers it firmly within its scope for phase 2 to further review this
purpose in the context of the System for Standardized Access / Disclosure
(SSAD);

·         For recommendation #12, some additional context has been provided
that may help explain the thinking behind the EPDP Team’s original
recommendation. However, there is no agreement at this stage on whether or
not the Board’s non-adoption should be supported.



The EPDP Team understands that following the GNSO Council’s consultation
with the ICANN Board you will follow up with us to provide an update on
dialogue with ICANN Board and request further input on the possible next
steps for GNSO Council. The EPDP Team stands ready to assist as needed.



Best regards,



Janis Karklins
_______________________________________________
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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190612/0a209c97/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: EPDP Team input phase 1 consultation - 6 June 2019.docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 32058 bytes
Desc: not available
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190612/0a209c97/attachment.docx>