Dear all,

 

Let me first wish to you an excellent and healthy 2023 year.

 

Thanks Gaurav for your valid question.

I cannot thank Martin and Mike via this list anymore for their answers.

 

There are ongoing discussions (within and outside the ASO) to have a balanced Board composition between new members (with fresh and new views) and members with experience, which is also necessary.

Coming back to the ASO AC, we try before each election to conduct the best outreach we can to have a set of “good” candidates (taking into account the global technical internet governance model knowledge – naming and numbering – and thinking about diversity – gender, geography, etc. – ).

I think we have a “not too bad” process we try to improve continually.

 

Let continue that discussion this year 😊

 

Regards,

 

Hervé

 

 

 

Orange Restricted

De : AC-DISCUSS <ac-discuss-bounces@aso.icann.org> De la part de Gaurav Kansal
Envoyé : mardi 3 janvier 2023 08:13
À : silber.mike@gmail.com; hannigan@gmail.com
Cc : ac-discuss@aso.icann.org
Objet : Re: [AC-DISCUSS] Operational Procedures Review

 

Thanks Martin and Mike for the detailed explanation.

Have a Happy New Year to all. 

 

Regards,

Gaurav Kansal

 

 

On 31-Dec-2022, at 22:07, silber.mike@gmail.com wrote:

 

Thanks Martin

 

I am likewise on my way out so let me agree with Martin and add a few thoughts:

 

- most ASO appointments have been of people having “outside and independent views” as they come from the number community (the forgotten “N” in ICANN

 

- as ICANN does no number policy work (just rubber stamping global policies the number community develops) it is unlikely that someone from the number community would have a vested interest in naming policy

 

- having served on two nomcoms and on the ICANN board there is a fine balance required of people who have enough knowledge of ICANN that they don’t spend most or all of their 3 year term just learning the ropes and someone who is too deeply embedded so as to be serving their own or other interests while on the board

 

- the ASO appointees have generally been excellent at striking the balance of knowing enough about ICANN to be immediately valuable and not being involved in naming policy so as to be potentially compromised or conflicted 

 

- the ICANN nomcom is tasked with balancing the board composition. It is not the ASO’s responsibility to do so

 

As such, I recommend the ASO continues its current approach and does not try introduce additional elements or criteria in its selection process.

 

Regards 

 

Mike

 

On Sat, 31 Dec 2022 at 17:48, Martin Hannigan <hannigan@gmail.com> wrote:

 

Today is my last day in term as an elected representative from the ARIN region. Thank you all for yet another memorable and productive term, if not very difficult due to the pandemic. The work simply went on. Kudos to all of us.

 

Regrading the below and concluding you mean our appointments, my opinion is that seats 9 and 10 are to address just what you mention, views. But in these cases views of the RIR community. 

 

Many have assumed it is our duty to put the best qualified forward. This is true. However, that should be the best quality from the RIR community. Not At-Large, GNSO or random. There is a nom-com and if that process is broken it should be fixed. However the RIR’s have a process that is a privelege and should not be squandered. Many have assumed that the ASO AC appointment was an “Easy” way to circumvent the ICANN nom-com. We usually prove that to be incorrect.

 

Good luck everyone and have an excellent holiday and safe New Year!

 

Warm regards,

 

Martin Hannigan

 

 

 

On Fri, Dec 30, 2022 at 11:15 PM Gaurav Kansal <gaurav.kansal@nic.in> wrote:

Hello friends,

 

I need some clarity about our (ASO AC) views on appointment to the ICANN Board. 

Some of the ICANN leaders in the past have stated the need of having outside and independent views in ICANN leadership and mentioned that only limited set of persons have occupied the Board and other leadership position ( ref ICANN_Board page https://icannwiki.org/ICANN_Board).

 

What’s our views on this ?

 

Regards,

Gaurav Kansal

 

On 30-Dec-2022, at 17:50, ac-discuss@aso.icann.org wrote:

 

Hi Hervé.
Thanks for the summary. I think it covers discussions we have had very well.

Wish you and all the group and relatives a happy festivities for the new year.

Best regards,

On 29/12/22 15:39, herve.clement@orange.com wrote:

Dear all,
I hope you’re doing well.
According to the Action Item 221207-1, I’ve tried to gather in a single document all the recommendations developed by the Review Team, sorted by topic (thanks to everyone).
This file can serve as a basis for the early ASO AC 2023 discussions to elaborate an updated operational procedures version.
Have a good end of year.
Best regards
Hervé
Orange Restricted
*De :*AC-DISCUSS <ac-discuss-bounces@aso.icann.org> *De la part de* German Valdez Aviles
*Envoyé :* vendredi 9 décembre 2022 08:28
*À :* ac-discuss@aso.icann.org
*Objet :* [AC-DISCUSS] Minutes: ASO AC 7 December 2022 Teleconference
Dear ASO AC
Here is the minutes and updated open action list of this week teleconference
*Updated Action Item 221025-2:*Esteban L., James K, and Jorge V. to start working on the ASOA AC slide deck for ICANN 76.
*New Action Item 221207-1:*All ASO AC members will have two weeks to review the proposals shared by the Procedures Review Team so that the Team can consolidate a Procedures Review document to work on in early 2023.
*New Action Item 221207-2:*German V. to circulate the proposed 2023 ASO AC meeting schedule to incoming members. Barring any concerns, the schedule will be approved as of 20 December.
*New Action Item 221207-3:*German V. to prepare the schedule for the 2023 NomCom appointment, which needs to be approved in January 2023.
Regards
German
_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
_______________________________________________
AC-DISCUSS mailing list - Workspace for ASO AC operations. Posting is restricted, archive is publicly available.
AC-DISCUSS@aso.icann.org
https://aso.icann.org/mailman/listinfo/ac-discuss


_______________________________________________
AC-DISCUSS mailing list - Workspace for ASO AC operations. Posting is restricted, archive is publicly available.
AC-DISCUSS@aso.icann.org
https://aso.icann.org/mailman/listinfo/ac-discuss

 

 

_______________________________________________
AC-DISCUSS mailing list - Workspace for ASO AC operations. Posting is restricted, archive is publicly available.
AC-DISCUSS@aso.icann.org
https://aso.icann.org/mailman/listinfo/ac-discuss

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.