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

Proposed agenda - New gTLD Subsequent Procedures PDP WG - Monday, 30 March at 1500 UTC
by Julie Hedlund March 27, 2020

March 27, 2020

Dear all, Please find below the proposed agenda for the call on Monday, 30 March 2020 at 15:00 UTC for 90 minutes: Proposed Agenda: 1. Review Agenda/Updates to Statements of Interest 2. Discussion of Final Report Topics: 2.7.4 String Similarity Evaluation – See: https://docs.google.com/document/d/1kUlmZH8nxWTgfcRluA5FxLheMm4XhhOwkRt7om5… page 61 3. 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>. Kind regards, Julie Julie Hedlund, Policy Director

1 0

Notes and Action Items - New gTLD Subsequent Procedures PDP WG - 26 March 0300 UTC
by Julie Hedlund March 26, 2020

March 26, 2020

Dear Working Group members, Please see below the notes from the meeting on 26 March at 0300 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-03-26+New+gTLD+Subsequent+Pr…. Kind regards, Julie Notes and Action Items: Actions: 2.5.4 Applicant Support Implementation Guidance xx (rationale 4): ACTION ITEM: Remove the brackets. ACTION ITEM: Confirm the timing of the Communication Period and create a flow chart diagram for communications and outreach. Recommendation xx (rationale 3): ACTION ITEM: For review by the WG on the list: Leadership & staff to change from a recommendation to a question for public comment, but removing the bracketed text, and develop a question for WG review to ask whether ongoing registry level fees should be included in financial assistance. Re: Whether there should be any changes to the 2012 approach of establishing priority between applications if there are more qualified applicants than funds available. ACTION ITEM: Add this as an Implementation Guideline for the IRT to consider. Work Plan: ACTION ITEM: Leadership Team to consider how to address the additional drafting proposed for community applications and panels doing outside research and the redlines in GAC Consensus Advice; add these items back on the calendar and consider whether they make sense to add to the 6 April meeting. Notes: 1. Updates to Statements of Interest: No updates provided. 2. Discussion of Final Report Topics a. 2.5.4 Applicant Support – see attached PDF for clean version and redline at:https://docs.google.com/document/d/1xXu7gPKiblS3Vh4MCuK6NWfeRmMolXf9VF5s… Recommendation xx (rationale 3): The Working Group recommends expanding the scope of financial support provided to Applicant Support Program beneficiaries beyond the application fee to also cover costs such as application writing fees, attorney fees related to the application process, and [ongoing <https://newgtlds.icann.org/sites/default/files/agreements/agreement-approve…> ICANN registry-level fees]. Discussion: -- Not supported by the RySG: RySG comment about support beyond financial: “The RySG believes that ICANN's support should be limited to financial support for the application fee. Further involvement in the operational, technical and business aspects of a registry/registrar will only serve to unnecessarily involve ICANN in the operations of a registry/registrar and will serve as a de facto endorsement of certain registries/registrars and set a negative precedent for future entities that want to enter the registry/registrar business.” -- Look at level of support and opposition to this question from the public comments. -- Not sure how this ended up as a recommendation. -- Having financially dependent registries puts registrants at risk. -- The text is bracketed to indicate that it is for WG discussion/consideration. -- We did discuss this in the Work Track – a lot of community interaction on this topic. Originally we carefully noted that the applicant support itself wasn’t a problem but the sustainability was something that should be considered. -- The language in the Initial Report was: 2.5.4.c.7: Additionally, financial support should go beyond the application fee, such as including application writing fees, related attorney fees, and ICANN registry-level fees. [emphasis added] -- This support also gives such a registry a warranted, better chance in succeeding. -- Just because a registry is getting pro-bono assistance doesn’t mean it’s not sustainable and secure. -- Re: Paul’s comment that there is a huge conceptual difference between applicant support and new proposed category of registry support. Can we discuss this? -- Part of the conceptual leap is that the initial idea behind this would be to open the door to applicants who can’t raise the very high application fee, and you need to hire lawyers, etc. To help people who have innovative ideas to open a brand new registry. But now we are talking about what happens after delegation and whether there should be an ongoing subsidy for registries that aren’t financially viable. That seems to be something we don’t agree on. That’s why we do a financial background check to make sure that registries can operate and be viable after delegation. -- How is it different to offer these non-financial pro-bono services in subsidizing these registry fees? If it’s third parties and not ICANN that is terrific and that drives down the cost of running a registry. No problem with third parties doing good, but that is not the same thing as saying that ICANN should subsidize registries that don’t have a viable business model. -- ICANN should have an interest in registry succeeding beyond the application process. -- The registries have had conversations with ICANN in the past to request some of the excess fees being applied to a fee reduction. ICANN has consistently pushed back that it isn’t their job to prop up a registry that is failing. Don’t agree with the argument that this is ICANN’s responsibility. -- Agree that financial sustainability is not something that ICANN should be contributing to. -- In favor of other support, such as in-kind support, joining the RySG, etc. Applicant support should be a one-shot process and shouldn’t be registry support. -- But ASP registries should be an exceptional group. I understand the concerns against. In a spirit of compromise would folks in opposition find the suggestion of limiting this support to a SPECIFIED period amenable? -- Needs to be a minimum sustainable financial model. -- Applicant support should end at contracting. -- ICANN is in the business of providing opportunity not guaranteeing success. -- If you go back to 2012 there were a lot of unknowns – this time around we would hope that applicants would be more attuned and inform their decisions. -- Propose: Because this language was in the Initial Report: 1) remove the bracketed language and ask a very specific question on this, yes/no should ongoing registry level fees be included; 2) keep the language bracketed and ask the same question. At a minimum we should ask a question about this, but WG should decide whether to keep the text in brackets or remove it. -- We are hearing more voices than just the RySG reps that don’t support this. Seems like it wouldn’t support a consensus call. -- We should disclose the fact that we’ve taken it out and ask a question about it. It was only one group that had an issue with it. We still should ask a question. -- It does make sense to respect the comments on the Initial Report and the Work Track. -- Looking at the comments – other than the RySG who opposed it and Council of Europe who endorsed it, the rest of the comments don’t seem to specifically support or oppose. ACTION ITEM: For review by the WG on the list: Leadership & staff to change from a recommendation to a question for public comment, but removing the bracketed text, and develop a question for WG review to ask whether ongoing registry level fees should be included in financial assistance. Implementation Guidance xx (rationale 4): Outreach and awareness-raising activities should be delivered well in advance of the application window opening, as longer lead times help to promote more widespread knowledge about the program. [Such Outreach and education should commence no later than the start of the Communication Period.] Discussion: -- Not sure why we bracketed the language, but perhaps to agree on the time period. -- Communication Period is at least 4 months, or as commensurate with the requirements of the program. -- Support for the bracketed language. ACTION ITEM: Remove the brackets. ACTION ITEM: Confirm the timing of the Communication Period and create a flow chart diagram for communications and outreach. Implementation Guidance xx (rationale 4): Outreach efforts should not only target the Global South, but also “middle applicants,” which are located in struggling regions that are further along in their development compared to underserved or underdeveloped regions. In addition, the evaluation criteria for Applicant Support must treat “middle applicants” similar to those currently set forth in Criteria #1, Section 4 (Operation in a developing economy) of the Financial Assistance Handbook. Discussion: -- It’s not just outreach to target “middle applicants” but in 2012 it gave extra points/prioritized those that were in developing regions so we wanted to make sure that because we are changing that to “middle applicants” we should be consistent in our evaluation criteria. -- Seemed to be supported in the ICANN67 discussion. Recommendation xx (rationale 6): ICANN Org must develop a plan for funding the Applicant Support Program, as proposed in the Implementation Guidelines below. Implementation Guideline xx (rationale 6): ICANN Org should evaluate whether it can provide funds (as they did in 2012) or whether additional funding is needed for the Applicant Support Program in subsequent rounds. Implementation Guideline xx (rationale 6): ICANN Org should seek funding partners to help financially support the Applicant Support Program, as appropriate. Discussion: -- During ICANN67 there was discussion to add a reference – that if we had a fee floor established because the costs were below that floor that one of the purposes for the excess fees would be that they would go to applicant support – added a footnote. -- Question: Does that encourage inflated application fees? Answer: ICANN dictates the fees, but from a cost-recovery basis if the fees are below what we would consider a floor then one of the purposes of the excess could be to go to the applicant support program. -- Question: Could this open up to ICANN saying that the application fee will be x-plus, meaning the fee would be higher than it would otherwise be to take into account that some of the excess fees will go to the application support program? Answer: ICANN would probably consider the fees as part of the cost in the cost-recovery to run the gTLD program. We have specific criteria as to how a floor should be set. Rationale for the fee will also be published. Re: Whether there should be any changes to the 2012 approach of establishing priority between applications if there are more qualified applicants than funds available. -- On the issue of thinking about a mechanism to handle "over demand" on ASP funds, even if we do not come up with a recommendation, could we suggest that IRT consider this somehow? ACTION ITEM: Add this as an Implementation Guideline for the IRT to consider. 3. AOB: Future Scheduling and the Work Plan -- Because we have covered sections more quickly than we expected we are able to move topics up in the Work Plan. WG members should review the Work Plan at: https://docs.google.com/spreadsheets/d/1SN8GX1nVER30p_VmX1fAEJUTRLByXhrI96k… -- Looking much more likely that we can get the report out before ICANN68. -- Sections of the Report will look very much like the material the WG has been reviewing. -- We will use the time after discussing the sections to come up with questions for public comment. -- We will have a couple longer meetings in April and May – extending two calls in each month for an additional half hour for more focused conversations on topics that will take longer. April 6 and 16, and May 4 and 14. -- Consensus calls will not occur until we analyze public comments on the draft Final Report. -- Would like to get the Final Report to the Council before the ICANN69 meeting. -- Staff will update the rest of the Work Plan now that topics have been moved up. -- Question: What happened to the topics where additional drafting was proposed, such as community applications and what constitutes the “necessary” when a panels is doing outside research; and the discussion on GAC Consensus Advice and redlines from Paul McGrady? We need to jump on those things. How can we expedite those drafting proposals? Answer: Leadership Team will discuss and get back to the WG. ACTION ITEM: Leadership Team to consider how to address the additional drafting proposed for community applications and panels doing outside research and the redlines in GAC Consensus Advice; add these items back on the calendar and consider whether they make sense to add to the 6 April meeting.

