<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body>
<p>Hi Jeff, <br>
</p>
<p>When are the new Redlined sections (as revised by Staff) reviewed
by the full WG? How/when can it be shared that a redline edit may
not be reflective of a change the WG thought it was making?</p>
<p>Best, Kathy<br>
</p>
<div class="moz-cite-prefix">On 2/27/2020 10:37 AM, Jeff Neuman
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:LNXP123MB1786744064A913BE96B7997990EB0@LNXP123MB1786.GBRP123.PROD.OUTLOOK.COM">
<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:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@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:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1756127282;
mso-list-type:hybrid;
mso-list-template-ids:1563062148 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:38.4pt;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:74.4pt;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:110.4pt;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:146.4pt;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:182.4pt;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:218.4pt;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:254.4pt;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:290.4pt;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:326.4pt;
text-indent:-.25in;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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]-->
<div class="WordSection1">
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><i>Dear Working Group members,</i><o:p></o:p></p>
<p class="MsoNormal"><i> </i><o:p></o:p></p>
<p class="MsoNormal"><i>The Co-Chairs would like to add an item
to the agenda for the call later today. As discussed on our
13 February Working Group call, the WG leadership team has
been considering the best way to manage the WG’s process for
reviewing and revising draft recommendations to include in
the draft Final Report. The WG has now discussed a number of
draft report sections on calls, and would like to propose
the following next steps:</i><o:p></o:p></p>
<p class="MsoNormal"><i> </i><o:p></o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph"
style="margin-left:2.4pt;mso-list:l0 level1 lfo1"><i><span
style="font-size:11.0pt">We are currently using the
following Working Document to support initial review and
discussion of draft recommendations:
<a
href="https://docs.google.com/document/d/1kUlmZH8nxWTgfcRluA5FxLheMm4XhhOwkRt7om52aQU/edit"
moz-do-not-send="true">
https://docs.google.com/document/d/1kUlmZH8nxWTgfcRluA5FxLheMm4XhhOwkRt7om52aQU/edit#</a>.
This will continue to be the document where you will
find newly drafted recommendations that have not yet
been discussed on a call. You are encouraged before each
call to review the sections on the upcoming agenda and
insert comments into the document and/or raise
questions/concerns on the mailing list. Staff will
continue to note preliminary suggested edits in the
Working Document during the call as items are discussed.
</span></i><o:p></o:p></li>
<li class="MsoListParagraph"
style="margin-left:2.4pt;mso-list:l0 level1 lfo1"><i><span
style="font-size:11.0pt">Once a section has been
discussed on a call (or multiple calls), the leadership
team will work on revisions in redline in the Working
Document.
</span></i><o:p></o:p></li>
<li class="MsoListParagraph"
style="margin-left:2.4pt;mso-list:l0 level1 lfo1"><i><span
style="font-size:11.0pt">When a set of revised sections
are ready for review by the WG, the leadership team will
add a “clean” version of those sections to a new
document, what we are tentatively calling the
“Production” document, which will be read-only. These
sections will be released in logical clusters, for
example all sections related to Pre-Launch Activities.
The leadership team will send an email to the group with
date by which any comments on those sections should be
provided. A redline of the revisions will be available
in the Working Document for reference, but once the
revision is sent out, members should not add new
comments or suggestions in the Working Document.
Instead, they should follow the process below.</span></i><o:p></o:p></li>
<li class="MsoListParagraph"
style="margin-left:2.4pt;mso-list:l0 level1 lfo1"><i><span
style="font-size:11.0pt">The Working Group will use the
method used successfully by the EPDP Team in the
finalization of their Initial Report. Specifically, WG
members will be asked to limit comments to items in the
revised section that they absolutely “cannot live with.”
If there is text that they cannot accept, they will fill
out a form like the one attached and send it to the WG
by email. The form asks for the specified text that the
WG member cannot accept, a suggested revision, and the
rationale for the revision.</span></i><o:p></o:p></li>
<li class="MsoListParagraph"
style="margin-left:2.4pt;mso-list:l0 level1 lfo1"><i><span
style="font-size:11.0pt">Any issues identified will be
addressed and resolved on the mailing list, or if
necessary, scheduled for discussion on a subsequent
call.</span></i><o:p></o:p></li>
</ul>
<p class="MsoNormal"><i> </i><o:p></o:p></p>
<p class="MsoNormal"><i>We realize that this process is new and
WG members may have questions about it, which is why we are
starting this discussion about the process on the upcoming
call. Given the large amount of material we have to cover in
the coming months and the importance of staying on schedule
with the revised work plan, the leadership team is confident
that the proposed path forward will keep the group moving
forward. We look forward to continuing the discussion as we
finalize the next steps.
</i><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b><span
style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black"
lang="EN-GB">Jeff Neuman & Cheryl Langdon-Orr<o:p></o:p></span></b></p>
<p class="MsoNormal"><b><i><span
style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black"
lang="EN-GB">Subsequent Procedures PDP Co-Chairs</span></i></b><i><span
style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black"
lang="EN-GB"><o:p></o:p></span></i></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<hr>
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"
moz-do-not-send="true">www.comlaude.com</a>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Gnso-newgtld-wg mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Gnso-newgtld-wg@icann.org">Gnso-newgtld-wg@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg">https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg</a>
_______________________________________________
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (<a class="moz-txt-link-freetext" href="https://www.icann.org/privacy/policy">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a class="moz-txt-link-freetext" href="https://www.icann.org/privacy/tos">https://www.icann.org/privacy/tos</a>). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.</pre>
</blockquote>
</body>
</html>