Iran warns on nuclear cooperation

September 17th, 2008 By: Michael van der Galien | Tags:
Iran warned on Tuesday it will not respond to every adverse claim about its nuclear drive, after a damning report from the UN atomic watchdog left the global community divided about future action.

Amid continuing fears that one response might be a US or Israeli strike on Tehran’s nuclear programme, a top aide to Iran’s supreme leader again raised the specter that his country could bring oil shipments from the Gulf to a halt if attacked.

“We are against offering the agency an open door once more and that they expect Iran to respond to any claim,” said Alaeddin Borujerdi, head of parliament’s national security and foreign affairs commission…

Iran’s envoy to the UN atomic agency also warned that Tehran would only cooperate within the framework of the nuclear Non-Proliferation Treaty and its safeguard agreements.

“We continue cooperating with the IAEA but they should not expect us to apply the additional protocol,” Ali Asghar Soltanieh told state television.

Of course they shouldn’t After all, it’s not like the UN should pursue a policy that would actually prevent you guys from developing nuclear weapons, right?

And so, while Americans are focused on their own elections… which will take place in November, Iran continues to defy the West and to produce nuclear weapons.

But lets talk about that ad. That nasty one!

Share and Enjoy:
  • Digg
  • del.icio.us
  • Technorati
  • SphereIt
  • NewsVine
  • TailRank
  • Reddit
  • StumbleUpon
  1. Interested
    September 17th, 2008 at 06:17
    Reply | Quote | #1

    Iran won’t stop shipments of oil, and Europe will play their spineless roll as usual with Russia enjoying the conflicted region.

    Iran won’t do much of anything until a new US Prez is elected and then they’ll provoke to see if the new Prez will be as spineless as Europe or not.

  2. Interested
    September 17th, 2008 at 06:18
    Reply | Quote | #2

    er role not roll

PoliGazette Comments Policy

PoliGazette encourages comments from all viewpoints, especially those that disagree. Comments submitted must, however, adhere to the following standards. Comments that violate these standards may be edited or deleted without notice at the sole discretion of the editors. Commenters who repeatedly or egregiously violate these standards or who attempt to argue publicly with editors regarding the comments policy may be banned from commenting further.

(1) Comments should address the substantive content of the post. Comments that repeatedly or blatantly misrepresent the content of the post or of others' comments are not welcome. Comments that respond to something other than which the contributor or commenter may have said are irrelevant and should not be posted.

(2) Comments should avoid vulgarity as well as racial, ethnic, religious, or sexual bigotry.

(3) Comments should not personally attack the character, personal integrity, or professional reputation of any PoliGazette contributor or of other commenters.

(4) Comments should reflect the contributions of the commenters themselves and should not include extensive cut-and-paste reproductions of others' words except insofar as necessary to supplement the commenter's own arguments. Link spam, trackback spam, and propaganda spam will be instantly deleted.

(5) Public figures are considered open to all substantive criticism of their policies and statements. Comments that present objectively false factual information about public figures (i.e. "Obama is a Muslim") or that attack public figures by attacking their families are not welcome. Comments that merely repeat slogans for or against a candidate without engaging in substantive comment are not welcome.

Questions or challenges to these policies or their application should be directed to the editors by email only.


Warning: is_writable() [function.is-writable]: open_basedir restriction in effect. File(error_log) is not within the allowed path(s): (/home/p6525pol:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/p6525pol/public_html/wp-includes/wp-db.php on line 500