Versions Compared

Key

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

Justine Chew is currently serving as the ALAC Liaison to the GNSO Council. Selected by the ALAC in October 2021, she was seated on the Council on 27 October 2021, just prior to the ICANN72 AGM which took place on 28 October 2021.

...

Deck of Cards
idUpdates


Card
defaulttrue
idDevelopments_2022
labelSHOW ME

Developments in 2021-2022 on:


Card
idAddSubPro
labelADDITIONAL WORK ON SUBSEQUENT PROCEDURES

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

2022

  • 25 Aug: Council resolved unanimously to initiate the GGP using a "Representative + Observers" WG model with each SG/C/AC to be invited to nominate a representative. The GGP will start with Applicant Support first, with the possibility of adding further topics down the line.
  • 12 Aug: Council is expected to consider and vote on a new version of the GGP on Application Support. In brief, this version of the GPP on Application Support proposes as follows: 
    • A (smaller) Working Group employing a “Representative + Observers” model, to conduct and conclude its work, and oversight activities, in an efficient/effective manner while allowing for inclusive community participation. GNSO Council retains oversight, as with any GNSO WG.
    • Each AC/SG, ASO and ccNSO may appoint 1 Member to the WG, who are expected to represent the view of their appointing organization and may be called on to provide the official position of their appointing
      organization and will be responsible for participating in GGP consensus calls. Appointing organizations may replace their Member(s) at their discretion.
    • Members must either possess a level of expertise in previous deliberations and/or knowledge that may have been lacking during those initial deliberations.
    • The WG has the flexibility/discretion to rely on Subject Matter Experts (SMEs) in specific fields to aid in deliberations for certain tasks, but these SMEs will not be considered as Members of the WG.
    • The GNSO Liaison to the ODP may serve as an non-voting member of the WG to advise on issues discussed within the SubPro PDP.
  • 21 Jul: Council considered a late proposed amendment to the substantive motion to establish a GGP to work just on Applicant Support. The amendment received some support and it was decided to defer this issue to Council's August 2022 meeting to allow opportunity to incorporate supported element(s) into the substantive motion for Council's consideration.
  • 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. This GGP is the proposed mechanism to address SubPro Implementation Guidance 17.5, which suggests the creation of a dedicated IRT and it be charged “with developing implementation elements of the Applicant Support Program. In conducting its work, the Implementation Review Team should revisit the 2011 Final Report of the Joint Applicant Support Working Group as well as the 2012 implementation of the Applicant Support program.” This dedicated IRT was to be charged with making substantive decisions on outreach activities and allocation of scarce resources (e.g., when there are more qualified applicants than available funds), among other activities.
  • 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

  • 2 Sep: (CG): Council leadership initiates selection by SGs for their representatives for the dialogue.
  • 9 Aug: (CG): ALAC receives invitation to formally join GNSO and GAC as parties to the Dialogue on Closed Generics.
  • 21 Jul: (CG): Still awaiting convening of the Dialogue, which is inter alia subject to the identification/nomination of representatives from the GNSO and GAC.
  • 29 Jun: (CG): Council has sent a letter to the Board and the GAC relaying its recommendations on the GAC-GNSO Dialogue; cc-ed to ALAC Chair, appending the Jun 2022 report of the Council Small Team on Closed Generics.
  • 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
idSubPro
labelSubsequent Procedures ODP

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

2022

   *14 Oct: SubPro ODP Team releasesSubPro ODP Community Status Update #4 (last of four planned updates). The output of this ODP (i.e. the ODA - Operational Design Assessment)  is now expected to be completed on 9 Nov and delivered to the ICANN Board on 12 Dec.

   *15 Aug: SubPro ODP Team releases SubPro ODP Community Status Update #3 (the 3rd of four planned updates) which refers to Assumptions Subsequent Procedures ODP v.5. The last update is scheduled for 15 Oct.

   *25 May: SubPro ODP Team releases Assumptions Subsequent Procedures ODP v.4

   *16 May: SubPro ODP Team releases SubPro ODP Community Status Update #2, the 2nd of four planned updates. The next update is scheduled for 15 Aug.

   *29 Apr: SubPro ODP Team releases Assumptions Subsequent Procedures ODP v.3  

   *28 Mar: SubPro ODP Team releases SubPro ODP Community Status Update #1, the 1st of four planned updates. The next update is scheduled for 16 May.

   *23 Mar: SubPro ODP Team releases Initial & Overarching Assumptions Subsequent Procedures ODP v.2

   *28 Feb: SubPro ODP Team releases Initial Assumption Subsequent Procedures ODP v.1

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 #2ICANN 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.
  • 18 Nov: GNSO SubPro ODP Liaison update - Relay of Question set #1
    • Question set #1 sought clarity on (i) Applications Assessed in Rounds, (ii) RVCs & PICs, specifically on DNS Abuse Mitigation (iii) Applicant Reviews, and (iv) Auctions.
  • 16 Nov: GNSO SubPro ODP Liaison update #1


