<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
p.MsoNoSpacing, li.MsoNoSpacing, div.MsoNoSpacing
{mso-style-priority:1;
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri",sans-serif;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle23
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle24
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Dear All,<o:p></o:p></span></p>
<div>
<div>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p></o:p></span></p>
<div>
<div>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Please find the attendance and recording of the call attached to this email and the AC Chat below for the New gTLD Subsequent Procedures Sub Team – Track
2 – Legal/Regulatory Issues held on Thursday, 06 October 2016 at 20:00 UTC. </span>
<a href="http://audio.icann.org/gnso/gnso-new-gtld-subsequent-16may16-en.mp3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"><br>
</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> <o:p></o:p></span></p>
</div>
<div>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">The recordings of the calls are posted on the GNSO Master Calendar page:<o:p></o:p></span></p>
</div>
<div>
<p style="margin:0in;margin-bottom:.0001pt"><a href="http://gnso.icann.org/en/group-activities/calendar#nov" target="_blank"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:purple">http://gnso.icann.org/en/group-activities/calendar</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> <o:p></o:p></span></p>
</div>
<div>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> <o:p></o:p></span></p>
</div>
<div>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">** Please let me know if your name has been left off the list **<o:p></o:p></span></p>
</div>
<div>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> <o:p></o:p></span></p>
</div>
<div>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Mailing list archives: </span><a href="http://mm.icann.org/pipermail/gnso-newgtld-wg-wt2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#3B73AF;background:white">http://mm.icann.org/pipermail/gnso-newgtld-wg-wt2</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
</div>
<div>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> <o:p></o:p></span></p>
</div>
<div>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Wiki page: </span><a href="https://community.icann.org/x/FwSbAw"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">https://community.icann.org/x/FwSbAw</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p></o:p></span></p>
</div>
<div>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> <o:p></o:p></span></p>
</div>
<div>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Thank you.<o:p></o:p></span></p>
</div>
<div>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Kind regards,<o:p></o:p></span></p>
</div>
<div>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Terri
<o:p></o:p></span></p>
</div>
<div>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
</div>
<div>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">-------------------------------<o:p></o:p></span></p>
</div>
<div>
<p style="margin:0in;margin-bottom:.0001pt"><b><u><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Adobe Connect chat transcript
</span></u></b><b><u><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">for 06 October 2016<span style="color:black"><o:p></o:p></span></span></u></b></p>
<p class="MsoPlainText"> <span style="color:black"><o:p></o:p></span></p>
</div>
</div>
</div>
</div>
<div>
<p class="MsoNoSpacing">Terri Agnew: Welcome to the New gTLD Subsequent Procedures Sub Team – Track 2 – Legal/Regulatory Issues call held onThursday, 06 October 2016 at 20:00 UTC.<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Terri Agnew: agenda wiki page: https://community.icann.org/x/Tw_4Aw<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Alexander Schubert: Hello everybody :-)<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Alexander Schubert: 5: Reserved names. 2nd level or top level?<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Michael Flemming: Hello Alex and welcome.<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Michael Flemming: Both<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Michael Flemming: In a sense<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Michael Flemming: We will save that fun for last today :)<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">jeff neuman: Not everyone gets your humor :)<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Cheryl Langdon-Orr (CLO): Hi there Sorry I had to wrap up another call<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Cheryl Langdon-Orr (CLO): My morning is all back to back calls it seems<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Terri Agnew: Welcome Cheryl, still plenty of time left LOL<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Alexander Schubert: Well, if you're going to apply for a prepreviously ineligible string - it's not fun!<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">jeff neuman: I can provide a background on this<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">jeff neuman: 3<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Steve Chan: As noted, T&Cs are available as Module 6 of the AGB, but also available on the web here: https://newgtlds.icann.org/en/applicants/agb/terms<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Jim Prendergast: I would also ask - did the community have input into the T&Cs or the ability to suggest changes to them? Seems like everyone was focused on modules 1-5. Im not sure anyone every commented on module 6.<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Rubens Kuhl: Jeff's audio is fading<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Rubens Kuhl: (at least for me)<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Berry Cobb: Another vector for the group to monitor/consider is the changes to RfR and eventual release of the updated IRP as a result of the CCWG Accountability work. It did not specifically touch upon what these mean for subsequent
rounds/procedures, but it will be changing in the future.<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Rubens Kuhl: For me it seems it doesn't require a charter amendment in this case, but policy staff could enlight us on that...
<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Berry Cobb: Request for Reconcideration. <o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Berry Cobb: Yes<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Rubens Kuhl: What we could say at a policy level would be "Have T's&C's to reduce ICANN liability to the minimum level allowed by ICANN Bylaws, California law and US law".
<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Rubens Kuhl: Reference material: AGB Module 6, RfRs from the 2012 round, IRPs from the 2012 round...
<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Rubens Kuhl: + lawsuits from the 2012 round. <o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">jeff neuman: yes<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Rubens Kuhl: Two stress tests I suggest to T&C is the TAS issues that occurred, (1) freezing the application process (2) data leak...
<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Rubens Kuhl: TAS was the application system used by applicants in the 2012-round<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Rubens Kuhl: https://docs.google.com/spreadsheets/d/1mA_hTUhLhJSsfcmoQwREtUqxykZ5KfJffzJAAhEvNlA/edit#gid=0<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Rubens Kuhl: https://docs.google.com/document/d/1k1HrFIjwzupuJqr33WmGmBUD45SQ5Cv1-vNP7ZRztPk/edit<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Phil Marano (Mayer Brown): Another suggested stress test for the T&Cs: The threatened termination of a new gTLD application by ICANN based on rationale not established within the AGB, i.e. failure to meet a newly established interim
milestone.<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Rubens Kuhl: I would also add "Sponsored TLDs", which although being a twin brother of Community TLDs, have different regulatory framework.
<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Raymond Zylstra - Neustar: Question - Is reviewing 'categories' part of this WT? Or is it just if a single agreement makes sense?<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Alexander Schubert 2: And there is applications fitting in 4 of these categories in the same time ......<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Rubens Kuhl: Raymond, I believe it's WT1, and that we need to sequence our discussion on WT2 once the types discussion is settled.
<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">jeff neuman: Its the overall group, right<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Raymond Zylstra - Neustar: Another Consideration: 1 Size Fits All vs. 2 Sizes Fits All – Introducing version(s) of the Registry Agreement may just change the problem. Within categories of TLDs there will still be differing business models.<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Kristina Rosette (Amazon Registry): I have a clarifying question: Does "different base agreement" mean (a) a completely different base agreement for every category; (b) a standard base agreement with additional specifications that differ
(like Specification 13); or (c) something else entirely? (If the answer is (c), please elaborate). Thanks.<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Kristina Rosette (Amazon Registry): Thanks. <o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Rubens Kuhl: Note that we already have two different agreements at the 2012-round, and it's not based on specifications... it's the governmental and standard versions of the agreement.
<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Rubens Kuhl: What Jeff is saying. <o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Rubens Kuhl: Spec 9 - Code of Conduct (not applied for exclusive use TLDs and for Brand TLDs) Spec 12 - Community TLDs Spec 13-Brand TLDs.
<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">jeff neuman: Any participant of this WT<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Julie Hedlund: @Jeff: Not sure I captured your word correctly.<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Rubens Kuhl: Just to complicate Jeff's idea, there are Community Brand TLDs... ;-)<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Raymond Zylstra - Neustar: Question ‘What is the outcome of the ‘Scope of Work’? What is it that we working towards delivering?’<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">jeff neuman: Yes, scope of work is to make policy recommendations and to provide rationale for those recommendations<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Gg Levine (NABP): Wouldn't it be simpler to keep single base agreement and then fine-tune specs per catagory? Multiple specs might apply to applicants.. Doesn't make sense to have separate agreements.<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">jeff neuman: Gg - Yes that could be one outcome<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">jeff neuman: My goal is to take the abstract principle and make it more concrete<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Berry Cobb: I might suggest that you take a more targeted approach. Brands = Martin Sutton; Geos = RyO from a geo TLD; Community = RyOs that have gone through that. We know that these "categories" for lack of a better word exist today.<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Kristina Rosette (Amazon Registry): I would hope that the folks advocating for different agreements have a very good idea about what they do - and do not- want in a base agreement so it shouldn't take too long to articulate. Otherwise,
we could be doing this for a long time <o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">jeff neuman: I agree with Kristina. These groups are not going to draft a new agreement now<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Berry Cobb: I'd also recommend that it be communicated that the default is a single agreement at this point and only looking for rationale on why the WT should consider different versions.<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Terri Agnew: Next New gTLD Subsequent Procedures Sub Team – Track 2 – Legal/Regulatory Issues will take place on Thursday, 20 October 2016 at 20:00 UTC.<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">jeff neuman: I can reach out to Martin/Cecilia (from the BRG) and relay this conversation<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">jeff neuman: Cool. Thanks! Good Call.<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Cheryl Langdon-Orr (CLO): Thanks everyone... Thanks Michael... Talk again soon ... bye for now<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Alexander Schubert 2: bye<o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
</div>
</body>
</html>