RIPE IPv6 Allocation & Prefix Management

Self-service management

For RIPE IPv6 allocations you can manage everything from your service dashboard:

• Assign the prefix to your RIPE org object
• Create and manage ROA records
• Delegate RPKI management

Prerequisite: authorize our maintainer

Before we can assign a RIPE prefix to your organization, add GETIPV6-MNT to the mnt-ref attribute of your org object. This authorizes us to create assignments referencing your organization.

RPKI & ROA

We support RPKI delegation for your allocation. The RIPE Hosted CA does not currently accept delegation, so to run delegated RPKI you operate your own Krill instance and select delegation to it in the RIPE RPKI Dashboard.

Don't want to run Krill but still need ROAs? We support ROA hosting — add the ROA entries you need directly on your service page.

Letter of Authorization (LoA)

We can issue an LoA for your prefix on request, but not by default — we encourage choosing upstream providers that support ROA validation to improve BGP security. If your provider requires an LoA, open a support ticket.

Before requesting an LoA, the prefix must first be assigned to your org object so WHOIS is accurate. Include in your ticket:

• Authorized party name — the name on the LoA
• Authorized prefix(es) — the prefix(es) to cover
• Authorized ASN — the AS number announcing the prefix

Processing time

RIPE IPv6 self-service operations take effect immediately. Ticket-based requests are typically processed within one business day.