<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="">Dear Justine: I support the line that Alberto has suggested.<div class=""><br class=""></div><div class="">There are several aspects pdf the likely PDP recommendations that should be open for discussion and comment by GAC members and At Large.</div><div class="">The multistakeholder composition of the PDP and WT5 does not yet take into consideration either the public interest or the specific issue of individual users’ interests.</div><div class=""><br class=""></div><div class="">I would be glad to contribute to drafting related proposals, if asked.-</div><div class=""><br class=""></div><div class="">Regards</div><div class=""><br class=""></div><div class="">Christopher</div><div class=""><br class=""></div><div class="">PS: As most colleagues will know, I was a member of GAC 1998-2002 and GAC Secretary 2002-2005, when I retired.</div><div class=""> I consider that it is extremely important that GAC and At Large converge on a mutually supportive concept of the public interest in ICANN.</div><div class=""><br class=""></div><div class=""><br class=""><div class=""><br class=""><blockquote type="cite" class=""><div class="">On 4 Dec 2019, at 22:49, Justine Chew <<a href="mailto:justine.chew@gmail.com" class="">justine.chew@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div dir="ltr" class=""><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small">All,<br class=""><br class="">Thank you for your input, Alberto. <br class=""><br class="">This matter was discussed by CPWG on its 4 Dec call whereupon <u class="">feedback was received to react positively to the GAC letter</u>. <br class=""><br class="">It was also decided that I should re-circulate my email (see below after Alberto's reply) for input for another 48 hours, and thereafter, I was to highlight the outcome to the ALAC for their onward action. <br class=""><br class="">Thus, if anyone has additional reactions to this issue, please let me have the same <u class="">by 7 Dec</u>.</div><div class=""><div dir="ltr" data-smartmail="gmail_signature" class=""><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div class=""><br class=""><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small">Thank you,</div><br class=""><font face="trebuchet ms, sans-serif" class=""><b class=""><span class="gmail_default" style="font-family:arial,sans-serif;font-size:small"></span></b></font><font face="trebuchet ms, sans-serif" class=""><b class="">Justine <span class="gmail_default">Chew</span></b></font><br class=""><div class="gmail_default"><font face="trebuchet ms, sans-serif" class="">At-Large/ALAC liaison for Subsequent Procedures</font></div><div class="gmail_default"><font face="trebuchet ms, sans-serif" class="">ALAC Member</font></div>-----</div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div><br class=""></div><br class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, 28 Nov 2019 at 21:30, <<a href="mailto:alberto@soto.net.ar" target="_blank" class="">alberto@soto.net.ar</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div lang="ES-AR" class=""><div class=""><p class="MsoNormal"><span lang="EN-US" class="">The GAC notes the benefit of a comment period that includes all draft final recommendations.<u class=""></u><u class=""></u></span></p><p class="MsoNormal"><span lang="EN-US" class="">We do not know what final recommendations could affect end users.<u class=""></u><u class=""></u></span></p><p class="MsoNormal"><span lang="EN-US" class="">In my humble opinion and from what I hear in the SubPro PDP WG, ALAC should discuss giving support to the GAC note. And a small group research on issues that may affect end users.<u class=""></u><u class=""></u></span></p><p class="MsoNormal"><span lang="EN-US" class=""><u class=""></u> <u class=""></u></span></p><p class="MsoNormal"><span lang="EN-US" class="">Kind regards<u class=""></u><u class=""></u></span></p><p class="MsoNormal"><span lang="EN-US" class=""><u class=""></u> <u class=""></u></span></p><p class="MsoNormal"><span lang="EN-US" class="">Alberto<u class=""></u><u class=""></u></span></p><p class="MsoNormal"><span lang="EN-US" class=""><u class=""></u> <u class=""></u></span></p><p class="MsoNormal"><b class=""><span lang="ES" class="">De:</span></b><span lang="ES" class=""> Justine Chew <<a href="mailto:justine.chew@gmail.com" target="_blank" class="">justine.chew@gmail.com</a>> <br class=""><b class="">Enviado el:</b> jueves, 28 de noviembre de 2019 3:56<br class=""><b class="">Para:</b> CPWG <<a href="mailto:cpwg@icann.org" target="_blank" class="">cpwg@icann.org</a>><br class=""><b class="">Asunto:</b> Subsequent Procedures: Request for reactions to letter by GAC Chair to SubPro PDP WG Co-Chairs relaying GAC input on the scope of upcoming SubPro public comment<u class=""></u><u class=""></u></span></p><p class="MsoNormal"><u class=""></u> <u class=""></u></p><div class=""><div class=""><p class="MsoNormal"><span style="font-family:Arial,sans-serif" class="">Dear all, <br clear="all" class=""><u class=""></u><u class=""></u></span></p></div><div class=""><div class=""><div class=""><div class=""><div class=""><div class=""><div class=""><p class="MsoNormal"><u class=""></u> <u class=""></u></p></div><div class=""><div class=""><p class="MsoNormal"><span style="font-family:Arial,sans-serif" class="">RE:</span><strong class=""><span style="font-family:"Segoe UI",sans-serif;color:rgb(23,43,77)" class=""><a href="https://gac.icann.org/contentMigrated/gac-input-on-scope-of-upcoming-new-gtlds-subsequent-procedures-pdp-wg-public-comment" target="_blank" class=""><span style="color:rgb(0,82,204)" class="">Letter from the GAC Chair, Manal Ismail, on behalf of GAC Membership: GAC Input on Scope of Upcoming New gTLDs Subsequent Procedures PDP WG Public Comment</span></a></span></strong><span style="font-family:Arial,sans-serif" class=""> <u class=""></u><u class=""></u></span></p></div></div><div class=""><p class="MsoNormal"><u class=""></u> <u class=""></u></p><div class=""><p class="MsoNormal"><span style="font-family:Arial,sans-serif" class="">I had tabled for discussion at yesterday's (27 Nov) CPWG call the above-referenced correspondence from the GAC Chair to the Subsequent Procedures PDP WG Co-Chairs which relayed GAC's input on the scope of the upcoming (additional) call for public comments to recommendations (whether preliminary or not) of the SubPro PDP WG. However, as I was otherwise detained, I was unable to make the said CPWG call and am now taking a remedial step to initiate the intended discussion. <br class=""><br class=""><b class=""><u class="">Context</u></b><br class=""><br class="">SubPro PDP WG is close to completing its review of public comments to its Initial Report of 2018, although some work is ongoing in respect of certain topics which have raised new ideas and are likely to lead to significant changes for subsequent procedures (IMO). <br class=""><br class="">Among others, one key question that <u class="">SubPro PDP WG is determining is, in basic terms, whether <span style="color:blue" class="">[A] to confine the additional call for public comments to preliminary recommendations (or questions) relating to those topics which SubPro PDP WG Leadership opines were not put out for Community input in earlier calls for public comments.</span></u><span style="color:blue" class=""> </span>This decision is still pending and debate among members of the SubPro PDP WG on this matter is ongoing, <u class="">with an alternative being proposed, which is <span style="color:fuchsia" class="">[B]</span> <span style="color:fuchsia" class="">to put, again in basic terms, a version of a "draft Final Report" with recommendations in its entirety, out for public comment</span></u>. In that scenario the document would not be "final" in form, of course.<br class=""><br class="">If I may abbreviate hereon, the rationale for <span style="color:blue" class="">[A]</span> limiting the scope of what would be put out for public comment centres around the elements of (1) duplicity - we have already asked for community input on much of the WG's earlier work; (2) public comment fatigue; and (3) pressure to complete the WG's work within an already elongated timeline.<br class=""><br class="">While the arguments put forth for <span style="color:fuchsia" class="">[B]</span> putting a report in its entirety out for comment revolve around (1) keeping open opportunity for broad-based indirect participation by the Community; (2) enabling the Community to better understand and appreciate crucial connections between topics which would otherwise be effectively severed, ie. "allow Community to see the whole picture because changes to one part of the picture might affect perspectives to other parts of the picture"; (3) this is needed precursor work to better facilitate the goal of Community-wide accepted Final Report recommendations.<br class=""><br class=""><b class=""><u class="">Request for Reactions</u></b><br class=""><br class="">The afore-linked letter from the GAC Chair sets out the GAC's reaction to this question. <br class=""><br class="">I invite feedback, <u class="">especially from At-Large colleagues active on the SubPro PDP WG</u>, on whether At-Large/ALAC should also react to this question, and if yes, how so. <br class=""><br class="">Discussion on this list can be expected to be taken up at a subsequent CPWG call. <u class=""></u><u class=""></u></span></p></div></div><div class=""><p class="MsoNormal"><u class=""></u> <u class=""></u></p></div><div class=""><div class=""><p class="MsoNormal" style="margin-bottom:12pt"><span style="font-family:Arial,sans-serif" class="">Thank you,<u class=""></u><u class=""></u></span></p></div><p class="MsoNormal"><b class=""><span style="font-family:"Trebuchet MS",sans-serif" class="">Justine </span></b><span class=""><b class=""><span style="font-family:"Trebuchet MS",sans-serif" class="">Chew</span></b></span><u class=""></u><u class=""></u></p><div class=""><p class="MsoNormal"><span style="font-family:"Trebuchet MS",sans-serif" class="">At-Large/ALAC liaison for Subsequent Procedures</span><u class=""></u><u class=""></u></p></div><div class=""><p class="MsoNormal"><span style="font-family:"Trebuchet MS",sans-serif" class="">ALAC Member</span><span style="font-size:12pt" class=""><u class=""></u><u class=""></u></span></p></div><p class="MsoNormal"><br class="">-----<u class=""></u><u class=""></u></p></div></div></div></div></div></div></div></div></div></div></blockquote></div>
</div>
_______________________________________________<br class="">CPWG mailing list<br class=""><a href="mailto:CPWG@icann.org" class="">CPWG@icann.org</a><br class=""><a href="https://mm.icann.org/mailman/listinfo/cpwg" class="">https://mm.icann.org/mailman/listinfo/cpwg</a><br class=""><br class="">_______________________________________________<br class="">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 (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). 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.</div></blockquote></div><br class=""></div></div></body></html>