Summary

  • RIPE NCC says it plans to contact affected users to correct 166 database objects referencing IANA1-RIPE.
  • The live role object names the Internet Assigned Numbers Authority. RIPE Database contact fields use role handles for operational correspondence, making accurate references a practical registry question.

The October member update slipped a small number into a crowded list of technology work: 166 RIPE Database objects reference IANA1-RIPE, and RIPE NCC plans to contact affected users to correct them. A database can accept a handle perfectly well while leaving a human reader wondering who is actually responsible for a record.

The live role object identifies IANA1-RIPE as the Internet Assigned Numbers Authority. RIPE NCC's database FAQ explains why role handles matter: fields such as admin-c and tech-c identify network contacts for operational correspondence, including troubleshooting. IANA has a global coordination role. It is a curious name to find on a local contact card that someone else is expected to maintain.

The announced remedy starts with users, not a blind bulk rewrite. RIPE NCC says it will contact affected users to correct the objects. Its brief update gives neither the affected object types and fields nor a completion date. Those details would show which records need a new contact, how much work falls to operators and when a query will point readers to the updated role.

The inverse-query documentation describes how to find objects referencing a role in specified attributes. That supplies a concrete follow-up: count the remaining references, then compare the corrected objects with what RIPE NCC said it would address. A registry's address book earns trust one contact at a time. The 166 lines are a manageable test of whether the address book still knows whom to call.