<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><meta http-equiv="Content-Type" content="text/html; charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><p lang="en-US" style="margin-bottom: 0in" class=""><br class=""></p><p lang="en-US" style="margin-bottom: 0in" class="">Good afternoon :</p><p lang="en-US" style="margin-bottom: 0in" class="">In the question of the
Implementation Review Teams (IRT's) by any other name, I come to this
rather unexpectedly. So, before joining the 'SMALL GROUP' established
by the PDP Call on 6 May, I would wish to just summarize and explain
what I said during that call.<br class=""><br class=""><b class="">1. Predictability</b> :
It is a primary röle for the PDP to establish rules and procedures
which give rise to predictability for all parties concerned. At
present the PDP and the work Tracks, (particularly WT5) are far from
creating a predictability framewlork. This is primarily because some
participants express a tangible reluctance to accept rules and
procedures that would be predictable for third parties.<br class=""><br class="">Thus,
the primary responsibility of the PDP is to fix the predictability
issues including those that have not been resolved at the Work Track level.<br class=""><br class="">Meanwhile,. It is not appropriate to charge IRTs
with 'interlpreting' the consequences of unresolved policy
issues.<br class=""><br class=""><b class="">2. Implementation vs. Policy</b> : This
risques becoming a false distinction. What is a minor issue for some
could be a major issue for others. Specifically the resolution of a
minor issue for one application could become a precedent for other
applications. Any eventual IRT would inevitably be 'looking over its
shoulder' to see what would be the consequences elsewhere i.e.
Policy.<br class=""><br class="">
</p>
<ol start="3" class="">
<li class=""><p lang="en-US" style="margin-bottom: 0in" class=""><b class="">Third Parties</b> :
The expansion of the DNS inevitably impinges on the interests of
parties that are neither contdracted pardtdies, nor applicatns. To
ignore this would absolutely guarantee a lack of predictability both
for the applicants and for third parties concerned. <br class=""><br class="">There
is a discontinuity between the presuppositions in the PDP andl the
GNSO as to how matters should proceed, and the natural assumptions
of concerned third lparties which are « Write to the Board »
or « Write to the GAC member ». Thus considerably
reducing the scope for eventual IRTs to handle questions that will
rapidly go beyond their control, particularly it becomes a matter of
Policy.<br class=""><br class=""><b class="">4. The 'Standing IRT?'</b> Should it become
necessary to create an entity 'between' the AGB process and the
Staff on the one hand, and the GNSO and the Board on the other hand,
we would be creating an entity with significant power. If so, it must be
enhanced with full transparency, independence and accountability
to the Community, that is to all Stakeholders, By dealing with unforeseen
issues affecting applicants and third parties, the entity will
inevitably create policy by precedent, if not by its intended decisions.<br class=""><br class="">5.
In <b class="">Conclusion</b>: I come back to the first point that is that
the PDP and WT5 need to do a lot more concrete work to create
predictability. With regard to third party interests, a lack of
predictability will undermine predictability for applicants;
unresolved issues will simply escalate and create delays and
uncertainties. As before.<br class=""><br class="">Let us bear in mind that in future
'rounds' most applicants may not benefit from experience from 2012,
nor from inside knowledge of the PDP and Work Tracks.</p><div style="margin-bottom: 0in;" class=""><br class=""></div><div style="margin-bottom: 0in;" class="">An 'IRT' would not be
able to resolve lacunae arising from the PDP itself.</div><p lang="en-US" style="margin-bottom: 0in" class=""><br class="">Regards
Christopher Wilkinson</p><p lang="en-US" style="margin-bottom: 0in" class=""><br class="">Xàbia, 8 May 2019Good evening :</p><p lang="en-US" style="margin-bottom: 0in" class=""><br class="">
</p><p lang="en-US" style="margin-bottom: 0in" class=""><br class=""></p></li></ol><div class=""><blockquote type="cite" class=""><div class="">On 7 May 2019, at 22:05, Aikman-Scalese, Anne <<a href="mailto:AAikman@lrrc.com" class="">AAikman@lrrc.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="WordSection1" style="page: WordSection1; caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(31, 73, 125);" class="">Dear WG members:<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(31, 73, 125);" class="">Regarding the smaller group assembled to work on how staff and the proposed “post-launch Standing IRT” might determine whether an issue is policy or implementation, I would like to clarify again the history that led to the existing GNSO processes designed to address these issues whenever they arise –either Pre- or –Post launch:<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(31, 73, 125);" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(31, 73, 125);" class="">The Policy & Implementation Working Group grappled with this question of policy versus implementation for many months and concluded it was impossible to make determinations about that in advance because “one person’s policy is another person’s implementation”. That is exactly why we have the result we have in the form of GNSO Input (which is essentially for implementation issues), GNSO Guidance, and GNSO EPDP. In fact, it was Marika Koenigs who first suggested to the Policy & Implementation WG that, based on our case studies of issues that arose in the 2012 round, it was impossible to “predict” issues that might arise and label them as clearly policy or clearly implementation. Jeff has pointed out that applicants want more “predictability” in the process so that time delays do not result. Thus, the proposed “Predictability Framework” anticipates that ICANN staff and/or or some newly created body will be able to decide issues that arise post-launch. The “problem” Jeff is trying to resolve as Co-Chair is that if an issue reaches the GNSO, it may take too long to resolve and thus is not practical for registry applicants. However, as far as I know, we have not yet tried out these new processes (except for the EPDP on the Temp Spec) so it seems to me a bit premature to be inventing new processes and acronyms on top of the ones that have not yet been tried. <b class="">It strikes me that for various Implementation issues that actually rise to the level of an issue post-launch, the existing GNSO Input process (which has not yet been used) is adequate and is in fact designed to operate in that fashion since GNSO can raise such a concern “at any time it deems appropriate”.<o:p class=""></o:p></b></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(31, 73, 125);" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><u class=""><span style="color: rgb(31, 73, 125);" class="">Under existing GNSO processes established as a result of the work of the Policy & Implementation Working Group</span></u><span style="color: rgb(31, 73, 125);" class="">, the “gateway” is in fact a question of the interaction between and among Staff, an IRT (or Post-launch Standing IRT), and the GNSO Council. Staff can raise an issue, IRT can raise an issue, and ANY GNSO Council member can raise an issue and so these are the “gates”. (In other words, there are multiple gates and they all ultimately lead to oversight by GNSO Council.) My own view (having worked actively in the Policy & Implementation Working Group on several case studies of issues that arose Post-Launch in the 2012 round) is that if an issue is truly implementation, no one is going to raise the issue to the level of GNSO. Issues will only rise to that level if a stakeholder believes that GNSO Council should address it and that applies whether it’s merely implementation (“GNSO Input” Annex) or involves policy (“GNSO Guidance” Annex or “GNSO EPDP” Annex). <span class="Apple-converted-space"> </span><o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(31, 73, 125);" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(31, 73, 125);" class="">Before the Sub Pro Initial Report issued, the Co-Chairs and staff ultimately agreed to make reference to the GNSO Input, Guidance, and EPDP processes but those processes were only referenced and footnoted, not actually explained to the ICANN community or the public. Importantly, the draft Initial Report language was clarified to delete the reference to the Standing IRT “deciding” an issue based on the Predictability Framework. Instead, in the Initial Report, there is a reference to the Standing IRT being able to “recommend” a resolution of the issue. In terms of ICANN governance and the ByLaws as modified after the Policy & Implementation WG finished its work, that is the correct stance. Establishing some other “gate” or some method for determining in advance what is policy and what is implementation when the existing processes adopted after a full WG process have not been tried does not make sense to me.<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(31, 73, 125);" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(31, 73, 125);" class="">By way of additional background, the whole Policy & Implementation Working Group evolved from the fact that then-CEO Fadi Chehade decided that the “Strawman Solution” in relation to trademarks was implementation, not policy. Fadi issued a public statement to this effect. GNSO Council members were upset about this and our Co-Chair Jeff Neuman wrote the letter to the ICANN Board stating that if the Board took action (such as the Strawman Solution) that amounted to a change in policy, they had to come back to GNSO for its views on the topic and more specifically, to make a determination as to whether the topic required more policy work or merely some GNSO input. <o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(31, 73, 125);" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(31, 73, 125);" class="">Clearly the timing as to when an issue arises (either pre- or post- launch) is NOT a determiner of whether it is Policy or Implementation. So Chuck Gomes led the P & I WG as a result of the GNSO Council’s dissatisfaction with the handling of that issue (and others) that arose Post-Launch and we spent more than year (probably about 2 years) reviewing numerous issues that arose after applications were filed in the 2012 round. That is why the GNSO processes called Input, Guidance and EPDP were adopted by the GNSO Council and that is why the ICANN ByLaws were amended. <o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(31, 73, 125);" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(31, 73, 125);" class="">Hopefully the above history helps to clarify why I was quoting existing GNSO Operating Procedures and Annexes. Again, I don’t think the public understood these processes when the Initial Report issued. The current Consensus Policy Implementation Framework (“CPIF”) of the GNSO makes specific reference to these processes and requires that IRT members be briefed on them.<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(31, 73, 125);" class="">Anne<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(31, 73, 125);" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><a name="_MailEndCompose" class=""><span style="color: rgb(31, 73, 125);" class=""><o:p class=""> </o:p></span></a></div><div class=""><div style="border-style: solid none none; border-top-width: 1pt; border-top-color: rgb(225, 225, 225); padding: 3pt 0in 0in;" class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><b class="">From:</b><span class="Apple-converted-space"> </span>Gnso-newgtld-wg [<a href="mailto:gnso-newgtld-wg-bounces@icann.org" style="color: rgb(149, 79, 114); text-decoration: underline;" class="">mailto:gnso-newgtld-wg-bounces@icann.org</a>]<span class="Apple-converted-space"> </span><b class="">On Behalf Of<span class="Apple-converted-space"> </span></b>Jeff Neuman<br class=""><b class="">Sent:</b><span class="Apple-converted-space"> </span>Tuesday, May 7, 2019 1:57 AM<br class=""><b class="">To:</b><span class="Apple-converted-space"> </span><a href="mailto:gnso-newgtld-wg@icann.org" style="color: rgb(149, 79, 114); text-decoration: underline;" class="">gnso-newgtld-wg@icann.org</a><br class=""><b class="">Subject:</b><span class="Apple-converted-space"> </span>[Gnso-newgtld-wg] FW: Follow up from May 6th and CALL FOR SMALL GROUP<o:p class=""></o:p></div></div></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><strong class=""><span style="font-size: 9pt; font-family: Helvetica, sans-serif;" class="">[EXTERNAL]</span></strong><span style="font-size: 9pt; font-family: Helvetica, sans-serif;" class=""><o:p class=""></o:p></span></div><div class="MsoNormal" align="center" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; text-align: center;"><span style="font-size: 12pt; font-family: "Times New Roman", serif;" class=""><hr size="2" width="100%" align="center" class=""></span></div></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">All,<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Following up on the call yesterday, we have revised the document on the Proposed New Predictability Model. You can find it here: <a href="https://docs.google.com/document/d/12_x8zYR9r6zXqfA7dmoosSPH12NmcyJ-2FEjecGrBh4/edit?usp=sharing" style="color: rgb(149, 79, 114); text-decoration: underline;" class="">https://docs.google.com/document/d/12_x8zYR9r6zXqfA7dmoosSPH12NmcyJ-2FEjecGrBh4/edit?usp=sharing</a>. The comments made during the call should be incorporated either as revised language itself, or as “comments” for draft language to be created.<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">As we discussed, we would like to have a smaller group dedicated to working through the issues that remain on this topic so that a more comprehensive proposal can be presented to the full working group at a later date on the Predictability Framework. The group is open to any current Working Group members. However, if you join the small group, you are expected to put in some time to try and resolve whatever issues remain. The small group MAY have a call or two, but the hope is that all of the work can be done in e-mail and through the documents itself. We will create a mailing list to work on these issues. This is NOT a formal group.<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">So far, I think we captured the following people to be on this group (from the call last night):<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Jeff Neuman<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Cheryl-Langdon Orr<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Kathy Kleiman<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Christopher Wilkinson<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Kristina Rosette<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">There may have been others that already volunteered, but may not have captured, so please indicate your interest to us if you want to be a part of the smaller team. <o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">We will not be doing formal consensus calls as part of this smaller group, but rather just making the proposal better and filling in the holes to present to the full working group.<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Please let me know if you have any questions.<span class="Apple-converted-space"> </span><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Best regards,<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><b class=""><span lang="EN-GB" style="font-size: 9pt; font-family: Arial, sans-serif;" class="">Jeffrey J. Neuman</span></b><span lang="EN-GB" style="font-size: 9pt; font-family: Arial, sans-serif;" class=""><br class="">Senior Vice President<o:p class=""></o:p></span></div><p class="MsoNormal" style="margin: 0in 0in 12pt; font-size: 11pt; font-family: Calibri, sans-serif;"><b class=""><span lang="EN-GB" style="font-size: 9pt; font-family: Arial, sans-serif;" class="">Com Laude | Valideus<br class=""></span></b><span lang="EN-GB" style="font-size: 9pt; font-family: Arial, sans-serif;" class="">1751 Pinnacle Drive , Suite 600<br class="">Mclean , VA 22102<br class="">UNITED STATES <br class="">T: +1.703.635.7514<br class="">M: +1.202.549.5079<o:p class=""></o:p></span></p><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span lang="EN-GB" style="font-family: Arial, sans-serif;" class=""> <o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span lang="EN-GB" style="font-size: 8pt; font-family: Arial, sans-serif;" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span lang="EN-GB" style="font-size: 8pt; font-family: Arial, sans-serif;" class="">CONFIRMATION OF ORDERS: Please note that we always confirm receipt of orders. To assist us in identifying orders, please use the word ORDER in the subject line of your email. If you have sent us an order and have not received confirmation on the same working day (PST) it is possible that your order has not been received or has been trapped by our spam filter. In this case, please contact your client manager or<span class="Apple-converted-space"> </span><a href="mailto:admin@comlaude.com" style="color: rgb(149, 79, 114); text-decoration: underline;" class="">admin@comlaude.com</a><span class="Apple-converted-space"> </span>for confirmation that the order has been received and is being processed. Thank you.<o:p class=""></o:p></span></div></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div class=""><div style="border-style: solid none none; border-top-width: 1pt; border-top-color: rgb(225, 225, 225); padding: 3pt 0in 0in;" class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><b class="">From:</b><span class="Apple-converted-space"> </span>Gnso-newgtld-wg <<a href="mailto:gnso-newgtld-wg-bounces@icann.org" style="color: rgb(149, 79, 114); text-decoration: underline;" class="">gnso-newgtld-wg-bounces@icann.org</a>><span class="Apple-converted-space"> </span><b class="">On Behalf Of<span class="Apple-converted-space"> </span></b>Julie Hedlund<br class=""><b class="">Sent:</b><span class="Apple-converted-space"> </span>Monday, May 6, 2019 11:40 PM<br class=""><b class="">To:</b><span class="Apple-converted-space"> </span><a href="mailto:gnso-newgtld-wg@icann.org" style="color: rgb(149, 79, 114); text-decoration: underline;" class="">gnso-newgtld-wg@icann.org</a><br class=""><b class="">Subject:</b><span class="Apple-converted-space"> </span>[Gnso-newgtld-wg] Notes and Action Items - New gTLD Subsequent Procedures PDP WG - 06 May 2019<o:p class=""></o:p></div></div></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Dear Working Group members,<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""> <o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Please see below the notes from the meeting today, 06 May 2019. These high-level notes are designed to help WG members navigate through the content of the call and are not a substitute for the recording, transcript, or the chat, which will be posted at:<span class="Apple-converted-space"> </span><a href="https://community.icann.org/display/NGSPP/2019-05-06+New+gTLD+Subsequent+Procedures+PDP" style="color: rgb(149, 79, 114); text-decoration: underline;" class="">https://community.icann.org/display/NGSPP/2019-05-06+New+gTLD+Subsequent+Procedures+PDP</a>.<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""> <o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Please also see the referenced documents at: <a href="https://docs.google.com/document/d/1R4zXTH3hIgfbqoxyqsSp19Bl6J96NNeV7oCgxsXKD-w/edit?usp=sharing" title="https://docs.google.com/document/d/1R4zXTH3hIgfbqoxyqsSp19Bl6J96NNeV7oCgxsXKD-w/edit?usp=sharing" style="color: rgb(149, 79, 114); text-decoration: underline;" class="">https://docs.google.com/document/d/1R4zXTH3hIgfbqoxyqsSp19Bl6J96NNeV7oCgxsXKD-w/edit?usp=sharing</a>.<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""> <o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Kind regards,<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Julie<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Julie Hedlund, Policy Director<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""> <o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><b class="">Notes and Action Items:</b><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""> <o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><b class="">Action Items:</b><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">ACTION ITEM 1: Staff to incorporate edits as discussed into the 2.2.2 Predictability document.<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">ACTION ITEM 2: Gather a small group to further develop the 2.2.2 Predictability document at:<a href="https://docs.google.com/document/d/12_x8zYR9r6zXqfA7dmoosSPH12NmcyJ-2FEjecGrBh4/edit#heading=h.8vi2q2obcb8w" style="color: rgb(149, 79, 114); text-decoration: underline;" class="">https://docs.google.com/document/d/12_x8zYR9r6zXqfA7dmoosSPH12NmcyJ-2FEjecGrBh4/edit#heading=h.8vi2q2obcb8w</a>. Jeff will send out a call for volunteers to the list. Volunteers thus far: Kristina Rosette, Kathy Kleiman and Christopher Wilkinson.<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><b class="">Notes:</b><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">1. Updates to Statements of Interest (SOIs): No updates provided.<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">2. Review of Summary Documents – (see:<span class="Apple-converted-space"> </span><a href="https://docs.google.com/document/d/1R4zXTH3hIgfbqoxyqsSp19Bl6J96NNeV7oCgxsXKD-w/edit?usp=sharing" style="color: rgb(149, 79, 114); text-decoration: underline;" class="">https://docs.google.com/document/d/1R4zXTH3hIgfbqoxyqsSp19Bl6J96NNeV7oCgxsXKD-w/edit?usp=sharing</a>)<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">a. Continued: 2.2.2 Predictability / 2.2.2.2 Clarity of Application Process: See:<a href="https://docs.google.com/document/d/12_x8zYR9r6zXqfA7dmoosSPH12NmcyJ-2FEjecGrBh4/edit#heading=h.8vi2q2obcb8w" style="color: rgb(149, 79, 114); text-decoration: underline;" class="">https://docs.google.com/document/d/12_x8zYR9r6zXqfA7dmoosSPH12NmcyJ-2FEjecGrBh4/edit#heading=h.8vi2q2obcb8w</a><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">-- Note: If we don’t come to consensus on a topic then the status quo will be as it was implemented in 2012. On the record that some do not support that approach.<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">-- There are some different things relating to IRTs that could be new.<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">2.2.2 Predictability:<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">-- Added bullet:<span class="Apple-converted-space"> </span><i class="">The Predictability Model<span class="Apple-converted-space"> </span><u class="">complements</u><span class="Apple-converted-space"> </span>the existing GNSO processes and procedures and shall not in any way operate to be a substitute or replacement for those. In fact, they are incorporated into the Predictability Framework explicitly.</i><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><u class="">Discussion</u>:<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">-- “they” references existing processes and procedures.<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">-- To avoid any doubt in future we might want to add, “In the event of a conflict, existing GNSO processes and procedures take precedent.”<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">-- Change from “shall not in any way operate to be” to “is not intended to be”.<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">What are we proposing:<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><u class="">B. Changes to ICANN Organization Internal Processes</u><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><u class="">Discussion:</u><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">-- Comfortable that we have a distinction for minor changes.<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">-- For the first bullet under (b) -- re: “anything visible” -- what does that encompass? Add “change the application or any of the other processes set forth in the applicant guidebook”. Or “those parts of the application that are scored”?<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">-- Third bullet -- New processes: Some examples have direct relevance for the entire community. Such as a new public comment platform.<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">-- Standing IRT decides what is implementation or policy -- but some WG members disagree.<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">-- Change to “Material adverse impact”?<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">-- Second bullet -- “all non-minor changes” -- in written policy? Answer: The output of this whole thing will eventually be the AGB and if there are changes to the AGB they would be written.<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">-- So not a reasonable response that a process will just take longer -- just being a communication. Seems like there should be more accountability. Add a comment/note to see if that falls under a different category.<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">-- Filter out those things that can be dealt with in a practical matter.<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">-- Third bullet: Need a gateway process before we get to these items. Wherever something affects the underlying rules has huge implications. <o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">-- Might need to clarify: “New public comment platform” means changes to the tools being used to submit. The rules for commenting is the same, but the platform is different.<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">-- Second bullet: Not meant to be a change in the timing, but a change in a portal. <o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">-- Add a line after bullet three, “These proposed changes are intended to be only those that involve mechanisms with no substantive impact.” Question: How is that different from this text, “but rather a New ICANN Organization Internal Process and it is likely to have a materially [adverse] impact on applicants or community members…” Seems similar in meaning.<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">-- An example of a change that wouldn’t be substantive but could have a material adverse impact would be requiring that Legal Rights Objections be filed through a proprietary platform instead of email. Wouldn't affect the substantive LRO (elements, standing, etc), but there may be some potential objectors that, for one reason or another, can't use that platform.<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">-- Are timelines on filing objections seen as a different type of timeline as a third-party timeline?<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">-- What might be a minor change for one party could be a major change to others. Adverse outcomes -- for whom? Should there be a policy gateway to determine? We don’t have a framework that would be considered to be predictable.<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">-- If there is a gateway then that could delay any changes.<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">-- Overriding principle is predictability. Trying to improve predictability from the last round.<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">C.<span class="Apple-converted-space"> </span><u class="">Fundamental Possible Policy Level Changes</u><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><u class="">Discussion:</u><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">-- Some examples seem to be out of scope for an IRT.<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">-- Deciding something that is policy: a standing IRT can raise that issue and the GNSO Liaison can take that back to the Council. Any Council member also can raise something for consideration at the Council level.<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">-- So a standing IRT can raise something, but only the Council can decide what is policy or implementation, but it sounds like we are setting up a separate gateway. The standing IRT cannot be the final arbiter, and the Council also can raise it directly.<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">-- Add to the bullet point that the standing IRT can make a recommendation to the GNSO Council as to whether something is policy or implementation, but the GNSO will make the final decision.<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">-- Ensure that this document is cross-referenced to the current policies and processes for IRTs.<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">-- What do we mean by “Staff will collaborate with the community”? Answer: That is meant to first go to the standing IRT, which makes a recommendation for additional consideration, and then the GNSO decides how to handle it -- GNSO Input Process, EPDP, etc.<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">-- Delete this text, “Staff will collaborate with the community to consider the issue and agree upon the mechanism by which the solution will be developed. Options could include:” And emphasize the point that this is meant to be a community+staff decision, not just staff. Mark them as redlined and to be replaced. Come back to this in another WG meeting.<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">-- Helpful to have a workflow diagram for the Predictability Framework once concepts are agreed and reconcile with existing ones from IRT Guidelines.<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">D.<span class="Apple-converted-space"> </span><u class="">Fundamental Possible Policy Level New Proposals</u><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><u class="">Discussion</u>:<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">-- Carry over changes from bullets under C.<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">-- Reaching out to the community means staff reaching out to the standing IRT. But don’t think the standing IRT has the authority to decide if something is a policy or implementation change. Could have a new group that includes members of the IRT, and also Council members, and then decide if it goes to the standing IRT.<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">-- Want to change what we call this because of previous problems with IRTs. Want to get the composition right so it is representative of the community. Meant to ensure that it is a gateway.<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">-- A number of groups supported the recommendations in the Initial Report but also some dissenting views: ACTION: Form a smaller group to further develop this document for the full WG. Volunteers thus far: Kristina Rosette, Kathy Kleiman and Christopher Wilkinson.<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div class="MsoNormal" align="center" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; text-align: center;"><span style="font-size: 12pt; font-family: "Times New Roman", serif;" class=""><hr size="2" width="100%" align="center" class=""></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 12pt; font-family: "Times New Roman", serif;" class="">The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that the Com Laude Group does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28-30 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 06181291 and registered office at 28-30 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176, having its registered office at 33 Melville Street, Edinburgh, Lothian, EH3 7JF Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, headquartered at 1751 Pinnacle Drive, Suite 600, McLean, VA 22102, USA; Com Laude (Japan) Corporation, a company registered in Japan having its registered office at Suite 319,1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan. For further information see<a href="https://comlaude.com/" target="_blank" style="color: rgb(149, 79, 114); text-decoration: underline;" class="">www.comlaude.com</a><o:p class=""></o:p></span></div></div><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><hr style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><font face="Arial" color="Gray" size="1" style="font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><br class="">This message and any attachments are intended only for the use of the individual or entity to which they are addressed. If the reader of this message or an attachment is not the intended recipient or the employee or agent responsible for delivering the message or attachment to the intended recipient you are hereby notified that any dissemination, distribution or copying of this message or any attachment is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the sender. The information transmitted in this message and any attachments may be privileged, is intended only for the personal and confidential use of the intended recipients, and is covered by the Electronic Communications Privacy Act, 18 U.S.C. §2510-2521.<span class="Apple-converted-space"> </span><br class=""></font><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class=""></span><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">_______________________________________________</span><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">Gnso-newgtld-wg mailing list</span><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><a href="mailto:Gnso-newgtld-wg@icann.org" style="color: rgb(149, 79, 114); text-decoration: underline; font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;" class="">Gnso-newgtld-wg@icann.org</a><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><a href="https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg" style="color: rgb(149, 79, 114); text-decoration: underline; font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;" class="">https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg</a></div></blockquote></div><br class=""></div></div></body></html>