March 2023 - Bc-gnso - lists.icann.org

Re: [bc-gnso] Mason and Mark in the ICANN Deck of Cards
by Andrew Mack March 12, 2023

March 12, 2023

Bravo Superheroes! Andrew Mack Principal C: +1 (202) 256-1077 O: +1 (202) 642-6429 Skype: Andrew.Mack [signature_2312459691] www.amglobal.com<http://www.amglobal.com/> | amack(a)amglobal.com<mailto:amack@amglobal.com> From: Bc-gnso <bc-gnso-bounces(a)icann.org> on behalf of Steve DelBianco via Bc-gnso <bc-gnso(a)icann.org> Reply-To: Steve DelBianco <sdelbianco(a)netchoice.org> Date: Saturday, March 11, 2023 at 1:26 PM To: BC List <bc-gnso(a)icann.org> Subject: [bc-gnso] Mason and Mark in the ICANN Deck of Cards A rare treat for BC members attending ICANN75 in Cancun: The ICANN76 Deck of Players includes Mason and Mark D: [cid:image002.jpg@01D95504.76D793D0]

1 0

Policy Calendar for 13-Mar BC Meeting
by Steve DelBianco March 12, 2023

March 12, 2023

Here’s the Policy Calendar for the BC OPEN MEETING on 13-Mar (also in attachment “policy calendar.pdf”) Channel 1. BC participation in ICANN Public Comment process: On 28-Feb we commented<https://itp.cdn.icann.org/public-comment/proceeding/Proposed%20Procedure%20…> on Proposed Procedure<https://itp.cdn.icann.org/en/files/root-system/procedure-selecting-top-leve…> for Selecting a Top-Level Domain String for Private Use. (See comments page<https://www.icann.org/en/public-comment/proceeding/proposed-procedure-for-s…> and SAC 113<https://www.icann.org/en/system/files/files/sac-113-en.pdf>, published Sep-2020.). This is about locally-defined domain names that enterprises use to support their applications and infrastructure, where that domain TLD is not present in the root zone. “Two examples of private-use TLDs that are well known within the ICANN community are .corp and .home.” Thanks to Rajiv Prasad for drafting. On 13-Feb we commented<https://cbu.memberclicks.net/assets/docs/positions-statements/2023/2023_02F…> on the FY24-28 Operating & Financial Plan, FY24 Op plan & budget. (comments page<https://www.icann.org/en/public-comment/proceeding/draft-fy2428-operating-f…>). Thanks to Tim Smith for drafting. Selected ICANN Public Comments<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2…> and other opportunities for the BC to comment: 1. proposed ICANN bylaws amendments<https://itp.cdn.icann.org/en/files/additional-reviews/proposed-amendments-t…> for the IANA Naming Function Review (comments page<https://www.icann.org/en/public-comment/proceeding/iana-naming-function-rev…>). Comments close 18-Apr. This review was added to ICANN bylaws as part of the IANA transition, to let customers of IANA naming function confirm performance of the IANA Naming Function Contract between ICANN and its affiliate, Public Technical Identifiers. In 2021 the BC supported<https://cbu.memberclicks.net/assets/docs/positions-statements/2021/2021_03M…> a minor amendment to the IANA contract. In 2020 we commented on the first IANA Naming Function Review<https://www.icannbc.org/assets/docs/positions-statements/2020/2020_12Decemb…>, thanks to Jimson Olufuye. Looking for volunteer(s) to draft a BC comment on these bylaw amendments. 2. NIS2, followed closely by Andrew Bennett, Nik Lagergren, and Marie Pattullo. NIS2 final text<https://www.europarl.europa.eu/doceo/document/A-9-2021-0313-AM-281-281_EN.p…> was approved by European Parliament on 10-Nov, and by Council on 28-Nov. That final text published on 27-Dec<https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ:L:2022:333:FULL&…> (p.82), which begins the 21-month period for Member States to transpose into national laws and regulations. See Caroline’s 12-Mar email regarding NIS2 discussions in Cancun on Saturday. Channel 2. Support for discussion and votes of our representatives on GNSO Council Marie Pattullo and Mark Datysgeld are our GNSO Councilors. Previous Council meeting was 16-Feb. See Agenda<https://community.icann.org/x/mgjVD>, Transcript<https://gnso.icann.org/sites/default/files/policy/2023/transcript/transcrip…>, Zoom Recording<https://icann.zoom.us/rec/share/qYmJbvdD2iftNPPz29ZL3fJUNMO2_e0asCMeWlcTRWl…>. Meeting highlights include: Unanimously approved amended charter<https://gnso.icann.org/sites/default/files/policy/2023/correspondence/novoa…> for Transfer Policy Review PDP and Project Change Request<https://gnso.icann.org/sites/default/files/policy/2023/correspondence/carne…> Unanimously approved revised Charter<https://gnso.icann.org/sites/default/files/policy/2023/draft/draft-scbo-cha…> for the Budget and Operations Townhall (formerly known as the SCBO). Next Council meeting is 15-Mar at 18:15 UTC while in Cancun. Agenda<https://community.icann.org/display/gnsocouncilmeetings/Final+Proposed+Agen…> highlights include: Item 4: Vote on adopting Council committee to oversee continuous improvement recommendations<https://gnso.icann.org/sites/default/files/policy/2023/correspondence/chen-…> Item 5: Discuss next steps for Expired Domain Deletion Policy and Recovery Policy, small team recommendation<https://docs.google.com/document/d/1zxxyIsg7HVGtAK7HsaTfw3nMX_zZfY3hUrdiDoa…>. Item 6: Discuss GNSO projects that may impact SubPro timeline Item 7: Continue discussing SubPro Item 8: Discuss next steps for Whois Disclosure System Steve is on Council small team<https://community.icann.org/pages/viewpage.action?pageId=186779415> on SSAD ODA<https://www.icann.org/en/system/files/files/ssad-oda-25jan22-en.pdf>, to review a“ticketing system” without obligations for use or for disclosure. On 13-Sep ICANN staff released a design paper<https://www.icann.org/en/system/files/files/whois-disclosure-system-design-…>. Highlights: ICANN org says development over nine months; development and two-year maintenance would be $100,000 * It does not include accreditation of the requestors. * It does not include a billing function or any fees to the requestor. * There is no obligation of automated processing of requests by contracted parties. We pushed for logging and reporting of request data, even when the registrar is not currently participating. The design paper<https://www.icann.org/en/system/files/files/whois-disclosure-system-design-…> and addendum<https://gnso.icann.org/sites/default/files/policy/2022/correspondence/ducos…> indicate access to data, even for non-participating registrars: "The system will provide reporting on a periodic basis not to exceed the recommended durations. The exact form of the reporting is to be determined. It is envisioned that eventually the data will be made available through the Open Data platform for public consumption." (p.31) Marika (Staff) added this to the addendum<https://gnso.icann.org/sites/default/files/policy/2022/correspondence/ducos…> at p.4: “To facilitate the evaluation of the WHOIS Disclosure System, the small team will continue to work with ICANN Org to ensure that the necessary data is available to ensure the proper evaluation of the Whois Disclosure System, taking into account legal limitations that may exist to share certain information.” See Council’s 17-Nov letter to the Board<https://www.icann.org/en/system/files/correspondence/ducos-to-sinha-17nov22…>. On 27-Feb-2023 the Board directed<https://www.icann.org/en/board-activities-and-meetings/materials/approved-r…> ICANN org to develop the Whois Disclosure System within 11 months. On 11-Mar-2023 the small team held a session in Cancun to hear about progress from Org’s development team. The system is now named Registration Data Request Service Steve asked for the data model, up-front. To include images of screenshots submitted with requests. Granularity of reporting can be adjusted later. Suggested batch request feature from vendors like AppDetex and Fairwinds Steve said: Usage has 2 dimensions: Quantity of requests and responses Quality of requests (origin, reason, detail, registrar, domain name, etc.) Staff said they can evolve the data model over time (huh?). Asked us to say what we want reported. Other Council activities: 1. Closed Generic gTLDs in the next round. following an invitation from the Board, GNSO and GAC will “formulate a workable framework to identify and handle closed generic applications for the immediate next round of new gTLDs”, and in this dialogue we will be joined by ALAC. The framework discussion will focus on options other than the two endpoint positions (i.e. no closed generics at all; closed generics without restrictions) as per the Board’s Proposed Parameters for Dialogue. As discussed on our 14-Nov call, Steve researched prior BC positions on closed generic going back a decade to our comments during the 2012 round of gTLD expansion. See attached email from Steve with the full explanation. To summarize In a sentence, we’d say: The BC would be concerned about consumer deception and competitor exclusion if a single competitor in an industry manages a closed TLD where the TLD string is closely identified with the industry. For example, say a travel company or a hotel chain runs .HOTELS as a closed TLD -- not allowing competitors to register second level names, while also controlling content on domains such as search.hotels, eco.hotels, family.hotels, best.hotels, cheap.hotels, luxury.hotels, etc. It’s easy to see how the TLD owner could bias content and search results on those consumer information sites, without consumers being fully aware. 2. Transfer Policy Working Group. (Zak Muscovitch and Arinola Akinyemi). Work group evaluated public comment report<https://itp.cdn.icann.org/en/files/inter-registrar-transfer-policy-irtp/sum…> on its initial report<https://itp.cdn.icann.org/en/files/inter-registrar-transfer-policy-irtp/tra…>. Now discussing Charter Questions<https://docs.google.com/document/d/1i6tLO_qbSa-ace0BnKaAn7voP1UA1RjYlrRo2Zn…> related to the Transfer Dispute Resolution Policy (TDRP) 3. GNSO Guidance Process (GGP). (Lawrence Olawale-Roberts). Work on Applicant Support kicks off on Monday, 21 November at 1500 UTC with an initial call of the working group. The main wiki pag<https://community.icann.org/display/GGPGIRFAS/GNSO+Guidance+Process+%28GGP%…>e that provides the status and background of the task and the page that lists the Members and Alternates<https://community.icann.org/display/GGPGIRFAS/Members+and+Mailing+List> are linked within. Observers will have ability to view member chat and information shared in the zoom webinar room, but observers will not be able to use chat or raise hands during sessions. BC member Segunfunmi Olajide has signed up as an observer. 4. DNS Abuse small team. Mark Datysgeld serves as co-lead. CPH representatives met with ICANN Org for negotiations on RAA and RyA amendments to address DNS Abuse. (Sally’s letter<https://www.icann.org/en/system/files/correspondence/costerton-to-heineman-…>). To inform that negotiation, Mason drafted and sent this letter<https://www.icann.org/en/system/files/correspondence/cole-et-al-to-sinha-co…> from BC, IPC, and ALAC on 23-Jan Channel 3. Supporting discussion/voting on matters before the Commercial Stakeholders Group (CSG) Tim Smith is the CSG Liaison for the BC. See final schedule for ICANN 76 in Cancun<https://icann76.sched.com/>, 11-Mar thru 16-Mar Board Seat 14. CSG ExComm has now offered 2 candidates to NCSG and are awaiting their consideration. Determining the candidate who will be put forward on behalf of the NCPH will likely take us through ICANN 76 and we are hopeful we can find a common candidate from the two SGs. CSG is also seeking more ongoing dialogue with NCSG and our ExComm has proposed more regular meetings, even intersessional between ICANN meetings, to discuss our common interests. ICANN Board and CSG will meet – Tuesday, March 14, 21:30 UTC (4:30pm) Additional upcoming meetings CPH DNS Abuse Outreach – Monday, March 13, 18:15 UTC (1:15pm) CSG Membership Meeting – Tuesday, March 14, 15:30 UTC (10:30am)