Card
defaulttrue
idDNS_Abuse
labelON DNS ABUSE

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

2022

  • 20 10 Oct:  Small Team's draft report and recommendations were submitted to be considered by GNSO Council for consideration.
  • 21 Sep:  Small Team's draft report and recommendations were presented and discussed at ALAC-GNSO meeting at ICANN75.

  *17 Aug: Justine's 3rd Presentation to CPWG on Small Team deliberations on comments received from SGs/Cs/DNSAI; + discussion on draft report

  • 4 Aug: Small Team completes deliberation on comments received from outreach exercise and moves onto producing their report

  *20 Jul: Justine's 2nd Presentation to CPWG on Small Team deliberations on comments received from ALAC, GAC, SSAC

  • 16 Jun: Small Team conducts meeting at ICANN 74
  • 2 Jun: Small Team begins review of responses from Contractual Compliance. 

  *25 May: Justine's 1st Presentation to CPWG on 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

2022

  • 10 Oct: The Scoping Team has completed Assignment #1 (enforcement and reporting) and Assignment #2 (measurement of accuracy) and submitted its write up to the Council on 5 September 2022. In the write up, the group is suggesting moving forward with two proposals that would not require access to registration data, namely a registrar survey (recommendation #1) and a possible registrar audit (recommendation #2) that may help further inform the team’s work on assignment #3 (effectiveness) and #4 (impact & improvements), while it awaits the outcome of the outreach to the European Data Protection Board (EDPB) by ICANN org in relation to proposals that would require access to registration data (recommendation #3). GNSO Council is seeking a new Chair for the Scoping Team.
  • 10 May: The RDA Scoping Team submitted a Project Change Request (PCR) to Council. 

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


...

Deck of Cards
idOct2022


Card
idShow_Oct2022
labelSHOW ME

GNSO Council Meeting #10 of 2022 held on 20 Oct 2022 


Card
idAgenda_Oct2022
labelAGENDA

GNSO Council Meeting #10 of 2022 held on 20 Oct 2022

Full Agenda  |  Motions 

  • Item 1: Administrative Matters
  • Item 2: Opening Remarks / Review of Projects & Action List
  • Item 3: Consent Agenda
  • Item 4: COUNCIL DISCUSSION - Whois Disclosure System Next Steps
  • Item 5: COUNCIL DISCUSSION - Registration Data Accuracy Scoping Team - Assignments #1 (Enforcement and Reporting) and #2 (Measurement of Accuracy) Write Up
  • Item 6. COUNCIL DISCUSSION - Discussion of GAC’s request for additional members in Applicant Support GGP Working Group
  • Item 7: COUNCIL DISCUSSION - DNS Abuse Small Team Report 
  • Item 8: COUNCIL UPDATE - Expedited Policy Development Process (EPDP) on Internationalized Domain Names (IDNs)
  • Item 9: COUNCIL DISCUSSION - SPS planning
  • Item 10: ANY OTHER BUSINESS 

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


Card
idMOI_Oct2022
labelMATTERS OF INTEREST

