<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>Reminder – so far I have received one apology. Please let me know off-list if you cannot make the meeting on Tuesday 24 March at 14.00 UTC.</div>
<div><br>
</div>
<div>Best regards,</div>
<div><br>
</div>
<div>Marika</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Marika Konings <<a href="mailto:marika.konings@icann.org">marika.konings@icann.org</a>><br>
<span style="font-weight:bold">Date: </span>Tuesday 10 March 2015 16:30<br>
<span style="font-weight:bold">To: </span>"<a href="mailto:gac-gnso-cg@icann.org">gac-gnso-cg@icann.org</a>" <<a href="mailto:gac-gnso-cg@icann.org">gac-gnso-cg@icann.org</a>><br>
<span style="font-weight:bold">Subject: </span>[Gac-gnso-cg] Notes & Action items from today's GAC-GNSO CG meeting<br>
</div>
<div><br>
</div>
<div>
<div 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;">
<p>Dear All,</p>
<p>Please find below the notes & action items from today’s GAC-GNSO Consultation Group meeting. Note that the next meeting will be scheduled for
<u>Tuesday 24 March at 14.00 UTC</u> (if you cannot make the meeting, please let staff know off-list as soon as possible). </p>
<p>Best regards,</p>
<p>Marika</p>
<p><b>Notes & Action Items 10/3:</b></p>
<p><i>2. Membership Update</i></p>
<p>Olga Cavalli has joined the CG as a representative from the GAC. </p>
<p>GNSO to review distribution of members amongst SG/C to ensure balance and adequate representation. </p>
<p><b>Action item</b>: Olof to confirm membership from the GAC side and ensure all members on the list are still interested in staying on.</p>
<p><b>Action item</b>: Marika to confirm membership from the GNSO side and ensure all members on the list are still interested in staying on. </p>
<p><i>3. ICANN meeting in Singapore & current status review</i></p>
<p>Presentation to and discussion with the GAC during the GAC-GNSO joint session. Support expressed in the GAC Communique to go ahead with the Preliminary Recommendations concerning Issue Scoping. Formal approval anticipated during next week's GNSO Council
meeting (19 March) to go ahead with trial period. </p>
<p><i>4. Review draft work plan and discuss way forward</i></p>
<p>What are the success criteria that will be used to evaluate the quick look mechanism? Maybe the CG should have a wider look, beyond how the GAC and GNSO may make assessment, at what the success measures are for this as well as possible future recommendations.
Should CG have closer look at whether/how the success criteria are met, and if not, what was the point of failure? Ensure that success criteria are identified for any and all recommendations that are developed by the CG.</p>
<p><b>Action item</b>: develop / map success criteria for pilot (Amr, Carlos and Olga to develop first draft)</p>
<p>In relation to a possible procedure for how to proceed in cases where GAC early input is in conflict with a GNSO proposal and a mutual agreement could not be found - is it possible to have a very firm process around that, or is it something that should be
evaulated in process. Sub-processes could potentially be identified for each stages in case GAC advice/input differs from GNSO (preliminary) recommendations/viewpoint. Key issue is to exchange information and enhance understanding between the different parties
which is aimed to increase mutual understanding and reduce potential for conflicts. </p>
<p>Merge two work streams and work though these as a committee of the whole. Support for proposed meeting schedule (meeting every three weeks). </p>
<p><b>Action item</b>: Staff to prepare list of items that need to be worked on, including proposed priority order. Review reference materials that have been prepared earlier and could serve as a starting point. </p>
<p><u>Next meeting will be scheduled for 24 March at 14.00 UTC. </u></p>
</div>
</div>
</span>
</body>
</html>