Thanks Greg.  This is helpful and I agree—we should follow up on our letter to the board and ask for a conversation.  Perhaps one in person at the ICANN meeting would make the most sense. 

 

Damon

 

J. Damon Ashcraft

office: 602.382.6389 | mobile: 602.510.1640

dashcraft@swlaw.com

Snell & Wilmer

swlaw.com | disclaimer

 

From: council <council-bounces@gnso.icann.org> On Behalf Of DiBiase, Gregory via council
Sent: Thursday, February 1, 2024 9:46 AM
To: COUNCIL@GNSO.ICANN.ORG
Subject: [council] Status Update on Council Requests

 

[EXTERNAL] council-bounces@gnso.icann.org

 


Dear Councilors,

 

In an effort to keep track of Council’s requests and letters sent to ICANN Org and Board (and the responses we’ve received), Council Leadership plans to periodically send a summary of outstanding items (see below). Some of these items will be on the agenda for February’s meeting, but we thought it might be useful to see them in a single place. Please bring concerns or items we’ve missed to February’s Council meeting for discussion.

 

Council Requests:

 

Council Request (January 2024 GNSO Meeting): Timeline and plan for restarting the PPSAI IRT

ICANN Response: Update and timeline will be provided at ICANN 79

Proposed Next Steps: Send reminder to ICANN Staff that Council is expecting a detailed briefing and timeline on this topic at ICANN 79

 

Council Request (October 2023 GNSO Meeting): Timeline and plan for releasing reserved IGO acronyms

ICANN Response: Work is underway, but no clear timeline or workplan provided to date

Proposed Next Steps: Press ICANN Staff for a substantive update and timeline at ICANN 79

 

Council Request: (Multiple Council Meetings in 2023): Timeline for completion of DPA between ICANN and Contracted Parties.

ICANN Response: Work in progress; no clear timeline.

Proposed Next Steps: Press ICANN Staff for a substantive update and timeline at ICANN 79. Remind them that Council has work that is impacted by the delay in executing this agreement.

 

Council Letters:

 

Council Letter: Update regarding closed generics (link).

ICANN Response: Letter from Tripti Sinha addressing questions related to closed generics (link).

Proposed Next Steps: Close this work off of Council’s worry list; remove from ADR.

 

Council Letter: Request for continued dialogue re: Board Resolutions 2023.10.26.11 and 2023.10.26.12 (link)

ICANN Response: None.

Proposed Next Steps: Write again to ICANN Board and ask for them to engage in this dialogue.

 

We hope this summary is helpful.

 

Thanks,

Greg