Topic
Registry Governance
Within the Topic facet, Registry Governance topic intelligence connects articles that share a specific subject, signal focus, or monitoring theme. The page gives readers a richer path through related reporting, source evidence, market actors, and infrastructure implications, with enough context to understand why the topic matters across company movements, governance decisions, regional exposure, and operational risk. Readers can compare recurring signals, affected organisations, public evidence, market context, service continuity, procurement, competition, compliance, and strategic planning questions behind the subject instead of stopping at a thin list of matching articles. It explains what the topic covers, which infrastructure actors or policies are involved, what evidence supports the coverage, and why the subject may matter for operators, customers, investors, and policy readers.
Story
RIPEstat Is Rebuilding Routing History to Enable CSP. The New View Needs a Parity Record
A safer browser should not leave an operator wondering whether a changed graph reflects changed routes or changed presentation. RIPE NCC has a sound reason to replace legacy RIPEstat visualisations. Routing History is precisely where the migration needs a small public receipt…
CASE FILE
A Registry-Lock Quorum Counts Approvals, Not Independent Authority
Two approval messages can look like two-person control while both are recoverable through the same compromised mailbox. A proposed EPP registry-lock extension can count authorising contacts; the harder task is proving that the authorities behind those contacts were genuinely…
Story
RIPE NCC Publishes in Eight Languages. English Still Has Final Say
RIPE NCC now advertises information in eight languages and is recruiting community volunteers to translate material about its Information Services. The invitation broadens access, but the Language Centre’s own disclaimer fixes a sharp boundary: translated pages are informational…
CASE FILE
An EPP Balance Can Gate Transactions Without Exposing the Ledger
A registrar can be told exactly how much spending room it has and still be unable to explain why the next domain command was refused. The emerging EPP balance mapping makes funding state operational; it does not turn that state into an accounting record.
Story
ARIN Lets You Name a ROA. Its Online Search Still Ignores the Name
ARIN Lets You Name a ROA. Its Online Search Still Ignores the Name intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences that may follow. The…
Story
APNIC’s Definition Page Shows a Draft. Its Official Text Is Still Active
APNIC built one definition document so the same words would not acquire different meanings as they crossed policy files. The document now has a different problem. Its main web page presents version 004 as a draft; its stable official-text address still presents version 003 as…
CASE FILE
A Successful EPP Server Validation Is a Dated Policy Verdict, Not a Health Certificate
The word “success” can survive on a dashboard long after the observation that produced it has expired. A new EPP proposal would make the result portable; governance begins by refusing to make it timeless.
CASE FILE
The EPP Same-Entity Set Turns an External Policy Into an Atomic Boundary
A registrar can submit a command naming one domain while the repository must decide whether that command reaches a set too large to list. The protocol message is visible; the rule that draws its boundary may sit somewhere else.
Story
APNIC’s Online SIG Ballot Still Requires In-Person Attendee Check-In
APNIC 62 opened its SIG ballot online on 8 September. That describes the voting medium, not the electorate: an individual conference attendee still has to be in Mumbai, check in at the registration desk and show a record of participation in an earlier APNIC or APRICOT meeting.…
CASE FILE
The EPP Extension Registry Records Coexistence, Not a Winner
Two extensions can solve much the same provisioning problem, use different XML namespaces and both deserve a place in the same public registry. That is not a defect in the catalogue. It is the governance fact the catalogue must preserve.
Story
AFRINIC's Six-Month Implementation Rule Has Two Start Dates
A policy clock is useful only when the institution and its community can identify the event that started it. AFRINIC's current Consolidated Policy Manual starts its six-month implementation expectation at the end of Last Call. AFRINIC's current public explanation starts it at…
IETF
Michelle Cotton and the Code Point That Arrived Before Its RFC
The awkward moment comes before a standard is finished: two implementations need the same numeric language to meet, but the registry would normally wait for publication. Michelle Cotton’s RFC 7120 turned that timing gap into a visible, expiring state. Its most important word is…
Story
A 90-Day RIR Emergency Can Be Renewed Without Another All-Community Process
The recommended RIR governance draft gives an emergency service arrangement a 90-day interval and a route to renewal. It also changes the participation rule at that boundary: engagement with every RIR community is mandatory after initiation, but another such process after renewal…
Story
LACNIC Says to Email the Bulk WHOIS Form. The Same Page Says Email Is Not Accepted
LACNIC’s public instructions give a Bulk WHOIS applicant two doors and no label for the threshold between them. The signed form is to be emailed first, the original is to be posted after approval, yet the same page ends by saying emailed forms are not accepted. The problem is not…
CASE FILE
HTTP 200 Is Not an EPP Registry Decision
Putting a registry protocol inside HTTPS creates two answers to one request: what happened to the web exchange, and what happened to the registry command. Governance fails when an operator stores only the easier answer.
Story
RIPE Database Is Switching to OIDC. Maintainer Authority Does Not Move With the Session
RIPE NCC plans to replace a site-wide cookie with an OIDC session for interactive RIPE Database use. That can improve authentication, but the harder acceptance question begins after login: which `mntner` authorises this identity to change this entity, under which session regime…
Story
RIPE Closed RRC18 With a Restart. Fourteen Minutes Later It Opened a Similar RRC24 Incident
RIPE NCC restored one RIS collector by restarting two backend services while its cause remained unknown. Its next public incident post described the same publication symptom at a very different collector and warned that the fault might not stop there. The sequence makes…
Story
ARIN Closed the ROA Wording Fix. The Published Example Drops the Mask Interval
ARIN answered a precise operator complaint in five weeks and marked the documentation repair complete. That is the constructive part of the record. The harder question is why the live example no longer contains the length boundary that made the requested correction capable of…
Story
AFRINIC's upd-to Receives Failed Update Notices, Not Database Authority
An unexpected Whois update can place a complete rejected entity in somebody's inbox. AFRINIC's `upd-to` field explains why that person received the warning; it does not identify the sender, confer a credential or prove that the attempted change ever reached the registry.
Story
ARIN Added §4.10 Misuse to Its Fraud Process. Its Form Names Two Other Cases
ARIN now tells the public that misuse of reserved address pools, including space issued under NRPM §4.10, belongs inside its fraud-reporting process. Follow the link to the live intake form, however, and the explanatory copy still names only fraudulently obtained resources and…