Skip to main content

Briefing Desk

Latest Briefings

Concise reporting on the developments shaping internet governance and infrastructure. Browse each area for recent news, context and watchpoints.

  1. UPS Prices $9 Million of Retention in Class B, Settles in Class A

    UPS has attached US$9 million of restricted stock units to two executives carrying its new global operating model. The divisor will be the 1 September Class B closing price, but vested units will deliver Class A shares with ten votes apiece. That difference matters because the grants reward service through 2029, not a disclosed operating result.

  2. The UUID Sorted. The Event Was Not Proven: RFC 9562 and the Boundary Between Identifier Order and Evidence Time

    At 14:03, a review screen puts two rows in an immaculate order. The smaller UUIDv7 belongs to `reversal-requested`; the larger one belongs to `reversal-completed`. It looks like a ready-made account of what happened. But the first identifier may have been allocated before a transaction began, the second may have come from a retrying outbox, and the clocks that supplied their millisecond fields may have belonged to different hosts. A tidy line of keys is useful. It is not yet a case file.

  3. Dynatrace’s 41% Organic Net-New ARR Growth Has No Dollar Bridge

    Dynatrace says organic net-new annual recurring revenue grew 41% in its first fiscal quarter. That is a striking acceleration signal, but it is not 41% growth in the company’s US$2.136 billion ARR balance. It is growth in an adjusted quarterly increment whose two dollar values are not disclosed. The difference determines what the headline can—and cannot—tell investors about demand.

  4. GameStop Pays $358.4 Million to End Its Dilution Formula

    GameStop has replaced the unfinished part of a 35-trading-day share formula with US$358.4 million of cash. The amendment fixes this note exchange at approximately 55.5 million shares and brings expected closing forward, but it does not erase those shares or the US$2.8 billion of convertible principal scheduled to remain.

  5. WCAG-EM’s 10% Random Check Is Not 10% of the Product

    An accessibility report can contain a precise percentage and still leave its denominator invisible. W3C’s new WCAG Evaluation Methodology says the random part of a representative sample should equal 10% of the structured part. It does not say that evaluators inspect 10% of the product. That distinction is more than arithmetic: it determines what the evidence can support, who is accountable for selecting it and whether a public statement is mistaken for a whole-product WCAG conformance claim.

  6. The Collector Received a Delay. It Did Not Receive a Verdict: RFC 9951

    At 09:17, a collector receives a Flow Record with a mean delay, a maximum delay and an identifier for the transit point that exported them. By 09:20, someone wants the record to settle three larger questions: whether a customer suffered, whether a path changed, and which team must act. That acceleration is understandable. It is also the point at which a useful measurement is asked to become an institution.

  7. The Architecture Retreat Named Five Problems. It Did Not Pick the Next Internet: RFC 1287

    In 1991, a group of Internet architects looked at growth, address exhaustion, multiple protocol suites, security, real-time traffic and the next generation of applications. RFC 1287 is the record they left behind. It is tempting to read such a record backwards: it discusses 64-bit addresses, aggregation, policy routes, application gateways and a more adaptable Internet, so it must have chosen the Internet that followed. The document itself supplies a better discipline. It is an Informational RFC offered for discussion and comment, not a standard. Its consensus assumptions make a planning horizon visible; its five work areas focus attention; its proposed actions invite research and engineering. None of those moves turns a future direction into an adopted architecture, a route into reachability, or a technical agenda into authority over a later deployment.

  8. Aon's 14.5x USI Multiple Includes Synergies Due by 2029

    Aon calls its net purchase price for USI 14.5 times synergized adjusted EBITDA. The arithmetic works only after replacing part of the seller's earnings definition and crediting the full run-rate value of synergies expected to be substantially realised between closing and 2029. The multiple is therefore an underwriting destination with a calendar, not a measurement of earnings available on signing day.

  9. AFRINIC Says Douala-IX Strengthens Local Exchange. Its Public Snapshot Does Not Yet Measure It.

    AFRINIC’s March community bulletin frames its support for Douala-IX as a way to strengthen local interconnection in Cameroon. The public evidence now available is useful, but it is an inventory of exchange attributes—not a measurement of the claimed operational result.

  10. Palo Alto’s QRadar Liability Fell US$274m; US$154m Was Paid

    Palo Alto Networks ended April with a US$240 million liability for contingent payments on the IBM QRadar acquisition, down from US$514 million nine months earlier. Cash explains only US$154 million of that movement. A US$120 million net fair-value reduction explains the rest—and turns the balance-sheet decline into a test of customer-qualified transactions, valuation assumptions and earnings quality rather than a story about one large payment.

  11. W3C Calls Sustainability ‘Ratings.’ One Total Still Ranks 71 Guidelines

    On 6 August, a W3C repository changed one word: “Measurement” became “Ratings.” Twelve days later, the Sustainable Web Interest Group published its first Group Note Draft under the narrower name. The distinction is honest. The document combines evidence and expert judgment, not four direct measurements. Yet it still turns ratings for People, Planet and Prosperity, plus an expected timeframe, into one number that can order 71 guidelines. The name now admits judgment; the total still hides where that judgment entered.

  12. After a Reboot, “Secure” Must Not Mean “Resume”: RFC 10021 and Group OSCORE Recovery

    A controller can regain a safe cryptographic footing after a power loss without regaining permission to continue the process it interrupted. RFC 10021 makes that distinction operational: restore the security context first; decide separately whether anything should resume.

  13. Charter's CFO Will Leave After the First Cox Quarter Closes

    Jessica Fischer will leave Charter Communications after helping close the quarter ending 30 September, the first quarter-end since Charter completed its Cox and Liberty transactions. The timing protects continuity through the accounting cut-off. It also places the combined company's first post-close consolidation, secured-credit perimeter and deleveraging plan in the hands of a controller serving as interim finance chief.

  14. Slow broadband deters UK home movers, survey finds

    Hyperoptic’s survey suggests broadband is being checked before a move, raising the value of clear availability and fast activation.

  15. The Benchmark Found a Limit. It Did Not Grant a Capacity Claim: RFC 9971

    A network benchmark often arrives in a meeting as a single number. That number then begins doing work it was never designed to do. It is used to imply that a cloud function has production headroom, that a supplier has met an obligation, that a release is safe, or that a customer path will remain within an objective. RFC 9971 offers a more disciplined object: a method for producing comparable results about a stated system under test, under stated traffic and loss goals. It strengthens the number by refusing to let it become a blank cheque.

  16. The Hybrid Signature Arrived. The Verification Rule Still Had to Be Chosen: RFC 9955

    Two signature components can travel together without forcing every receiver to treat them as one indivisible verification event. RFC 9955 makes the distinction useful: a hybrid artifact records a design choice; the receiver's verification rule still decides what was actually checked and what an acceptance means.

  17. Data centre water use could hit 644bn litres

    Rystad says cooling choices could cut 2030 water demand sharply, but some lower-water systems require more electricity.

  18. LACNIC Ratified the Sub-Assignment Rule. An Operating Log Still Needs Its Own Receipt.

    LACNIC records LAC-2025-5 as ratified on 24 March 2026. Its final text calls for a WHOIS link and a public start-and-end movement log for qualifying IPv4 sub-assignments. Those are consequential commitments, but a ratification history is not itself a record of an individual operating event.

  19. Meta data centre could raise Alberta power bills

    Pembina says Meta’s new load could raise wholesale power prices even if the company pays the direct cost of connecting its data centre.

  20. The Queue Found a Flow. It Did Not Find a Culprit: RFC 9957 and DOCSIS QProt

    When a low-latency queue begins to grow, an operator wants a fast answer to a hard question: which traffic should lose the privileged path first? RFC 9957 describes a careful local answer for DOCSIS. It is not an answer to the wider and more tempting questions. A Queue Protection score can support the reclassification of an arriving packet at one queue under one configuration. It does not identify a subscriber, establish intent, diagnose an application, assign end-to-end fault, or instruct the next network to make the same choice.

  21. ITU’s Proposed Video-Traffic Metric Needs a Public Measurement Contract

    One line in ITU’s proposed 2028–2031 strategy would turn the world’s video streams into evidence of institutional impact. The 5 August paper proposes measuring the share of global video traffic carried by ITU-standardized codecs. That may be a useful reach statistic. Yet the public proposal supplies neither a baseline nor the rules required to reproduce the percentage, and it does not explain how use of jointly developed codecs becomes performance attributable to ITU. Before PP-26 adopts the indicator, the number needs a public measurement contract.

  22. The Trusted Host Filled the Password Gap. It Did Not Prove the Host: RFC 1258 and BSD rlogin

    In 1991, BSD rlogin made a familiar promise of convenience. A person sitting at one Unix machine could arrive at another without typing a password again, if the receiving system treated the originating host as trusted. RFC 1258 did not disguise the exchange as a proof ceremony. It recorded a remote-terminal protocol, the fields it carried, and then a caution with unusually clear consequences: one compromised trusted host could open every system configured to accept it. The gap in the password prompt was filled by a local trust decision. It was not filled by proof that the host deserved that trust.

  23. Anthropic reportedly agrees US$35bn Lambda compute deal

    The reported deal depends on Hut 8 delivering Texas capacity before Lambda can turn Anthropic’s commitment into usable compute.

  24. Symbotic's US$22.5bn RPO Excludes Walmart's Conditional 400-System Lane

    Symbotic has US$22.5 billion of remaining performance obligations, but Walmart's promise to purchase 400 store-level automation systems is not in that number. The promise remains contingent on defined performance metrics and could add more than US$5.0 billion to future RPO. Treating the two disclosures as a US$27.5 billion current order book would erase the contract's most important gate.

  25. SMA launches AI data centre power portfolio

    The systems are designed to smooth volatile AI loads before they reach grids or generators, with an 800VDC option planned for 2027.

  26. Ecolab links cooling-loop fill to week-long data centre outage

    A week-long outage linked to the wrong cooling-loop fill shows why coolant verification matters before direct-to-chip systems enter operation.

  27. ARIN-2025-1 Has Two Official Status Labels. Neither Is Adoption.

    One ARIN page records a 25 August Recommended Draft action for ARIN-2025-1. Another places it in the Recommended Draft list while its own status cell says Draft Policy. That public difference is a reason to preserve the record, not a licence to guess which label wins.

  28. The Tunnel Made One Network. Discovery Still Had to Reach Everyone: RFC 1234

    In June 1991, RFC 1234 offered a compact way to carry IPX across an IP internet: place the IPX datagram inside UDP and let an implementation regard the IP internet as one IPX network. It is tempting to read that sentence as a story of effortless unification. The rest of the RFC tells a more exact story. A direct unicast mapping was available for a known IPX host, but the broadcasts through which servers, routers and clients found one another had to be reproduced by separate unicast packets to a hand-maintained list of peers. The tunnel made a common transport. It did not make discovery reach everyone by itself.

  29. Vodafone Idea reaffirms ₹49,000 crore spectrum plan

    The payments rise sharply through FY29 while Vi is also trying to fund a ₹45,000 crore network expansion programme.

  30. The Device Left SCIM. Its Network Access Still Needed a Decision: RFC 9944

    A deleted Device record can settle what a SCIM service will show. It cannot, on its own, settle what a network will enforce. RFC 9944 makes that distinction unusually plain: removal is an application's signal of intent, while a SCIM server and its back-end policy decide whether infrastructure access is revoked.

  31. India reportedly doubles 5G EMF limit to 10W/m²

    The higher ceiling would give operators more radio-power headroom at each site, but coverage gains will depend on how individual networks are designed.

  32. The Map Reached a Router. It Did Not Decide the Path: RFC 9962 and LISP-Decent

    A network can reduce a control-plane dependency and still retain a decision boundary. RFC 9962 makes that distinction unusually visible. It lets LISP Tunnel Routers participate in distributing the EID-to-RLOC mappings they use, rather than leaving all mapping state with a separately managed provider. An authenticated Map-Register can arrive, a Map-Notify can confirm processing, peers can replicate state, and a DNS or multicast mechanism can locate the next mapping function. None of those events decides that the selected locator is reachable from this requester, that the endpoint is the intended counterparty, that traffic will arrive, or that the operator who bears the consequence should use the path.

  33. Compu Dynamics moves AI data-centre construction off-site

    Compu Dynamics is expanding factory-built delivery for AI projects, shifting more power, cooling and white-space work away from the construction site.

  34. ICANN Logged a Javanese LGR Correction—The Final XML Is Still Pending

    One character name separates the rule ICANN put out for comment from the rule its Javanese contributor says was intended. The April draft lets U+A9B4 follow U+A9BA or U+A9BC; the correction substitutes U+A9BB for U+A9BC. ICANN’s 24 August summary records the change and promises community discussion before final incorporation. It does not yet supply the final machine-readable file. That distinction is the news: a correction has entered the governance record, while the artifact that implementers can test remains one state behind.

  35. Nexans qualifies 525kV HVDC repair system for 3,000m

    Nexans has qualified a 525kV HVDC cable and repair joint for 3,000-metre depths on the planned Crete-Cyprus interconnector.

  36. Guidewire's US$5.9m Services Allocation Does Not Change ARR

    Guidewire placed US$5.9 million of recurring licence-and-support or subscription contract value in services revenue during the first nine months of fiscal 2026. Its ARR calculation did not follow that allocation. The distinction is neither an error nor an extra pot of revenue: one measure maps transaction price to performance obligations, while the other preserves the annualised recurring value of active contracts.

  37. The Alarm Changed State. The Cause Still Had to Be Found: RFC 9940 and the Evidence Boundary

    An alert can be prompt, honest and operationally useful without being a verdict. RFC 9940 gives network teams a vocabulary for that restraint: a measurement, an event, a fault, a problem, a suspected cause and a decision are related, but they are not interchangeable.

  38. Subsea Cable Assets launches carousel rental service

    The new service gives subsea contractors temporary access to 4,000- and 6,000-tonne cable carousels, with a first European contract already secured.

  39. Alberta NDP seeks pause on AI data-centre approvals

    Alberta’s NDP wants new AI data-centre approvals paused until the province sets broader rules for assessing project impacts.

  40. The DNS ID Was Zero. The Cache Still Needed a Clock: RFC 9953 and DoC Evidence

    A cache can make a constrained network quieter without becoming the authority that decided what the answer means. RFC 9953 makes that line unusually precise: it lets equivalent DNS-over-CoAP requests share a representation, then requires a separate clock before anyone may rely on it.

  41. Sault Ste. Marie moves to pause data centres above 50MW

    Council has ordered a bylaw for 21 September that would pause applications above 50MW while the city writes rules for large data centres.

  42. Supermicro's US$2.612bn RPO Mirrors Deferred Revenue; Short-Term Backlog Is Excluded

    A US$943.4 million increase in non-refundable product advances helped push Super Micro Computer's contract liabilities to US$2.612 billion. The disclosed remaining performance obligations landed on the same rounded figure, but the RPO disclosure still omits contracts originally expected to last a year or less—so the number is neither a complete order book nor a second pool of customer cash.

  43. ICANN’s Sponsorship RFP Pairs Screening With an Up-to-Twofold Goal

    ICANN is seeking one agency to find sponsors, screen them, sell packages, execute contracts and report the resulting funding. The same request asks for opportunities to reach up to twice the current sponsorship baseline. That combination is not evidence of capture, and ICANN keeps review and stop powers. It does create a governance junction: the initial gatekeeper will also be measured on commercial growth. A two-key authorization receipt could keep the vendor’s recommendation, ICANN’s mission-risk decision and the benefits actually delivered in separate, attributable records.

  44. The Token Named the Chip. It Did Not Decide the Door: RFC 9783 and PSA Attestation Authority

    A signed attestation token can arrive at a policy boundary looking more decisive than it is. Its nonce matches the challenge. Its client identifier is familiar. It describes an instance, an implementation, a lifecycle state and the software components in the measured PSA scope. A portal, broker or service can be tempted to treat that neat packet as a ready-made “yes.” RFC 9783 supplies a more valuable discipline: it specifies protected evidence and the meaning of particular claims. It does not decide whether a relying party should enroll a device, grant access, accept a workload, retain a record or approve an action later in the process.

  45. ARIN’s Caribbean IPv6 Ranking Needs a Source-Coverage Receipt

    The new Caribbean table is useful precisely because it avoids pretending to be a verdict on every network. Its next improvement is equally modest: show which available measurement sources made each jurisdictional average.

  46. Getty Says It Can Pay. A 30-Day Interest Grace Period Is the Plan

    Getty Images has put a clock on a financing decision without saying that it lacks the money to settle it. The company intends to use contractual 30-day grace periods for two interest payments due on 1 September, says it has sufficient cash to pay, and has hired Guggenheim to examine alternatives. The signal is not a default. It is that one month of optionality now matters more than paying on the first available day.

  47. The Contact Lost Its UID. It Did Not Lose Its Boundaries: RFC 9982 and Record Identity Authority

    A contact card without a globally convenient identifier can make a synchronization team uncomfortable. The usual reflex is to manufacture one: a string is easy to add, relational tables prefer stable keys, and downstream software wants a value to point at. RFC 9982 takes a more disciplined position. JSContact 2.0 permits a Card to lack `uid`; when a vCard lacks `UID`, conversion to JSContact 2.0 must not invent one. The absence narrows what a record may safely claim. It does not erase the contact, prove it is a different person, or authorize a system to decide who the record represents.

  48. ICANN Replaced GNSO Charter Review Clocks With Negotiated Timelines

    ICANN’s updated process for amending GNSO Stakeholder Group and Constituency charters is now in force. It adds earlier contact with ICANN org, templates and room for deeper review. It also removes the old process’s public 10-business-day and 30-calendar-day clocks and its Board-meeting backstops. The replacement is a timeline tailored by ICANN org and the affected group. That flexibility can be useful, but it leaves one governance object unspecified: a public receipt showing the agreed schedule, the current phase, who owns the next action and why an estimate changed.

  49. ScanSource Booked US$161m of Recurring Revenue—and 33.7% of Gross Profit

    ScanSource put three figures into its fiscal-2026 record: US$2.88 billion billed by Intelisys suppliers to end users, US$161.209 million of recurring revenue recognised by the company, and 33.7% of total gross profit attributed to recurring revenue. They look like successive stages of one commercial funnel. They are not. Each belongs to a different contractual perimeter, and the distance between them is where the economics of agency distribution actually sits.

  50. APNIC’s Orbit Email Queue Was Delayed for 32 Hours. Its Release Needs a Receipt.

    APNIC has recorded the service window and the stuck email processor. That is a useful notice. It is not yet a public account of the transition from a delayed mailing-list queue to a reconciled delivery record.