[ripe-list] News from ASO AC

Dear all,

Sorry first for not having answered sooner.
The work dedicated to ICP-2 and related exchanges can be read via the public ASO AC mailing list archive: AC-DISCUSS - aso-apps-2.ripe.net<https://aso-apps-2.ripe.net/hyperkitty/list/[email protected]/>
Please find in particular the short report from our working sessions in Montevideo (29-30 January) I sent February 7th.

The ASO AC will have another Face-2-face meeting during ICANN 79<https://meetings.icann.org/en/meetings/icann79/> (4-6 March) and ICP-2 will be the main subject we will work on.
The agenda can be found here: ICANN79 | San Juan: Schedule<https://icann79.sched.com/>

Best regards

Hervé

De : ripe-list <ripe-list-bounces at ripe.net> De la part de Howard, Lee
Envoyé : lundi 29 janvier 2024 16:09
À : Kurt Erik Lindqvist <kurtis at kurtis.pp.se>; constanze buerger <cobuerger at gmail.com>; ripe-list at ripe.net
Objet : Re: [ripe-list] News from ASO AC

I'm not currently on the ASO AC/NRO NC, and I haven't been sitting in on many of their calls, but I note the lengthy ICP-2 discussion from November minutes:
https://aso.icann.org/wp-content/uploads/2023/12/20231101_ASO-AC-Meeting-Minutes-FINAL.pdf

ICP-2 is about the recognition of new RIRs. The current initial prompts are, from those minutes, "1) implementation procedures for the existing ICP-2, 2) strengthening the ICP-2"

With AFRINIC in potentially existential crisis, I can imagine several interesting questions.
If another RIR were to be recognized, how could we inoculate it against the difficulties AFRINIC has had? How could we ensure succession in the case of an RIR failure or collapse?

Seems like useful conversation to me. But first, we'll need a framework for asking questions, receiving input, and incorporating feedback.

Lee Howard


From: ripe-list <ripe-list-bounces at ripe.net<mailto:ripe-list-bounces at ripe.net>> On Behalf Of Kurt Erik Lindqvist
Sent: Monday, January 29, 2024 6:35 AM
To: constanze buerger <cobuerger at gmail.com<mailto:cobuerger at gmail.com>>; ripe-list at ripe.net<mailto:ripe-list at ripe.net>
Subject: Re: [ripe-list] News from ASO AC

You don't often get email from kurtis at kurtis.pp.se<mailto:kurtis at kurtis.pp.se>. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification>
This message is from an EXTERNAL SENDER - be CAUTIOUS, particularly with links and attachments.



Constanze,

Thank you for sharing this. Could you share some insight into what the discussion around ICP-2 is?

Best regards,

Kurtis

Sent from Outlook for iOS<https://aka.ms/o0ukef>

________________________________
From: ripe-list <ripe-list-bounces at ripe.net<mailto:ripe-list-bounces at ripe.net>> on behalf of constanze buerger <cobuerger at gmail.com<mailto:cobuerger at gmail.com>>
Sent: Sunday, January 28, 2024 2:15 PM
To: ripe-list at ripe.net<mailto:ripe-list at ripe.net> <ripe-list at ripe.net<mailto:ripe-list at ripe.net>>
Subject: [ripe-list] News from ASO AC

Dear All,
Hervé, Sander and I are on the way to the f2f Meeting with the ASO AC colleagues in Montevideo. One of our  main topics is, to discuss the Internet Coordination Policy 2 (ICP-2).
Further informations we will communicate after the meeting and please  check also
https://aso.icann.org/aso-ac.
All the best
Constanze
____________________________________________________________________________________________________________
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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </ripe/mail/archives/ripe-list/attachments/20240219/6c7a8766/attachment.html>