- Gnso-newgtld-wg - lists.icann.org

Please share: ICANN69 Policy Outlook Report is now available
by Terri Agnew Oct. 7, 2020

Oct. 7, 2020

Dear all, The ICANN69 Policy Outlook Report (formerly known as the Pre-ICANN69 Policy Report) is now available: http://go.icann.org/outlook69 [go.icann.org]<https://urldefense.com/v3/__http:/go.icann.org/outlook69__;!!PtGJab4!svNgH6…>. IMPORTANT NOTE: Participation links will be posted 24-hours prior to the session start times for security purposes. Meeting registration is now required to view the full meeting schedule. Thank you. Kind regards, Terri

1 0

REMINDER TO REGISTER! / ICANN69: GNSO Sessions - How to Get Organized and Remote Participation Details
by Julie Bisland Oct. 7, 2020

Oct. 7, 2020

Dear all, All ICANN69 GNSO sessions have been listed for your reference on the ICANN69 GNSO wiki page. For all access information and Zoom details however, please refer to the ICANN69 schedule on the meeting website. Registration is compulsory to access the meeting schedule. Access information will not be circulated via mailing lists. The ICANN meeting website, which ICANN Meetings’ Team has put together, allows you to download all GNSO-related meetings to your inbox calendar in one go. HOW TO DOWNLOAD ICANN69 SESSION INFORMATION TO YOUR CALENDARS: Step 1 - Create a profile and your personalized ICANN69 schedule Go to the Meeting Schedule webpage [69.schedule.icann.org]<https://urldefense.com/v3/__https:/69.schedule.icann.org/__;!!PtGJab4!sbCM1…> and create a profile and login. Every session on the Full Agenda can be selected and added to your individual schedule by clicking the [cid:image001.png@01D69C7B.8F6BDE90] (blue ‘ + ’ box) in the upper right corner of each meeting. This adds it to your individual schedule, My Agenda, which you can then add to your calendar. See next step. Step 2 - To import your schedule into your calendar: once you’ve added all your chosen meetings to your schedule, click on [cid:image002.png@01D69C7B.8F6BDE90] (View My Agenda) * Click the down arrow next to Export * Select Export My Agenda (ics) * Open the exported meetings .ics and add to your chosen calendar (click on “Other Calendar” if the feature is not working properly) * For Microsoft Outlook, right-click on the exported meetings .ics file and choose Show in Folder Right-click on the file, and select Open with Microsoft Outlook. Save & Close. Note: Your Agenda can only be exported from the desktop app; the ICANN69 phone app does not offer this feature Step 3 - All remote participation sessions will use Zoom rooms. You can find the Zoom room links for public meetings on the ICANN69 Meeting Schedule [69.schedule.icann.org]<https://urldefense.com/v3/__https:/69.schedule.icann.org/agenda*/?limit=20&…>. PLEASE ENSURE YOU HAVE UPDATED YOUR ZOOM APP TO THE LATEST VERSION TO ACCESS ICANN69 SESSIONS. Please download the latest Zoom app [zoom.us]<https://urldefense.com/v3/__https:/zoom.us/download__;!!PtGJab4!sbCM1efylOx…> on your participation device (mobile or desktop computer). Need to learn or brush-up on using Zoom? Check out the Joining a Zoom Meeting Tutorial [support.zoom.us]<https://urldefense.com/v3/__https:/support.zoom.us/hc/en-us/articles/201362…>. Step 4 - Download the mobile app by searching for “ICANN Meetings” in your app stores. There are three options to connect your audio: 1) Via VoIP, choose Computer Audio (from a smartphone choose Call using Internet Audio) 2) Getting a dial out from Zoom to your phone, choose Call Me (from a smartphone choose Call My Phone) 3) Phoning into the audio bridge (access numbers and Meeting ID are provided for that option), choose Telephone Audio (from a smartphone choose Dial in) 3 LINKS TO BOOKMARK NOW: ICANN69 Meeting Schedule [69.schedule.icann.org]<https://urldefense.com/v3/__https:/69.schedule.icann.org/agenda*/?limit=20&…> GNSO ICANN69 Wiki Page<https://community.icann.org/x/NwGNC> GNSO Session agendas<https://community.icann.org/x/CwGNC> For all GNSO meeting related queries (RP or others), please email us at: gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> and we will be more than happy to assist! Kind regards, GNSO SO/AC Support team -- Julie Bisland GNSO SO/AC Support coordinator Internet Corporation for Assigned Names and Numbers (ICANN) Skype ID: 79613b691cb8a6c1 Find out more about the GNSO by visiting: https://learn.icann.org/<https://urldefense.proofpoint.com/v2/url?u=https-3A__learn.icann.org_&d=DwM…> Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGN…> Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_grou…>

