IRRD v4 Migration

RADb Transition to IRRDv4: Key Information

The transition to IRRDv4 introduces several changes to how routing information is managed and queried within the RADb. Below is a comprehensive breakdown of the transition details and what you need to know.

1. NRTM Configuration Update

• Does this transition require updates to NRTM configurations?
  Yes, the transition requires changes. The whois.radb.net server will no longer respond to NRTM queries.

• New NRTM Host: The new server for mirroring is nrtm.radb.net on port 43.

• CURRENTSERIAL Reset: The CURRENTSERIAL will be reset back to 0, requiring a reseed.

2. Data Import and Object Handling

• What objects will be imported?
  All objects from the IRRDv3 database export will be imported into IRRDv4.

• Handling of Role/Person Objects

• role and person objects are used to define administrative and technical contacts.

• The admin-c and tech-c attributes reference nic-hdl attributes within role or person objects.

• These attributes act as primary keys and must have matching nic-hdl attributes already registered in the database.

• If no valid contact exists, the placeholder DUMMY-RADB can be used.

Example Person Object:

Example Role Object:

Example Route Object with Admin-C and Tech-C:

3. Handling Invalid nic-handles

• All existing objects will be imported as-is.

• After the transition, any updates to an object with invalid nic-handle(s) will require corrections.

Open

4. RPKI Validation and Management

• Do I need to undertake RPKI for the transition?
  No, RPKI adoption is not mandatory.

• Impact on RPKI Invalid Objects:

  • RPKI Invalid objects will no longer be visible in query responses after IRRDv4 goes live.

  • No objects will be deleted; invalid ones will be marked and filtered out.

• New and Updated Objects:

  • New RPKI Invalid route objects will be rejected.

  • Updating an existing RPKI Invalid object will also be rejected.

• How to Check RPKI Status:

  • Use the RIPE RPKI Validator to verify your object status.

  • Objects marked as "Not Found" or "Valid" are not impacted.

• Handling Conflicting ROA Information:

  • No existing objects will be deleted, even if they have conflicting ROA information.

  • New route objects with conflicting ROA will be rejected.

5. Maintainer and Password Management

• Do I need to update my maintainer object?
  No updates are necessary unless your object contains incorrect information, which can be corrected through the RADb Portal.

• Will I have to update my maintainer password?
  No, your maintainer password remains unchanged.

6. Impact on Existing Objects

• Existing objects that are not RPKI Invalid will remain unaffected.

• Only RPKI Invalid objects will be filtered from query responses.

7. Test and Demo Environments

• To familiarize yourself with the new IRRDv4, you can use the following demo environments:

  • WHOIS Demo: whoisdemo.radb.net (IRRDv4 with sample data)

  • API Demo: apidemo.radb.net (Available from October 1st)

8. Key Takeaways

• Update your NRTM configurations to point to nrtm.radb.net:43.

• Prepare to reseed due to the CURRENTSERIAL reset.

• Ensure that admin-c / tech-c attributes in your objects match valid nic-hdl values.

• RPKI Invalid objects will be filtered, not deleted.

• New RPKI Invalid objects will be rejected during creation.

• Use the provided demo environments to test your configurations.