AT-LARGE GATEWAY

At-Large Website

ALAC

RALOs

At-Large Regional Policy Engagement Program (ARPEP)

At-Large Governance

At-Large Reports

Policy Comments & Advice

Working Groups

ICANN Meetings

At-Large Summit (ATLAS III)

At-Large Review Implementation Plan Development

ALAC and RALO Elections, Selections, and Appointments

At-Large FY25 Strategic Priority Activities

Versions Compared

Old Version 215

changes.mady.by.user Justine Chew

Saved on

compared with

New Version 216

changes.mady.by.user Justine Chew

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Deck of Cards
idUpdates


Card
idAddSubPro
labelADDITIONAL WORK ON SUBSEQUENT PROCEDURES

Additional Work on Subsequent Procedures  – TO MONITOR THIS for ALAC/At-Large participation.

2022

  • 15 Jun: Council to proceed with a motion in its Jul meeting to establish a GGP to work just on Applicant Support through a Steering Committee (of a representative+observer model) with ultimate oversight by Council. 
  • 19 May: Council to explore (intersessionally) the Draft New gTLD Subsequent Procedures GNSO Guidance Process (GPP) Initiation Request.
  • 5 May: Council received a Draft New gTLD Subsequent Procedures GNSO Guidance Process (GPP) Initiation Request for its consideration. This will likely be discussed at Council's May 2022 meeting.
  • 9 Mar: Based on GNSO SubPro ODP Liaison update - Question set #2, Council discussed options for the way forward to deal with a number of areas possibly considered as incomplete in terms policy-development: including on Applicant Support, SPIRT, challenges and appeals. But Council has yet to determine the mechanism to adopt.

RE: Closed Generics, specifically

  • 29 Jun: (CG): Council has sent a letter to the Board and the GAC relaying its recommendations on the GAC-GNSO Dialogue. Links to letter and updated recommendations pending.
  • 15 Jun: (CG): Council has agreed to relay its recommendations to the Board and GAC as the next step leading to the start of the GAC-GNSO Dialogue, with ALAC participation.  
  • 19 May (CG): Council Chair Philippe Fouquart received a reply from Maarten Botterman to Council's 27 Apr letter; inter alia encourages GAC and Council to confer on the question of ALAC's participation in the consultative process.
  • 5 May (CG): Council's reconstituted Small Team now comprises Paul McGrady (NCA-Non CPH), Kurt Pritz (RySG), Manju Chen (NCSG), Jeff Neuman (GNSO Liaison to GAC), Justine Chew (ALAC Liaison to GNSO), Greg Dibiase (RrSG), Desiree Miloshevic (NCA-CPH), and Marie Pattulo (CSG); also Council leadership comprising Philippe Fouquart, Sebastien Ducos, and Tomslin Samme-Nlar.
  • 27 Apr (CG): Council replied to the ICANN Board, accepting the invitation for a facilitated dialogue with the GAC on Closed Generics.
    • In its reply, Council noted there being no SubPro recommendation to change current policy on Closed Generics, the approach for the immediate next round of New gTLD applications would be out of harmony with GAC Advice on Closed Generics (namely that closed generics ought to serve a public interest goal).
    • Council stated that Council will pursue next steps for the dialogue (a) on the basis of the Board having asked that its facilitated dialogue be limited to making Closed Generics available with restrictions, including for eg. that they serve a public interest goal; (b) subject to mutual agreement with the GAC on conditions for that dialogue.
    • Council also noted to the Board, NCSG's opposition to the limited dialogue party approach. 
    • (NB. The earlier convened Council small team will now be reconstituted with a larger/more representative membership of Councillors to develop conditions for the dialogue)
  • 22 Apr (GC): GAC responded to the Board's 6 Mar and 10 Mar letters, raising points on the ICANN Org's Framing Paper.
  • 6 Apr (CG): Council CGs Framing Paper Small Team convened with narrow remit of "proposing to Council next steps in responding to the Board proposal (i.e., whether or not the Council is open to working with the GAC on developing a framework for closed generics)" – Council to decide.
  • 30 Mar (CG): Board replied to GAC's 10 Mar letter, acknowledging GAC’s willingness to have ALAC participate in the consultation process; encourages GAC and GNSO Council to consider this matter as part of the discussions regarding the proposed dialogue.
  • 15 Mar (CG): Council to convene small team to review the ICANN Org's framework paper regarding the Board-facilitated dialogue between GNSO-GAC, and to suggest next steps.
  • 10 Mar (CG):  Further to the 7 Mar correspondence, the Board forwarded ICANN Org's Framing Paper for the dialogue on Closed Generics.
  • 10 Mar (CG): GAC replied to the Board's 6 Mar letter, agreeing to participate in dialogue and welcomed participation from the At-Large Advisory Committee (ALAC) in this consultation process.
  • 6 Mar (CG): ICANN Board wrote to the GAC and Council requesting for facilitated dialogue on way forward with Closed Generics (CG).


