<div dir="ltr"><table class="gmail-cf gmail-gJ" cellpadding="0"><tbody><tr class="gmail-acZ"><td class="gmail-gF gmail-gK"><table class="gmail-cf gmail-ix" cellpadding="0"><tbody><tr><td><h3 class="gmail-iw"><span class="gmail-gD" name="Robin Gross">Robin Gross</span> <span class="gmail-go"><a class="gmail-acP" href="https://support.google.com/mail/answer/1311182?hl=en" target="_blank"><font color="#222222">via</font></a> <a href="http://icann.org">icann.org</a> </span></h3></td></tr></tbody></table></td><td class="gmail-gH"><div class="gmail-gK"><span><span title="Wed, Nov 29, 2017 at 6:48 PM" class="gmail-g3" id="gmail-:1np" alt="Wed, Nov 29, 2017 at 6:48 PM">6:48 PM (1 hour ago)</span><div tabindex="0" class="gmail-zd gmail-bi4" style="outline:0px"><span class="gmail-T-KT"><img class="gmail-f gmail-T-KT-JX" alt="" src="https://mail.google.com/mail/u/0/images/cleardot.gif"></span></div></span></div></td><td class="gmail-gH"><td class="gmail-gH gmail-acX" rowspan="2"><div tabindex="0" class="gmail-T-I gmail-J-J5-Ji gmail-T-I-Js-IF gmail-aaq gmail-T-I-ax7 gmail-L3"><img class="gmail-hB gmail-T-I-J3" alt="" src="https://mail.google.com/mail/u/0/images/cleardot.gif"></div><div tabindex="0" class="gmail-T-I gmail-J-J5-Ji gmail-T-I-Js-Gs gmail-aap gmail-T-I-awG gmail-T-I-ax7 gmail-L3" id="gmail-:1o0"><img class="gmail-hA gmail-T-I-J3" alt="" src="https://mail.google.com/mail/u/0/images/cleardot.gif"> within the lines</div><div tabindex="0" class="gmail-T-I gmail-J-J5-Ji gmail-T-I-Js-Gs gmail-aap gmail-T-I-awG gmail-T-I-ax7 gmail-L3"><br></div></td></td></tr><tr class="gmail-acZ gmail-xD"><td colspan="3"><table class="gmail-cf gmail-adz" cellpadding="0"><tbody><tr><td class="gmail-ady"><div class="gmail-iw gmail-ajw"><span class="gmail-hb">Dear All, I wish to comment on comments made by Robin</span></div><div class="gmail-iw gmail-ajw"><span class="gmail-hb">to <span class="gmail-g2" dir="ltr" name="gnso-newgtld-w.">gnso-newgtld-w.</span> </span></div><div tabindex="0" class="gmail-ajy"><img class="gmail-ajz" id="gmail-:1nz" alt="" src="https://mail.google.com/mail/u/0/images/cleardot.gif"></div></td></tr></tbody></table></td></tr></tbody></table><div class="gmail-qQVYZb"><div class="gmail-utdU2e"><div class="gmail-btm"><div class="gmail-aHl"><div tabindex="-1" id="gmail-:1ny"><div class="gmail-ii gmail-gt gmail-adP gmail-adO" id="gmail-:1nn"><div class="gmail-a3s gmail-aXjCH gmail-m16008e5e75092821">I didn’t have audio on last night’s WT5 call, so thought I’d send my comments directly to the list today about the proposed Terms of Reference revealed yesterday.<br><br><em> Paragraph 1: It is not appropriate to include an “approval" model as something this group will make recommendations on, that presumptively moves away from the model that the GNSO and Board created in the last round, which intentionally and explicitly did not require a permission-based model for names. It is simply inappropriate for this fundamental policy change to be slipped-in to the Terms of Reference before we begin our work. We would be ill-advised to “put the cart before the horse”, but this bracketed language does exactly that.</em><br><br><font color="#0000ff"> Reply</font></div><div class="gmail-a3s gmail-aXjCH gmail-m16008e5e75092821"><font color="#0000ff">This is your views, </font></div><div class="gmail-a3s gmail-aXjCH gmail-m16008e5e75092821"><font color="#0000ff">Views of many GAC MEMBER<em> </em>is entirely <em>in line with draft </em>The course of action mentioned by the Board is before 2016 there were two procedure either seeking agreement or apply the mitigation. Several GAC<em> </em>members opposed to the second option <em>.There are</em> <em>several GAC ADVICE IN THIS REGARD</em></font></div><div class="gmail-a3s gmail-aXjCH gmail-m16008e5e75092821"><em><font color="#0000ff"> .</font></em></div><div class="gmail-a3s gmail-aXjCH gmail-m16008e5e75092821"><em>Paragraph 2: Regulating "names with a cultural significance" and "names with economic significance" are outside the scope of this PDP. This is a PDP regarding geo-names, so adding-on two additional types of names into the ToR is an inappropriate expansion of the scope of this group’s mandate. Let’s focus on defining what “geo-names” are, rather than including other concepts into the ToR -- that are geo-names. This PDP was set-up to work on geo-names, the chartering organizations agreed to participate under the understanding that it would be limited to geo-names, so we need to stick to our mandate and our agreement in setting up the WT</em></div><div class="gmail-a3s gmail-aXjCH gmail-m16008e5e75092821"><font color="#0000ff">Reply</font></div><div class="gmail-a3s gmail-aXjCH gmail-m16008e5e75092821"><font color="#0000ff">Again this is your personal views as many GAC members associate crucial importance to these two criteria <br></font><br> While I support giving significant consideration to risks in our analysis, let's flesh this concept out more and also include benefits in the analysis, rather than being singularly focused on risks. We are in danger of having a wholly “negative” analysis that won’t consider “positives” as well. We may wish to recognize that some risks are worth taking and consider some element of a risk-to-benefit analysis in order to be more complete in our own evaluation. Our analysis should recognize that some issues create risks to one part of ICANN community while simultaneously creating benefits to other parts of the ICANN community — we need to consider how we will handle such mixed outcomes and viewpoints in our analysis. So I think this can be a highly useful approach, but needs to be fleshed out, balanced, and nuanced a bit further in light of the complexities.<br><em><font color="#0000ff">Reply</font></em></div><div class="gmail-a3s gmail-aXjCH gmail-m16008e5e75092821"><em><font color="#0000ff">While I disagree to start with risk based approach at the begining of the process , I disagree with you catégorisions it as negative</font></em></div><div class="gmail-a3s gmail-aXjCH gmail-m16008e5e75092821"><em>Regards</em></div><div class="gmail-a3s gmail-aXjCH gmail-m16008e5e75092821">Kavouss <br></div></div></div></div></div></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Nov 29, 2017 at 7:56 PM, Martin Sutton <span dir="ltr"><<a href="mailto:martin@brandregistrygroup.org" target="_blank">martin@brandregistrygroup.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="-ms-word-wrap: break-word;">
Hi Robin,
<div><br>
</div>
<div>Thank you for sending through your comments. We will combine your comments on the ToR with those provided on the call and subsequent submissions from WT5 members, so we can review on next week’s call.</div>
<div><br>
</div>
<div>Regarding the risk approach, I over-simplified the slides in order to focus attention on drawing out the risks as a primary goal before leading us into assessing the risks. At that stage we must look at whether the risks themselves warrant any
specific controls (beyond the monitoring and enforcement mechanisms for a live registry) and how these could impact any positive elements of enabling new gTLDs relating to geographic terms. This is an important aspect of the process and needs to balance the
risks we are concerned about with the level of controls applied. Back to my physics days, every action has an equal and opposite reaction - so as we move the dial of controls, we do need to appreciate the impact of such changes with the aim of achieving an
acceptable balance. I should have made that clearer and I note that some of the comments in the chat I have subsequently read picked up on this point as well.</div>
<div><br>
</div>
<div>Kind regards,</div>
<div><br>
</div>
<div>Martin</div><span class="HOEnZb"><font color="#888888">
</font></span><div><span class="HOEnZb"><font color="#888888"> <br>
<div>
<div style="color:rgb(0,0,0);text-transform:none;text-indent:0px;letter-spacing:normal;word-spacing:0px;white-space:normal">
<div style="-ms-word-wrap: break-word;">
<div style="color:rgb(0,0,0);text-transform:none;text-indent:0px;letter-spacing:normal;font-family:Helvetica;font-size:12px;font-style:normal;font-weight:normal;word-spacing:0px;white-space:normal;font-variant-caps:normal">
<b>Martin Sutton</b></div>
<div style="color:rgb(0,0,0);text-transform:none;text-indent:0px;letter-spacing:normal;font-family:Helvetica;font-size:12px;font-style:normal;font-weight:normal;word-spacing:0px;white-space:normal;font-variant-caps:normal">
Executive Director</div>
<div style="color:rgb(0,0,0);text-transform:none;text-indent:0px;letter-spacing:normal;font-family:Helvetica;font-size:12px;font-style:normal;font-weight:normal;word-spacing:0px;white-space:normal;font-variant-caps:normal">
Brand Registry Group</div>
<div style="color:rgb(0,0,0);text-transform:none;text-indent:0px;letter-spacing:normal;font-family:Helvetica;font-size:12px;font-style:normal;font-weight:normal;word-spacing:0px;white-space:normal;font-variant-caps:normal">
<a href="mailto:martin@brandregistrygroup.org" target="_blank">martin@brandregistrygroup.org</a></div>
</div>
</div>
</div></font></span><div><div class="h5">
<div><br>
<blockquote type="cite">
<div>On 29 Nov 2017, at 17:48, Robin Gross <<a href="mailto:robin@ipjustice.org" target="_blank">robin@ipjustice.org</a>> wrote:</div>
<br class="m_6836279137858885485Apple-interchange-newline">
<div>
<div>I didn’t have audio on last night’s WT5 call, so thought I’d send my comments directly to the list today about the proposed Terms of Reference revealed yesterday.<br>
<br>
Paragraph 1: It is not appropriate to include an “approval" model as something this group will make recommendations on, that presumptively moves away from the model that the GNSO and Board created in the last round, which intentionally and explicitly did not
require a permission-based model for names. It is simply inappropriate for this fundamental policy change to be slipped-in to the Terms of Reference before we begin our work. We would be ill-advised to “put the cart before the horse”, but this bracketed
language does exactly that.<br>
<br>
Paragraph 2: Regulating "names with a cultural significance" and "names with economic significance" are outside the scope of this PDP. This is a PDP regarding geo-names, so adding-on two additional types of names into the ToR is an inappropriate expansion
of the scope of this group’s mandate. Let’s focus on defining what “geo-names” are, rather than including other concepts into the ToR -- that are geo-names. This PDP was set-up to work on geo-names, the chartering organizations agreed to participate under
the understanding that it would be limited to geo-names, so we need to stick to our mandate and our agreement in setting up the WT.
<br>
<br>
While I support giving significant consideration to risks in our analysis, let's flesh this concept out more and also include benefits in the analysis, rather than being singularly focused on risks. We are in danger of having a wholly “negative” analysis that
won’t consider “positives” as well. We may wish to recognize that some risks are worth taking and consider some element of a risk-to-benefit analysis in order to be more complete in our own evaluation. Our analysis should recognize that some issues create
risks to one part of ICANN community while simultaneously creating benefits to other parts of the ICANN community — we need to consider how we will handle such mixed outcomes and viewpoints in our analysis. So I think this can be a highly useful approach,
but needs to be fleshed out, balanced, and nuanced a bit further in light of the complexities.<br>
<br>
Thanks,<br>
Robin<br>
<br>
______________________________<wbr>_________________<br>
Gnso-newgtld-wg-wt5 mailing list<br>
<a href="mailto:Gnso-newgtld-wg-wt5@icann.org" target="_blank">Gnso-newgtld-wg-wt5@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg-wt5" target="_blank">https://mm.icann.org/mailman/<wbr>listinfo/gnso-newgtld-wg-wt5</a></div>
</div>
</blockquote>
</div>
<br>
</div></div></div>
</div>
<br>______________________________<wbr>_________________<br>
Gnso-newgtld-wg-wt5 mailing list<br>
<a href="mailto:Gnso-newgtld-wg-wt5@icann.org">Gnso-newgtld-wg-wt5@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg-wt5" target="_blank" rel="noreferrer">https://mm.icann.org/mailman/<wbr>listinfo/gnso-newgtld-wg-wt5</a><br></blockquote></div><br></div>