Profile
Research
Research profile intelligence connects person, company, institution, and other entity coverage for readers comparing the subjects behind BTW.MEDIA reporting. The page helps compare public profiles, related events, evidence packs, role changes, operating footprints, governance exposure, organisational links, and market relevance while keeping organisation and people records distinct from ordinary news chronology. Readers can understand the subject behind the headline, the evidence supporting that profile, and the infrastructure or market relationships that make the profile relevant. They can see who or what the profile represents, which public sources support it, how it connects to companies, markets, governance bodies, or events, and what changes may deserve continued attention as the subject evolves.
Story
RIPE NCC Counted 1,799 Registry Checks. Its Public Target Has No Cohort Ledger
Seven RIPE NCC member updates report 1,799 Assisted Registry Checks completed from January through July 2026. That is nearly three-quarters of the annual 2,400-check commitment. It is a clear production count. It is not yet a coverage account: the public series does not say how…
AFNOG
AfNOG’s Speaker-Cost Rule Separates Programme Access From Travel Support
AfNOG’s 2007 call waived registration for presenters and instructors but expected them to fund their own travel because organisational funds were limited.
History
The Push That Was Never a Message Boundary: TCP's PSH Flag
An application asks TCP to push a buffer because waiting for later data could stall the exchange. TCP marks the last segment it creates from that buffer with PSH. Yet the mark does not turn that segment into a message: the sender's write, the packets on the wire, the receiver's…
AFNOG
AfNOG’s Reproduction-Permission Rule Turns a Talk Into a Commons Asset
AfNOG’s 2007 call asked contributors not only for a proposal, but also for permission to reproduce and publish the resulting presentation.
History
The Connection One Side Forgot: TCP's Half-Open Reset
A TCP connection can look alive from one endpoint and already be gone from the other. The classic specifications called that split a half-open connection. Their recovery examples turn the next packet into a test of shared memory: sequence expectations collide, a reset makes the…
Global Institutional Trends
Who controls the clock when ISC software has a vulnerability?
Internet Systems Consortium’s authority over supported BIND and Kea releases is real, but it is not the authority of a regulator or a universal command centre. It is stewardship power: the ability to concentrate information, coordinate disclosure, produce an official remediation…
AFNOG
AfNOG’s Repeat-Attendance Rule Turns Training History Into Access Authority
AfNOG’s 2005 workshop notice made prior training, subsequent use, available space and financial support part of a single access decision.
History
When Both Sides Knocked at Once: TCP's Simultaneous Open
The standard picture of TCP begins with a client knocking and a server listening. The protocol itself has never required that casting. Its original 1981 specification described what happens when two endpoints knock at once: their SYN segments cross, each side becomes both…
AFNOG
AIS’s Shortlist Rule Turns Agenda Time Into Editorial Authority
The AIS 2025 presentation call invited a wide technical community, then made clear that limited programme time would place only shortlisted abstracts on the agenda.
History
The Host That Had to Wait Before Speaking: TCP's Quiet Time After Restart
A restarted machine may look clean precisely because it has forgotten too much. TCP's original quiet-time rule addressed that paradox: if a host lost the sequence numbers used before a crash, it was told to emit nothing for one maximum segment lifetime. Silence was not a repair…
Story
The New RIR Draft Says Enforceability Does Not Wait for the Procedure
Article 1.3 of the new RIR Governance Document draft says a missing common implementation procedure does not stop the document from being enforced. The next clause, added in Version 3, says a decision must still follow the procedure relevant to the entity making it, including any…
AFNOG
AfNOG’s Host-Selection Rules Turn Infrastructure Capacity Into Convening Power
An archived Africa Internet Summit hosting call shows that choosing a host is both an operational-risk decision and a distribution of institutional attention.
History
The Reset That Ended Waiting Too Soon: TCP's TIME-WAIT Assassination Hazard
TIME-WAIT looks passive: a closed connection remains in a table while a clock runs down. In 1992, RFC 1337 showed that the state could be destroyed by active protocol behavior. One old segment provoked an acknowledgment; that acknowledgment provoked a reset; the reset erased the…
AFNOG
AfNOG’s NII Service Award Turns Recognition Into a Governance Signal
AfNOG’s published award language does more than celebrate individuals. It identifies service, sustained technical contribution and mentorship as conduct the institution wants its community to value.
IETF
The Ports That Outlived Their Protocols: RFC 9900 and the Discipline of Giving Numbers Back
Ports 831, 832, and 833 can persist in diagrams, service files, and filters even after the NETCONF transports once attached to them never reached known production deployment. RFC 9900 therefore retires the number bindings without erasing their semantic history.
AFNOG
AfNOG’s Bursary Criteria Turn Travel Funding Into a Knowledge-Sharing Mandate
A dated AfNOG-hosted bursary application ties individual travel support to the ability to reuse and share meeting knowledge within an African country and region.
IETF
One Name, Many Rules: RFC 9899 and the Control Surface of Reusable ACL Sets
A security team changes one named prefix set once, and every ACL that references it can inherit the change without rewriting each parent rule. That mechanism is the promise—and the control problem—behind RFC 9899’s reusable policy entities.
History
The Deadline That Was Not a Retransmission Timer: TCP User Timeout
TCP can decide to retransmit a segment and still decide, on a different clock, that the connection has waited too long. The first decision schedules another attempt. The second ends the connection. RFC 5482 made that persistence preference visible to a peer without turning it…
IETF
Shrink the Trust Domain: RFC 9898 and the IPv6 Neighbor-Discovery Isolation Choice
On one IPv6 access segment, three different root causes can surface together: multicast load, implicit trust of every on-link node, and router Neighbor Cache Entries created on demand. The practical question is therefore not which symptom to patch, but which part of the Neighbor…
Story
LACNIC Whois owner-c Marks Administrative Authority, Not Network Operation
LACNIC Whois owner-c Marks Administrative Authority, Not Network Operation 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…