<div>Alan, Thomas, et. al.,</div>
<div> </div>
<div>In as much as the motion and its intended action (to take another look at the protections given ICO and INGOs in the new gTLD program) is as much politics as policy, I don't think delaying the discussion and vote enhances likelihood of passage. There are voices in the BC who question why we are willing to re-open a decision that was unanimously closed.</div>
<div> </div>
<div>Cheers,</div>
<div> </div>
<div>Berard</div>
<div> </div>
<blockquote class="threadBlockQuote" style="border-left: 2px solid #C2C2C2; padding-left: 3px; margin-left: 4px;">--------- Original Message ---------
<div>Subject: Re: [council] IGO/RC motion<br />From: "Alan Greenberg" <alan.greenberg@mcgill.ca><br />Date: 7/23/14 11:41 am<br />To: "Thomas Rickert" <rickert@anwaelte.de>, "GNSO Council List" <council@gnso.icann.org><br /><br /><br /> Thanks for the heads up Thomas.<br /> <br /> That unfortunately adds another month to the <br /> process. Is there really no way to get <br /> clarification of what they meant outside of a <br /> Council meeting? This does not speak well to our communications skills.<br /> <br /> Alan<br /> <br /> At 23/07/2014 01:24 PM, Thomas Rickert wrote:<br /> >All,<br /> >in my previous e-mail on this subject, I <br /> >mentioned that Chris will join the upcoming GNSO <br /> >Council call. We have now spotted that I invited <br /> >him for the 25th and not the 24th (my bad - I <br /> >took the June date from the GNSO master calendar <br /> >instead of the July date) and Chris is in a <br /> >plane at that time. I am happy to report that <br /> >the NGPC willing to provide us with information. <br /> >However, such information will not be with us before the call.<br /> ><br /> >In my view, we have two topics to discuss, which are<br /> ><br /> >- getting a better understanding and clarity on <br /> >how to invoke a procedure that the Council has never invoked before and<br /> >- the substance of the motion itself.<br /> ><br /> >Having discussed this with Jonathan, I would <br /> >like to ask that we discuss the procedural issue <br /> >during the call. We might also discuss the <br /> >substance of the motion, but I would like to let <br /> >you know that I will likely withdraw the motion <br /> >during the meeting pending further clarification.<br /> ><br /> >Thanks,<br /> >Thomas<br /> ><br /> >Am 19.07.2014 um 20:59 schrieb Thomas Rickert <rickert@anwaelte.de>:<br /> ><br /> > ><br /> > > All,<br /> > > in the light of the discussions on the list, <br /> > I have asked Chris Disspain to join the <br /> > upcoming Council call and he accepted the invitation.<br /> > ><br /> > > I am sure that this will help us understand <br /> > better what the NGPC's thinking is so we can <br /> > take this into account when discussing the <br /> > motion. I suggest to get back to the amendments <br /> > that were proposed once we have heard Chris.<br /> > ><br /> > > Thanks,<br /> > > Thomas<br /> > ><br /> > > =============<br /> > > thomas-rickert.tel<br /> > > +49.228.74.898.0<br /> > ><br /> > >> Am 17.07.2014 um 11:37 schrieb Volker <br /> > Greimann <vgreimann@key-Systems.net>:<br /> > >><br /> > >><br /> > >> I support the suggestions James made.<br /> > >><br /> > >> V.<br /> > >><br /> > >> Am 16.07.2014 19:14, schrieb James M. Bladel:<br /> > >>> Some other thoughts:<br /> > >>><br /> > >>> First ³Resolved² clause: Are we, in fact, re-convening the PDP WG? I<br /> > >>> thought the goal was to reconvene volunteers that had previous served on<br /> > >>> the PDP WG to form a consultative WG to consider the amendments. Also, I<br /> > >>> don¹t know if the Council should re-confirm Thomas, rather let the WG<br /> > >>> decide if he should be reconfirmed, or if <br /> > they even need a permanent chair<br /> > >>> for this short-term effort.<br /> > >>><br /> > >>> Proposed (friendly?) amendment:<br /> > >>> ³The GNSO Council hereby calls for volunteers that have previously served<br /> > >>> in the IGO/NGO PDP WG to reconvene as a <br /> > [Review Team], and establishes the<br /> > >>> previous Chair (Thomas Rickert) as Interim Chair."<br /> > >>><br /> > >>><br /> > >>> Second ³Resolved² Clause: Whatever we end up calling this group, it<br /> > >>> should flow through the subsequent clauses.<br /> > >>> Proposed (friendly?) amendment:<br /> > >>> ³The GNSO requests the reconvened [Review Team] to considerŠ.²<br /> > >>><br /> > >>> Third ³Resolved² Clause: 45 days is a <br /> > tight deadline, should we allow the<br /> > >>> new group to report back if it needs more time?<br /> > >>> Proposed (friendly?) amendment:<br /> > >>> ³The GNSO Council requests that the [Review <br /> > Team] provide the Council with<br /> > >>> its recommendations in relation to the proposed amendment/modification<br /> > >>> within forty-five (45) days of reconvening the group, or report back to<br /> > >>> the Council prior to the end of this period <br /> > with an updated time frame for<br /> > >>> completion of its work.²<br /> > >>><br /> > >>><br /> > >>> Thanks‹<br /> > >>><br /> > >>><br /> > >>> J.<br /> > >>><br /> > >>><br /> > >>><br /> > >>><br /> > >>><br /> > >>><br /> > >>><br /> > >>>> On 7/14/14, 13:53 , "Thomas Rickert" <rickert@anwaelte.de> wrote:<br /> > >>>><br /> > >>>> All,<br /> > >>>> I herewith submit the attached motion as discussed during the London<br /> > >>>> meeting. I am sure we will continue the conversation in the light of the<br /> > >>>> latest developments.<br /> > >>>><br /> > >>>> Kind regards,<br /> > >>>> Thomas<br /> > >>>><br /> > >>>><br /> > >>>><br /> > >>>><br /> > >>><br /> > >><br /> > >> --<br /> > >> Bei weiteren Fragen stehen wir Ihnen gerne zur Verfügung.<br /> > >><br /> > >> Mit freundlichen Grüßen,<br /> > >><br /> > >> Volker A. Greimann<br /> > >> - Rechtsabteilung -<br /> > >><br /> > >> Key-Systems GmbH<br /> > >> Im Oberen Werk 1<br /> > >> 66386 St. Ingbert<br /> > >> Tel.: +49 (0) 6894 - 9396 901<br /> > >> Fax.: +49 (0) 6894 - 9396 851<br /> > >> Email: vgreimann@key-systems.net<br /> > >><br /> > >> Web: www.key-systems.net / www.RRPproxy.net<br /> > >> www.domaindiscount24.com / www.BrandShelter.com<br /> > >><br /> > >> Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:<br /> > >> www.facebook.com/KeySystems<br /> > >> www.twitter.com/key_systems<br /> > >><br /> > >> Geschäftsführer: Alexander Siffrin<br /> > >> Handelsregister Nr.: HR B 18835 - Saarbruecken<br /> > >> Umsatzsteuer ID.: DE211006534<br /> > >><br /> > >> Member of the KEYDRIVE GROUP<br /> > >> www.keydrive.lu<br /> > >><br /> > >> Der Inhalt dieser Nachricht ist vertraulich <br /> > und nur für den angegebenen Empfänger bestimmt. <br /> > Jede Form der Kenntnisgabe, Veröffentlichung <br /> > oder Weitergabe an Dritte durch den Empfänger <br /> > ist unzulässig. Sollte diese Nachricht nicht <br /> > für Sie bestimmt sein, so bitten wir Sie, sich <br /> > mit uns per E-Mail oder telefonisch in Verbindung zu setzen.<br /> > >><br /> > >> --------------------------------------------<br /> > >><br /> > >> Should you have any further questions, <br /> > please do not hesitate to contact us.<br /> > >><br /> > >> Best regards,<br /> > >><br /> > >> Volker A. Greimann<br /> > >> - legal department -<br /> > >><br /> > >> Key-Systems GmbH<br /> > >> Im Oberen Werk 1<br /> > >> 66386 St. Ingbert<br /> > >> Tel.: +49 (0) 6894 - 9396 901<br /> > >> Fax.: +49 (0) 6894 - 9396 851<br /> > >> Email: vgreimann@key-systems.net<br /> > >><br /> > >> Web: www.key-systems.net / www.RRPproxy.net<br /> > >> www.domaindiscount24.com / www.BrandShelter.com<br /> > >><br /> > >> Follow us on Twitter or join our fan <br /> > community on Facebook and stay updated:<br /> > >> www.facebook.com/KeySystems<br /> > >> www.twitter.com/key_systems<br /> > >><br /> > >> CEO: Alexander Siffrin<br /> > >> Registration No.: HR B 18835 - Saarbruecken<br /> > >> V.A.T. ID.: DE211006534<br /> > >><br /> > >> Member of the KEYDRIVE GROUP<br /> > >> www.keydrive.lu<br /> > >><br /> > >> This e-mail and its attachments is intended <br /> > only for the person to whom it is addressed. <br /> > Furthermore it is not permitted to publish any <br /> > content of this email. You must not use, <br /> > disclose, copy, print or rely on this e-mail. <br /> > If an addressing or transmission error has <br /> > misdirected this e-mail, kindly notify the <br /> > author by replying to this e-mail or contacting us by telephone.<br /> > >><br /> > >><br /> > >><br /> > ><br /> > ><br /> ><br /> ><br /> <br /> </div>
</blockquote>