<div dir="ltr"><div>Dear, Kathy,</div><div><br></div><div>We have one volunteer so far -
<font face="Times New Roman">Ephraim Percy Kenyanito</font> <br></div><div>Let me know what you all think.<br></div><div><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div><br></div><div>Warmly,<br></div>Tomslin<div><span style="color:rgb(0,0,0);font-size:12.8px"></span></div><div><span style="color:rgb(0,0,0);font-size:12.8px"><br></span></div></div></div></div></div></div></div></div></div></div></div></div></div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, 10 May 2023 at 00:57, Kathy Kleiman <<a href="mailto:Kathy@kathykleiman.com">Kathy@kathykleiman.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi All,<br>
<br>
Who can we think of to server on the New gTLD Rules Implementation <br>
Review Team - otherwise known as the SubPro IRT?? This is the roll-out <br>
of the rules for New gTLD applications, review processes, evaluations of <br>
special applications (like Community Priority Evaluation), and more!<br>
<br>
Anyone who goes through this process will be one of the world experts on <br>
New gTLD rules - and ready to help a lot of people/groups/orgs with <br>
their applications when the next round opens.<br>
<br>
I was on the SubPro Working Group writing these recommendations, but <br>
cannot be on the IRT. That said, I am happy to help whoever(s) we choose!<br>
<br>
Best, Kathy<br>
<br>
On 4/6/2023 1:46 PM, Johan Helsingius wrote:<br>
><br>
><br>
><br>
> -------- Forwarded Message --------<br>
> Subject: Appointment of representative and alternate to the SubPro <br>
> IRT<br>
> Date: Thu, 6 Apr 2023 17:42:37 +0000<br>
> From: Lars Hoffmann <<a href="mailto:lars.hoffmann@icann.org" target="_blank">lars.hoffmann@icann.org</a>><br>
> To: <a href="mailto:julf@julf.com" target="_blank">julf@julf.com</a> <<a href="mailto:julf@julf.com" target="_blank">julf@julf.com</a>><br>
> CC: Steve Chan <<a href="mailto:steve.chan@icann.org" target="_blank">steve.chan@icann.org</a>>, Julie Hedlund <br>
> <<a href="mailto:julie.hedlund@icann.org" target="_blank">julie.hedlund@icann.org</a>>, <a href="mailto:gnso-secs@icann.org" target="_blank">gnso-secs@icann.org</a> <<a href="mailto:gnso-secs@icann.org" target="_blank">gnso-secs@icann.org</a>>, <br>
> Andrea Glandon <<a href="mailto:andrea.glandon@icann.org" target="_blank">andrea.glandon@icann.org</a>>, Brenda Brewer <br>
> <<a href="mailto:brenda.brewer@icann.org" target="_blank">brenda.brewer@icann.org</a>>, Karen Lentz <<a href="mailto:karen.lentz@icann.org" target="_blank">karen.lentz@icann.org</a>>, Bob <br>
> Ochieng <<a href="mailto:bob.ochieng@icann.org" target="_blank">bob.ochieng@icann.org</a>>, Elisa Busetto <br>
> <<a href="mailto:elisa.busetto@icann.org" target="_blank">elisa.busetto@icann.org</a>>, Raoul Plommer <<a href="mailto:plommer@gmail.com" target="_blank">plommer@gmail.com</a>>, <br>
> <a href="mailto:benakin@gmail.com" target="_blank">benakin@gmail.com</a> <<a href="mailto:benakin@gmail.com" target="_blank">benakin@gmail.com</a>><br>
><br>
><br>
><br>
> Dear Julf,<br>
><br>
> Following the publication of our recent blog <br>
> <<a href="https://www.icann.org/en/blogs/details/next-round-of-new-gtlds-forming-the-implementation-review-team-04-04-2023-en" rel="noreferrer" target="_blank">https://www.icann.org/en/blogs/details/next-round-of-new-gtlds-forming-the-implementation-review-team-04-04-2023-en</a>>‘Next <br>
> Round of New gTLDs: Forming the Implementation Review Team’, the <br>
> Internet Corporation for Assigned Names and Numbers (ICANN) <br>
> organization (org) is pleased to invite you to nominate a <br>
> representative and an alternate to the Subsequent Procedures (SubPro) <br>
> Implementation Review Team (IRT).<br>
><br>
> The implementation process is an ICANN org-driven exercise; in <br>
> alignment with the Board resolution <br>
> <<a href="https://www.icann.org/en/board-activities-and-meetings/materials/approved-resolutions-regular-meeting-of-the-icann-board-16-03-2023-en" rel="noreferrer" target="_blank">https://www.icann.org/en/board-activities-and-meetings/materials/approved-resolutions-regular-meeting-of-the-icann-board-16-03-2023-en</a>>and <br>
> subsequent Generic Name Supporting Organization (GNSO) Council <br>
> consultation <br>
> <<a href="https://icann.zoom.us/rec/share/5X-rZUIDBhfyn17mnEkRrK0ihJfhONSJ18TaGu9rxwZFeSw3_d5n8IFzpJeH3oMd.Hh3V44Eak3VVsytm?startTime=1678651300000" rel="noreferrer" target="_blank">https://icann.zoom.us/rec/share/5X-rZUIDBhfyn17mnEkRrK0ihJfhONSJ18TaGu9rxwZFeSw3_d5n8IFzpJeH3oMd.Hh3V44Eak3VVsytm?startTime=1678651300000</a>>, <br>
> ICANN org will pilot a “Open + Representative Model” based on <br>
> theGNSO’s PDP 3.0 <br>
> <<a href="https://gnso.icann.org/sites/default/files/file/field-file-attach/pdp-3-2-working-group-models-10feb20-en.pdf.pdf" rel="noreferrer" target="_blank">https://gnso.icann.org/sites/default/files/file/field-file-attach/pdp-3-2-working-group-models-10feb20-en.pdf.pdf</a>>model. <br>
> The goal is to provide a structure that allows for efficient <br>
> resolution of issues that may occur.<br>
><br>
> We kindly ask that the NCSGnominate up to threerepresentative and up <br>
> to threealternate to participate in IRT. Please note, we are asking <br>
> all of ICANN’s supporting organizations and advisory committees to <br>
> nominate up to one representative and one alternate; the GNSO’s <br>
> contracted party stakeholder groups are being asked to nominate one <br>
> representative and one alternate each, too, and its non-contracted <br>
> party stakeholder groups three representatives and three alternatives <br>
> each.<br>
><br>
> Putting forward a representative and alternate is optional; all <br>
> members of the NCSG, NCUC and NPOC are welcome to join the SubPro IRT <br>
> as participants. In fact, we strongly urge anyone who is interested in <br>
> being selected as a representative to join the IRT as a participant, <br>
> so that the selection process does not hold up the timely launch of <br>
> the IRT. As you will see below the role of participants and <br>
> representatives are nearly identical, with the representatives’ main <br>
> function being that of an information-bridge to their community <br>
> groups. Please note, we have published a separate call for volunteers <br>
> <<a href="https://www.icann.org/en/announcements/details/icann-calls-for-volunteers-for-the-new-gtld-program-next-round-implementation-review-team-05-04-2023-en" rel="noreferrer" target="_blank">https://www.icann.org/en/announcements/details/icann-calls-for-volunteers-for-the-new-gtld-program-next-round-implementation-review-team-05-04-2023-en</a>>already.<br>
><br>
> ICANN org plans to host the first SubPro IRT call no later than the <br>
> week of 14 May 2023. We therefore request that you conclude the <br>
> nomination process and inform us of the nominees no later than Monday, <br>
> 7 May 2023.<br>
><br>
> *The Role of the IRT:*<br>
><br>
> Per the Consensus Policy Implementation Framework <br>
> <<a href="https://www.icann.org/uploads/ckeditor/CPIF_v2.0_2019CLEAN.pdf" rel="noreferrer" target="_blank">https://www.icann.org/uploads/ckeditor/CPIF_v2.0_2019CLEAN.pdf</a>>(CPIF) <br>
> and the IRT Principles & Guidelines <br>
> <<a href="https://www.icann.org/en/system/files/files/irt-principles-guidelines-23aug16-en.pdf" rel="noreferrer" target="_blank">https://www.icann.org/en/system/files/files/irt-principles-guidelines-23aug16-en.pdf</a>>, <br>
> the IRT members will:<br>
><br>
> * Serve as a resource to ICANN org on policy and technical questions<br>
> that arise with regard to the Board-approved recommendations of the<br>
> Final Report on the new gTLD Subsequent Procedures Policy<br>
> Development Process<br>
><br>
> <<a href="https://gnso.icann.org/sites/default/files/file/field-file-attach/final-report-newgtld-subsequent-procedures-pdp-02feb21-en.pdf" rel="noreferrer" target="_blank">https://gnso.icann.org/sites/default/files/file/field-file-attach/final-report-newgtld-subsequent-procedures-pdp-02feb21-en.pdf</a>>(Final <br>
><br>
> Report).<br>
> * Serve as a resource to ICANN org regarding the background and<br>
> rationale of the Final Report’s policy recommendations, and seek<br>
> additional guidance from the GNSO Council, as required.<br>
> * Assist ICANN org with developing the details of policy<br>
> implementation to ensure that the implementation conforms to the<br>
> intent of the policy recommendations as detailed in the Final Report.<br>
><br>
> There will be no distinction between participants and representatives <br>
> regarding the ability to perform these tasks.<br>
><br>
> *Open + Representative Model Pilot:*<br>
><br>
> As detailed above, participants and representatives will be equal <br>
> members of the IRT, sharing the same ability to take the floor and <br>
> post to the mailing list, working constructively with ICANN org to <br>
> assist in the implementation of the recommendations. Both will be <br>
> expected to understand the role and remit of the IRT for the <br>
> implementation project as described in the SubPro IRT Statement of <br>
> Participation <br>
> <<a href="https://www.icann.org/en/system/files/files/subpro-irt-statement-participation-05apr23-en.pdf" rel="noreferrer" target="_blank">https://www.icann.org/en/system/files/files/subpro-irt-statement-participation-05apr23-en.pdf</a>>, <br>
> which all IRT members are expected to commit to.<br>
><br>
> To be clear, the model will not change the ability of any IRT member <br>
> to raise concerns about the implementation approach taken by ICANN <br>
> org, as detailed in the IRT Principles & Guidelines <br>
> <<a href="https://www.icann.org/en/system/files/files/irt-principles-guidelines-23aug16-en.pdf" rel="noreferrer" target="_blank">https://www.icann.org/en/system/files/files/irt-principles-guidelines-23aug16-en.pdf</a>>.<br>
><br>
> *Why Have Representatives at All?*<br>
><br>
> While participants always speak in their own personal capacity, <br>
> representatives are expected to speak on behalf of their constituency, <br>
> stakeholder group, supporting organization, or advisory committee. <br>
> Therefore, a key part of the NCSG, NCUC and NPOCrepresentative’s’ role <br>
> will be to engage actively and consistently with their NCSG, NCUC and <br>
> NPOCcolleagues to ensure they can convey the NCSG, NCUC and <br>
> NPOCviewpoints to the IRT. Please note, that this will require an <br>
> efficient process for representatives to inform and receive input from <br>
> their respective groups. To put this into place will be the <br>
> responsibility of each representative.<br>
><br>
> In addition, when determining the level of consensus in the <br>
> circumstance described in Section V.E. of the IRT Principles & <br>
> Guidelines, the GNSO Liaison, in the Open + Representative model, <br>
> shall take into consideration that members who are representatives are <br>
> expected to express the viewpoint of their respective community groups <br>
> and participants to express their own views. This does not impact each <br>
> member’s ability to raise any concern they may have, nor does it <br>
> absolve ICANN org or the GNSO Council liaison from “exercis[ing] all <br>
> reasonable efforts to resolve disagreements” within the IRT.<br>
><br>
> *What is ICANN org’s Role?*<br>
><br>
> ICANN org’s role is to implement “the community’s recommendations at <br>
> the direction of the Board and under the supervision of the CEO”. When <br>
> implementing recommendations, ICANN org is “responsible for the entire <br>
> implementation lifecycle, from creating an implementation plan, <br>
> engaging the Implementation Review Team (IRT) (if there is one), <br>
> consulting with relevant ICANN org staff and any outside parties that <br>
> are required, and conducting outreach surrounding the implementation, <br>
> including communicating with the public and relevant stakeholders <br>
> regarding the progress of implementation.” See CPIF <br>
> <<a href="https://www.icann.org/uploads/ckeditor/CPIF_v2.0_2019CLEAN.pdf" rel="noreferrer" target="_blank">https://www.icann.org/uploads/ckeditor/CPIF_v2.0_2019CLEAN.pdf</a>>.<br>
><br>
> *Next Steps*<br>
><br>
> As noted above, we plan to start the IRT calls no later than the week <br>
> of 14 May 2023. ICANN org is currently working on a Charter for the <br>
> IRT, which will be shared after it is finalized. We are also drafting <br>
> an IRT work plan and timeline that we plan to share during the first <br>
> IRT meeting.<br>
><br>
> We are looking forward to getting the IRT underway and, please, do not <br>
> hesitate to reach out should have any questions.<br>
><br>
> Best wishes,<br>
><br>
> Lars<br>
><br>
> ---<br>
><br>
> Lars Hoffmann<br>
><br>
> ICANN, Senior Director, Policy Research and Stakeholder Programs<br>
><br>
> _______________________________________________<br>
> NCSG-PC mailing list<br>
> <a href="mailto:NCSG-PC@lists.ncsg.is" target="_blank">NCSG-PC@lists.ncsg.is</a><br>
> <a href="https://lists.ncsg.is/mailman/listinfo/ncsg-pc" rel="noreferrer" target="_blank">https://lists.ncsg.is/mailman/listinfo/ncsg-pc</a><br>
_______________________________________________<br>
NCSG-PC mailing list<br>
<a href="mailto:NCSG-PC@lists.ncsg.is" target="_blank">NCSG-PC@lists.ncsg.is</a><br>
<a href="https://lists.ncsg.is/mailman/listinfo/ncsg-pc" rel="noreferrer" target="_blank">https://lists.ncsg.is/mailman/listinfo/ncsg-pc</a><br>
</blockquote></div>