In a two-part tweet, the premier stated that this was the first-ever meeting over the Kashmir issue in over 50 years by the highest diplomatic forum.
I welcome the UNSC meeting to discuss the serious situation in Occupied Jammu & Kashmir. It is for the first time in over 50 yrs that the world’s highest diplomatic forum has taken up this issue. There are 11 UNSC resolutions reiterating the Kashmiris right to self determination.
— Imran Khan (@ImranKhanPTI) August 17, 2019
He said there are 11 UNSC resolutions reiterating Kashmiri's right to self-determination and the meeting reaffirmed those resolutions.
The prime minister also added that the world body recognised the suffering of the Kashmiri people at the hands of Indian occupying forces.
The PM Imran added that it is the responsibility of the Security Council to resolve the dispute.
And the UNSC meeting was a reaffirmation of these resolutions. Therefore addressing the suffering of the Kashmiri people & ensuring resolution of the dispute is the responsibility of this world body.
— Imran Khan (@ImranKhanPTI) August 17, 2019
UNSC meet negates Indian claim of IOK being 'internal matter': Qureshi
India’s envoy to the UN Syed Akbaruddin on Friday admitted that Indian-Occupied Jammu and Kashmir was a disputed territory and New Delhi was conditionally ready to engage with Islamabad over the matter.
India has regularly blocked discussion on Occupied Kashmir at the UN because it considers the matter an ‘internal affair’.
After coming into power last year, Prime Minister Imran Khan had extended an olive branch to his Indian counterpart Narendra Modi on multiple occasions, however, India never responded positively.
Foreign Minister Shah Mahmood said India endeavoured to block the UNSC meet but to no avail, adding that the international community had rejected India’s stance on Kashmir being its “internal matter”. Rather, he added, it had been recognised as an international conflict.
COMMENTS
Comments are moderated and generally will be posted if they are on-topic and not abusive.
For more information, please see our Comments FAQ