v4 and v6 objects created on the ARIN IRR. Will delete them from RIPE next week.

From https://github.com/job/irrexplorer/issues/52#issuecomment-371497341 and to make everything clean, I'm considering replacing the current ROAs (some using max-length) to new ROAs using exact length.

In T235886#6005076, @ayounsi wrote:

From https://github.com/job/irrexplorer/issues/52#issuecomment-371497341 and to make everything clean, I'm considering replacing the current ROAs (some using max-length) to new ROAs using exact length.

Created all the exact-length ROAs after talking to John. Will delete the old ones next week.

Mentioned in SAL (#wikimedia-operations) [2020-03-30T11:22:48Z] <XioNoX> delete ARIN allocations from RIPE's IRR - T235886

Mentioned in SAL (#wikimedia-operations) [2020-03-30T11:59:49Z] <XioNoX> delete unused ROAs for RIPE prefixes - T235886

Mentioned in SAL (#wikimedia-operations) [2020-03-30T12:03:22Z] <XioNoX> delete unused ROA for ARIN v6 prefixes - T235886

The last unused ARIN ROA was bundled with the one used for ulsfo.
I created a new dedicated one for ulsfo and will delete the old one tomorrow.

I don't think it's possible to delete the arin-whois as they match the assigned prefixes.

Mentioned in SAL (#wikimedia-operations) [2020-03-31T08:01:14Z] <XioNoX> delete unused ROA for ARIN v4 prefixes - T235886

About:

We found that the prefixes 185.15.56.0/22 and 2a02:ec80::/29 are in use but not documented in the RIPE Database as assignments.

After discussing it with John, the deeper issue might be that they are "ALLOCATED PA" while they should be "ASSIGNED PI".

I inquired to know if it was possible.

For the time being, I created the inetnum records for the two Cloud /24s under 185.15.56.0/22. If any sub-allocation is made from 2a02:ec80::/29 then inet6num need to be created as well.

In T235886#6026275, @ayounsi wrote:

We found that the prefixes 185.15.56.0/22 and 2a02:ec80::/29 are in use but not documented in the RIPE Database as assignments.

After discussing it with John, the deeper issue might be that they are "ALLOCATED PA" while they should be "ASSIGNED PI".

No, that's not right. It's correct as it is, and it should not/cannot be ASSIGNED PI.

We are a LIR - so our /22 & /32 is space that has been allocated to us by the RIPE NCC. What this means is that this isn't ours to use by default; we are just managing it, not using it ourselves necessarily. We can use that space to assign from it to end users (customers, other networks, etc.), or to ourselves, for infrastructure use. We can make one assignment from it, or multiple ones (even smaller than /24). This is all PA -provider aggregatable- space and it must remain like that, PIs are not common nowadays.

What needs to happen here is that we need to create different assignments, i.e. inetnums with status ASSIGNED PA. We should be able to do this ourselves from the LIR portal. We should just create assignments for the parts of the space that we are using today -- I think WMCS could most likely be a separate assignment, but let's double check the rules (It's been a few years since I last read RIPE policies).

Happy to discuss more offline. Let's discuss before you do anything here -including with RIPE-, it can be tricky :)