What are the requirements for adding RIPE-NCC allocated subnets to the IPXO Marketplace?
IPXO is a fully automated IP address lease and monetization platform. To get the most out of it, make sure to get acquainted with the minimum requirements for listing RIPE NCC-issued subnets.
Check the subnet’s Whois information
Make sure the inetnum you are adding exists in RIPE’s Whois database. Use the RIPE Database query search tool to look this information up.
Authorize IPXO to manage the subnet
IPXO supports two types of authorization for RIPE NCC allocated IP addresses:
ROA: Use this method when adding a /24 Allocated PA subnet by issuing a non-specific ROA for a given subnet with ASN: 834 (no other ROAs should exist) and adding IPXO-MNT as mnt-lower, mnt-domains, mnt-routes
Check if the subnet’s status is accepted
Based on the Inetnum Status, perform the required action from the following table:
Inetnum Status
Action
Sub-allocated PA
Authorize by adding IPXO-MNT as mnt-by
Legacy
Unsupported
Allocated PA (mask = 24)
Authorize via ROA and by adding IPXO-MNT as mnt-lower, mnt-domains, mnt-routes
Assigned PA
Unsupported: Recreate the inetnum with a Sub-Allocated PA status
Allocated PA (mask < 24)
Create a more specific inetnum with Sub-Allocated PA status and add IPXO-MNT as mnt-by