1 0

Mason and Mark in the ICANN Deck of Cards
by Steve DelBianco March 11, 2023

March 11, 2023

A rare treat for BC members attending ICANN75 in Cancun: The ICANN76 Deck of Players includes Mason and Mark D: [cid:image001.jpg@01D9541D.006E6580]

1 0

DNS Abuse Institute Newsletter - March 2023
by Steve DelBianco March 11, 2023

March 11, 2023

For those BC members who are interested. View this email in your browser<https://mailchi.mp/dnsabuseinstitute.org/dns-abuse-institute-newsletter-oct…> [https://mcusercontent.com/feb87794e3b3c6cb0d7949bdf/images/8f06597e-6713-73…] MARCH 2023 EDITION With ICANN 76 in Cancun drawing near, it seemed a good time to provide an update on the activities of the DNS Abuse Institute. Below we’ve got news on our measurement project DNSAI Compass™, NetBeacon™, and some recent work on bulk domain registrations. DNSAI COMPASS We have now been publishing data<https://dnsabuseinstitute.us16.list-manage.com/track/click?u=feb87794e3b3c6…> as part of our measurement initiative for over 6 months. The intention of Compass is to establish a credible source of metrics for addressing DNS Abuse. We hope this will enable focused conversations, and identify opportunities for improvement, help us understand through these reports which factors, policies, and processes are effective, and empower the industry with evidence. As Compass matures, we’re working towards public reporting on individual Top Level Domains (TLD) and registrar performance. Our aim is to celebrate and recognize observed good practice, as well as shine a spotlight on potential for areas of improvement in the industry. We’ve also been working on developing individualized reports for registrars and TLDs ahead of ICANN76 in Cancun. These are the reports we show to registrars and registry operators when we meet with them directly to give them a sense of how they’re doing. These are not for public consumption and we do not intend to publish them. However, they do contain a number of metrics which could be used as part of an approach to public reporting. For those of you headed to ICANN76, we’ll be presenting at the CPH DNS Abuse Outreach Session during the 'upcoming community work' section, and giving a preview of some of the data we hold (with permission from the relevant registry and registrar). This session takes place at 13:15 Cancun (UTC-5), 13 March 2023<https://dnsabuseinstitute.us16.list-manage.com/track/click?u=feb87794e3b3c6…>. We’re offering an opportunity for all registries and registrars to meet with us and view the domain registration and abuse data we have collected on your registrar/registry. If you would like to chat with us in person in Cancun, Please contact us<https://dnsabuseinstitute.us16.list-manage.com/track/click?u=feb87794e3b3c6…> for more information or book a time<https://dnsabuseinstitute.us16.list-manage.com/track/click?u=feb87794e3b3c6…> directly. Alternatively, we can organize a virtual meeting later in March/April 2023. NETBEACON When we began developing NetBeacon<https://dnsabuseinstitute.us16.list-manage.com/track/click?u=feb87794e3b3c6…>, our free abuse reporting system, we concentrated on ensuring it had the features needed to improve the experience of receiving reports for Registrars. This meant ensuring reports were standardized, enriched with useful information, and distributed to where registrars wanted to get them. While there is always more work to do on the recipient side, we’ve been recently working to add useful features for the people and organizations that wish to report DNS Abuse. We’re pleased to announce that NetBeacon now has the ability to “verify” abuse reporters. Anyone who represents an organization can request verification from the Identity settings page in NetBeacon. This allows verified abuse reporters to include their organization name in report subject lines, and to include boilerplate text on every abuse report they submit. We’ve got a number of other reporter-specific features in the pipeline we look forward to sharing soon. Check out NetBeacon here<https://dnsabuseinstitute.us16.list-manage.com/track/click?u=feb87794e3b3c6…>. PUBLICATIONS Letter to the GNSO on Bulk Registrations In January, the DNSAI received a letter from the GNSO asking for information on the relationship between bulk domain registration and DNS Abuse. We recently published our response here<https://dnsabuseinstitute.us16.list-manage.com/track/click?u=feb87794e3b3c6…>. Briefly, we surveyed all the research we could find on bulk registrations, and found that there were no consistent definitions of the issue. In addition, none of the research attempted to understand what proportion of bulk registered domains were abusive, only that some abusive domains were registered in bulk. While we’re conducting our own investigations into the issue, it seems clear to us that more research would be necessary to justify work from the community. Best Practices Anti-Fraud Tools and Registration Flows for Registrars<https://dnsabuseinstitute.us16.list-manage.com/track/click?u=feb87794e3b3c6…> Making Phishing Reports Useful<https://dnsabuseinstitute.us16.list-manage.com/track/click?u=feb87794e3b3c6…> Abuse Reporter Expectation Management<https://dnsabuseinstitute.us16.list-manage.com/track/click?u=feb87794e3b3c6…> Generic Abuse Policy for Registrars and Registries<https://dnsabuseinstitute.us16.list-manage.com/track/click?u=feb87794e3b3c6…> Secure Your Website, Save the Internet<https://dnsabuseinstitute.us16.list-manage.com/track/click?u=feb87794e3b3c6…> DNSAI IN THE NEWS DNSAI Compass: Six Months of Measuring Phishing and Malware An article the Institute published in CircleID<https://dnsabuseinstitute.us16.list-manage.com/track/click?u=feb87794e3b3c6…> to share information on lessons learnt six months on measuring phishing and malware. Introduction to the Institute in Spanish Thank you to .ec for hosting us on their webinar and translating our introduction to the Institute into Spanish. Available online<https://dnsabuseinstitute.us16.list-manage.com/track/click?u=feb87794e3b3c6…> (at 38 mins). UPCOMING EVENTS ICANN Cancun We will be available for meetings with interested parties. In particular, if you’re a registrar or registry and you haven’t met with us to view your unpublished data we encourage you to do so. You can book a meeting here<https://dnsabuseinstitute.us16.list-manage.com/track/click?u=feb87794e3b3c6…>. Nordic Domain Days Graeme will be in Stockholm for Nordic Domain Days, May 8th & 9th, 2023. We’ll be participating in a DNS Abuse workshop, and introducing everyone to NetBeacon and our Compass reporting. If you’re planning on attending and want to catch up, please reach out. Thanks for reading, and as usual, please feel free to reach out directly. Graeme Bunton, Executive Director, DNS Abuse Institute @graemebunton graeme(a)dnsabuseinstitute.org<mailto:graeme@dnsabuseinstitute.org> [Twitter]<https://dnsabuseinstitute.us16.list-manage.com/track/click?u=feb87794e3b3c6…> [Facebook]<https://dnsabuseinstitute.us16.list-manage.com/track/click?u=feb87794e3b3c6…> [Website]<https://dnsabuseinstitute.us16.list-manage.com/track/click?u=feb87794e3b3c6…> Copyright © 2023 Public Interest Registry, All rights reserved. You are receiving this email because you joined our news mailing list at the dnsabuseinstitute.org website. Our mailing address is: Public Interest Registry 11911 Freedom Dr Ste 1000 Reston, VA 20190-5631 Add us to your address book<https://dnsabuseinstitute.us16.list-manage.com/vcard?u=feb87794e3b3c6cb0d79…> Want to change how you receive these emails? You can update your preferences<https://dnsabuseinstitute.us16.list-manage.com/profile?u=feb87794e3b3c6cb0d…> or unsubscribe from this list<https://dnsabuseinstitute.us16.list-manage.com/unsubscribe?u=feb87794e3b3c6…>.

