Iran sends ceasefire reply; Trump rejects

The story here is diplomacy under fire — literally. Iran sent back an answer to the latest U.S. ceasefire proposal on Sunday, May 10, using Pakistan as the go-between, and President Donald Trump publicly swatted it down almost immediately. That means the war’s political off-ramp is still blocked even though everyone involved has reasons to want one. The result is a ceasefire that exists on paper but looks weaker by the day. ### What actually happened on May 10? Iran delivered its response through Pakistani mediators after the U.S. floated another plan to stop the fighting and open broader talks. Trump then posted that Tehran’s answer was “TOTALLY UNACCEPTABLE!” and did not spell out a new counteroffer. That quick rejection is the news — not just that talks are hard, but that the latest concrete exchange failed almost instantly. (usnews.com) ### Why is Pakistan in the middle? Because Washington and Tehran still do not have a normal, direct negotiating channel that can absorb a crisis like this. Pakistan has been acting as an intermediary in these war-ending talks, passing proposals back and forth when the two sides either cannot or will not do it themselves. That matters because every extra handoff slows things down, and slow diplomacy is a bad fit for a conflict where strikes, ship attacks, and regional flare-ups keep changing the facts on the ground. (usnews.com) ### What did Iran want? The clearest reported sticking point is that Iran’s reply stressed ending the war “on all fronts” and lifting sanctions on Tehran. In plain English, Iran does not want a narrow pause that freezes one battlefield while pressure continues elsewhere through sanctions, proxy clashes, or allied military action. Tehran seems to be asking for a broader package. Trump’s camp, at least publicly, treated that as unacceptable rather than a basis for more bargaining. (usnews.com) ### Why is the ceasefire still described as shaky? Because the diplomacy is lagging behind the violence. By Monday, reports described the truce as increasingly fragile, with recent exchanges of fire, attacks involving ships and Gulf states, and renewed fighting involving Israel and Hezbollah. So this is not a clean ceasefire waiting for paperwork. It is more like a cracked dam — still standing, but under pressure from multiple directions at once. (independent.co.uk) ### Why do markets care so much? Oil traders hear “Iran,” “Gulf shipping,” and “failed talks,” and they immediately think about supply risk. Brent crude moved above $100, with some live market coverage putting it above $105 as the latest rejection deepened fears that the conflict could widen or drag on. That is why this story escapes the foreign-policy page so fast — energy prices can turn a regional war into a global inflation problem. (timesofindia.indiatimes.com) ### What does Beijing have to do with it? Trump is heading into a China trip this week, and Iran hangs over that visit because Beijing has real leverage in the broader regional picture. China is a major player in Iran’s economic and diplomatic environment, so an unresolved war makes the summit more complicated. Instead of arriving with a fresh de-escalation win, Trump now goes to Beijing with an active dispute still sputtering and a peace channel that just failed another test. (financialexpress.com) ### Is this a collapse or just another round? For now, it looks more like another impasse than a final collapse. Both sides are still signaling through intermediaries, which usually means neither wants to slam the door completely. But the catch is simple — every failed exchange raises the odds that events on the battlefield, not negotiators, decide the next move. (timesofindia.indiatimes.com) ### So what’s the bottom line? A ceasefire reply was supposed to be a step toward narrowing the gap. Instead, it showed how wide the gap still is. Iran wants a broader end-state, Trump wants terms he can call a real concession, and the region is still volatile enough that waiting itself is dangerous. (usnews.com) (timesofindia.indiatimes.com)