1 0

Post call | New gTLD Subsequent Procedures Working Group call / Thursday, 26 March 2020 at 03:00 UTC
by Julie Bisland March 26, 2020

March 26, 2020

Dear all, All recordings for the New gTLD Subsequent Procedures Working Group call held on Thursday, 26 March 2020 at 03:00 UTC can be found on the agenda wiki page <https://community.icann.org/x/ZiOJBw> (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

Proposed agenda - New gTLD Subsequent Procedures PDP WG - Thursday, 26 March at 0300 UTC
by Julie Hedlund March 24, 2020

March 24, 2020

Dear all, Please find below the proposed agenda for the call on Thursday, 26 March 2020 at 03:00 UTC for 90 minutes: Proposed Agenda: 1. Review Agenda/Updates to Statements of Interest 2. Discussion of Final Report Topics * 2.5.4 Applicant Support – see attached PDF for clean version and redline at: https://docs.google.com/document/d/1xXu7gPKiblS3Vh4MCuK6NWfeRmMolXf9VF5sO7O… * 2.3.3 Applicant Freedom of Expression – see: https://docs.google.com/document/d/1kUlmZH8nxWTgfcRluA5FxLheMm4XhhOwkRt7om5… 3. 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>. Kind regards, Julie Julie Hedlund, Policy Director

