A report from your GNSO councilor
Nyama mutondo
nyamamutondo at GMAIL.COM
Wed Apr 2 22:44:17 EEST 2025
Dear Farzaneh,
I trust that you are well.
This is noted and received with many thanks.
What are the requirements for one to be part of the small team being put
together?
Kind regards,
Nyama.
On Tue, Apr 1, 2025, 9:16 AM farzaneh badii <farzaneh.badii at gmail.com>
wrote:
> Hello NCSG
>
> I am one of NCSG GNSO councilors. For those who recently joined us, the
> GNSO council provides oversight and approves policies related to generic
> names.
>
> Here is a brief follow up and actions that we can take following the last
> council meeting.
>
>
>
>
> ------------------------------
>
> NCSG Next Steps Following the 12 March 2025 GNSO Council Meeting and ICANN
> Seattle meeting
>
> ------------------------------
>
> 1. Transfer Policy Review PDP – Human Rights Follow-Up
>
>
> Action:
>
> NCSG will follow up on the integration of the human rights checklist for
> the Transfer Policy Review (TPR) PDP. Although it will be formally
> incorporated into the Latin Diacritics PDP going forward, the Council
> suggested that NCPH members and Roger Carney review it for the TPR PDP.
>
>
> NCSG will:
>
> • Review and provide input on the checklist’s relevance to TPR
> recommendations.
>
>
> ------------------------------
>
> 2. Registration Data Accuracy – Shaping the Small Team
>
>
> Action:
>
> A small team is being formed to synthesize inputs on registration data
> accuracy. NCSG has already emphasized that accuracy measures are not a
> solution to cybercrime and that ICANN’s remit must be respected.
>
>
> We can
>
> • Ensure strong representation in the small team.
>
> • Define the limits of Council’s role, emphasizing privacy, data
> minimization, and proportionality.
>
> • Reinforce that ICANN should not become a tool for law enforcement
> overreach.
>
> ------------------------------
>
> 3. Billing Contact Issue
>
>
> Action:
>
> The Council will vote on whether to accept the IRT determination that
> billing contact data collection was a drafting error in EPDP Phase 1. NCSG
> has clearly stated it does not support a compromise that would weaken
> privacy principles has provided evidence that epdp intended to remove
> billing contact from the registration policy
>
>
> NCSG councilors will vote on the motion in the next meeting. The motion
> that the leaders have prepared is very acceptable.
>
> I will vote yes on the motion.
>
>
> ------------------------------
>
> 4. Urgent Requests & Law Enforcement Authentication
>
>
> Action:
>
> We raised concerns about PSWG unintentionally stepping into policy
> territory as it develops an authentication mechanism for urgent data
> disclosure requests.
>
>
> We can
>
> • Monitor PSWG outputs and ensure any resulting mechanisms are reviewed
> through the IRT.
>
> • Define what constitutes “policy” vs “implementation” in this context,
> and push for transparency.
>
> ------------------------------
>
> 5. Internet Governance Representation
>
>
> Action:
>
> There was discussion about GNSO’s presence in broader Internet governance
> spaces like WSIS+20 and IG in general. We highlighted the importance of
> strong messaging.
>
>
> We can
>
> • Promote clear messaging around the GNSO’s policy work and its
> contribution to a secure, open DNS as well as protecting human rights.
>
> • Emphasize the value of the multistakeholder model in keeping the
> internet globally interoperable.
>
> • Support efforts to prepare a GNSO “impact summary” for broader Internet
> governance forums.
>
> ------------------------------
>
> 6. Continuous Improvement & Readiness Work
>
>
> Action:
>
> Discussions around operational improvement were flagged for potential SCCI
> engagement.
>
>
> NCSG will:
>
> • Participate in or monitor the Standing Committee on Continuous
> Improvement.
>
> • Advocate for inclusion of issues like documentation practices, clarity
> between policy and implementation, and improved accessibility for
> marginalized voices.
>
>
> Thank you Manju!
>
> ------------------------------
>
>
> 7. Shape the Approach to DNS Abuse
>
>
> NCSG can:
>
> • Re-engage the DNS Abuse small team on the council. The goal can be
> starting discussions grounded in human rights impact assessments (HRIAs).
>
> • Promote safeguards for due process, transparency, and proportionality in
> any DNS abuse mitigation discussions.
>
> • Advocate for the development of clear guidelines on how DNS abuse
> measures intersect with freedom of expression and user rights.
>
>
>
>
>
> Farzaneh
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-discuss/attachments/20250402/52e67a5f/attachment.htm>
More information about the Ncsg-discuss
mailing list