1 0

Agenda for GNSO Council Meeting | Wednesday, 15 March 2023
by Steve DelBianco March 4, 2023

March 4, 2023

Please find below the final proposed agenda for the GNSO Council Meeting on 15 March 2023. Please note that all documents referenced in the agenda have been gathered on a Wiki page for convenience and easier access: https://community.icann.org/x/2QGjDQ GNSO Council meeting on Wednesday, 15 March at 18:15 UTC: https://tinyurl.com/y4naum35. (Wednesday) 11:15 Los Angeles; 14:15 Washington DC; 18:15 London; 19:15 Paris; 21:15 Moscow; (Thursday) 05:15 Melbourne GNSO Council Meeting Remote Participation: [Published 24 hours prior to meeting] Councilors should notify the GNSO Secretariat in advance if they will not be able to attend and/or need a dial out call. ___________________________________ Item 1: Administrative Matters (10 minutes) 1.1 - Roll Call 1.2 - Updates to Statements of Interest 1.3 - Review / Amend Agenda 1.4 - Note the status of minutes for the previous Council meetings per the GNSO Operating Procedures: Minutes<https://gnso.icann.org/sites/default/files/policy/2023/minutes/minutes-gnso…> of the GNSO Council meeting on 19 January 2023 were posted on 02 February 2023. Minutes<https://gnso.icann.org/sites/default/files/policy/2023/minutes/minutes-gnso…> of the GNSO Council meeting on 16 February 2023 were posted on 02 March 2023. Item 2: Opening Remarks / Review of Projects & Action List (5 minutes) 2.1 - Review focus areas and provide updates on specific key themes / topics, to include review of Projects List<https://gnso.icann.org/en/council/project> and Action Item List. <https://community.icann.org/x/RgZlAg> Item 3: Consent Agenda (5 minutes) TBD Item 4: COUNCIL VOTE - Adoption of the Council Committee for Overseeing and Implementing Continuous Improvement (CCOICI) Working Group Self-Assessment (WGSA) Recommendations Report (10 Minutes) The GNSO Council initiated<https://gnso.icann.org/en/council/resolutions/2020-current#202106> the GNSO Framework for Continuous Improvement Pilot Project on 16 June 2021, and, as part of this Framework, the Council established the Committee for Overseeing and Implementing Continuous Improvement (CCOICI). As part of the pilot, the CCOICI was tasked<https://community.icann.org/pages/viewpage.action?pageId=170787421> to consider if/how the GNSO WG Self-Assessment could be improved and possibly enhanced with a periodic assessment and an exit interview, with the goal of giving interested parties an opportunity to help identify potential issues and potential future improvements the GNSO Council could consider. The CCOICI started the Working Group Self-Assessment assignment in October 2021 and concluded its work on this assignment in February 2022. However, the CCOICI deferred conducting the public comment until it could be combined with recommendations related to the GNSO Statement of Interest (SOI). The consolidated public comment proceeding<https://www.icann.org/en/public-comment/proceeding/updates-to-the-gnso-stat…> on Proposed Updates to the GNSO Operating Procedures was initiated on 09 September 2022 and closed on 14 November 2022. The CCOICI integrated public comments received as appropriate and submitted its Recommendations Report<https://gnso.icann.org/sites/default/files/policy/2023/correspondence/chen-…> to the Council on 5 January 2023. Here, the Council will vote to adopt the Working Group Self-Assessment (WGSA) Recommendations Report. 4.1 – Presentation of motion - (Manju Chen, Chair, Committee for Overseeing and Implementing Continuous Improvement (CCOICI)) 4.2 – Council discussion 4.3 – Council vote (voting threshold: simple majority) Item 5: COUNCIL DISCUSSION - Next Steps for Consideration of Expired Domain Deletion Policy (“EDDP”) and Expired Registration Recovery Policy (“ERRP”) (15 minutes) The GNSO Council previously considered when to request a Policy Status Report (“PSR”) for the purpose of conducting a review of the two Expiration Policies, the EDDP and the ERRP. In November 2020, given concerns about its capacity and no known issues with the policies, the Council agreed to delay the request for the Policy Status Report (PSR) for a period of 24 months. As 24 months have now passed, the Council is reconsidering whether now is an appropriate time to request a Policy Status Report. To that end, in July 2022, the Council agreed that it would be helpful to consult with both registrars and ICANN org to help determine if there are any known issues or concerns with either of the two Expiration Policies which could warrant requesting a PSR. ICANN org shared a report<https://mm.icann.org/pipermail/council/2022-November/026164.html> from Contractual Compliance colleagues on 1 November 2022, and GNSO Councilors from the Registrar Stakeholder Group shared feedback from registrars on previous Council calls. During its meeting on 17 November 2022<https://community.icann.org/display/gnsocouncilmeetings/Final+Proposed+Agen…>, representatives from ICANN org’s Contractual Compliance Team provided a briefing of the report<https://mm.icann.org/pipermail/council/2022-November/026164.html>, and the Council briefly considered potential next steps. Following the meeting, Nacho Amodoz, Greg DiBiase, and Susan Payne volunteered to closely review the report<https://mm.icann.org/pipermail/council/2022-November/026164.html> from ICANN org and determine if any of the issues raised warrant a PSR request. Here, the Council will receive an update on the small team’s recommendation. 5.1 – Introduction of topic (Greg DiBiase, GNSO Council Vice-Chair) 5.2 – Council discussion 5.3 - Next steps Item 6: COUNCIL DISCUSSION - Review GNSO-owned projects that may impact SubPro timeline (10 minutes) During the Council’s Strategic Planning Session (SPS), a recurring theme emerged. The Council emphasized it should take care to ensure that any SubPro related work within its control should be carefully managed for timely delivery. The Council does not want its work to serve as an impediment to the timely implementation and launch of the next round of new gTLDs. In order to address this recurring theme, the Council agreed that it would like to receive frequent updates on the work that is connected to the next round of new gTLDs. Those projects include: 1. IDNs EPDP Phase 1 (top-level charter questions) 2. GNSO Guidance Process on Applicant Support 3. Closed Generics Facilitated Discussion 4. Yet to be formed Small Team to review SubPro recommendations likely pending Board action. Here, the Council will receive a brief update on the above-referenced projects. 6.1 – Introduction of topic (Steve Chan) 6.2 – Council discussion 6.3 – Next steps Item 7: COUNCIL DISCUSSION - Continuation of Informal GNSO Council SubPro Discussion (20 minutes) On 12 September 2021 the ICANN Board directed<https://www.icann.org/resources/board-material/resolutions-2021-09-12-en#1.a> the ICANN President and CEO to organize the resources required to begin work on the Operational Design Phase (ODP) for the GNSO’s New gTLD Subsequent Procedures Final Report<https://gnso.icann.org/sites/default/files/file/field-file-attach/final-rep…> and the Affirmations, Recommendations, and Implementation Guidance contained in that report. On 20 December 2021, ICANN org announced<https://www.icann.org/en/announcements/details/icann-launches-new-gtld-subs…> that the SubPro ODP had formally launched, starting at the beginning of January 2022. The ODP Team has shared numerous updates to the community and sent several sets of assumptions/questions to the GNSO Council via the Council’s liaison to the ODP. While ICANN org published the SubPro Operational Design Assessment (ODA) on 12 December, the Council received a briefing during a webinar on 7 December. The Council formed a small team to review the ODA in detail and provided its input<https://www.icann.org/en/system/files/correspondence/ducos-to-sinha-20jan23…> to the ICANN Board on 20 January, in advance of the Board's workshop in January 2023. As discussed in the Chair's blog<https://www.icann.org/en/blogs/details/chairs-blog-recap-of-the-january-boa…>, the ICANN Board spent a full day reviewing the SubPro Outputs and ODA. On 28 February 2023, the Council and ICANN Board had a joint meeting<https://icann.zoom.us/rec/play/7rCLjaxCWtoD3dTl87DnB9A1WO-dHO5NFMqTOzmaxNAL…> on SubPro, and the Council had a follow-up informal discussion on 7 March 2023. Here, the Council will discuss the joint meeting with the Board and the informal discussion, and consider appropriate next steps. 7.1 – Introduction of topic (Sebastien Ducos) 7.2 – Council discussion 7.3 – Next steps Item 8: COUNCIL DISCUSSION - Whois Disclosure System Next Steps (15 minutes) ICANN org published the Whois Disclosure System design paper<https://archive.icann.org/meetings/icann75/files/content=t_attachment,f_%22…> in September 2022 and presented it to the GNSO Council and the EPDP Phase 2 Small Team during ICANN75<https://archive.icann.org/meetings/icann75/meetings/wmhLk2gj2Dm6PQaz2.html>. The small team subsequently reviewed the design paper and continued its consultations with ICANN org, resulting in an addendum<https://gnso.icann.org/sites/default/files/policy/2022/correspondence/ducos…> to its preliminary report. The GNSO Council accepted the addendum and communicated to the ICANN Board its support for the request that the ICANN Board proceed with the implementation of the Whois Disclosure System, provided that the updates identified by the small team in the addendum are made. On 27 February 2023, the Board directed<https://www.icann.org/en/board-activities-and-meetings/materials/approved-r…> ICANN org to develop and launch the Whois Disclosure System (System) as requested by the GNSO Council within 11 months from 27 February 2023. The Board also directed ICANN org to operate the System for up to two years from the date of launch, and collect and report on usage data. Furthermore, the ICANN Board has urged “the GNSO Council to consider a Policy Development Process or other means to require registrars to use the System”. During ICANN76, on 11 March 2023, the EPDP Phase 2 Small Team will meet with ICANN org to receive an update the status of implementation of the Whois Disclosure System and continue its consideration of some of the aspects identified as requiring further discussion in the addendum. In addition to receiving an update from the Small Team on its meeting with ICANN org, the Council will consider if/how the instructions to the Small Team should be updated to reflect the Council’s expectations of the Small Team during the implementation phase as well as post-implementation, in addition to the ask from the Board to consider a Policy Development Process or other means to require registrars to use the System. 8.1 Introduction of topic (Greg DiBiase) 8.2 Council Discussion 8.3 Next Steps Item 9: ANY OTHER BUSINESS (10 minutes) 9.1 GNSO Chair Election Timeline Announcement 9.2 Policy Status Report on Policy and Implementation Working Group Final Recommendations Report<https://gnso.icann.org/sites/default/files/filefield_47703/policy-implement…>

1 0