US Ambassador David Hale calls on army chief General Qamar Bajwa at the GHQ in Rawalpindi on Monday. PHOTO: ISPR
In a meeting with Hale at the GHQ in Rawalpindi on Monday, both the COAS and the US ambassador reiterated their nations’ commitment to a secure, stable, and prosperous Afghanistan, said a statement issued by the US Embassy Islamabad.
#PressRelease: 🇺🇸 #AmbHale meets with 🇵🇰 Chief of Army Staff General Qamar Javed Bajwa >> https://t.co/IzRORMNZRS pic.twitter.com/2FTbb2Eywk
— U.S. Embassy Islamabad (@usembislamabad) May 22, 2017
Iran accuses US of 'Iranophobia', arming 'dangerous terrorists'
Ambassador Hale, the communique said, reiterated US President Donald Trump's call during his recent speech at the Arab-Islami summit for a vision of peace, security, and prosperity, and unity in conquering extremism and terrorism.
“Ambassador Hale affirmed Pakistan’s role and great sacrifices in this effort,” it said.
A similar statement was released by the Inter-Services Public Relations (ISPR), which said that the US ambassador acknowledged Pakistan Army's efforts in securing control of areas on Pakistan side of the border.
PR274/17
— DG ISPR (@OfficialDGISPR) May 22, 2017
US Amb met COAS."Our soil is not being used for T activities agnst any other cty nor 'll we tolerate any such action angst Pak"COAS pic.twitter.com/iA84m4Wa0A
“Both the countries can carry forward the work done towards enduring peace and stability in the region through enhanced coordination and cooperation,” the military media wing quoted Hale as saying.
The army chief also made it clear that no cross-border attack shall be tolerated by Pakistan.
Islamabad blames Kabul for hosting Jamaatul Ahrar and other militants responsible for carrying out a wave of attacks in February that killed 130 people across the country and prompted fears of a militant resurgence.
Afghanistan also routinely accuses Pakistan of providing safe haven to the Afghan Taliban.
COMMENTS (3)
Comments are moderated and generally will be posted if they are on-topic and not abusive.
For more information, please see our Comments FAQ