<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi Robin, <div><br></div><div>The SOI are for those only on the GNSO.</div><div>Somehow I've not been issued one, nor is there instructions how to receive one.</div><div>As you can not complete the form without a SOI, please advise.</div><div><br></div><div>Warmly,</div><div><br></div><div>Kristina Macaulay </div><div>
<br><div><div>On 26 Feb 2013, at 03:05, Robin Gross <<a href="mailto:robin@ipjustice.org">robin@ipjustice.org</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
It is great to see robust debate on this list on a pending policy matter. And I'd like to encourage those members who have an opinion in this debate to consider working on a public comment to file to ICANN on the matter.<div><br></div><div>A reminder however, that those NCSG members wishing to submit pubic comments or otherwise advocate positions in the arena should fill-out ICANN's standard <a href="https://community.icann.org/display/gnsosoi/New+SOIs">"Statement of Interest" Form</a> and disclose any commercial interest one may have on the commented issue. These "SOI's" are also required to be filled-out by anyone participating in an ICANN Working Group or other policy debate as part of ICANN's commitment to transparency.</div><div><br></div><div>Thanks!</div><div>Robin</div><div><br></div><div><br></div><div><br><div><div>On Feb 25, 2013, at 6:15 PM, Nicolas Adam wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"> <br> They should try co.caine <br> <br> or the obvious .blow<br> <br> or .patente (than it'd be the flour mills that would panic)<br> <br> or <a href="http://cocaine.com">cocaine.com</a>, cocaine.co, cocaine.pe, cocaine.snifs, cocaine.whiffs, cocaine.goodforyou, .... .<br> <br> I am quite against colonizing/enclosing generic words and languages within closed legal system, and I frequently oppose IP's settling attempt into languages here in the dns, but I also *trust* languages/signs to evolve and be diverse and strong.<br> <br> That is, of course, if we let it be strong and not say, say, that co.caine is too similar to .cocaine ....<br> <br> So my humble suggestion, let a thousand [saussurian] signifier bloom.<br> <br> <br> Nicolas<br> <br> <br> <br> <div class="moz-cite-prefix">On 2/25/2013 4:56 PM, Alex Gakuru wrote:<br> </div> <blockquote cite="mid:CAL67KoC8KhVpAHO92gHE8K22iMZCG5Q2nim2qB5e0q3d8SO4HA@mail.gmail.com" type="cite">And wonder if the US southerly neighbours successfully registered .cocaine (if they had a chance in hell) whether big pharma would be told, "where were you late when it was registered? Just go on and register .<span class="st">benzoylmethylecgonine</span> ?" rules/arguments would be "adjusted"?<br> <br> <div class="gmail_quote">On Mon, Feb 25, 2013 at 8:43 AM, Nicolas Adam <span dir="ltr"><<a moz-do-not-send="true" href="mailto:nickolas.adam@gmail.com" target="_blank">nickolas.adam@gmail.com</a>></span> wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <div class="im">On 2/24/2013 12:44 PM, Avri Doria wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> hi,<br> <br> In which case, if I really wanted honey for some reason I would apply for .miele or .דבש or .asali<br> <br> or register honey.shop or <a moz-do-not-send="true" href="http://honey.coop/" target="_blank">honey.coop</a> or <a moz-do-not-send="true" href="http://honey.ri.us/" target="_blank">honey.ri.us</a> or honey.eat or honey.farm or honey.food or .....<br> </blockquote> <br> </div> Yes, yes, and yes. Otherwise, it's just one big free public trust of strings, whose use needs to be planned and centralized, entailing endless (and random) specific adjudication.<br> <br> As for generic word capture: language(s) is (are) big. Many ways to talk about miel. <div class="HOEnZb"> <div class="h5"><br> <br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <br> I do not see the point of arguing about what content someone allows in their gTLD. And to me this largely comes down to a content issue. We are saying that everyone has a right to put content under the TLD .honey. And I just don't see it.<br> <br> I also see it as an association issue. Why does ICANN have authority to tell a gTLD owner who they must associate with, i.e who they must allow to use the gTLD they have been allocated.<br> <br> As I said, I think the gulf between the two positions is quite wide.<br> <br> avri<br> <br> <br> On 24 Feb 2013, at 18:12, Alex Gakuru wrote:<br> <br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> But Avri,<br> <br> Let's take honey, for example. Someone registers the word to the exclusion of everyone else in the domain name space. Surely honey is harvested at many places around the world, therefore *all* somewhere.honey equally deserve registration with whomever rushed to grab the word. Else would mean advocating for English to be now considered as a proprietary language.<br> <br> Regards,<br> <br> Alex<br> </blockquote> </blockquote> </div> </div> </blockquote> </div> <br> </blockquote> <br> </blockquote></div><br><div> <span class="Apple-style-span" style="font-size: 12px; "><div><br class="Apple-interchange-newline"><br class="khtml-block-placeholder"></div><div><br class="khtml-block-placeholder"></div><div>IP JUSTICE</div><div>Robin Gross, Executive Director</div><div>1192 Haight Street, San Francisco, CA 94117 USA</div><div>p: +1-415-553-6261 f: +1-415-462-6451</div><div>w: <a href="http://www.ipjustice.org/">http://www.ipjustice.org</a> e: <a href="mailto:robin@ipjustice.org">robin@ipjustice.org</a></div><br class="Apple-interchange-newline"></span><br class="Apple-interchange-newline"> </div><br></div></div></blockquote></div><br></div></body></html>