1 0

ICANN69 GNSO Policy Briefing Available for Download
by Julie Bisland Oct. 6, 2020

Oct. 6, 2020

Dear All, On behalf of the GNSO Team, I am happy to report that the GNSO Policy Briefing for ICANN69 is now available for download at https://go.icann.org/gnsobriefing [go.icann.org]<https://urldefense.com/v3/__https:/go.icann.org/gnsobriefing__;!!PtGJab4!qy…>. Happy reading! Best Regards, Julie -- Julie Bisland GNSO SO/AC Support coordinator Internet Corporation for Assigned Names and Numbers (ICANN) Skype ID: 79613b691cb8a6c1 Find out more about the GNSO by visiting: https://learn.icann.org/<https://urldefense.proofpoint.com/v2/url?u=https-3A__learn.icann.org_&d=DwM…> Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGN…> Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_grou…>

1 0

Corrected: Notes and Action Items - New gTLD Subsequent Procedures PDP WG - 01 October at 03:00 UTC
by Julie Hedlund Oct. 1, 2020

Oct. 1, 2020

Dear Working Group members, -- Please see below the corrected email. In the previous version the notes were incomplete. -- Please see below the notes from the meeting on 01 October at 03:00 UTC. 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: https://community.icann.org/display/NGSPP/2020-10-01+New+gTLD+Subsequent+Pr…. Kind regards, Julie Notes and Action Items: Actions: CPE Guidelines and WG Recommendations / Implementation Guidance 4-B Opposition: ACTION ITEM: Add to the Guidelines where it says for non-negligible size consider the proportion to the overall size of the community that the applicant is aiming to serve. ACTION ITEM: Check to see if the issue of whether there is a direct or remote connection between the group opposing and the string being applied for is captured in the existing Guidelines (see At-Large proposal). Notes: 1. Updates to Statements of Interest: No updates provided. 2. Public Comments on Draft Final Report: -- The public comment forum closed today. -- We’ve received comments from the GAC, the Board, and ICANN org. -- Staff will produce a Public Comment Review Tool in the next few weeks that is arranged by topic, so you don’t need to rely on the Google spreadsheet that is posted, which is hard to read. -- Staff also will post a more easily readable and downloadable version of the spreadsheet. -- Staff will prioritize input into the tool for those topics that we want to discuss at the two ICANN69 sessions (Closed Generics, Predictability, etc.). These are the same topics we covered in the Webinar a few weeks ago. -- We aren’t going to do the type of quantitative analysis – number and type of response – with the donut charts as they did in the RPMs PDP WG because we are focusing on doing a qualitative assessment. 3. CPE Guidelines and WG Recommendations / Implementation Guidance with WG redlines/comments: https://drive.google.com/file/d/1Ih_1NARViJXNNewDg-q87sQzQoC1dCtC/view?usp=… and also the redline submitted by Justine Chew reflecting the changes from the Proposal by At-Large dated 11 Jun 2020:https://docs.google.com/document/d/1RS13a70f3BGx0b1gOyjvvRCoAKvxtlfO/e… – start at 4-B Opposition in the WG document, page 19, and then proceed to Criterion 1/overall comments from Justine 4-B Opposition: -- We did make a recommendation on are a couple other recommendations, namely that evaluators can question, those that submitted letters of support and or opposition: “Letters of opposition to a community based application if any must be considered in balance with documented support for the application.” Discussion: Re: “Relevance” and “relevant” refer to the communities explicitly and implicitly addressed. This means that opposition from communities not identified in the application but with an association to the applied for string would be considered relevant.” -- Comment from Jamie Baxter re: “Relevance” -- As discussed on the last call, guidance for “relevance” in 4-B must include a balance of opposition in relation to documented support, and not just an isolated determination of whether the opposing entity is part of the community explicitly or implicitly addressed. One misaligned community member/entity should not have the power to impact CPE scores of a largely aligned community, yet that was the EIU’s interpretation and practice in the 2012 round. To illustrate this point, if an applicant has hundreds of organizations from around the world supporting an application, and those endorsements represent the voices of tens of thousands of other local and regional organizations, then an expression of opposition from one single, small and even locally based organization from within the defined community among the thousands globally expressing support should not be able to put 1 of the 2 CPE points for this criteria in jeopardy.” -- It's also about the size of that opposition compared to the scope of that community. One small segment in a larger community really doesn’t have relevance in the larger picture. Make sure we capture that concept. -- That is included in the balance part of our recommendation. -- The definition of relevance is incredibly important because as you see there if just one group submits a letter of opposition and it's deemed to be relevant, then the score automatically goes you know down a point and in an evaluation, where one needed to score 14 out of 16. That is pretty substantial against an applicant. -- There just needs to be a better calculus here because otherwise, it doesn't give the applicant any way of understanding how they're going to rule on a lot of this stuff. “Non-negligible” is a bizarre definition with no real basis. -- Who we appointed as the evaluator becomes important. Okay, so that's that goes back to the At-Large request to have more communities participation and saying, who is appointed as the evaluator. -- Recommended the introduction of a challenge mechanism for those applicants who thought they had been misjudged. -- We haven’t addressed the role of applicant comment in totality. The identities of the commenters should be established. -- Don’t think we have established a fixed period of application comment for Community Based-Applicants that should be the same as all other applicants, and there shouldn’t be a separate call for letters of support or opposition. -- The GAC has said that the evaluators should be experts in communities, with a list of criteria. -- Do need to include whether opposition is negligible or is of non-negligible size in proportion to the overall size of the community that is being represented by the applicant – that the applicant is aiming to serve. -- At-Large proposal: The bit about whether there is a direct or remote connection between the group opposing and the string being applied for that may not be captured in the existing document. ACTION ITEM: Add to the Guidelines where it says for non-negligible size consider the proportion to the overall size of the community that the applicant is aiming to serve. ACTION ITEM: Check to see if the issue of whether there is a direct or remote connection between the group opposing and the string being applied for is captured in the existing Guidelines (see At-Large proposal). Overall Principles (At-Large Proposal): Delineation between economic and non-economic communities. Criterion #1: Community Establishment: “Any distinction between a Community based on a common economic interest (CEI model) and a Community advocating for Human Rights (CHR model) should not serve as a basis for preferring one over the other.” -- For scoring 1 point changed to “reasonably delineated community” rather than “clearly delineated” so there's a bit of flexibility there. -- We also attempted to introduce community expertise into the fold by suggesting that any reasonably delineated community that is recognized by, say for example, United Nations or maybe any international other international organizations or Subject Matter Expert with international or regional standing, they recognize the community as existing then it should score high that that community should by right feature quite highly. -- On Delineation: If it's an economic grouping you score high if it's a human rights grouping you also score high, so long as they are you know either clearly delineated or by a general governmental organization or some expert of reasonable standing, and if the grouping is less clearly delineated it could still score one. -- Question: Why do you say “non-economic community” instead of “human rights” community? Not sure what a human rights community encompasses. Answer: The concern that was raised when we were discussing this was a clear distinction between economic groupings and non-economic groupings, but in particular with the non-economic groupings they would encompass mostly human rights. Some human rights are not rights in some countries and could even be illegal, which could prevent some people from being members of a certain grouping or declaring support, but that group should be at a disadvantage if it can’t have a clear membership. -- Question: Could you instead have two groupings, one that is based on economic or common economic interest and one that is not, to avoid using the term “human rights”? -- If you look at the United Nations, there are various protected classes. The opportunity here is to allow an applicant to show how they're delineated based on existing standards or prior identifications whether their classes or whatever. And that is how they establish third delineation. -- Why not just say any distinction between a community based on common economic interest and a community, not based on a common economic interest should not serve as a basis for prefer one over the other. Scoring Threshold: -- The working group to consider recommending lowering the threshold for preventing CP from 14 to 12 points. -- We will need to have a separate conversation on the threshold. You might say that if you got a zero on any criterion you should be excluded. Need to think about how it flows through the sub-criteria. -- If the criteria and sub-criteria are not linked then the likelihood of that happening is actually very low. -- From the AGB: “The sequence of the criteria reflects the order in which they will be assessed by the panel. The utmost care has been taken to avoid any "double-counting" - any negative aspect found in assessing an application for one criterion should only be counted there and should not affect the assessment for other criteria.” -- If the applicants hadn’t been under such scrutiny in the 2012 round the scores probably would have been higher. -- Improving the scoring criteria and lowering the scoring threshold would provide the best improvement of the CPE. -- If the WG makes these changes then the intention would be to increase the number of applicants that pass CPE, so we need to confirm that intention. Next Meeting: -- Applicant Support -- Selected Board comments on the draft Final Report

