Kremlin Confirms Next Round of Russia-Ukraine Talks in Abu Dhabi
Speaking at a press briefing in Moscow, Peskov said the talks, initially scheduled for February 1, were postponed to accommodate the schedules of all participants. "Indeed, Wednesday-Thursday, this second round will take place. In Abu Dhabi, this, too, we can confirm," he said.
Ukrainian President Volodymyr Zelenskyy had announced on Sunday that the previously scheduled February 1 talks were rescheduled for February 4-5.
On the progress of the negotiations, Peskov noted: "On some issues, we have clearly progressed because there were discussions and conversations, and on some issues, it is easier to find common ground." He added that on other issues, reaching agreement remains difficult: "Unfortunately, convergence cannot yet be confirmed there."
When asked about the status of the energy truce, Peskov replied: “I have nothing to add to what I told you at the previous conference call, where we talked specifically about Feb. 1.” Last week, he confirmed that Russia accepted US President Donald Trump’s proposal not to target Ukraine’s energy infrastructure to create favorable conditions for the Abu Dhabi talks.
Regarding a potential meeting between Zelenskyy and Russian President Vladimir Putin, Peskov reiterated the invitation for the Ukrainian leader to visit Moscow.
Legal Disclaimer:
MENAFN provides the
information “as is” without warranty of any kind. We do not accept
any responsibility or liability for the accuracy, content, images,
videos, licenses, completeness, legality, or reliability of the information
contained in this article. If you have any complaints or copyright
issues related to this article, kindly contact the provider above.
Legal Disclaimer:
EIN Presswire provides this news content "as is" without warranty of any kind. We do not accept any responsibility or liability for the accuracy, content, images, videos, licenses, completeness, legality, or reliability of the information contained in this article. If you have any complaints or copyright issues related to this article, kindly contact the author above.
