[Epdp-dt] Reminder - input on outstanding items

Fri Jul 13 13:15:07 UTC 2018

I don’t think there’s any reason to fiddle with the council liaison role

--
Mr Michele Neylon
Blacknight Solutions
Hosting, Colocation & Domains
https://www.blacknight.com/
http://blacknight.blog/
Intl. +353 (0) 59  9183072
Direct Dial: +353 (0)59 9183090
Personal blog: https://michele.blog/
Some thoughts: https://ceo.hosting/
-------------------------------
Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty
Road,Graiguecullen,Carlow,R93 X265,Ireland  Company No.: 370845

From: Epdp-dt <epdp-dt-bounces at icann.org> on behalf of Marika Konings <marika.konings at icann.org>
Date: Friday 13 July 2018 at 13:57
To: "epdp-dt at icann.org" <epdp-dt at icann.org>
Subject: Re: [Epdp-dt] Reminder - input on outstanding items

Apologies for the oversight, but there is actually one more issue that was called out:

  *   Council Liaison: Edits have been suggested by Ayden which would require the liaison to be someone who is not coming off the Council at the AGM and who should be an ex-officio member of Council leadership. Donna has commented that she does not see any reason to why the liaison should become an ex-officio member (supported by Rubens). Should this be left as is (no specific eligibility requirements for the Council liaison) or are restrictions to be put in place on who is eligible to take up the role of liaison as well as whether this person should become an ex-officio member of Council leadership?

Best regards,

Marika

From: Epdp-dt <epdp-dt-bounces at icann.org> on behalf of Marika Konings <marika.konings at icann.org>
Date: Friday, July 13, 2018 at 14:46
To: "epdp-dt at icann.org" <epdp-dt at icann.org>
Subject: [Epdp-dt] Reminder - input on outstanding items

Dear all,

Staff has gone ahead and applied all changes as discussed during Wednesday’s DT meeting to the charter (see https://app.luminpdf.com/viewer/pYWFe2XKvPJc2u9uB/share?sk=b4c15252-e532-42d2-b21d-214b38362588 [app.luminpdf.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__app.luminpdf.com_viewer_pYWFe2XKvPJc2u9uB_share-3Fsk-3Db4c15252-2De532-2D42d2-2Db21d-2D214b38362588&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=7_PQAir-9nJQ2uB2cWiTDDDo5Hfy5HL9rSTe65iXLVM&m=Alm9sKmhg2q9ZGZLr4Y8gBx95PKRewVPTrS7rK8SYQA&s=mD-lZbnAFy1XK90pwT8TWeiVnNe0WXoMAxOe_TYJEzM&e=>). There were a couple of outstanding items that did not get specifically discussed but which were highlighted in the version of the charter that was circulated on Tuesday namely:

  *   Recommended working methods: Any objections to the approach that staff has taken to reflect the input provided?
  *   Rules of engagement – decision-making methodologies: Any objections to the proposed approach by staff (not editing this section further to not deviate from the GNSO WG Guidelines)?
  *   Problem Issue Escalation: re. restriction participation in the case of serious disruption, Ayden has suggested to change the decision-making structure from Chair in consultation with the Council Liaison to Chair in consultation with the GNSO Council. This would be a deviation from the GNSO Working Group Guidelines. Is there support for making this change, or should it remain as currently is (in line with what is in the GNSO Working Group Guidelines)?
  *   Problem Issue Escalation: Comment from Donna: This section needs to acknowledge the Chair’s ability to take action against a member if they believe the member is not adhering to the Statement of Participation. The paragraph dealing with restricting participation in case of serious disruption has been updated (new language in bold) so it now reads ‘who seriously disrupts the Working Group or does not adhere to the statement of participation’? Is there any objection to this change?

If you have any input on these items or any other parts of the charter, please share your feedback with the DT mailing list by COB today Friday 13 July.

Best regards,

Marika

Marika Konings
Vice President, Policy Development Support – GNSO, Internet Corporation for Assigned Names and Numbers (ICANN)
Email: marika.konings at icann.org<mailto:marika.konings at icann.org>

Follow the GNSO via Twitter @ICANN_GNSO
Find out more about the GNSO by taking our interactive courses [learn.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__learn.icann.org_courses_gnso&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=7_PQAir-9nJQ2uB2cWiTDDDo5Hfy5HL9rSTe65iXLVM&m=Alm9sKmhg2q9ZGZLr4Y8gBx95PKRewVPTrS7rK8SYQA&s=PjPRuRrGIJKx97avUuj-nrafB3JpVkYeYmUajbM2lXs&e=> and visiting the GNSO Newcomer pages [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gnso.icann.org_files_gnso_presentations_policy-2Defforts.htm-23newcomers&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=7_PQAir-9nJQ2uB2cWiTDDDo5Hfy5HL9rSTe65iXLVM&m=Alm9sKmhg2q9ZGZLr4Y8gBx95PKRewVPTrS7rK8SYQA&s=S1XelWrzW_iUrxSw4ujOQ5lpxA5kraVtZWrG9t8SxVw&e=>.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/epdp-dt/attachments/20180713/ba69cac5/attachment-0001.html>