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