United Nations Security Council Resolution 1882

United Nations Security Council Resolution 1882 was unanimously adopted on 4 August 2009.

UN Security Council
Resolution 1882
Date4 August 2009
Meeting no.6,132
CodeS/RES/1873 (Document)
SubjectChildren and armed conflict
Voting summary
  • 15 voted for
  • None voted against
  • None abstained
ResultAdopted
Security Council composition
Permanent members
Non-permanent members

Resolution

Parties to armed conflict engaging in patterns of "killing and maiming of children and/or rape and other sexual violence against children" must also be listed in the Secretary-General's reports on children in armed conflict, according to resolution 1882 (2009), adopted unanimously by the Security Council.

The Council action was the culmination of a day-long debate on 29 April during which Secretary-General Ban Ki-moon urged the 15-nation body to "strike a blow against... impunity" by, at a minimum, expanding its criteria to include on the “list of shame", parties committing rape and other serious sexual violence against children during armed conflict.

Before the vote, only state and nonstate parties that had recruited child soldiers or used children in situations of armed conflict were explicitly named, the so-called list of shame, in annexes to the Secretary-General's annual report on the implementation of resolution 1612 (2005), which established a Monitoring and Reporting Mechanism and set up a working group on Children and Armed Conflict.

The reports cover compliance and progress in ending six grave violations: the recruitment and use of children; killing and maiming of children; rape and other grave sexual violence; abductions; attacks on schools and hospitals; and denial of humanitarian access to children. Document S/2009/158 lists 56 such parties, including 19 persistent violators who have been listed for more than four years. [1]

gollark: String interpolation, while quite convenient, can lead to injection things since it's easier than doing things properly with bound parameters or HTML escaping or whatever.
gollark: Well, at least it's not *memory*-unsafe, although it introduces !!FUN!! new problems.
gollark: People can earn money writing COBOL.
gollark: That doesn't make the language good.
gollark: PHP is *fairly* bad, although less so in PHP 7/8.

See also

References

This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.