After Pakistan, Iran summons Afghan envoy for 'disrespecting' national anthem

Afghan delegate cites Taliban's ban on public music as the reason for remaining seated


News Desk September 20, 2024
The flag of Iran is seen over its consulate building, with Pakistan's flag in the foreground, in Karachi, Pakistan January 18, 2024. PHOTO: REUTERS

Iran has summoned the acting head of Afghanistan’s embassy following an incident where an Afghan official remained seated during the playing of Iran's national anthem at a conference on Islamic unity in Tehran. 

This incident echoes a similar occurrence just days earlier in Pakistan, where Afghan officials faced backlash for not standing during the Pakistani national anthem.

In Tehran, the Iranian foreign ministry lodged a “strong protest” against the Afghan representative's actions, describing them as “unconventional and unacceptable.” The ministry stressed the importance of respecting national symbols and condemned the incident as a violation of diplomatic custom. 

The Afghan delegate, while apologising, cited the Taliban's ban on public music as the reason for remaining seated, stating that it was their custom to do so.

This incident in Iran came shortly after Pakistan summoned the Afghan charge d’affaires over similar disrespect shown by Afghanistan’s acting consul general and another official during an event in Peshawar. 

Pakistani officials reported that the Afghan representatives did not stand during their national anthem due to cultural prohibitions regarding music, clarifying that no disrespect was intended.

The Foreign Office spokesperson in Pakistan condemned the Afghan officials' actions as contrary to diplomatic norms and reiterated the necessity for guests to honour the symbols of their host country. 

Both Iran and Pakistan have expressed their grievances, conveying strong protests to the Afghan authorities in Kabul and Islamabad.

COMMENTS

Replying to X

Comments are moderated and generally will be posted if they are on-topic and not abusive.

For more information, please see our Comments FAQ