Hi David,
>
Both the AS number and the prefix(es) are resources issued by an RIR. Are you saying both the AS number and the prefix(es) for ROA must be issued by RIPE to
be accepted? I think that would be overly restrictive.
> I could see maybe only accepting ROAs authorizing address resources that RIPE has issued.
That was exactly what I had in mind as well.. as per ROA’s, filter to accept only what was allocated / assigned by the RIPE NCC. The AS nr could be from any rir.
Thank you for clarifying your intent; while I think this policy could have its reasons, it still might be a little bit too restrictive, at least without a more definitive reason for only allowing RIPE-issued address resources to be published through the RIPE publication service.
For example, if I have ten address blocks from RIPE and one address block from ARIN, I don't see the harm in allowing the publishing of one ARIN block through the RIPE service. If there is harm from allowing this, please help me understand it.
Nevertheless, it seems rational to require at least some of the resources in the publication set to have been issued by RIPE as a requirement to use the RIPE publication service.
Or, stated conversely, it doesn't make sense to allow the use of the RIPE publication service for resources with no nexus to RIPE.
Maybe a slightly more specific and restrictive way to say this is; all ROAs published through the RIPE service must have a nexus with RIPE resources; that is, either the prefix, the ASN, or both are RIPE-issued resources. However, ROAs, where both the ASN and the prefix are not RIPE resources, are not allowed to use the RIPE publication service.
Thanks
Thanks.
===============================================
David Farmer
Email:farmer@umn.eduNetworking & Telecommunication Services
Office of Information Technology
University of Minnesota
2218 University Ave SE Phone: 612-626-0815
Minneapolis, MN 55414-3029 Cell: 612-812-9952
===============================================