Treat registry data, routing authorisation, upstream approval, BGP and DNS as related but separate checks. They do not form one universal sequence, and the party responsible for each depends on the resource arrangement, database maintainers, RPKI setup, network design, service agreement and upstream policy.
For the service and current application route, see RIPE IPv6 leasing and prefix options.
Scope: RIPE registry and routing coordination. This guide is not vendor-specific router configuration or a guarantee that a route will propagate across the Internet.
Five functions to confirm
| Function | Who controls it | What to check |
|---|---|---|
| RIPE resource record / inet6num | The RIPE NCC member / LIR maintaining the resource record; some database actions may be delegated to a customer maintainer. | Exact prefix, parent-child relationship, contacts and applicable registration model. A database status describes registry data; it does not, by itself, prove commercial lease terms. |
| route6 / IRR | The maintainer authorised to create or update the route6 object for the address space. | Prefix and origin ASN match the intended announcement. Confirm whether the upstream uses this IRR data for filters. |
| ROA / RPKI | The operator of the resource certificate authority, through a hosted or delegated CA arrangement. | The ROA permits the intended origin ASN and every planned prefix length. |
| BGP origination | The network operator controlling the origin ASN and the router or service that announces the route. | The actual announcement uses the agreed prefix and origin ASN, and the network is prepared to carry and return traffic. |
| Upstream acceptance | The transit or upstream provider, under its own routing policy and customer agreement. | Accepted prefixes and origin ASN, IRR/RPKI requirements, filters, and any requested Letter of Authorization (LOA). |
Check the tracks separately
1. Confirm the resource and intended announcement
Record the exact IPv6 prefix, the origin ASN and all prefix lengths you plan to announce. Ask the resource provider and upstream to confirm the agreed arrangement before records or router policy are changed.
RIPE registration models differ. For example, ALLOCATED-BY-LIR describes an LIR-to-ISP sub-allocation in the RIPE Database; it is not a universal label for every lease or customer arrangement. Check the actual inet6num object and agreement. See what ALLOCATED-BY-LIR means in the RIPE Database.
2. Check route6 / IRR data and its authorisation
A RIPE Database route6 object records an IPv6 route and its origin ASN. Confirm that the object matches the planned announcement and ask whether the upstream builds filters from this IRR data. An IRR object does not make a BGP announcement or guarantee that another network accepts it.
RIPE Database authorisation for creating a route(6) object checks the relevant existing route(6) or address-space maintainers. The documented maintainer precedence is mnt-routes, then mnt-lower, then mnt-by. This is an object-authentication rule; it does not define who owns the commercial relationship or who operates BGP.
3. Check the ROA and RPKI validation
A ROA authorises an origin ASN to announce a prefix up to a specified maximum length. The person or organisation able to publish it depends on the resource certificate setup: the CA may be hosted by RIPE NCC or delegated. Confirm the intended origin ASN and maximum length with the CA operator.
- Valid: a matching ROA authorises the announced origin ASN and prefix length.
- Invalid: covering ROA data exists, but the origin ASN or announced length is not authorised by a matching ROA.
- Unknown: no covering authorisation is available for the announcement.
Do not increase a ROA maximum length merely to make a mismatch disappear. First confirm which more-specific routes are required and accepted by the upstream. The upstream decides how its routing policy uses RPKI validation.
4. Ask the upstream what it will accept
Upstreams can have different requirements for prefix length, customer documentation, IRR records and RPKI validation. Ask for the accepted prefix and origin ASN, whether its filters have been updated, and whether it requires an LOA. An LOA may document permission for a particular provider or arrangement; it is not a substitute for route6, ROA, BGP configuration or upstream acceptance, and it is not a universal RIPE prerequisite.
5. Verify the actual BGP announcement
After the responsible network operator announces the route, verify the observed prefix and origin ASN using the upstream’s view and independent routing data, such as RIPEstat. A route visible from one vantage point does not prove global propagation or application reachability. Test the intended traffic path, including return routing and firewall policy.
Reverse DNS is a separate track
IPv6 reverse DNS uses ip6.arpa. The resource-side operator can delegate the reverse zone to authoritative nameservers, and the DNS operator then serves the records. Confirm the delegation and test it if reverse DNS is part of the service. It is not a prerequisite for a BGP announcement and changing it does not announce a route.
Practical pre-announcement checklist
- Prefix, origin ASN and planned announcement lengths are written down and agreed.
- The inet6num and maintainer permissions match the intended resource arrangement.
- route6 / IRR data matches the planned prefix and origin, if required by the upstream.
- A matching ROA exists for the origin ASN and planned lengths, if RPKI is used.
- The upstream has confirmed its filters, acceptance policy and any LOA requirement.
- The BGP operator knows what to announce and how the route will be independently verified.
- Reverse DNS delegation is checked separately when included in the deployment.
Keep a record of the agreed state. Coordinate prefix, origin ASN or maximum-length changes before they are announced. A registry record, route6 object or ROA is not proof that traffic currently reaches the intended service.
Official references
- RIPE NCC: Obtain and Register IPv6
- RIPE Database: Protection of Route(6) Object Space
- RIPE Database: Primary Objects, including route6
- RIPE NCC: BGP Origin Validation
- RIPE NCC: Using the RPKI System
- RIPE NCC: Reverse Delegation
Elisteka's standard IPv6 /32 lease fee is €29 per month, with €87 for the first 3 months paid upfront, excluding VAT. This price does not guarantee route propagation or upstream acceptance.
To estimate the lease cost, try the IPv6 lease fee calculator. For the commercial process, see how to lease a RIPE IPv6 /32.
Discuss your IPv6 /32 requirements
Share your company, intended use and proposed origin ASN. Request an IPv6 /32 lease or email sales@elisteka.com. No payment is collected through the application form.