Live Wire
View all briefingsLead Report / History
Every IPv4 address fits into the same 32 bits. Its operational meaning does not. A destination can describe this host, one link, a private interior, an example, a laboratory or a public endpoint. RFC 3330 gathered those exceptions into one catalog—and exposed why the catalog could never be a timeless blacklist.
North America Datacenter Trends
Kodiak Gas Services has disclosed a six-year, 76 MW gas-power contract for a West Texas data centre, with deployment due to start this quarter. The harder investment question is not whether the campus needs power, but which enforceable promise pays Kodiak: the release describes three unnamed parties in separate relationships and does not show that downstream support reaches the generator’s receivable.
History
In M2UA, “user” did not mean the person making a call. It meant MTP3, the layer immediately above an SS7 signalling link. RFC 3331 kept the wire and MTP2 machinery at a gateway, then carried that upper boundary across SCTP to a remote controller. The resulting system could show a healthy IP association, an active application process and a failed physical link at the same time.
History
A registrar could know which contact to call without knowing every proxy that a future call had to cross. RFC 3327 attached an ordered Path to a contact binding so the home proxy could reuse those route references after REGISTER had finished. That Path prescribed later routing; it was not a trace of the packet path that had already occurred.
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.
Governance
The number at the bottom of the waveform had two incompatible jobs. RTP treated it as an ordinary sample. A DV deck treated it as notice that no sample had survived. RFC 3190 made the bridge choose which meaning would cross.
Market
A positive PCEP reply can put a clean route on an operator's screen before any router has accepted it. Adrian Farrel's PCE architecture matters because it lets us say exactly what has happened—and what has not.
Market / Trends
Overwriting one object can leave several generations on the bill. A shorter minimum duration, a new invoice and a new price each change a different part of that history.
Market / Companies
Cloudflare lists no charge for outbound transfer from R2 and documents a way to copy objects out. The remaining economic question is what customers must spend—and successfully operate—to turn that export into a working replacement.
Governance / NOGS
AfNOG’s dated host call strongly prefers hosts familiar with its workshop requirements through prior participation. The reviewed page does not publish an equivalent proof route for a first-time host.
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.
Africa NOGs
Asia-Pacific NOGs
Asia-Pacific NOGs
North America NOGs
Asia-Pacific NOGs
Latin America and Caribbean NOGs
Asia-Pacific NOGs
Asia-Pacific NOGs
Europe and Middle East NOGs
History of the Internet
The old application believed it had received an IPv4 address. On the wire, no such destination needed to exist. RFC 3338's Bump-in-the-API mechanism intercepted name and socket calls, assigned a temporary IPv4-shaped value from a private local pool, and used that value to recover the real IPv6 peer inside the host. The address was not a global identity. It was a handle whose meaning lived in a table, a scope and a moment.
The old application believed it had received an IPv4 address. On the wire, no such destination needed to exist. RFC 3338's Bump-in-the-API mechanism intercepted name and socket calls, assigned a temporary IPv4-shaped value from a private local pool, and used that value to recover the real IPv6 peer inside the host. The address was not a global identity. It was a handle whose meaning lived in a table, a scope and a moment.
Leadership Alliance
The receiver wanted one clean fact: the picture was finished. RFC 3189 put that news in the marker bit of the last packet, then warned that the packet carrying the news might be the one the network lost. The convenient signal could shorten delay. It could not be the authority for where a frame ended.
The receiver wanted one clean fact: the picture was finished. RFC 3189 put that news in the marker bit of the last packet, then warned that the packet carrying the news might be the one the network lost. The convenient signal could shorten delay. It could not be the authority for where a frame ended.
