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.
ICANN
A .Brand String Change Can Add Words, But Cannot Create or Expand Contention
ICANN’s 2026 Round gives a qualifying .Brand applicant a narrow way to change a string when contention arises. It is not a general opportunity to rename an application.
Number Resource Society
An ASPA Is Not a Complete AS-Path Attestation
An ASPA can help an operator test whether an AS path is consistent with published customer-to-provider authorizations. That is valuable route-leak evidence. It is not a signature over every hop, a proof of route origin, a commercial contract, or a guarantee that the published…
ICANN
A Material Change to Public Application Content Opens 30 Days of Comment, Not Automatic Approval
When ICANN finds that a requested change materially affects public application content, the request enters a 30-day comment process but has not crossed the approval line.
Story
AFRINIC Offered In-Person Registry Checks at AfPIF. The Frozen Page Does Not Report Outcomes
AFRINIC promoted face-to-face help with registry records, identity checks and open requests at AfPIF 2026; the frozen source set does not show what was completed.
Number Resource Society
An RPKI Cache Serial Is Not a Freshness Timestamp
Two RPKI caches can report perfectly accurate serial numbers and still tell an operator nothing about which cache holds newer global data. RFC 8210 scopes a serial to one cache session and protocol version. Treating the larger number as the fresher view manufactures a chronology…
ICANN
GAC Consensus Advice Starts a 21-Day Response Record, Not an Automatic Board Outcome
Formal GAC Consensus Advice changes the applicant's procedural position, but it does not itself supply the ICANN Board's decision.
IETF
When a Drone ID Becomes a DNS Delegation: RFC 9886 and the Registry Chain Behind Remote ID
A Broadcast Remote ID can carry a compact DRIP Entity Tag (DET), while the public evidence needed to authenticate registry inclusion is distributed across reverse-DNS delegations, HHIT and BRID records, and a certificate chain. The practical question is therefore not only whether…
Number Resource Society
A ROA maxLength Is Not a Traffic-Engineering Policy
A route can be RPKI Valid because a ROA’s maxLength admits its prefix length. That result proves a bounded origin authorization. It does not prove that the more-specific route was planned, approved, currently announced or preferred by the operator. Those are separate facts, and…
Story
LACNIC’s IPv6 allocation rules make scale plannable
**BTW analysis:** IPv6 offers a vast address space, but abundance alone does not tell a network operator what it may request, how need will be assessed, or what obligations follow an allocation. In Latin America and the Caribbean, those practical questions meet LACNIC’s published…
Leaders
Artem Izbaenkov and the Cost of Representation at RIPE NCC
Artem Izbaenkov’s 2024 campaign for a seat on the RIPE NCC Executive Board turned an operator’s career in DDoS defence and cloud security into a wider argument about who can participate effectively in registry governance—and what language, fees and institutional attention have to…
Number Resource Society
A BGPsec Router Certificate Is Not Route-Origin Authority
A BGPsec Router Certificate Is Not Route-Origin Authority 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 Number…
ICANN
A GAC Early Warning Is a Signal, Not a Veto: The Applicant's Response Record
The 2026 Round gives a government representative a way to flag a concern without turning that notice into an automatic decision on the application.
Story
LACNIC’s 2025 Path Study Does Not Date Its Measurements
A year in a report title tells readers when an edition belongs on the shelf. It does not tell a network operator when the packets behind its charts crossed the wire. LACNIC’s regional path study offers a useful view of routes and latency, but leaves that second clock unstated.
Story
LACNIC 46's Machine Records Still Say LACNIC 39 and LACNIC 45
The closing entry in LACNIC 46's current agenda belongs to the right event when read through its canonical taxonomy and presentation title. Three other fields still name LACNIC 45. A separate homepage field goes further back, to LACNIC 39. This is a small data-integrity problem…
Story
ARIN’s IRR Objects Keep the Channel That Created Them
An IRR object migrated from ARIN’s email service can be deleted in ARIN Online but not edited there. The asymmetry is defensible as a record of provenance. The trouble begins when the web remedy—delete and recreate—changes that provenance without a visible continuity receipt.
Story
ARIN's SMS Country List Is Now an Attack-Cost Boundary
A request to make SMS authentication more convenient ended with a security-cost decision. ARIN says the limited numbers it supported outside its service region created a costly attack vector; the public record explains the boundary it chose, but not the attack it measured.
Story
APNIC’s Resource Quality Check Is Not an Address Attribute
APNIC made a careful change in 2019: “assurance” became “check”. The distinction matters because a registry can observe routes, filters and reputation signals, but it cannot make thousands of other networks carry the result forward.
Story
APNIC proposal tests a one-/24 IPv4 bridge for IPv6-only networks
APNIC prop-165 version 4 would let an organisation eligible for an initial IPv6 allocation request one IPv4 `/24` for transitional functions in an IPv6-only deployment. The proposal is still under discussion: its practical significance lies less in the size of the grant than in…
Number Resource Society
A Ghostbusters Record Is Not an Incident Command Roster
An RPKI relying party can validate every byte of a Ghostbusters Record and still not know whether anyone is watching the listed channel when action is needed. The signed entity solves discovery of minimal CA-maintainer contact data; operational accountability begins where that…
Number Resource Society
A Trust Anchor Rollover Needs an Acceptance Ledger
An RPKI trust-anchor operator can publish a successor key without making every relying party ready to use it. The transition is a sequence of verified observations, not a launch date: a defensible record must show what was announced, what remained stable, which validators crossed…