1 0

Post call | New gTLD Subsequent Procedures Working Group call on Monday, 23 March 2020 at 20:00 UTC
by Andrea Glandon March 23, 2020

March 23, 2020

Dear all, All recordings for the New gTLD Subsequent Procedures Working Group call held on Monday, 23 March 2020 at 20:00 UTC can be found on the agenda wiki page <https://community.icann.org/x/ZCOJBw> (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 Andrea

1 0

Notes and Action Items - New gTLD Subsequent Procedures PDP WG - 23 March 2000 UTC
by Julie Hedlund March 23, 2020

March 23, 2020

Dear Working Group members, Please see below the notes from the meeting on 23 March at 2000 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-03-23+New+gTLD+Subsequent+Pr…. Kind regards, Julie Notes and Action Items: Actions: 2.8.1 Role of GAC Early Warnings/Advice CLEAN LANGUAGE -- Implementation Guidance xx (rationale 2): To the extent that the GAC provides Advice in the future on categories of TLDs, the Working Group urges the GAC to provide this Advice, and the Board to take any corresponding action, prior to the finalization of the next Applicant Guidebook. Once the application period has begun, the Working Group urges the GAC to limit Advice to individual applications only, based on the merits and details of the application for a particular string, not [only] on groups or classes of applications or string types. ACTION ITEM: Can the clean language be changed in a way that would satisfy the WG? Paul will gather a small group for a rewrite if necessary. Recommendation xx (rationale 3): ACTION ITEM: Re-write to emphasize that the AGB should reference the section of the Bylaws that govern how GAC Advice is addressed by the Board. Recommendation xx (rationale 4): ACTION ITEM: Change the first sentence to: “The Working Group recommends that GAC Early Warnings are issued during a period that is concurrent with the application comment period, as described in the 2012 Applicant Guidebook.” Delete sticken text and footnote. Recommendation xx (rationale 6): ACTION ITEM: Change the text to: “Relevant GAC members are strongly encouraged to make themselves available during a specified period of time period for direct dialogue with applicants impacted by GAC Early Warnings or GAC Advice to determine if a mutually acceptable solution can be found.” Delete stricken text (second instance of “period”). c. New issues raised in deliberations since publication of the Initial Report, if applicable. Re: CCT-RT Recommendation 33: ACTION ITEM: Leadership and staff to gather up categories on which the GAC has already provided advice and see if the WG has addressed or will address them. Notes: 1. Updates to Statements of Interest 2. Discussion of Final Report Topics – see the documents at: https://docs.google.com/document/d/1xXu7gPKiblS3Vh4MCuK6NWfeRmMolXf9VF5sO7O… a. 2.8.1 Role of GAC Early Warnings/Advice Affirmation xx -- Suggested change from Paul McGrady: -- Add at the beginning, “The Working Group acknowledges the ability of the GAC to issue GAC Consensus Advice in accordance with the ICANN Bylaws.” ACTION ITEM: Leave in the reference to the section of the Bylaws. Clean Version Text: Implementation Guidance xx (rationale 2): To the extent that the GAC provides Advice in the future on categories of TLDs, the Working Group urges the GAC to provide this Advice, and the Board to take any corresponding action, prior to the finalization of the next Applicant Guidebook. Once the application period has begun, the Working Group urges the GAC to limit Advice to individual applications only, based on the merits and details of the application for a particular string, not [only] on groups or classes of applications or string types. Suggested changes from Paul McGrady -- Change Implementation Guidance to Recommendation: Implementation Guidance xx (rationale 2): Recommendation xx: To the extent that the GAC provides GAC Consensus Advice (as defined in the ICANN Bylaws) in the future on categories of TLDs, the Working Group urges the GAC to should provide this Advice, and the Board to take any corresponding action, prior to the finalization of the next Applicant Guidebook. In the event that such GAC Consensus Advice is issued after the finalization of the next Applicant Guidebook, the ICANN Board must, in the absence of extraordinary circumstances, vote to reject the GAC Consensus Advice. Once the application period has begun, the Working Group urges the GAC to limit should limit GAC Consensus Advice to that which applies to individual applicationsstrings only, based on the merits and details of the applications for a particularthat string, not [only] on groups or classes of applications or string types. [ In the event that GAC Consensus Advice is issued after the application period has begun and the GAC Consensus Advice applies to groups or classes of applications or string types, the ICANN Board must, absent extraordinary circumstances, vote to reject the GAC Consensus Advice.] Discussion: -- Concerns about the suggested edits -- that they would constrain GAC advice. -- Suggest a softer approach to encourage GAC to give its advice earlier. -- The GAC has been trying to look for ways to intercede in ways that are constructive. -- The GAC operates more efficiently now than it did during the early days of the last round. And is more engaged. -- Question: Where did we come out on the timing of public comment depending on the number of applications? Answer: There is a separate section that talks about timelines. Let’s focus on the substance of GAC Advice and Early Warning. -- It might be helpful to focus on the implications, say the advice on closed generics, in terms of a hypothetical -- how the language that Paul is suggesting would work. How do we ensure that the GAC gives the advice before the AGB is published. -- Concerned about trying to time limit when the GAC can give advice -- GAC cannot be expected to predict where it might need to provide advice. -- This would not preclude the GAC from issuing advice on single strings. This applied to GAC Advice for categories or groups of applications. GAC could still give advice on all of the individual strings in a particular category, and just not call it a “category”. -- I don’t think we can say what the Board “must” do -- even if they accept this recommendation. -- We could say that the Board should take into account whether the GAC had a clear opportunity to give this advice before the milestone (not deadline), in considering whether to adopt GAC advice. -- Stick to “urges” and not say “should” or “must”. ACTION ITEM: Can the clean language be changed in a way that would satisfy the WG? Paul will gather a small group for a rewrite if necessary. Recommendation xx (rationale 1): -- Suggestion to delete footnote #18. Recommendation xx (rationale 3): -- Question: How does ICANN Org “mitigate concerns”? I thought they facilitate mitigation between applicants and the GAC. Answer: There were a couple of ways it did in 2012, and we’re not stating how they should do it. They could use PICs. -- When we talk about a “strong presumption” we need another reference to the Bylaws to substitute for this. Need to refer applicants to the Bylaws section that governs this. It is referenced in footnote #19. We aren’t trying to write the AGB here. -- Should be more specific that there should be Implementation Guidance that the AGB has to reference the relevant section of the Bylaws. ACTION ITEM: Re-write to emphasize that the AGB should reference the section of the Bylaws that govern how GAC Advice is addressed by the Board. Recommendation xx (rationale 4): -- Reference to 2012 Applicant Guidebook is confusing. Suggests that the WG might be recommending the same time period as in the 2012 AGB. Delete “as described in the 2012 Applicant Guidebook” and the footnote. ACTION ITEM: Change the first sentence to: “The Working Group recommends that GAC Early Warnings are issued during a period that is concurrent with the application comment period, as described in the 2012 Applicant Guidebook.” Delete sticken text and footnote. c. New issues raised in deliberations since publication of the Initial Report, if applicable. Re: CCT-RT Recommendation 33 states: “As required by the October 2016 Bylaws, GAC consensus advice to the Board regarding gTLDs should also be clearly enunciated, actionable and accompanied by a rationale, permitting the Board to determine how to apply that advice. ICANN should provide a template to the GAC for advice related to specific TLDs, in order to provide a structure that includes all of these elements. In addition to providing a template, the Applicant Guidebook (AGB) should clarify the process and timelines by which GAC advice is expected for individual TLDs.” -- Question: Can we provide a recommendation that encourages the GAC to provide advice to applicants about strings that they would find concerning? What would be really helpful for applicants is to know that they are going down the wrong path. Answer: GAC could say that they have already provided advice on certain categories. It would be good for us to determine whether to incorporate that Advice first and then see if there are other categories that they are currently concerned about. ACTION ITEM: Leadership and staff to gather up categories on which the GAC has already provided advice and see if the WG has addressed or will address them. 3. AOB: Upcoming Meeting Planning -- We are going to keep the calls on the schedule. -- We record all the calls and the email list is open. -- We know this is a dynamic situation that could change rapidly.