1 0

FW: ICANN Org SubPro comments
by Karen Lentz Oct. 1, 2020

Oct. 1, 2020

Dear all, Forwarding for your information the input from ICANN org to the draft Final Report. We have also submitted this for addition into the comment tool being used for this comment forum. Best regards, Karen From: Theresa Swinehart <theresa.swinehart(a)icann.org> Date: Wednesday, September 30, 2020 at 5:10 PM To: "jeff(a)jjnsolutions.com" <jeff(a)jjnsolutions.com>, "langdonorr(a)gmail.com" <langdonorr(a)gmail.com> Cc: Goran Marby <goran.marby(a)icann.org>, Karen Lentz <karen.lentz(a)icann.org>, David Olive <david.olive(a)icann.org>, Steve Chan <steve.chan(a)icann.org> Subject: ICANN Org SubPro comments Dear Cheryl and Jeff, Please find the attached letter and submission from ICANN org regarding the New gTLD Subsequent Procedures PDP Working Group Draft final report. I hope you and your families are well. Kind regards, Theresa

5 7

Notes and Action Items - New gTLD Subsequent Procedures PDP WG - 01 October at 03:00 UTC
by Julie Hedlund Oct. 1, 2020

Oct. 1, 2020

Dear Working Group members, Please see below the notes from the meeting on 01 October at 03:00 UTC. 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: https://community.icann.org/display/NGSPP/2020-10-01+New+gTLD+Subsequent+Pr…. Kind regards, Julie Notes and Action Items: Actions: CPE Guidelines and WG Recommendations / Implementation Guidance 4-B Opposition: ACTION ITEM: Add to the Guidelines where it says for non-negligible size consider the proportion to the overall size of the community that the applicant is aiming to serve. ACTION ITEM: Check to see if the issue of whether there is a direct or remote connection between the group opposing and the string being applied for is captured in the existing Guidelines (see At-Large proposal). Notes: 1. Updates to Statements of Interest: No updates provided. 2. Public Comments on Draft Final Report: -- The public comment forum closed today. -- We’ve received comments from the GAC, the Board, and ICANN org. -- Staff will produce a Public Comment Review Tool in the next few weeks that is arranged by topic, so you don’t need to rely on the Google spreadsheet that is posted, which is hard to read. -- Staff also will post a more easily readable and downloadable version of the spreadsheet. -- Staff will prioritize input into the tool for those topics that we want to discuss at the two ICANN69 sessions (Closed Generics, Predictability, etc.). These are the same topics we covered in the Webinar a few weeks ago. -- We aren’t going to do the type of quantitative analysis – number and type of response – with the donut charts as they did in the RPMs PDP WG because we are focusing on doing a qualitative assessment. 3. CPE Guidelines and WG Recommendations / Implementation Guidance with WG redlines/comments: https://drive.google.com/file/d/1Ih_1NARViJXNNewDg-q87sQzQoC1dCtC/view?usp=… and also the redline submitted by Justine Chew reflecting the changes from the Proposal by At-Large dated 11 Jun 2020:https://docs.google.com/document/d/1RS13a70f3BGx0b1gOyjvvRCoAKvxtlfO/e… – start at 4-B Opposition in the WG document, page 19, and then proceed to Criterion 1/overall comments from Justine 4-B Opposition: -- We did make a recommendation on are a couple other recommendations, namely that evaluators can question, those that submitted letters of support and or opposition: “Letters of opposition to a community based application if any must be considered in balance with documented support for the application.” Discussion: Re: “Relevance” and “relevant” refer to the communities explicitly and implicitly addressed. This means that opposition from communities not identified in the application but with an association to the applied for string would be considered relevant.” -- Comment from Jamie Baxter re: “Relevance” -- As discussed on the last call, guidance for “relevance” in 4-B must include a balance of opposition in relation to documented support, and not just an isolated determination of whether the opposing entity is part of the community explicitly or implicitly addressed. One misaligned community member/entity should not have the power to impact CPE scores of a largely aligned community, yet that was the EIU’s interpretation and practice in the 2012 round. To illustrate this point, if an applicant has hundreds of organizations from around the world supporting an application, and those endorsements represent the voices of tens of thousands of other local and regional organizations, then an expression of opposition from one single, small and even locally based organization from within the defined community among the thousands globally expressing support should not be able to put 1 of the 2 CPE points for this criteria in jeopardy.” -- It's also about the size of that opposition compared to the scope of that community. One small segment in a larger community really doesn’t have relevance in the larger picture. Make sure we capture that concept. -- That is included in the balance part of our recommendation. -- The definition of relevance is incredibly important because as you see there if just one group submits a letter of opposition and it's deemed to be relevant, then the score automatically goes you know down a point and in an evaluation, where one needed to score 14 out of 16. That is pretty substantial against an applicant. -- There just needs to be a better calculus here because otherwise, it doesn't give the applicant any way of understanding how they're going to rule on a lot of this stuff. “Non-negligible” is a bizarre definition with no real basis. -- Who we appointed as the evaluator becomes important. Okay, so that's that goes back to the At-Large request to have more communities participation and saying, who is appointed as the evaluator. -- Recommended the introduction of a challenge mechanism for those applicants who thought they had been misjudged. -- We haven’t addressed the role of applicant comment in totality. The identities of the commenters should be established. -- Don’t think we have established a fixed period of application comment for Community Based-Applicants that should be the same as all other applicants, and there shouldn’t be a separate call for letters of support or opposition. -- The GAC has said that the evaluators should be experts in communities, with a list of criteria. -- Do need to include whether opposition is negligible or is of non-negligible size in proportion to the overall size of the community that is being represented by the applicant – that the applicant is aiming to serve. -- At-Large proposal: The bit about whether there is a direct or remote connection between the group opposing and the string being applied for that may not be captured in the existing document. ACTION ITEM: Add to the Guidelines where it says for non-negligible size consider the proportion to the overall size of the community that the applicant is aiming to serve. ACTION ITEM: Check to see if the issue of whether there is a direct or remote connection between the group opposing and the string being applied for is captured in the existing Guidelines (see At-Large proposal). Overall Principles (At-Large Proposal): Delineation between economic and non-economic communities. Criterion #1: Community Establishment: “Any distinction between a Community based on a common economic interest (CEI model) and a Community advocating for Human Rights (CHR model) should not serve as a basis for preferring one over the other.” -- For scoring 1 point changed to “reasonably delineated community” rather than “clearly delineated” so there's a bit of flexibility there. -- We also attempted to introduce community expertise into the fold by suggesting that any reasonably delineated community that is recognized by, say for example, United Nations or maybe any international other international organizations or Subject Matter Expert with international or regional standing, they recognize the community as existing then it should score high that that community should by right feature quite highly. -- On Delineation: If it's an economic grouping you score high if it's a human rights grouping you also score high, so long as they are you know either clearly delineated or by a general governmental organization or some expert of reasonable standing, and if the grouping is less clearly delineated it could still score one. -- Question: Why do you say “non-economic community” instead of “human rights” community? Not sure what a human rights community encompasses. Answer: The concern that was raised when we were discussing this was a clear distinction between economic groupings and non-economic groupings, but in particular with the non-economic groupings they would encompass mostly human rights. Some human rights are not rights in some countries and could even be illegal, which could prevent some people from being members of a certain grouping or declaring support, but that group should be at a disadvantage if it can’t have a clear membership. -- Question: Could you instead have two groupings, one that is based on economic or common economic interest and one that is not, to avoid using the term “human rights”? -- If you look at the United Nations, there are various protected classes. The opportunity here is to allow an applicant to show how they're delineated based on existing standards or prior identifications whether their classes or whatever. And that is how they establish third delineation. -- Why not just say any distinction between a community based on common economic interest and a community, not based on a common economic interest should not serve as a basis for prefer one over the other. Scoring Threshold: -- The working group to consider recommending lowering the threshold for preventing CP from 14 to 12 points. -- We will need to have a separate conversation on the threshold. You might say that if you got a zero on any criterion you should be excluded. Need to think about how it flows through the sub-criteria. -- If the criteria and sub-criteria are not linked then the likelihood of that happening is actually very low. -- From the AGB: “The sequence of the criteria reflects the order in which they will be assessed by the panel. The utmost care has been taken to avoid any "double-counting" - any negative aspect found in assessing an application for one criterion should only be counted there and should not affect the assessment for other criteria.” -- If the applicants hadn’t been under such scrutiny in the 2012 round the scores probably would have been higher. -- Improving the scoring criteria and lowering the scoring threshold would provide the best improvement of the CPE.