Matters of interest to ALAC/At-Large

  • Item 1: Administrative Matters
    • Minutes of the GNSO Council meeting on 25 August 2022 were posted on 07 September 2022.
    • Minutes of the GNSO Council meeting on 21 September 2022 part 1 and part 2 were posted on 15 October 2022.
  • Item 3: Consent Agenda
    • Approval of the updated standard term for the GNSO liaison to the Governmental Advisory Committee (GAC).

    • Reappointment of Jeffrey Neuman to serve as the GNSO liaison to the GAC for a two-year term ending AGM 2024.

    • Confirmation of Greg DiBiase, GNSO Council Vice-Chair as the GNSO representative to the Empowered Community Administration.

    • Confirmation of Mike Silber to serve as the Chair of the GNSO Guidance Process (GGP) on Applicant Support.

  • Item 4: COUNCIL DISCUSSION - Whois Disclosure System Next Steps
    • The proposed design of the Whois Disclosure System was published prior to ICANN75 and ICANN org provided a presentation of the system design to the EPDP Phase 2 small team during ICANN75. Subsequently, the small team and Council held initial discussions amongst themselves, as well as with the Board during their joint session on Tuesday. The Council discussed during its meeting on Wednesday and the small team met informally on Thursday of ICANN75.
  • Item 5: COUNCIL DISCUSSION - Registration Data Accuracy Scoping Team - Assignments #1 (Enforcement and Reporting) and #2 (Measurement of Accuracy) Write Up
    • The RDA Scoping Team submitted a Project Change Request (PCR)  to  to Council on 10 May 2022. The Scoping Team has since completed Assignment #1 (enforcement and reporting) and Assignment #2 (measurement of accuracy) and submitted its write up to the Council on 5 September 2022. In the write up, the group is suggesting moving forward with two proposals that would not require access to registration data, namely a registrar survey (recommendation #1) and a possible registrar audit (recommendation #2) that may help further inform the team’s work on assignment #3 (effectiveness) and #4 (impact & improvements), while it awaits the outcome of the outreach to the European Data Protection Board (EDPB) by ICANN org in relation to proposals that would require access to registration data (recommendation #3).
    • As has been communicated previously, Michael Palage will be confirming his resignation as Chair of this group to the Council. The Council will need to consider the proper timing for identifying a new Chair for this effort.
    • Council will discuss how to proceed.
  • Item 6. COUNCIL DISCUSSION - Discussion of GAC’s request for additional members in Applicant Support GGP Working Group
    • On 25 August 2022, the GNSO Council voted to initiate a GNSO Guidance Process (GGP) on Applicant Support. Shortly thereafter, GNSO support staff sent messages to the SO/AC/SG/Cs, inviting them to identify Members for the Working Group, following the Working Group composition described in the initiation request.

    • In the GAC’s ICANN75 Kuala Lumpur Communique, the GAC communicated that its desire for the Council to, “allow broader participation from interested GAC participants, as well as other members of the community, beyond the single member per Advisory Committee presently envisioned by the call for volunteers communicated to the GAC.” The GAC also sent correspondence to the GNSO Council, requesting that membership be expanded from a single member to two (2) members and two (2) alternates from the GAC.

    • Council has noted that it has intentionally kept the membership narrow in order to better ensure an efficient and effective outcome. In that regard, the Council has noted that beyond the Working Group membership, external subject matter expertise can be pursued.

    • Council will discuss the GAC’s request and seek to agree on the appropriate outcome.

  • Item 7: COUNCIL DISCUSSION - DNS Abuse Small Team Report 
    • At ICANN72, the GNSO Council agreed to establish a small team to consider and recommend next steps for the Council related to DNS abuse, if any. An assignment form was drafted and the team held its first meeting 9 February 2022. The team performed outreach to interested community groups (ALAC, GAC, SSAC, the DNS Abuse Institute, SG/Cs) to better understand what DNS abuse related issues need to be addressed specifically via gTLD policy development.
    • The small team carefully considered all input received and has reached agreement on a set of 4 recommendations, by thinking of DNS abuse as taking place in phases (e.g., malicious domain registration/domain being compromised, DNS abuse being reported, action being taken by a well-positioned party). These phases helped the small team to better understand which elements are best addressed via policy development versus another mechanism. To that end, the small team has concluded that improvements in DNS abuse mitigation can be sought via three buckets: through education / communication / outreach, through contractual negotiations, and/or policy development.

    • The small team delivered its report to Council on 10 October 2022. Council will receive a briefing on the report and consider next steps.

  • Item 8: COUNCIL UPDATE - Expedited Policy Development Process (EPDP) on Internationalized Domain Names (IDNs)
    • The EPDP Team has been meeting weekly and making progress against its charter, but the complexity of the subject matter and the charter questions, as well as the implications on the New gTLD Program processes and other ICANN policies and procedures (and thus, the need to adequately understand all of these elements) has challenged agreed upon timelines in the work plan. The EPDP Team is anticipating submitting a Project Change Request (PCR) in November, but the Chair and the EPDP believes that it is important for the Council to understand the need for a project plan update, what is changing, and the implications of those changes, prior to being asked to make a decision on the PCR.
    • Council will be provided with an update on the EPDP on IDNs and an overview of the expected PCR.


Card
idMeet_Oct2022temp
labelMEETING DETAILS

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

GNSO Council meeting on Thursday, 20 October 2022 at 20:00 UTC: https://tinyurl.com/4yanvjs5 

13:00 Los Angeles; 16:00 Washington DC; 21:00 London; 22:00 Paris; 23:00 Moscow; (Friday) 07:00 Melbourne 

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


Card
idMeet_Oct2022
labelMEETING RECORD

Records of 20 Oct 2022 Meeting

  • Audio Recording
  • Zoom Recording (includes chat and visual and rough transcript. To access the rough transcript, select the Audio Transcript tab)
  • Transcript
  • Minutes
  • Special Summary Report


Card
idSumRep_Oct2022
labelSPECIAL REPORT

Special Summary Report of 20 Oct 2022 Meeting to ALT-PLUS

  • Pending


...