<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>Dear All, </div>
<div><br>
</div>
<div>Please find below the notes from today’s GAC-GNSO Consultation Group meeting. You are requested to take specific note of the following deadlines:</div>
<div>
<ul>
<li><b>Deadline for review of the GNSO Liaison to the GAC document</b>:<u> Monday 25 January</u>, following which proposed recommendations are shared with the GNSO and GAC for review. </li><li><b>Deadline for feedback on QLM proposed modifications and questions (see below)</b>:
<u>Monday 1 February</u></li><li><b>Deadline for feedback on PDP engagement opportunities</b>: <u>Monday 8 February</u></li></ul>
<div>The next meeting will be scheduled for <u>Tuesday 16 February at 14.00 UTC.</u></div>
</div>
<div><br>
</div>
<div>Best regards,</div>
<div><br>
</div>
<div>Marika</div>
<div><br>
</div>
<div><b><br>
</b></div>
<div><b>Notes 20/1 Meeting</b></div>
<div><br>
</div>
<div>Apologies received: Jonathan Robinson, Paul McGrady, Amr Elsadr, Jorge Cancio, Olof Nordling</div>
<div><br>
</div>
<div>Attendees: Manal Ismail, Mason Cole, Philip Corwin, Mark Carvell</div>
<div><br>
</div>
<ul>
<li>Documents were circulated prior to the meeting for review. Developed by staff in consultation with the CG leadership. </li><li>Consider setting a deadline for input on the three documents that were circulated.</li></ul>
<div><i>GNSO Liaison to the GAC</i>: </div>
<ul>
<li>Proposed CG response / recommendation is based on the previous discussion and input provided. </li><li>Consider shortening the first recommendation to bring it more in line with the other recommendations in the document. Also consider enumerating the recommendations. Consider adding 'regular' to timely updates to ensure that GNSO policy activities stay at
the forefront. </li><li>Consider reorganising the structure before it is submitted to the GNSO and GAC so that the individual views are removed and focus is on the actual recommendations. For the background on the recommendations, the GNSO and GAC can be referred to earlier versions
of the document and/or CG meetings.</li><li>Update 2nd recommendation to include 'and' instead of but.</li><li>Change outgoing to former (third skill description)</li><li>Update - Liaison to be reviewed on an annual basis (in the form of a conversation between the liaison and the Council) / confirmed on a yearly basis.</li><li>Clarify last recommendation that not being considered a non-voting member does not mean the liaison is considered a voting member. Check how other liaisons are referred to. Liaison should be able to participate and attend GNSO Council meetings, but not
necessarily considered as a member of the Council.</li></ul>
<div><i>QLM:</i></div>
<ul>
<li>CG to review proposed simplification / modifications proposed</li><li>CG to consider whether additional PDPs are needed to 'test' the proposed simplified process before it is recommended that it is included in the PDP manual and how that aligns with the work plan of the CG. Note that at this stage no new PDPs are imminent
(as far as staff is aware).</li></ul>
<div><i>GNSO PDP</i></div>
<ul>
<li>Table provides overview of all stages of the PDP, including recommendations already implemented, recommendations being considered and some new ideas for CG review and discussion.</li></ul>
<div><i>Next steps</i>:</div>
<ul>
<li>Deadline for review of the GNSO Liaison to the GAC document: Monday 25 January, following which proposed recommendations are shared with the GNSO and GAC for review. </li><li>Deadline for feedback on QLM proposed modifications and questions (see above): 1 February</li><li>Deadline for feedback on PDP engagement opportunities: 8 February</li><li>Next meeting to be scheduled for Tuesday 16 February at 14.00 UTC.</li></ul>
</body>
</html>