1 0

Post Call | New gTLD Subsequent Procedures Working Group | Thursday, 01 October 2020 at 03:00 UTC
by Julie Bisland Oct. 1, 2020

Oct. 1, 2020

Dear all, All recordings for the New gTLD Subsequent Procedures Working Group call held on Thursday, 01 October 2020 at 03:00 UTC can be found on the agenda wiki page <https://community.icann.org/x/MAjQC> (attendance included) and the GNSO Master calendar <https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_en_group…> . These include: * Attendance (please let me know if your name has been left off the attendance list) * Audio recording * Zoom chat archive * Zoom recording (including audio, visual, rough transcript) * Transcript As a reminder only members can join the call, observers can listen to the recordings and read the transcript afterwards. Please email gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> if you would like to change your status from observer to member. For additional information, you may consult the mailing list archives <http://mm.icann.org/pipermail/gnso-newgtld-wg/> and the main wiki page<https://community.icann.org/x/RgV1Aw>. Thank you. Kind regards Julie

1 0

FW: [CORRESPONDENCE] Maarten Botterman to Cheryl Langdon-Orr and Jeff Neuman New gTLD Subsequent Procedures PDP WG Draft Final Report
by Steve Chan Sept. 30, 2020

Sept. 30, 2020

Dear WG Members, Attached, please the letter from Maarten Botterman regarding the SubPro draft Final Report. Best, Steve From: Wendy Profit <wendy.profit(a)icann.org> Date: Wednesday, September 30, 2020 at 3:06 PM To: Cheryl Orr <langdonorr(a)gmail.com>, "jeff(a)jjnsolutions.com" <jeff(a)jjnsolutions.com> Cc: Maarten Botterman <maarten.botterman(a)board.icann.org>, Correspondence <Correspondence(a)icann.org>, Secretary <secretary(a)icann.org>, Board Ops Team <board-ops-team(a)icann.org>, Karen Lentz <karen.lentz(a)icann.org>, Steve Chan <steve.chan(a)icann.org>, Emily Barabas <emily.barabas(a)icann.org> Subject: [CORRESPONDENCE] Maarten Botterman to Cheryl Langdon-Orr and Jeff Neuman New gTLD Subsequent Procedures PDP WG Draft Final Report Dear Cheryl Langdon-Orr and Jeff Neuman, Please find the attached letter from Maarten Botterman regarding the New gTLD Subsequent Procedures PDP Working Group Draft final report. Thank you and best regards, Wendy Profit ICANN Board Operations Senior Manager 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094