Card
defaulttrue
idDNS_Abuse
labelON DNS ABUSE

Potential Council next steps regarding DNS abuse  – TO MONITOR THIS and ENSURE ALAC input is understood.

2022

  • 16 Jun: Small Team conducts meeting at ICANN 74
  • 2 Jun: Small Team begins review of responses from Contractual Compliance. 
  • 19 May: Small Team completes review of comments received from outreach to ALAC, GAC, SSAC, DNSAI, SGs and Cs.
  • 20 Apr: ALAC input to 7 Mar letter considered by Small Team and well received, in general.
  • 6 Apr: Input received from BC. Small Team met, to proceed with info gathering from Contractual Compliance in respect of action to do with DNS Abuse vis a vis Contracted Parties. Still awaiting input from other SG/Cs.
  • 4 Apr: Small Team received responses from ALAC, GAC, SSAC and DNSAI to 7 Mar letters. Small Team to meet 6 Apr.
  • 18 Mar: Reply date for 7 Mar letter to ALAC extended to 4 Apr.
  • 7 Mar: Council issued letters to ALAC, GAC, SSAC and the DNS Abuse Institute (DNSAI) to seek input on what DNS abuse issues are best mitigated via policy development specifically, if any, as a mechanism to help determine the Council’s next steps on DNS abuse; to reply by 21 Mar. Input to be sought from each SG also. More respondents may be approached at a later date. 
  • 9 Feb: Small Team initial meeting. Updates to be provided at Council Meeting #2 of 2022.
  • 4 Feb: Council small team (comprising Thomas Rickert, Mark Datysgeld, Wisdom Donkor, Maxim Alzoba, Sebastien Ducos, Greg DiBiase, and Justine Chew, also Philippe Fouquart, Tomslin Samme-Nlar, and Paul McGrady) set to begin work on 9 Feb.

2021

  • 28 Oct: A Council small team (comprising Thomas Rickert, Mark Datysgeld, Wisdom Donkor, Kristian Ormen, Maxim Alzoba, Sebastien Ducos) to draft potential GNSO Council next steps regarding DNS abuse. 


Card
defaulttrue
idConsensus_Policy
labelON MODIFYING GTLD CONSENSUS POLICIES

ICANN Org Discussion paper on Modifying gTLD Consensus Policies –  TO MONITOR THIS and assess for ALAC input opportunities.

2022

2021


Card
idTRP
labelTransfer Policy Review PDP

Transfer Policy Review Policy Development Process (TPR-PDP)

2021

  • 16 Dec: Council approved a Project Change Request (PCR) to update charter topics considered in Phase 1 of the TPR-PDP by moving the topic of NACK (rejection of transfer request) of an unauthorized transfer to Phase 1a scope from Phase 2.


Card
idIDN
labelInternationalized Domain Names EPDP

Internationalized Domain Names EPDP

