A new RIPE policy proposal mentions a potential idea of global policy (RPKI ROAs)
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.
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
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.commailto: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.orgmailto: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.
Hi Herve
Thanks for sharing this as well.
Perhaps we could also consider introducing a similar policy within the AfriNIC community working group.
Noah
*./noah* neo - network engineering and operations
On Sun, Nov 3, 2019 at 12:34 AM herve.clement@orange.com wrote:
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.
As ASO AC members we cannot give any advices on that but of course feel free to discuss this question as an individual within the AfriNIC community ;)
Hervé
De : Noah [mailto:noah@neo.co.tz] Envoyé : samedi 2 novembre 2019 22:44 À : 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 for sharing this as well.
Perhaps we could also consider introducing a similar policy within the AfriNIC community working group. Noah
./noah neo - network engineering and operations
On Sun, Nov 3, 2019 at 12:34 AM <herve.clement@orange.commailto:herve.clement@orange.com> wrote: 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.tzmailto:noah@neo.co.tz] Envoyé : samedi 2 novembre 2019 20:22 À : CLEMENT Herve TGI/OLN Cc : ac-discuss@aso.icann.orgmailto: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.commailto: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.orgmailto: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.
_________________________________________________________________________________________________________________________
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.
Ofcourse .... not specifically as ASO, but I know community members who would pick an interest :-) *./noah* neo - network engineering and operations
On Sun, Nov 3, 2019 at 12:47 AM herve.clement@orange.com wrote:
As ASO AC members we cannot give any advices on that but of course feel free to discuss this question as an individual within the AfriNIC community ;)
Hervé
*De :* Noah [mailto:noah@neo.co.tz] *Envoyé :* samedi 2 novembre 2019 22:44 *À :* 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 for sharing this as well.
Perhaps we could also consider introducing a similar policy within the AfriNIC community working group.
Noah
*./noah*
neo - network engineering and operations
On Sun, Nov 3, 2019 at 12:34 AM herve.clement@orange.com wrote:
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.
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.
Hi Herve, hope it is all fine.
Thanks for bringing this to our attention. I've been following that discussion and is very interesting.
Regarding the comments to make this a global policy I have some doubts.
According to the ASO MoU we have the following as definition of global proposal:
"Global policies are defined within the scope of this agreement as Internet number resource policies that have the agreement of all RIRs according to their policy development processes and ICANN, and require specific actions or outcomes on the part of IANA or any other external ICANN-related body in order to be implemented."
if the idea is to instruct IANA to generate ROAs for unallocated resources under its administration, that would apply.
But if the question is to RIRs generate those ROAs, then I don't think a global proposal would fit, as there would be no instruction to IANA.
I guess, and correct me if I am wrong, the last scenario could be seen as global *coordinated* proposal if similar text is presented in all RIR but in this case there would be no need to have them with the exact same text and neither all RIRs with it.
Regards, Ricardo
Em 02/11/2019 15:15, herve.clement@orange.com escreveu:
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
Thank you for highlighting that point, Ricardo. And I agree with your assessment, especially the point that the scope of the current text under discussion does not qualify the proposal to be a global policy proposal as defined.
And as a data point, there was also discussion at the ARIN 44 meeting last week on this topic.
Louie
On Sat, Nov 2, 2019 at 6:52 PM Ricardo Patara patara@registro.br wrote:
Hi Herve, hope it is all fine.
Thanks for bringing this to our attention. I've been following that discussion and is very interesting.
Regarding the comments to make this a global policy I have some doubts.
According to the ASO MoU we have the following as definition of global proposal:
"Global policies are defined within the scope of this agreement as Internet number resource policies that have the agreement of all RIRs according to their policy development processes and ICANN, and require specific actions or outcomes on the part of IANA or any other external ICANN-related body in order to be implemented."
if the idea is to instruct IANA to generate ROAs for unallocated resources under its administration, that would apply.
But if the question is to RIRs generate those ROAs, then I don't think a global proposal would fit, as there would be no instruction to IANA.
I guess, and correct me if I am wrong, the last scenario could be seen as global *coordinated* proposal if similar text is presented in all RIR but in this case there would be no need to have them with the exact same text and neither all RIRs with it.
Regards, Ricardo
Em 02/11/2019 15:15, herve.clement@orange.com escreveu:
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
-- Ricardo Patara
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
An expanded scope while enforcing downstream yes.....
@Louis is the discussion at a proposal level and is the problem statement similar.
Noah
On Sun, 3 Nov 2019, 05:03 Louie Lee, louie@louie.net wrote:
Thank you for highlighting that point, Ricardo. And I agree with your assessment, especially the point that the scope of the current text under discussion does not qualify the proposal to be a global policy proposal as defined.
And as a data point, there was also discussion at the ARIN 44 meeting last week on this topic.
Louie
On Sat, Nov 2, 2019 at 6:52 PM Ricardo Patara patara@registro.br wrote:
Hi Herve, hope it is all fine.
Thanks for bringing this to our attention. I've been following that discussion and is very interesting.
Regarding the comments to make this a global policy I have some doubts.
According to the ASO MoU we have the following as definition of global proposal:
"Global policies are defined within the scope of this agreement as Internet number resource policies that have the agreement of all RIRs according to their policy development processes and ICANN, and require specific actions or outcomes on the part of IANA or any other external ICANN-related body in order to be implemented."
if the idea is to instruct IANA to generate ROAs for unallocated resources under its administration, that would apply.
But if the question is to RIRs generate those ROAs, then I don't think a global proposal would fit, as there would be no instruction to IANA.
I guess, and correct me if I am wrong, the last scenario could be seen as global *coordinated* proposal if similar text is presented in all RIR but in this case there would be no need to have them with the exact same text and neither all RIRs with it.
Regards, Ricardo
Em 02/11/2019 15:15, herve.clement@orange.com escreveu:
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
-- Ricardo Patara
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
Hello Herve and all Thanks for bringing this to notice. I agree that there is need for unallocated addresses under RPKI etc. For this to be fully effective all RIRs need to implement this. @Ricardo Yes I see your point in ASO definition. However if there is strong use case and need, we should discuss to find a way for implementation by all RIRs. With regards Brajesh
Sent from my iPhone
On 02-Nov-2019, at 8:52 PM, Ricardo Patara patara@registro.br wrote:
Hi Herve, hope it is all fine.
Thanks for bringing this to our attention. I've been following that discussion and is very interesting.
Regarding the comments to make this a global policy I have some doubts.
According to the ASO MoU we have the following as definition of global proposal:
"Global policies are defined within the scope of this agreement as Internet number resource policies that have the agreement of all RIRs according to their policy development processes and ICANN, and require specific actions or outcomes on the part of IANA or any other external ICANN-related body in order to be implemented."
if the idea is to instruct IANA to generate ROAs for unallocated resources under its administration, that would apply.
But if the question is to RIRs generate those ROAs, then I don't think a global proposal would fit, as there would be no instruction to IANA.
I guess, and correct me if I am wrong, the last scenario could be seen as global *coordinated* proposal if similar text is presented in all RIR but in this case there would be no need to have them with the exact same text and neither all RIRs with it.
Regards, Ricardo
Em 02/11/2019 15:15, herve.clement@orange.com escreveu:
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
-- Ricardo Patara
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
Hi all,
Can I comment that a policy that requires a single RIR to do something, and is implementable by that RIR, is by definition NOT a global policy.
The APNIC policy is being implemented by APNIC and will result in the publication of 1 or more AS0 ROAs which include address blocks which we administer, and which are unallocated.
APNIC can implement this entirely on our own and it is useful regardless of whether other RIRs do something similar along the same lines. And other RIRs can certainly do the same, according to their own processes, and hopefully also according to the RFC. :-)
So again, not global policy.
Thanks,
Paul.
________________________________________________________________________ Paul Wilson, Director-General, APNIC dg@apnic.net http://www.apnic.net @apnicdg
On 2 Nov 2019, at 20:52, Ricardo Patara wrote:
Hi Herve, hope it is all fine.
Thanks for bringing this to our attention. I've been following that discussion and is very interesting.
Regarding the comments to make this a global policy I have some doubts.
According to the ASO MoU we have the following as definition of global proposal:
"Global policies are defined within the scope of this agreement as Internet number resource policies that have the agreement of all RIRs according to their policy development processes and ICANN, and require specific actions or outcomes on the part of IANA or any other external ICANN-related body in order to be implemented."
if the idea is to instruct IANA to generate ROAs for unallocated resources under its administration, that would apply.
But if the question is to RIRs generate those ROAs, then I don't think a global proposal would fit, as there would be no instruction to IANA.
I guess, and correct me if I am wrong, the last scenario could be seen as global *coordinated* proposal if similar text is presented in all RIR but in this case there would be no need to have them with the exact same text and neither all RIRs with it.
Regards, Ricardo
Em 02/11/2019 15:15, herve.clement@orange.com escreveu:
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
-- Ricardo Patara
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
Hi all
+1 Paul.
Even when the five RIR approve a similar police, it will continue to be a regional policy, because the scope of the operation requested is at RIR level.
Regards, Jorge
El 11/3/19 3:35 p. m., "Paul Wilson" <ac-discuss-bounces@aso.icann.org en nombre de pwilson@apnic.net> escribió:
Hi all,
Can I comment that a policy that requires a single RIR to do something, and is implementable by that RIR, is by definition NOT a global policy.
The APNIC policy is being implemented by APNIC and will result in the publication of 1 or more AS0 ROAs which include address blocks which we administer, and which are unallocated.
APNIC can implement this entirely on our own and it is useful regardless of whether other RIRs do something similar along the same lines. And other RIRs can certainly do the same, according to their own processes, and hopefully also according to the RFC. :-)
So again, not global policy.
Thanks,
Paul.
________________________________________________________________________ Paul Wilson, Director-General, APNIC dg@apnic.net http://www.apnic.net @apnicdg
On 2 Nov 2019, at 20:52, Ricardo Patara wrote:
> Hi Herve, hope it is all fine. > > Thanks for bringing this to our attention. > I've been following that discussion and is very interesting. > > Regarding the comments to make this a global policy I have some > doubts. > > According to the ASO MoU we have the following as definition of global > proposal: > > "Global policies are defined within the scope of this agreement as > Internet number resource policies that have the agreement of all RIRs > according to their policy development processes and ICANN, and require > specific actions or outcomes on the part of IANA or any other external > ICANN-related body in order to be implemented." > > if the idea is to instruct IANA to generate ROAs for unallocated > resources under its administration, that would apply. > > But if the question is to RIRs generate those ROAs, then I don't think > a > global proposal would fit, as there would be no instruction to IANA. > > I guess, and correct me if I am wrong, the last scenario could be seen > as global *coordinated* proposal if similar text is presented in all > RIR > but in this case there would be no need to have them with the exact > same > text and neither all RIRs with it. > > Regards, > Ricardo > > > Em 02/11/2019 15:15, herve.clement@orange.com escreveu: >> 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 >> > > -- > Ricardo Patara > > _______________________________________________ > 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
Hi Folks,
And reading through RFC6491, I noted that it mandated IANA [1] to consider implementing AS0 for reserved and unallocated, I am not sure if this is the case and if it's being done by AINA so to speak, and I haven't searched to ascertain that they do.... and while assuming IANA is not doing it, wouldn't a global policy suffice?
*./noah* neo - network engineering and operations
[1] Section 11. IANA Considerations. This document directs IANA to issue, or refrain from issuing, the specific RPKI objects described here for the current set of reserved, unallocated, and special registry Internet Number Resources. Further, IANA MUST notify all other INR registries that RPKI objects have been issued for the Internet Number Resources described in this document to avoid the potential for issuance of duplicate objects that might confuse relying parties.
On Mon, Nov 4, 2019 at 12:50 AM Jorge Villa villa@reduniv.edu.cu wrote:
Hi all
+1 Paul.
Even when the five RIR approve a similar police, it will continue to be a regional policy, because the scope of the operation requested is at RIR level.
Regards, Jorge
El 11/3/19 3:35 p. m., "Paul Wilson" <ac-discuss-bounces@aso.icann.org en nombre de pwilson@apnic.net> escribió:
Hi all, Can I comment that a policy that requires a single RIR to dosomething, and is implementable by that RIR, is by definition NOT a global policy.
The APNIC policy is being implemented by APNIC and will result in the publication of 1 or more AS0 ROAs which include address blocks whichwe administer, and which are unallocated.
APNIC can implement this entirely on our own and it is usefulregardless of whether other RIRs do something similar along the same lines. And other RIRs can certainly do the same, according to their own processes, and hopefully also according to the RFC. :-)
So again, not global policy. Thanks, Paul.
Paul Wilson, Director-General, APNICdg@apnic.net http://www.apnic.net @apnicdg
On 2 Nov 2019, at 20:52, Ricardo Patara wrote: > Hi Herve, hope it is all fine. > > Thanks for bringing this to our attention. > I've been following that discussion and is very interesting. > > Regarding the comments to make this a global policy I have some > doubts. > > According to the ASO MoU we have the following as definition ofglobal > proposal: > > "Global policies are defined within the scope of this agreement as > Internet number resource policies that have the agreement of all RIRs > according to their policy development processes and ICANN, and require > specific actions or outcomes on the part of IANA or any other external > ICANN-related body in order to be implemented." > > if the idea is to instruct IANA to generate ROAs for unallocated > resources under its administration, that would apply. > > But if the question is to RIRs generate those ROAs, then I don't think > a > global proposal would fit, as there would be no instruction to IANA. > > I guess, and correct me if I am wrong, the last scenario could be seen > as global *coordinated* proposal if similar text is presented in all > RIR > but in this case there would be no need to have them with the exact > same > text and neither all RIRs with it. > > Regards, > Ricardo > > > Em 02/11/2019 15:15, herve.clement@orange.com escreveu: >> 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 >> > > -- > Ricardo Patara > > _______________________________________________ > 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
Dear All, Just to clarify, due to COI - I will not comment on this.
Regards,
Aftab A. Siddiqui
On Sat, Nov 2, 2019 at 11:15 AM 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
Thanks Aftab, of course ! I’ve simply shared the news for information as the « global policy » notion was mentioned within a RIPE policy discussion and that’s something we would perhaps have to discuss internally if the discussions are going further… but it’s not the case at the time being.
Regards
Hervé
De : Aftab Siddiqui [mailto:aftab.siddiqui@gmail.com] Envoyé : dimanche 3 novembre 2019 19:17 À : 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)
Dear All, Just to clarify, due to COI - I will not comment on this.
Regards,
Aftab A. Siddiqui
On Sat, Nov 2, 2019 at 11:15 AM <herve.clement@orange.commailto: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.orgmailto: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.
Ah Sorry for not being clear. This is a good point to discuss for sure and really appreciate sharing it here. The reason why I consider COI (for myself ONLY) is because of this.
https://www.apnic.net/community/policy/proposals/prop-132
Regards,
Aftab A. Siddiqui
On Sun, Nov 3, 2019 at 10:25 AM herve.clement@orange.com wrote:
Thanks Aftab, of course !
I’ve simply shared the news for information as the « global policy » notion was mentioned within a RIPE policy discussion and that’s something we would perhaps have to discuss internally if the discussions are going further… but it’s not the case at the time being.
Regards
Hervé
*De :* Aftab Siddiqui [mailto:aftab.siddiqui@gmail.com] *Envoyé :* dimanche 3 novembre 2019 19:17 *À :* 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)
Dear All,
Just to clarify, due to COI - I will not comment on this.
Regards,
Aftab A. Siddiqui
On Sat, Nov 2, 2019 at 11:15 AM 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.
Dear Aftab,
IMHO, there is nothing that should revent you from entering this discussion. If the AC were to vote on something, then you may feel the need to abstain; but surely having already expressed an opinion publicly (as is your right), you should also be able to discuss the topic here.
Thanks,
Paul.
________________________________________________________________________ Paul Wilson, Director-General, APNIC dg@apnic.net http://www.apnic.net @apnicdg
On 3 Nov 2019, at 13:27, Aftab Siddiqui wrote:
Ah Sorry for not being clear. This is a good point to discuss for sure and really appreciate sharing it here. The reason why I consider COI (for myself ONLY) is because of this.
https://www.apnic.net/community/policy/proposals/prop-132
Regards,
Aftab A. Siddiqui
On Sun, Nov 3, 2019 at 10:25 AM <herve.clement@orange.commailto:herve.clement@orange.com> wrote: Thanks Aftab, of course ! I’ve simply shared the news for information as the « global policy » notion was mentioned within a RIPE policy discussion and that’s something we would perhaps have to discuss internally if the discussions are going further… but it’s not the case at the time being.
Regards
Hervé
De : Aftab Siddiqui [mailto:aftab.siddiqui@gmail.commailto:aftab.siddiqui@gmail.com] Envoyé : dimanche 3 novembre 2019 19:17 À : CLEMENT Herve TGI/OLN Cc : ac-discuss@aso.icann.orgmailto:ac-discuss@aso.icann.org Objet : Re: [AC-DISCUSS] A new RIPE policy proposal mentions a potential idea of global policy (RPKI ROAs)
Dear All, Just to clarify, due to COI - I will not comment on this.
Regards,
Aftab A. Siddiqui
On Sat, Nov 2, 2019 at 11:15 AM <herve.clement@orange.commailto: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.orgmailto: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.
_______________________________________________ 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
participants (8)
-
Aftab Siddiqui -
Brajesh Jain -
herve.clement＠orange.com -
Jorge Villa -
Louie Lee -
Noah -
Paul Wilson -
Ricardo Patara