1 0

REMINDER: Proposed Agenda - New gTLD Subsequent Procedures PDP WG - Thursday, 01 October at 03:00 UTC for 90 Minutes
by Julie Hedlund Sept. 30, 2020

Sept. 30, 2020

Dear WG Members, As a reminder, please find below the updated proposed agenda for the WG meeting on Thursday, 01 October 2020 at 03:00 UTC for 90 minutes. Proposed Agenda: 1. Review Agenda/Updates to Statements of Interest 2. CPE Guidelines and WG Recommendations / Implementation Guidance with WG redlines/comments: https://drive.google.com/file/d/1Ih_1NARViJXNNewDg-q87sQzQoC1dCtC/view?usp=… and also the redline submitted by Justine Chew reflecting the changes from the Proposal by At-Large dated 11 Jun 2020: https://docs.google.com/document/d/1RS13a70f3BGx0b1gOyjvvRCoAKvxtlfO/edit – start at 4-B Opposition in the WG document, page 19, and then proceed to Criterion 1/overall comments from Justine 3. Applicant Support * In the context of auctions; see: https://gnso.icann.org/sites/default/files/file/field-file-attach/draft-fin…, Topic 17: Applicant Support, page 67; Topic 35: Auctions: Mechanisms of Last Resort / Private Resolution of Contention Sets, page 167; and * Review as a comprehensive program; see Topic 17: Applicant Support, page 67 4. AOB If you need a dial out or would like to submit an apology, please email gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>. Best, Julie Julie Hedlund, Policy Director