2022

  • 20 Jan: Council to send letter to ICANN Board responding to the Board’s 20 Oct letter regarding the IDN Implementation Guidelines v4.0.

2021


Card
idRDA_Scoping
labelRegistration Data Accuracy Scoping Team

Registration Data Accuracy (RDA) Scoping Team

18 Nov 2021

  • Council received notice that the ICANN Board has selected two Board members to serve as liaisons to this Registration Data Accuracy Scoping Team. They are Becky Burr and Harald Alvestrand (alternate).
  • Council has acknowledged the Registration Data Accuracy - Scoping Team (RDA_ST) Project Plan


Card
idSSAD
labelTemp Spec for Registration Data / SSAD ODP

Temporary Specification for gTLD Registration Data / System for Standardized Access/Disclosure Operational Design Phase (SSAD ODP);  See: https://www.icann.org/ssadodp for more official info

2022

  • Mar: Council Small Team seated (comprising Members: Paul McGrady, Sebastien Ducos, Marc Anderson, Stephanie Perrin, John McElwaine, Olga Cavalli, Thomas Rickert, Laureen Kapin (GAC- shared membership), Chris Lewis-Evans (GAC- shared membership), Alan Greenberg, Sarah Wyld, Steve DelBianco, Becky Burr, Steve Crocker, Philippe Fouquart (GNSO Council Observing) , Tomslin Samme Nlar  (GNSO Council Observing); and Alternates: Gregory DiBiase)
  • 1 Feb: GNSO Council Chair invited GNSO SG/Cs, ALAC, GAC to nominate their EPDP Phase 2 representatives for a Council Small Team led by Sebastien Ducos to analyse the SSAD ODA to develop recommendations on next steps.  On 4 Feb, the ALAC Chair nominated Alan Greenberg (being one of the 2 ALAC EPDP Phase 2 representatives) for this Council Small Team.
  • 27 Jan: Council and ICANN Board Consultation on SSAD ODP
  • 18 Jan: SSAD ODP Project Update Webinar #5
  • 12 Jan: A follow up discussion is held for Council and and GNSO-appointed EPDP Phase 2 members to discuss next steps ahead of Council's meeting with the ICANN Board on 27 January on concerns around financial sustainability of the SSAD (wiki)
  • 5 Jan: A 4 Jan 2022 summary paper was circulated to Council members ahead of a 12 Jan call

2021


Card
idSubPro
labelSubsequent Procedures ODP

Subsequent Procedures Operational Design Phase (SubPro ODP);  See: https://www.icann.org/subpro-odp for more official info.

2022

