<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-GB link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Thanks Thomas.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>This could be a subject for informal discussion tomorrow @ 18h00 if necessary.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Jonathan<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Thomas Rickert [mailto:rickert@anwaelte.de] <br><b>Sent:</b> 23 June 2014 16:58<br><b>To:</b> GNSO Council List<br><b>Subject:</b> [council] IGO/RCRC - NGPC letter / briefing note to GAC?<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>All,<o:p></o:p></p></div><div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif"'>1. Following up to the discussion we had on this subject, please find attached: (1) a draft motion setting out the background (in the Whereas clauses) and proposed steps the Council will take in relation to possibly modifying the GNSO’s consensus recommendations on RCRC and IGO acronym identifier protections in response to the NGPC letter of 16 June; (2) a document containing the actual proposed modification for the Council to discuss forwarding on to the reconvened WG and including some background information such as the actual original WG recommendation and GAC advice; and (3) a comparison table showing the original WG recommendations and the proposed modifications side by side.<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif"'>This is to inform your discussion with your respective groups in preparation for the public meeting on Wednesday. Of course, the motion will not be voted on till the first meeting following this London gathering, but we thought it might be useful for the Council to have all the necessary documentation at the first possible opportunity.<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif"'>Please note also that we have not run the final versions of the recommended proposal by our legal colleagues as in the interests of time we thought it important for you to be able to review these early!<o:p></o:p></span></p></div></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Kudos to policy staff, especially Mary, for turning this around at such short notice and prepare the paperwork. Thanks so much!<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>2. During the GAC/GNSO session (which I think was an excellent meeting), there was only little time to discuss this issue. Having spoken to a few people afterwards, including a GAC member, I was wondering whether the current status and the suggested actions are sufficiently clear. In particular, I am afraid that there is the misconception that a full PDP might be required for changes to the recommendations. I would therefore suggest we send a small briefing note to the GAC (we = Jonathan :-). Chances would be that the GAC could consider this for its communiqué. <o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>***<o:p></o:p></p></div><div><p class=MsoNormal>Dear Heather, <o:p></o:p></p></div><div><p class=MsoNormal>following up to yesterday's GAC / GNSO session, we would like to briefly outline both the current status as well as the next steps with respect to the IGO/RCRC question.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>1. The GNSO Council has been approached by the NGPC with a letter of June 16th, 2014 suggesting that indefinite claims service to provide notice to the organization in question is offered for the designations in question whenever such designation has been registered. Currently, the GNSO policy recommendations provide for a 90 days claims service. <o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>The GNSO Council will continue its discussion on this subject during the public meeting on Wednesday. Should the GNSO Council decide so, the course of action would be to reconvene the PDP WG to consider this very question and get back to the GNSO Council. We would like to stress that this consultation process would presumably take a short period of time. The GNSO's PDP Manual offers such process. This would not be a PDP.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>2. The second suggestion is to modify certain aspects of the URS to enable its use by IGOs and the development of rules and procedures for an arbitration process to resolve claims of abuse of IGO names and acronyms. We note that this work is already under way with the PDP that has been initiated by the GNSO Council at its last meeting on June 5th, 2014. Thus, no action is required with respect to potential modifications of GNSO Council policy recommendations as the aspect of working on potential modifications of curative rights protection mechanisms was already included in the set of recommendations the GNSO Council unanimously adopted last year. While the work on the PDP is conducted, the temporary protections remain in place, as the NGPC confirmed.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>We welcome your and the IGO Coalition's collaboration on these matters. <o:p></o:p></p></div><div><div><div><p>Yours sincerely,<o:p></o:p></p><div><p class=MsoNormal>***<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div></div></div></div><div><p class=MsoNormal>Any thoughts or suggestions?<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Best,<o:p></o:p></p></div><div><p class=MsoNormal>Thomas<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div></div></body></html>