1 0

(Corrected body) Post-ICANN67 Policy Report Now Available
by Julie Bisland March 23, 2020

March 23, 2020

Dear all, The Post-ICANN67 Policy Report is now available. Please click here to access it: https://go.icann.org/post67 [go.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__go.icann.org_post67&d=…> . Thank you. Kind 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

Post-ICANN67 Policy Report Now Available
by Julie Bisland March 23, 2020

March 23, 2020

Dear all, The Post-ICANN66 Policy Report is now available. Please click here to access it: https://go.icann.org/post67 [go.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__go.icann.org_post67&d=…> . Thank you. Kind 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

Proposed agenda - New gTLD Subsequent Procedures PDP WG - Monday, 23 March at 2000 UTC
by Julie Hedlund March 23, 2020

March 23, 2020

Dear all, Please find below the proposed agenda for the call on Monday, 23 March 2020 at 20:00 UTC for 90 minutes: Proposed Agenda: 1. Review Agenda/Updates to Statements of Interest 2. Discussion of Final Report Topics – see the redlined documents at: https://docs.google.com/document/d/1xXu7gPKiblS3Vh4MCuK6NWfeRmMolXf9VF5sO7O… * 2.8.1 Role of GAC Early Warnings/Advice – see attached PDF for clean version * 2.5.4 Applicant Support – see attached PDF for clean version 3. 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>. Kind regards, Julie Julie Hedlund, Policy Director

2 1

Post call | New gTLD Subsequent Procedures Working Group call on Thursday, 19 March 2020 at 20:00 UTC
by Andrea Glandon March 19, 2020

March 19, 2020

Dear all, All recordings for the New gTLD Subsequent Procedures Working Group call held on Thursday, 19 March 2020 at 20:00 UTC can be found on the agenda wiki page <https://community.icann.org/x/YiOJBw> (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 Andrea

1 0