2021

  • 20 Dec;  ICANN org announces that ICANN GDS has informed ICANN Board that it is beginning this ODP in January 2022.
  • 16 Dec:  Council mainly considered the process for SubPro ODP interactions between the GNSO ODP Liaison and the ICANN Org's SubPro ODP Team - Councillors are meant to take suggested responses of the GSNO ODP Liaison to SubPro ODP Team's preliminary questions (Question Set #1) back to their respective SG/C for feedback to enable finalization and timeous relay of agreed responses to the SubPro ODP Team. ICANN Org has a public archive of engagement on the topic.
  • 1 Dec: GNSO SubPro ODP Liaison update #3 - First call with GDS (ICANN's SubPro ODP Team)
  • 22 Nov: GNSO SubPro ODP Liaison update #2. ICANN Org is still in internal project organization mode although GDD has posed a first set of questions to the GNSO ODP Liaison, Jeff Neuman. Formal kick-off of the ODP only expected at end of Nov 2021, thereafter proceeds for an approximate 10 months.
  • 17 Nov: GNSO SubPro ODP Liaison update #1


...

Deck of Cards
idJul2022


Card
idShow_Jul2022
labelSHOW ME

GNSO Council Meeting #7 of 2022 held on 20 Jul 2022 

  • Agenda
  • Matters of Interest
  • Meeting Records


Card
idAgenda_Jul2022
labelAGENDA

GNSO Council Meeting #7 of 2022 held on 20 Jul 2022

Full Agenda  Agenda  |  Motions  

For notes on highlighted items click on MATTERS OF INTEREST tab above

Motions 

  • Item 1: Administrative Matters
  • Item 2: Opening Remarks / Review of Projects & Action List
  • Item 3: Consent Agenda
  • Item 4: COUNCIL VOTE - Initiation of the GNSO Guidance Process on Applicant Support
  • Item 5: COUNCIL DISCUSSION - Policy Status Report for the Expired Domain Deletion Policy and the Expired Registration Recovery Policy - Next Steps
  • Item 6: COUNCIL DISCUSSION - PDP Improvements Tracker - Review of Format 
  • Item 7: COUNCIL DISCUSSION - Council Commitments Document 
  • Item 8: ANY OTHER BUSINESS

For notes on highlighted items click on MATTERS OF INTEREST tab above


Card
idMOI_Jul2022
labelMATTERS OF INTEREST

Matters of interest to ALAC/At-Large

  • Item 1: Administrative Matters

    • Minutes of the GNSO Council meeting on 19 May 2022 were posted on 03 June 2022.

    • Minutes of the GNSO Council meeting on 15 June 2022 were posted on 01 July 2022

  • Item 3: Consent Agenda 
    • Confirmation of the Recommendations Report to the ICANN Board regarding adoption of recommendations 1-5 contained in the Final Report from the EPDP on Specific Curative Rights Protections for IGOs. 
      • The resolved portion of the motion to be voted on reads, "The GNSO Council approves the Recommendations Report and instructs the GNSO Secretariat to transmit the report to the ICANN Board and communicate the outcomes from the GNSO Council’s decisions as appropriate."
  • Item 4: COUNCIL VOTE - Initiation of the GNSO Guidance Process on Applicant Support
    • In the course of Council's consideration of the ICANN Org SubPro ODP Team's work in February 2022 - and although specifically about the topic of Applicant Support at that point - broader procedural concerns arose about whether the level of substantive work receommended by SubPro to be conducted by an IRT, would be beyond the commonly understood scope of the IRT.
    • Council agreed to explore finding avenues to complete that level of substantive work in advance of the expected IRT that would be convened upon ICANN Board adoption of the SubPro Outputs. The potential model to address this work is the GNSO Guidance Process. ICANN org staff worked with Jeff Neuman and Council leadership to prepare a draft GGP Initiation request, which was shared on Council list on 4 May 2022.
    • The potential GGP was discussed further during the Council’s June meeting, with general agreement it should be limited to the singular topic of Applicant Support. There was however discussion that additional topics should be able to be added to the existing GGP, at the discretion of the Council.
    • The updated GGP, with Applicant Support as the only topic, was shared with the Council on [date].
    • Council to discuss and vote on the initiation of the GNSO Guidance Process on Applicant Support, which to be carried requires a Voting threshold of an affirmative vote of more than one-third (1/3) of each House or more than two-thirds (2/3) of one House)
      • The resolved portion of the motion to be voted on reads, 

1. The GNSO Council approves the GNSO Guidance Process Initiation Request and initiates the GGP.
2. The GNSO Council directs staff to:
a. communicate the results of this motion to the GNSO SG/Cs as well as ICANN SO/ACs and invite them to identify Members for the Steering Group following the Steering Group composition described in the initiation request;
b. communicate the results of this motion to the ICANN Org GDS Team and invite them to identify at least one (1) staff liaison for the Steering Group; and
c. launch a call for expressions of interest seeking interested candidates to Chair the Steering Group.

