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