Thanks Noah for your answer.

 

I ‘ve just read in the RIPE policy discussion that there is a similar proposal written by Aftab ;) within the APNIC region: https://www.apnic.net/community/policy/proposals/prop-132

It was mentioned that the text has already been approved by APNIC community in the September meeting and awaiting APNIC EC (Board) approval this month and will be implemented max by January 2020.

 

Hervé

 

De : Noah [mailto:noah@neo.co.tz]
Envoyé : samedi 2 novembre 2019 20:22
À : CLEMENT Herve TGI/OLN
Cc : ac-discuss@aso.icann.org
Objet : Re: [AC-DISCUSS] A new RIPE policy proposal mentions a potential idea of global policy (RPKI ROAs)

 

Hi Herve

Thanks much for sharing this information. I have read through it and I like the proposal already. I would personally vouch for this to go global, so lets see how the proposal plays out in discussions within RIPE.

./noah

neo - network engineering and operations

 

 

On Sat, Nov 2, 2019 at 9:15 PM <herve.clement@orange.com> wrote:

Dear all,

 

Just for your information, there is a new proposal within the RIPE region called "RPKI ROAs for Unallocated and Unassigned RIPE NCC Address Space" aiming to instruct the RIPE NCC to create ROAs with origin AS0 for all unallocated and unassigned address space under its control: https://www.ripe.net/participate/policies/proposals/2019-08.

 

In the “Arguments opposing the proposal” §, the authors note that “A global policy would be preferred, which covers all address space considered unallocated, unassigned, and for special use managed by IANA, and which requests that all the Regional Registries perform the same actions for address space which they manage directly”

 

This proposal is on the beginning of the development process (discussion phase).

I will keep you informed if there are specific news on it.

 

Best regards

 

Hervé

_________________________________________________________________________________________________________________________

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

_________________________________________________________________________________________________________________________

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.