[Gnso-review-wg] Agenda and Materials for GNSO Review WG Meeting 13 April 1200 UTC

Julie Hedlund julie.hedlund at icann.org
Wed Apr 12 20:38:18 UTC 2017


Dear GNSO Review Working Group members,

 

Please see below the notes and action items from the meeting on 30 March.  Per the action items revised charters are attached with redlines to show changes from the previous versions.  These have been loaded into the Adobe Connect room for discussion during tomorrow’s call: Thursday, 13 April at 1200 UTC.  Please also see the draft agenda for tomorrow’s call as follows:

 
Review agenda 
SOIs 
Flow chart of work
Review revised draft charters based on actions at 30 March meeting
Meeting Schedule: Next meeting 27 April
AOB
 

Best regards,

Julie

 

Julie Hedlund, Policy Director

 

 

Action Items/Discussion Notes 30 March

 

Action Items:

1.      Staff will send a Doodle Poll to confirm the timing of the next call that will be in two weeks on Thursday, 13 April.

2.      Recommendation 8: Include in the solution section a link to the IRT Principles.  Amend the KPIs that it is up to the future establishment of the WG to make them aware of the IRT requirements and principles.

3.      Recommendations 14 & 15: Combine recommendations 14 and 15 on timing and phasing and suggest possible language.

4.      Recommendations 16 & 18: Staff will provide context and background for Recommendation 18 and circulate them on the list.

 

Discussion Notes:

 

Review revised draft charters based on actions from ICANN 58:

 

Recommendation 8:

 

-- Staff perspective that implementation of GNSO Policy and Implementation WG recommendations addresses this recommendation from the GNSO Review.

-- General comment on recommendation charters regarding KPIs: Not clear what appropriate KPIs would be, if implementation measures are not measurable (example: if implementation involves changes in language to GNSO PDP Manual or GNSO WG Guidelines)

-- There was the requirement that the WG members should join the IRT.  Question: How is that incorporated in the solution?  Should we be more precise under #2?

-- KPIs: Up to the future establishment of the WG to make them aware and that could be enough.

 

>From the chat:

Marika Konings: The IRT Principles address composition so maybe it is worth referring to those as well?  This is what the IRT Principles say: "The call for IRT volunteers should at a minimum be sent to all members of thePDP working group that was responsible for developing the policy recommendations. The call for volunteers may need to reach beyond the working group members to ensure broad participation by parties directly impacted by the implementation and parties with specialized expertise needed for implementation. In some cases, additional outreach at the start or at a later stageof the IRT may be necessary to ensure that appropriate expertise is available and that directly affected parties are involved in the IRT."

 

Recommendation 15:

 

-- Makes sense to include it as part of the assessment process.

-- How to cycle that into future PDPs?

-- Every PDP is ideosyncratic.  Do we want to continue to have completely open PDPs?  Do we want size limitations?

-- Phasing could be a way to mitigate size.  Smaller groups addressing work simultaneously.

-- A plenary might be a good way to go.

 

>From the chat:

Marika Konings: Could that be part of the WG assessment? Ask a question on if/how the PDP could have moved faster?  And then those ideas could be shared / discussed?  @Julie - I think it is a link. The GOP refer to it, but do not dictate the questions as far as I am aware.

Amr Elsadr: One previous measure taken during a staff exercise for improving PDPs was including PDP WG charters in preliminary issues reports. This was meant to save time used to form charter drafting teams, draft the charters, submitting for public comments and having Council adopt them. This is now included in the process to accept issues report..

Lori Schulman: Does broad participation necessarily mean high numbers vs. having many interests represented?  Each PDP could be sized according to needs.  I think that idea of phasing.

Marika Konings: good point Lori - I guess the question is though how and who do you assess whether different interests are represented? would it be feasible to have each SG/C to appoint 3-4 reps representing those different interests? 

Amr Elsadr: @Lori: Public comment periods is one way to participate? Also during early PDP WG outreach to SOs/ACs?

Marika Konings: there may also be other models - it may be worth exploring similar organizations to see how they conduct similar activities?

 

Recommendations 16 & 18:

 

-- Question: Recommendation 18 points to policy effectiveness -- could have a wider frame than the PIA.  That the goals of the policy process have been achieved?  Or could the policy process be improved?

 

>From the chat:

Amr Elsadr: Does the WG also wish to address the distinction between periodic vs. ongoing post-implementation policy effectiveness evaluation?  Implementation of ongoing evaluations also need to be considered.

Wolf-Ulrich Knoben: Has "effectiveness" been defined in more detail in the report?

Amr Elsadr: @WUK: I don't believe it has. This would be dependent on how the DMPM recs are implemented?

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-review-wg/attachments/20170412/672e22ac/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: GNSO Review Implementation Charter Rec 8 v4 12 April 2017.docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 46383 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/gnso-review-wg/attachments/20170412/672e22ac/GNSOReviewImplementationCharterRec8v412April2017-0001.docx>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: GNSO Review Implementation Charter Rec 31 13 Mar 2017.docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 44176 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/gnso-review-wg/attachments/20170412/672e22ac/GNSOReviewImplementationCharterRec3113Mar2017-0001.docx>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: GNSO Review Implementation Charter Recs 14&15 v1 12 April 2017.docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 46430 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/gnso-review-wg/attachments/20170412/672e22ac/GNSOReviewImplementationCharterRecs1415v112April2017-0001.docx>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: GNSO Review Implementation Charter Recs 16 & 18 v3 12 April 2017.docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 51615 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/gnso-review-wg/attachments/20170412/672e22ac/GNSOReviewImplementationCharterRecs1618v312April2017-0001.docx>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4630 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/gnso-review-wg/attachments/20170412/672e22ac/smime-0001.p7s>


More information about the Gnso-review-wg mailing list