To create sub-allocations you need a /127 (IPv6) or /31 (IPv4) or larger space with status “ALLOCATED PA”, “ALLOCATED PI”, “ALLOCATED-BY-LIR”, “LEGACY” or “SUB-ALLOCATED PA”. The PA IPv6 space we provide is by default “ALLOCATED-BY-LIR”.
You can use the following table to see possible values for the new objects “status” field:
* ALLOCATED PI → ASSIGNED PI
* ALLOCATED PA → ASSIGNED PA, SUB-ALLOCATED PA
* SUB-ALLOCATED PA → ASSIGNED PA
* ALLOCATED-BY-LIR → ASSIGNED, ALLOCATED-BY-LIR
* LEGACY → LEGACY
We recommend to create a sub-allocation (= end user can create further sub assignments himself) or sub-assignment (= end user cannot create smaller objects) for every /64 or larger you assign. You do not need to use the customers data; using your own handles and just editing NETNAME and DESCR is fine.
On our PA IPv6 space (as offered for free or with ASN registration) sub-allocation/sub-assignment is required on subnets of size /48 or larger.
Please be vary about giving unknown persons MNT-BY on subnets - If they remove your maintainer from the object we have to contact RIPE to remove the object. Most things required can be accomplished by using MNT-LOWER or MNT-ROUTES.
We do not focus on IPv4 here but the process is nearly the same, an article on that will follow.
For a new sub-allocation you need the RIPE handles (MNT and Person/Role, optionally ORG) - You can view a guide to create them here: https://w.ip6.im/ripe:create_new_handles
Then navigate to the RIPE webupdates interface here:
First enter your maintainer password in the left sidebar.
Then select “inet6num” in the “Object type” field and “Create object in single text area” in the “Operation” field. Click create.
You can either edit the template RIPE displays or follow the guide below and just use the value fields you need. All-uppercase ones are required on any object.
This is the range to be assigned or allocated plus netmask. Ex. 2001:10::4/48
Network name, no spaces/special chars.
Network description, may contain spaces.
2 letter ISO code of the country of the end-user or the “LIR”. Not verified by RIPE. Used for geolocation by most DBs.
A geolocation value with longitude and latitude, separated by space. Used for geolocation rarely.
A value for the language of the end-user. No practical use currently.
RIPE ORG object, if available.
RIPE person/role handle of network admin. Can be repeated as required.
RIPE person/role handle of technical contact. May be the same as ADMIN-C. Can be repeated as required.
New status of the network, see table on top of this page.
Size of assignments within this block to end-users, i.e. 64 or 56.
Any remarks you might want to put into it, i.e. “Contact so-so at abuse”. Sometimes used for ASCII art. Can be repeated as often as required.
A mail address that receives all changes on the object in the future (also once if that value is removed again). Mail contains the old object for easy revert. Highly recommended to be set with valid email. Can be repeated as required.
Maintainer of the space, can change the object itself. Depending on trust relationship either you or your customers MNT. Can be repeated as required.
Can create smaller assignments/allocations (where applicable) but not edit the existing larger object. Your customers MNT goes in here.
Can create route object for IP space in question, usually the MNT of the datacenter or the MNT used on the end-users ASN. Can be added on space smaller than /48 but makes no sense.
Can create reverse DNS zones for IP space in question. Only works on /48 or larger. Not required if end-user has MNT-BY on space.
Used for security contacts of your local CERT or similar - More information from RIPE here. Not much used.