[CPWG] Ready, Fire, Aim yet again....

[Chokri Ben Romdhane]

Crucial thoughts dear Holly!
Those reflections are also available for UA, IDN and many others ICANN
services
I think that ICANN  should follow the ecosystem evolvement and innovate the
services provided to the differents DNS  actors including end users ,
At-large community could play a key roles in pushing ICANN to innovate
those services since this community have the flexibility to act and don't
have any legals or technicals or Business barrier like GAC or SSAC or any
others Contracted Party!
So it's more an *Innovation* issue than *Governance * , since improving the
governance of deprecated  services will not help.

Friendly regards
Chokri

Le ven. 1 sept. 2023, 05:30, Holly Raiche via CPWG <cpwg at icann.org> a
écrit :

> Folks
>
> As always, I agree with Evan and think working out a process to refine the
> issues the ALAC gets involved in would be a terrific step forward.  (I was
> involved in the first discussion and noted the complete lack of response -
> do I become involved in a second go???)
>
> But now for another issue that I think CPWG should worry about.  Heaven
> help us, talk of a SECOND round!  I recently attended  (and presented in)
> the APrIGF.  On the sidelines, I wound up with a discussion of Ram - who
> was there.  It started with a discussion on new gTLDs - in the context of
> UA.  And the thought in my mind was why are we talking about a second round
> when so  many new gTLDs don’t resolve.  (the nastier question - why is
> ICANN pocketing money for new GTLDs if they don’t work!)  This should be a
> particular issue for IDNs.  IDNs are one thing that IS on the ALAC agenda -
> the firm conviction that we should be making communications on the Internet
> easier for the billions of people whose first language is not English.  And
> - since one of the justifications (true or not) was to provide more gTLDs
> that reflect something of the actual name, why is their usability by the
> public not an issue?  If ICANN is happy to take money for new names, should
> that not come with some kind of assurance/industry commitment that the new
> names will work?
>
> Just a thought
>
> Holly
>
> On Sep 1, 2023, at 5:30 AM, Evan Leibovitch via CPWG <cpwg at icann.org>
> wrote:
>
> Given the short notice and unusual nature of such a travel request, I
> would like to suggest this timeline:
>
>    1. Have a "kickoff" in Hamburg, with me participating virtually. I
>    would prepare for and introduce the topic during the anniversary meeting
>    Jonathan mentioned and we would then start to assemble a working group. My
>    preference would be for a small team, preferably of people with strong
>    written English communications skills who have not participated in other
>    ICANN constituencies
>
>    2. The group would communicate by email list and ad-hoc virtual
>    meetings, reporting progress back to ALAC meetings. If human resources
>    allow, it would be optimal for a group representative to present and take
>    feedback at every RALO at least once.
>
>    3. The working group -- hopefully with me there in person -- would
>    present its work early in the week of ICANN79 meeting, conducting a public
>    workshop for last-minute fine-tuning, with the intention of ALAC
>    endorsement at its closing meeting.
>
>    4. The working group disbands, and proposes that ALAC revisit the
>    issue every five years.
>
> - Evan
>
> _______________________________________________
> CPWG mailing list
> CPWG at icann.org
> https://mm.icann.org/mailman/listinfo/cpwg
>
> _______________________________________________
> By submitting your personal data, you consent to the processing of your
> personal data for purposes of subscribing to this mailing list accordance
> with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and
> the website Terms of Service (https://www.icann.org/privacy/tos). You can
> visit the Mailman link above to change your membership status or
> configuration, including unsubscribing, setting digest-style delivery or
> disabling delivery altogether (e.g., for a vacation), and so on.
>
>
> _______________________________________________
> CPWG mailing list
> CPWG at icann.org
> https://mm.icann.org/mailman/listinfo/cpwg
>
> _______________________________________________
> By submitting your personal data, you consent to the processing of your
> personal data for purposes of subscribing to this mailing list accordance
> with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and
> the website Terms of Service (https://www.icann.org/privacy/tos). You can
> visit the Mailman link above to change your membership status or
> configuration, including unsubscribing, setting digest-style delivery or
> disabling delivery altogether (e.g., for a vacation), and so on.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mm.icann.org/pipermail/cpwg/attachments/20230901/1d1a2101/attachment.html>