Action by ALAC Liaison

    •  To monitor initiation of the request for the GNSO Guidance Process (GGP), and to ensure role for ALAC/At-Large in resulting process.

    See TAB under 'POST GNSO COUNCIL MEETING DEVELOPMENTS' section for easier tracking. 

  • Item 5: COUNCIL DISCUSSION - Policy Status Report for the Expired Domain Deletion Policy and the Expired Registration Recovery Policy - Next Steps
    • During the Council’s meeting in November 2020, it voted to approve a deferral for the request of a Policy Status Report (PSR) for the Expired Domain Deletion Policy (EDDP) and the Expired Registration Recovery Policy (ERRP). The EDDP defines a uniform delete practice that registrars must follow at the time of domain name expiry, as well as specific requirements for registrar handling of expired names that are subject to a UDRP dispute. The ERRP sets minimum renewal notification requirements for registrars before and after domain names expire, as well as certain requirements for renewal and restoration of expired domain names. In taking this action, the Council was careful to note that it recognized the importance of the PSR for these two expiration related Consensus Policies, but did not see the PSR as urgent at that time. After approximately 1.5 years, the potential PSR has again risen to the 0-1 month range of the Action Decision Radar.
    • Council must consider again whether a PSR is necessary and if it is timely to request a PSR from ICANN org’s Global Domains and Strategy (GDS) function. Council could consider interim steps prior to determining whether a full PSR is needed, such as reviewing ICANN Compliance data and/or requesting an update on expiration related complaints from ICANN Compliance, to help determine if there are known issues with either of the two policies.
    • Council to discuss appropriate next steps for the potential PSR for the EDDP and ERRP.

Action by ALAC Liaison

    •  To review for direct relevant to end-user (registrants), and to inform if need arises for a role for ALAC/At-Large in any resulting process 

  • Item 6: COUNCIL DISCUSSION - PDP Improvements Tracker - Review of Format
    • During the ICANN73 wrap up, the Council discussed a number of parallel conversations that have emerged since implementing PDP 3.0, identifying other aspects of the PDP where improvements could be considered. Council discussed the discussion paper and agreed that to better understand the concept, it would be helpful to have an example of what the tracker may look like. A draft of the PDP Improvements Tracker was prepared and discussed during the Council’s June meeting. While substantive review of the items in the tracker will take place in the near future, this agenda item is to help ensure that the format of the tracker meets the needs of the Council; a series of six questions are included in the PDP Improvements Tracker for consideration by the Council, to help make that determination.
    • Council will continue its review of the proposed format of the GNSO PDP Improvements tracker

Action by ALAC Liaison

    •  To review for direct relevant to end-user (registrants), and to inform if need arises for a role for ALAC/At-Large in any resulting process 
  • Item 8: ANY OTHER BUSINESS
    • 8.1 – Last call for input on the Council’s response to SubPro Question Set #4

Action by ALAC Liaison

    •  Participated in the Council Small Team on SubPro Questions Set #4

See TAB under 'POST GNSO COUNCIL MEETING DEVELOPMENTS' section for easier tracking.

    • 8.2 – ICANN75 Planning

Action by ALAC Liaison

    •  To establish if there is a need for an ALAC-GNSO Bilateral Meeting at ICANN75 


Card
idMeet_Jul2022temp
labelMEETING DETAILS

Meeting Details; non-Council members are welcome to observe the

Card
idMeet_Jul2022temp
labelMEETING DETAILS

Meeting Details; non-Council members are welcome to observe the meeting

GNSO Council meeting held at 05:00 UTC UTC https://tinyurl.com/mpz43kc2. 

(Wednesday) 22:00 Los Angeles; 01:00 Washington DC; 06:00 London; 07:00 Paris; 08:00 Moscow; 15:00 Melbourne 

GNSO Council Meeting Remote Participation: https://icann.zoom.us/j/92399217049?pwd=WU1GZmlaOTh6NzJ1NndkRVF0MnJEUT09 



Anchor
A-22-06
A-22-06
GNSO COUNCIL MEETING #6 (AT ICANN 74, JUN 2022)        (go up to Directory) 

...