1 0

FW: Ratified: ALAC Statement on GNSO New gTLD Subsequent Procedures Draft Final Report
by Emily Barabas Sept. 30, 2020

Sept. 30, 2020

Please see below. From: ICANN At-Large Staff <staff(a)atlarge.icann.org> Date: Wednesday, 30 September 2020 at 01:38 To: "langdonorr(a)gmail.com" <langdonorr(a)gmail.com>, "jeff(a)jjnsolutions.com" <jeff(a)jjnsolutions.com> Cc: Steve Chan <steve.chan(a)icann.org>, Julie Hedlund <julie.hedlund(a)icann.org>, Emily Barabas <emily.barabas(a)icann.org>, Justine Chew <justine.chew(a)gmail.com>, Maureen Hilyard <maureen.hilyard(a)gmail.com>, Evin Erdogdu <evin.erdogdu(a)icann.org>, ICANN At-Large Staff <staff(a)atlarge.icann.org> Subject: Ratified: ALAC Statement on GNSO New gTLD Subsequent Procedures Draft Final Report Dear Co-Chairs of the Subsequent Procedures PDP, Please find attached a Word Doc and PDF of the ALAC statement on GNSO New gTLD Subsequent Procedures Draft Final Report<https://community.icann.org/x/qQC1C>. Due to character limit issues in the Google Form, ALAC responses are being submitted via email and the ALAC responses are in red. The ALAC ratified the statement<https://www.bigpulse.com/pollresults?code=134012194ubnqKYKVjG9fjTtQC3> on 28 September 2020, with unanimous endorsement of all 15 ALAC Members. Many thanks go to Justine and the CPWG SubPro Small Team for their countless hours of volunteer work on the ALAC statement. Kind Regards, ICANN Policy Staff in support of the At-Large Community Website: atlarge.icann.org<https://atlarge.icann.org/> Facebook: facebook.com/icann<https://www.facebook.com/icannatlarge>atlarge<https://www.facebook.com/icannatlarge> Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<https://twitter.com/ICANNAtLarge>

1 0