Trender
Iran
Mike Johnson
War Powers Act
US Foreign Policy
Congress
Middle East

Speaker Johnson Says the U.S. Is 'Not at War' With Iran—But a 60-Day Clock Is Running

By · Published · Updated · 3 min read
Speaker Johnson Says the U.S. Is 'Not at War' With Iran—But a 60-Day Clock Is Running

Speaker Johnson Says the U.S. Is 'Not at War' With Iran—But a 60-Day Clock Is Running

Speaker Mike Johnson has publicly stated that the United States is "not at war" with Iran, even as a legally significant 60-day deadline tied to U.S. military strikes looms. The distinction matters enormously—not just rhetorically, but constitutionally.

What the 60-Day Deadline Actually Means

The clock Johnson is navigating comes from the War Powers Resolution of 1973, a law designed to limit a president's ability to commit U.S. forces to armed conflict without congressional authorization. Under the resolution:

  • The president must notify Congress within 48 hours of introducing military forces into hostilities
  • Once notified, Congress has 60 days to authorize the action—or the president must withdraw forces
  • If Congress does neither, the president gets an additional 30 days to complete withdrawal

Following U.S. military strikes on Iranian-backed targets—and, more significantly, direct strikes on Iranian soil targeting nuclear facilities—the 60-day window began ticking. Johnson's statement appears designed to argue that the strikes don't constitute an ongoing "war" requiring formal congressional authorization.

Why Johnson's Framing Is Legally Contested

The argument that the U.S. is "not at war" with Iran is a familiar executive-branch maneuver, but legal scholars and opposition lawmakers aren't buying it cleanly. Here's why the framing is under scrutiny:

  • Strikes on Iranian territory are categorically different from strikes on proxy forces in Yemen or Iraq—they represent direct engagement with a sovereign nation
  • The War Powers Resolution doesn't require a formal declaration of war to trigger its clock; "hostilities" is the operative word, and courts have generally deferred to Congress on that definition
  • Democratic lawmakers and some Republicans have argued that without a new Authorization for Use of Military Force (AUMF), the president is operating outside legal bounds
  • Johnson's position effectively shields the executive branch from having to seek a formal vote—a vote that could be politically damaging or fail outright

What's Actually at Stake

The 60-day question isn't just procedural. It forces a reckoning on several fronts:

Escalation risk: Iran has signaled willingness to negotiate on its nuclear program, but domestic hardliners in Tehran are using the strikes as justification for accelerating enrichment. A congressional debate could either constrain or greenlight further action.

Diplomatic window: Talks between U.S. and Iranian officials have continued through intermediaries. Johnson's "not at war" framing may be partly tactical—preserving diplomatic flexibility by avoiding the legal and political weight of a formal war footing.

Congressional authority: If Congress allows the deadline to pass without acting, it sets another precedent for executive unilateralism in military affairs—a pattern critics across the political spectrum have warned about for decades.

The Bottom Line

Whether or not the U.S. is technically "at war" with Iran depends heavily on who's doing the defining—and right now, Speaker Johnson wants that definition to stay vague. The 60-day deadline forces the issue into the open, and how Congress responds (or fails to) will shape both the immediate military situation and the long-term balance of war-making power in Washington.

View all posts