Skip to content
Briefings are running a touch slower this week while we rebuild the foundations.See roadmap
European Tech Sovereignty
17MAY

Russia GL-134B extended as Iran GL-U lapses

3 min read
14:28UTC

Treasury signed a seaborne-oil waiver for Russia to 16 May on the same Saturday it allowed the parallel Iranian authorisation to expire, producing a Russia-yes, Iran-no asymmetry in signed US policy text.

TechnologyDeveloping
Key takeaway

Treasury's 19 April paperwork draws the Russia-yes, Iran-no line into signed policy text for the first time.

The US Treasury extended GL-134B, the OFAC General License authorising Russian seaborne-oil transactions, to 16 May 2026 on the same calendar day Iran's GL-U was allowed to lapse 1. Treasury Secretary Scott Bessent oversees both files; either renewal could have been declined or signed at his discretion. Treasury's choice to sign one and not the other on a single Saturday produced a policy act rather than a scheduling artefact.

Russia's side of the ledger had a readable expiry. GL-134A expired on 11 April and an extension had been widely expected since ; Treasury's silence between 14 April and 19 April made the asymmetry predictable rather than surprising . When Treasury did break silence, it broke it only for Russia. GL-134B now covers Russian seaborne-oil transactions through 16 May; GL-U covers no Iranian tanker past midnight Washington time.

For crude buyers, Saturday's paperwork produces a legally two-tier oil market. An Indian state refiner loading Russian crude this week retains signed cover under GL-134B; the same refiner loading Iranian crude loses it under the GL-U lapse and picks up secondary-sanctions exposure. The instruments governing the two flows are no longer symmetrical, and the asymmetry is now on paper that compliance Teams, banks and foreign ministries can read without interpretation.

Deep Analysis

In plain English

Sanctions are legal rules that say 'you cannot do business with country X without special permission.' The US government grants those permissions through documents called General Licenses. On 19 April, the US did two things at the same time. It let Iran's special permission expire ; meaning ships carrying Iranian oil are now operating without legal cover. And it extended Russia's special permission through 16 May, meaning ships carrying Russian oil are still fully legal. Both decisions came from the same department ; the US Treasury ; on the same day. It is the first time US government documents show Iran and Russia being treated this differently at exactly the same moment, written into official text anyone can read.

Deep Analysis
Root Causes

GL-134B's extension to 16 May reflects the Trump administration's Ukraine-theatre calculus: ratcheting Russia energy sanctions during active Ukraine ceasefire diplomacy would remove leverage and signal bad faith to Moscow. Treasury's operational logic is to keep Russia sanctions pressure below the threshold that collapses ongoing talks.

The asymmetry's structural root is that GL-U and GL-134B were on different legal tracks from inception: GL-U was a war-emergency bridge instrument with a hard sunset; GL-134B was a rolling Russia waiver maintained across multiple renewal cycles. The same OFAC desk renewed one and allowed the other to lapse ; a decision that appears in the Federal Register as simultaneous administrative actions taken on the same calendar day.

What could happen next?
  • Precedent

    The first signed Russia-yes Iran-no asymmetry in US sanctions policy text gives trading partners a legally verifiable basis to distinguish their Russian and Iranian crude exposure.

    Immediate · 0.9
  • Consequence

    Countries like India that buy both Russian and Iranian crude face a regulatory wedge: maintaining Russian purchases while scaling back Iranian ones to avoid secondary-sanction exposure.

    Short term · 0.78
  • Risk

    If GL-134B's 16 May extension lapses without renewal while Iran negotiations remain unresolved, both Russian and Iranian crude simultaneously lose US legal cover ; a compound supply shock not yet priced by markets.

    Medium term · 0.62
First Reported In

Update #73 · Russia yes, Iran no: Treasury signs only one waiver

The White House· 19 Apr 2026
Read original
Different Perspectives
OpenForum Europe / open-source community
OpenForum Europe / open-source community
The EUR 350m Sovereign Tech Fund has no Commission host, no budget line, and no commissioner's name attached six weeks after the April conference, while Germany is already paying maintainers to staff international standards bodies. The CRA open-source guidance resolves contributor liability but leaves the financial-donations grey area open with the 11 September reporting clock running.
ASML / Christophe Fouquet
ASML / Christophe Fouquet
ASML's Q2 guidance miss of roughly EUR 300m below consensus reflects DUV revenue compression set by US export controls, not European policy. Fouquet said 2026 guidance accommodates potential outcomes of ongoing US-China trade discussions; a bipartisan US bill to tighten DUV sales further would accelerate the cross-subsidy thinning Chips Act II's equity authority is designed to address.
Anne Le Henanff / French G7 Presidency
Anne Le Henanff / French G7 Presidency
Le Henanff chairs the 29 May Bercy ministerial two days after Brussels adopts the Tech Sovereignty Package, making the G7 communique the first international read of the Omnibus enforcement split and CAIDA's scope. France's Cloud au Centre doctrine is already operational via the Scaleway Health Data Hub contract.
German federal government
German federal government
Berlin operationalises sovereignty through procurement mandates (the ODF requirement and the Sovereign Tech Standards programme) rather than waiting for Commission legislation. The Bundeskartellamt has still not received the Cohere-Aleph Alpha merger filing, leaving Germany's flagship AI champion in structural limbo six weeks after the deal resolved.
US Trade Representative
US Trade Representative
The USTR Section 301 investigation into EU digital rules closes with a 24 July 2026 final determination. CAIDA's public-sector cloud restriction sits within the criteria that triggered the 2020 Section 301 action against France's digital services tax, and the US has not signalled whether the Thales-Google S3NS arrangement resolves CLOUD Act jurisdiction concerns.
CISPE / Valentina Mingorance
CISPE / Valentina Mingorance
CISPE shipped its own pass-fail sovereignty badge in April to establish an industry-auditable floor the Commission could adopt. Whether CAIDA inherits the CISPE binary or the multi-tier SEAL approach will determine whether certification is enforceable by public contracting authorities or requires Commission discretion.