Live Wire
View all briefingsLead Report / History
The ISO code changed before the old domain stopped serving people. Between those dates, a temporary registry, replacement namespaces and a staged migration had to bridge the distance between administrative identity and addresses already embedded in daily use.
Europe and Middle East National Telecom Trends
The old Svalbard pair kept service through one cable break in 2022. Space Norway’s new Ciena award will standardize optical equipment across that legacy system and Arctic Way, but the public record still does not show how much traffic each route can carry, what fails together, or how quickly traffic can be restored.
Leaders
RFC 9293 gathered decades of TCP requirements into a current normative specification while leaving design explanations and many algorithms in companion documents. That boundary made the common rules easier to locate; it did not prove that deployed implementations behaved alike.
Leaders
A private contact list and a conference-room introduction could make the first peering conversation easier to start. They could not make two networks agree to connect.
Member Access
Strategic Circle turns infrastructure moves, policy shifts and market signals into a concise briefing in your chosen language—plus the research library and member forum—for USD 20/month.
Market / Trends
EXA Infrastructure will lead and deliver the planned cable, Xtera is its key supplier for optical engineering and wet and dry plant, and Prysmian says it will manufacture the cable. The Xtera acquisition changes who owns the supplier; it does not make the three roles interchangeable.
Governance
A commercial invitation travelled through a network directory built for a selective research community. The May 1978 replies show that the central dispute was who could use that access, and how a government use rule could be enforced through local network contacts.
Market
RFC 2525 turned reports of TCP implementation failures into a reusable diagnostic record: a named symptom, protocol context, packet-trace evidence, detection guidance and a known correction where the cause was understood. Mark Allman was one of nine coauthors; the document does not assign individual sections or fixes.
Market / Companies
The ransomware incident at IDC Frontier did not prove that IDCF Cloud Backup failed. It did expose a more useful market question: when the ordinary cloud console is stopped, who can reach a copy, authorize its use and supply somewhere to run the restored service?
Governance / NOGS
The first twenty minutes of a conference can reveal institutional relationships. They cannot, without supporting records, tell us who held the decisive authority.
Editorial position
Internet governance is too often described as theory, consensus, or institutional comfort while operators live with the consequences of structure, scarcity, jurisdiction, and incentives.
BTW shows how the system works when assumptions are tested: clear, uncomfortable, evidence-led reporting that keeps attention on structure rather than drama. Public reporting is published to travel: it may be indexed, quoted, translated, used in search and AI answers, and used to train models so the evidence can shape how infrastructure questions are understood.
Governance, market, and membership branches operating in one integrated intelligence model.
Reporting on address stewardship, representation, and the institutions shaping number-resource governance.
Five regional sessions: ARIN, RIPE NCC, APNIC, AFRINIC, and LACNIC.
North America policy and transfer market signals.
Europe governance transparency and accountability monitoring.
Asia Pacific allocation pressure and policy dynamics.
Board legitimacy, election process, and legal continuity.
Institutional adaptation and ICP-2 governance trajectory.
Operational intelligence from the communities where routing, peering, resilience, and deployment practice are tested.
Asia-Pacific NOGs
North America NOGs
Asia-Pacific NOGs
Latin America and Caribbean NOGs
Asia-Pacific NOGs
Africa NOGs
Asia-Pacific NOGs
Asia-Pacific NOGs
Europe and Middle East NOGs
History of the Internet
ALOHAnet began as an answer to a local problem: how could terminals scattered across Hawaiian islands reach computing resources without giving every terminal a permanent circuit? By 1974, the project was testing a second answer. A NASA satellite could carry bursts between distant sites, but the path still depended on a hub, a shared radio channel and a link that had to work under real noise.
ALOHAnet began as an answer to a local problem: how could terminals scattered across Hawaiian islands reach computing resources without giving every terminal a permanent circuit? By 1974, the project was testing a second answer. A NASA satellite could carry bursts between distant sites, but the path still depended on a hub, a shared radio channel and a link that had to work under real noise.
Leadership Alliance
Usenet’s 1980s network links did not all work the same way. RFC 977 made a narrow, useful distinction: negotiate article transfers on interactive links, but keep batch-and-discard behavior where a dial-up session made it faster.
Usenet’s 1980s network links did not all work the same way. RFC 977 made a narrow, useful distinction: negotiate article transfers on interactive links, but keep batch-and-discard behavior where a dial-up session made it faster.
