<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body dir="auto">
<div>Oy, sorry, cut off . . . </div>
<div id="AppleMailSignature"><br>
</div>
<div id="AppleMailSignature">ICANN is handcuffed by the terms and conditions agreed via the community process. When an individual applicant or group of applicants comes in after the public process has resolved requesting changes due to "extraordinary circumstances,"
ICANN must justify any changes it might accept in light of the opinion of every other applicant and constituency, whether it be the opinion of an IGO/GO, community, "brand" or other applicant or of the GAC, ALAC, etc. </div>
<div id="AppleMailSignature"><br>
</div>
<div id="AppleMailSignature">So I (personally) support having separate and unique agreements for distinct categories (assuming we properly define these categories) because it will help ICANN to enable and process these unique applications, but the distinctions
need to ensure security and stability across all TLDs. </div>
<div id="AppleMailSignature"><br>
<p class="MsoNormal" style="margin: 0in 0in 1pt; line-height: 18.399999618530273px;">
<b><span style="line-height: 16.100000381469727px; background-color: rgba(255, 255, 255, 0);">kevin kreuser<o:p></o:p></span></b></p>
<p class="MsoNormal" style="margin: 0in 0in 1pt; line-height: 18.399999618530273px;">
<span style="background-color: rgba(255, 255, 255, 0);"><b><span style="line-height: 16.100000381469727px;">senior assistant general counsel | </span></b><b><span style="line-height: 16.100000381469727px;">Go</span></b><b><span style="line-height: 16.100000381469727px;">Daddy<sup></sup></span></b><b><sup><span style="line-height: 16.100000381469727px;"><o:p></o:p></span></sup></b></span></p>
<p class="MsoNormal" style="margin: 0in 0in 1pt; line-height: 18.399999618530273px;">
<span style="background-color: rgba(255, 255, 255, 0);"><b><span style="line-height: 16.100000381469727px;"><a href="mailto:kkreuser@godaddy.com">kkreuser@godaddy.com</a></span></b><span style="line-height: 16.866666793823242px;"></span><b><span style="line-height: 16.100000381469727px;"> <o:p></o:p></span></b></span></p>
<p class="MsoNormal" style="margin: 0in 0in 1pt; line-height: 18.399999618530273px;">
<b><span style="line-height: 16.100000381469727px; background-color: rgba(255, 255, 255, 0);"><a dir="ltr" href="tel:602-420-4121" x-apple-data-detectors="true" x-apple-data-detectors-type="telephone" x-apple-data-detectors-result="8/1">602-420-4121</a> (o)
/ <a dir="ltr" href="tel:480-258-7957" x-apple-data-detectors="true" x-apple-data-detectors-type="telephone" x-apple-data-detectors-result="8/2">480-258-7957</a> (m)</span></b></p>
<p class="MsoNormal" style="margin: 0in 0in 1pt; line-height: 18.399999618530273px;">
<br>
</p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt;"><span style="background-color: rgba(255, 255, 255, 0);"> </span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt;"><i style="background-color: rgba(255, 255, 255, 0);">This email message and any attachments hereto is intended for use only by the addressee(s) named herein and may contain confidential information. If
you have received this email in error, please immediately notify the sender and permanently delete the original and any copy of this message and its attachments.</i></p>
</div>
<div><br>
On Oct 2, 2016, at 9:26 PM, Kevin Kreuser <<a href="mailto:kkreuser@godaddy.com">kkreuser@godaddy.com</a>> wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<div>As the guy that negotiated every RA with every applicant and drafted the final version of Spec 13, I disagree with Michael that ICANN wasn't equipped to understand brand concerns - it was a case, as is always case for ICANN, of not feeling <br>
<br>
<p class="MsoNormal" style="margin: 0in 0in 1pt; line-height: 18.399999618530273px;">
<b><span style="line-height: 16.100000381469727px; background-color: rgba(255, 255, 255, 0);">kevin kreuser<o:p></o:p></span></b></p>
<p class="MsoNormal" style="margin: 0in 0in 1pt; line-height: 18.399999618530273px;">
<span style="background-color: rgba(255, 255, 255, 0);"><b><span style="line-height: 16.100000381469727px;">senior assistant general counsel | </span></b><b><span style="line-height: 16.100000381469727px;">Go</span></b><b><span style="line-height: 16.100000381469727px;">Daddy<sup></sup></span></b><b><sup><span style="line-height: 16.100000381469727px;"><o:p></o:p></span></sup></b></span></p>
<p class="MsoNormal" style="margin: 0in 0in 1pt; line-height: 18.399999618530273px;">
<span style="background-color: rgba(255, 255, 255, 0);"><b><span style="line-height: 16.100000381469727px;"><a href="mailto:kkreuser@godaddy.com">kkreuser@godaddy.com</a></span></b><span style="line-height: 16.866666793823242px;"></span><b><span style="line-height: 16.100000381469727px;"> <o:p></o:p></span></b></span></p>
<p class="MsoNormal" style="margin: 0in 0in 1pt; line-height: 18.399999618530273px;">
<b><span style="line-height: 16.100000381469727px; background-color: rgba(255, 255, 255, 0);"><a dir="ltr" href="tel:602-420-4121" x-apple-data-detectors="true" x-apple-data-detectors-type="telephone" x-apple-data-detectors-result="8/1">602-420-4121</a> (o)
/ <a dir="ltr" href="tel:480-258-7957" x-apple-data-detectors="true" x-apple-data-detectors-type="telephone" x-apple-data-detectors-result="8/2">480-258-7957</a> (m)</span></b></p>
<p class="MsoNormal" style="margin: 0in 0in 1pt; line-height: 18.399999618530273px;">
<br>
</p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt;"><span style="background-color: rgba(255, 255, 255, 0);"> </span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt;"><i style="background-color: rgba(255, 255, 255, 0);">This email message and any attachments hereto is intended for use only by the addressee(s) named herein and may contain confidential information. If
you have received this email in error, please immediately notify the sender and permanently delete the original and any copy of this message and its attachments.</i></p>
</div>
<div><br>
On Oct 2, 2016, at 9:09 PM, Greg Shatan <<a href="mailto:gregshatanipc@gmail.com">gregshatanipc@gmail.com</a>> wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>I have to agree with Rubens and Michael, with the following additional thoughts:
<div><br>
</div>
<div>Specification 13 was an after the fact "patch" on the Registry Agreement, because it was fundamentally not "fit for purpose" for .Brand registries. There's no reason to perpetuate a patch, which effectively changes the agreement anyway, when we have an
opportunity to create an appropriate agreement for these registries.</div>
<div><br>
</div>
<div>Having a modest number of differing agreements sharing many common provisions is not going to cause "massive overhead" for anybody. This might a valid criticism if we were talking about hundreds of individual agreements drafted and negotiated from scratch
or from totally different templates (as might happen if the applicants, rather than ICANN, submitted the first drafts of their agreements), but that's not what anybody's suggesting.</div>
<div><br>
</div>
<div>Greg</div>
<div><br>
</div>
<div><br>
On Sunday, October 2, 2016, Michael Flemming <<a href="mailto:flemming@brightsconsulting.com">flemming@brightsconsulting.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div>From my own personal opinion and not in my role as Co-Chair, I reply with the following.</div>
<div><br>
</div>
I will have to echo Rubens in my opinion. I believe there is a firm demand for separate agreements
<div>because there exist many provisions within the 2012 RA that do not take into account the needs of</div>
<div>different categories. Moreover, noting that the 2012 RA was built around the one-size fits all gTLD</div>
<div>basis, it was not until we began asking ICANN for certain provisions/exemptions to the RA because</div>
<div>they didn't apply to the outlook of that TLD that we saw progress in this area. I think that I can argue</div>
<div>the point that ICANN has been very uncooperative in this area because they still think all TLDs must</div>
<div>operate around the same outlook. Whenever I have a conversation with ICANN about dotBrands, the</div>
<div>response is that ICANN has little experience, contractually and on a service level, with TLDs other than </div>
<div>gTLDs that operated until the New gTLD program. We are seeing the development of new categories,</div>
<div>that I believe we already have a consensus for in the overall working group, that have large issues</div>
<div>that do not pertain to other categories. While it is likely that potential category based RAs will have a</div>
<div>similar model and base for technical standards, it is necessary to build the contract with the outlook of</div>
<div>the TLD in mind. Keeping the same contract we have puts forth too much constraint on the TLDs and </div>
<div>limits the cooperation of ICANN to recognize how TLDs operate differently in the scope of their category.</div>
<div>Furthermore, as Rubens pointed out, most TLDs will likely switch over to the separate agreements</div>
<div>per their respective category in the future.</div>
<div><br>
</div>
<div>Regards, </div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">Michael Flemming<br>
<br>
<div class="gmail_quote">On Mon, Oct 3, 2016 at 8:57 AM, Rubens Kuhl <span dir="ltr">
<<a href="javascript:_e(%7B%7D,'cvml','rubensk@nic.br');" target="_blank">rubensk@nic.br</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word"><br>
<div><span>
<blockquote type="cite">
<div>On Oct 2, 2016, at 8:21 PM, Zylstra, Raymond <<a href="javascript:_e(%7B%7D,'cvml','Raymond.Zylstra@neustar.biz');" target="_blank">Raymond.Zylstra@neustar.biz</a>> wrote:</div>
<br>
<div>
<div style="font-family:Helvetica;font-size:12px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">
<div style="margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">
Dear all,<u></u><u></u></div>
<div style="margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">
<u></u><u></u></div>
<div style="margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">
I wanted to start the discussion on a question that was raised about the Base Agreement just prior to the end of the 22 September call the question of does a single base agreement make sense for all types of registries? and the need to have different agreements
for different categories of TLDs.<span> </span><u></u><u></u></div>
<div style="margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">
<u></u><u></u></div>
<div style="margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">
I do not believe that the concept of multiple Registry Agreements is warranted. This is an important topic and I believe the discussion should be broader than simply answering the question as posed. Provided below are some issues I believe we should consider
in order to respond to the question.<span> </span><u></u><u></u></div>
<div style="margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">
<u></u><u></u></div>
<div style="margin:0cm 0cm 0.0001pt 54pt;font-size:11pt;font-family:Calibri,sans-serif">
<span><span style="font-style:normal;font-weight:normal;font-size:7pt;line-height:normal;font-family:'Times New Roman'"> <span> </span></span></span>Predictab<wbr>ility This is something that is often talked about, and also applies in this
case. As an end user should I expect the same service levels and requirements of TLDs as I navigate the internet? I would argue yes. It seems that we could end up in a situation where 2012 Registry Operators have very different obligations.</div>
</div>
</div>
</blockquote>
<div><br>
</div>
</span>That is already not the case, due to the existence of ccTLDs and gTLDs... 2012 Registry Operators would possibly move to the new portfolio of agreements. </div>
<div><span><br>
<blockquote type="cite">
<div>
<div style="font-family:Helvetica;font-size:12px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">
<div style="margin:0cm 0cm 0.0001pt 54pt;font-size:11pt;font-family:Calibri,sans-serif">
<u></u><u></u></div>
<div style="margin:0cm 0cm 0.0001pt 54pt;font-size:11pt;font-family:Calibri,sans-serif">
<span><span style="font-style:normal;font-weight:normal;font-size:7pt;line-height:normal;font-family:'Times New Roman'"> <span> </span></span></span>Level Playing Field A level playing field is important for 2012 Applicants and Registry
Operators and those future Applicants; introducing a different Registry Agreement for future Applicants may unfairly disadvantage those who have signed the 2012 Registry Agreement.</div>
</div>
</div>
</blockquote>
<div><br>
</div>
</span>ICANN has moved most gTLDs with prior agreements to agreements that look a lot like 2012 RA, so that also doesn't hold. </div>
<div><span><br>
<blockquote type="cite">
<div>
<div style="font-family:Helvetica;font-size:12px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">
<div style="margin:0cm 0cm 0.0001pt 54pt;font-size:11pt;font-family:Calibri,sans-serif">
<u></u><u></u></div>
<div style="margin:0cm 0cm 0.0001pt 54pt;font-size:11pt;font-family:Calibri,sans-serif">
<span><span style="font-style:normal;font-weight:normal;font-size:7pt;line-height:normal;font-family:'Times New Roman'"> <span> </span></span></span>Status Quo We currently have a Registry Agreement, albeit with additional Specifications,
under which the various categories of TLDs can, and do, operate. While there are certainly situations where the Registry Agreement is not ideal, it is functional; there are things about it which we may not like, but they are not show stoppers.</div>
</div>
</div>
</blockquote>
<div><br>
</div>
</span>Some situations would be show stoppers if ICANN actually exercised those, so that is still to be seen... </div>
<div><span><br>
<blockquote type="cite">
<div>
<div style="font-family:Helvetica;font-size:12px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">
<div style="margin:0cm 0cm 0.0001pt 54pt;font-size:11pt;font-family:Calibri,sans-serif">
<u></u><u></u></div>
<div style="margin:0cm 0cm 0.0001pt 54pt;font-size:11pt;font-family:Calibri,sans-serif">
<span><span style="font-style:normal;font-weight:normal;font-size:7pt;line-height:normal;font-family:'Times New Roman'"> <span> </span></span></span>Where Does the Problem Lie As with many of you I have experienced many operational issues
dealing with ICANN and their lack of understanding of the diverse business models for different TLDs. I dont believe that having a different Registry Agreement will solve that issue, rather it is a case of working with ICANN to resolve those problems, and
I for one have had some success with this.</div>
</div>
</div>
</blockquote>
<div><br>
</div>
</span>Even if some success was achieved, that is still more stressful and costly that it should. </div>
<div><span><br>
<blockquote type="cite">
<div>
<div style="font-family:Helvetica;font-size:12px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">
<div style="margin:0cm 0cm 0.0001pt 54pt;font-size:11pt;font-family:Calibri,sans-serif">
<u></u><u></u></div>
<div style="margin:0cm 0cm 0.0001pt 54pt;font-size:11pt;font-family:Calibri,sans-serif">
<span><span style="font-style:normal;font-weight:normal;font-size:7pt;line-height:normal;font-family:'Times New Roman'"> <span> </span></span></span>Lengthy Process Without question the development of, and agreement to, multiple Registry
Agreements has the potential seriously compromise the timelines for the commencement of subsequent new gTLDs. Further, on the call brands were singled out; however, I am confident that many Registry Operators could argue some form of unique requirement which
they believe required a unique Registry Agreement.</div>
</div>
</div>
</blockquote>
<div><br>
</div>
</span>Actually I believe the call mentioned brand and exclusive use TLDs, both of which already have different specifications. Community TLDs also have a different specification, and there are also in the 2012 agreement a different version (not specification)
for governmental entities. See <a href="https://www.icann.org/resources/agreement/rio-2014-02-27-en" target="_blank">https://www.icann.org/reso<wbr>urces/agreement/rio-2014-02-27<wbr>-en</a> for one example that this is already in place in the 2012 agreement. </div>
<div><br>
</div>
<div><span>
<blockquote type="cite">
<div>
<div style="font-family:Helvetica;font-size:12px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">
<div style="margin:0cm 0cm 0.0001pt 54pt;font-size:11pt;font-family:Calibri,sans-serif">
<u></u><u></u></div>
<div style="margin:0cm 0cm 0.0001pt 54pt;font-size:11pt;font-family:Calibri,sans-serif">
<span><span style="font-style:normal;font-weight:normal;font-size:7pt;line-height:normal;font-family:'Times New Roman'"> <span> </span></span></span>Administr<wbr>ative Burden The introduction of multiple Registry Agreements and dealing
with these new agreements and the 2012 Registry Agreement will introduce massive overhead for ICANN, Registry Operators, Applicants, and service providers.</div>
</div>
</div>
</blockquote>
<div><br>
</div>
</span>I agree with the overhead for ICANN, but not necessarily for ROs, applicants and SPs; if different agreements come with less requirements, that can be less overhead for those. </div>
<span><font color="#888888">
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div>Rubens</div>
<div><br>
</div>
</font></span></div>
<br>
______________________________<wbr>_________________<br>
Gnso-newgtld-wg-wt2 mailing list<br>
<a href="javascript:_e(%7B%7D,'cvml','Gnso-newgtld-wg-wt2@icann.org');" target="_blank">Gnso-newgtld-wg-wt2@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg-wt2" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/l<wbr>istinfo/gnso-newgtld-wg-wt2</a><br>
</blockquote>
</div>
<br>
</div>
</div>
</blockquote>
</div>
</div>
</blockquote>
<blockquote type="cite">
<div><span>_______________________________________________</span><br>
<span>Gnso-newgtld-wg-wt2 mailing list</span><br>
<span><a href="mailto:Gnso-newgtld-wg-wt2@icann.org">Gnso-newgtld-wg-wt2@icann.org</a></span><br>
<span><a href="https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg-wt2">https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg-wt2</a></span></div>
</blockquote>
</div>
</blockquote>
</body>
</html>