<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> <meta name="Generator" content="Microsoft Word 15 (filtered medium)"> <style></style> </head> <body lang="en-DE" link="blue" vlink="purple" style="word-wrap:break-word"> <div class="WordSection1"> I don’t think the extend of sanctions compliance needs to be discussed. Obviously the RIPE NCC will need to comply with EU sanctions in full.<o:p></o:p> <o:p> </o:p> An explanation from RIPE’s legal team on who will be affected may be useful, but I don’t think there would be a lot of value in a meeting as few aspects of this are under the community’s (or the RIPE NCC’s) control.<o:p></o:p> <o:p> </o:p> Regarding “We all know now that EU banks will not allow the collection of the 2022 RIPE NCC fees from Russia, and invoices are due in a few days.”, I don’t think this is true. There would be issues where payers or their banks are involved in sanctions, but not for unrelated Russian entities. <o:p></o:p> <o:p> </o:p> Matthias Merkel<o:p></o:p> Staclar, Inc.<o:p></o:p> <o:p> </o:p> <div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm"> From: address-policy-wg <address-policy-wg-bounces@ripe.net> on behalf of Mathias Westerlund <mathias.westerlund@wdmab.se> Date: Saturday, 26. February 2022 at 19:39 To: Thomas Brenac IPv4 Broker <thomas@brenac.eu> Cc: Alexey Shkittin <alexey.shkittin@interlir.com>, RIPE Address Policy Working Group <address-policy-wg@ripe.net>, Gert Doering <gert@space.net> Subject: Re: [address-policy-wg] Block/Suspend sanctions on address space.<o:p></o:p> </div> <div> <div> I have to say, even tho we are a new entity, we do support the calling of a potential emergency meeting to alteast discuss this. <o:p></o:p> </div> RIPE is an EU entity. We need to be clear on what levels we are following EU sanctions.<o:p></o:p> </div> <o:p> </o:p> <div> <div> On Sat, Feb 26, 2022 at 5:35 PM Thomas Brenac IPv4 Broker via address-policy-wg <<a href="mailto:address-policy-wg@ripe.net">address-policy-wg@ripe.net</a>> wrote:<o:p></o:p> </div> <blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm"> Gert mentioned, '' NCC already does this - if a country is officially sanctioned by the EU (it can not opt to not-do this, anyway, if there is a legal requirement)'' Indeed, we can see in <a href="https://www.ripe.net/publications/docs/ripe-776" target="_blank"> https://www.ripe.net/publications/docs/ripe-776</a> ''As an organisation based in the Netherlands, the RIPE NCC must comply with EU sanctions. If we believe that a member or other resource holder is subject to EU sanctions, we freeze their resources in the RIPE Database'' As several Russian LIR starting with Yandex (exemple) do have a clear, publicly known, relationship / shareholders with sanctioned Russian individuals and Russian entities, as a LIR member I do suggest that RIPE NCC hold a proper emergency meeting on the matter. The report is made quarterly. There is now a situation of emergency that need a quick due diligence on the application of the EU sanctions on the resources hold by the Russian entities concerned by the EU sanctions, including transfer policy, access to RIPE database and services, routing, RDNS etc etc. and hopefully with more impact that the one mentioned in the last report. We all see the important use of allocated resources for massive DoS and other attacks, RIPE NCC shall support a clear limitation and use of the RIPE NCC services and resources of the Russian, Byelorussian LIRs (that are directly or indirectly , Byelorussian, Russian state owned or owned by listed sanctioned individuals). Side note: We all know now that EU banks will not allow the collection of the 2022 RIPE NCC fees from Russia, and invoices are due in a few days. That is a good reason to freeze the resources a bit faster that usual. Taken into account the number of LIR that could also impact the whole budget for 2022, and I'm not sure the rest of the community will be happy to support... Again, we need to see a quick reaction from RIPE NCC, within days, not on a quarterly basis. Thank you. ______________________ Thomas BRENAC CEO <a href="https://www.brenac.eu" target="_blank">https://www.brenac.eu</a> <<a href="https://www.brenac.eu/" target="_blank">https://www.brenac.eu/</a>> +33686263575 Registered IPv4 Broker by RIPE NCC, ARIN, APNIC and LACNIC, Member of AFRINIC. On 26/02/2022 10:07, "address-policy-wg on behalf of Gert Doering" <<a href="mailto:address-policy-wg-bounces@ripe.net" target="_blank">address-policy-wg-bounces@ripe.net</a> on behalf of <a href="mailto:gert@space.net" target="_blank">gert@space.net</a>> wrote: Hi, On Sat, Feb 26, 2022 at 08:44:35AM +0100, Alexey Shkittin wrote: > *Block/Suspend sanctions on address space.* > > Based on events with Russian aggression on Ukrain. > > Policy Proposal for discussion. > > Update RIPE NCC policy in according to be able suspend management of > internet resource numbers in RIPE NCC database of the countries under > Sanctions in EU/US. NCC already does this - if a country is officially sanctioned by the EU (it can not opt to not-do this, anyway, if there is a legal requirement). See here, for example, for the Q1 2022 sanctions transparency report: <a href="https://www.ripe.net/publications/docs/ripe-776" target="_blank">https://www.ripe.net/publications/docs/ripe-776</a> Gert Doering -- NetMaster -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard, Michael Emmer Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279 -- To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: <a href="https://mailman.ripe.net/" target="_blank"> https://mailman.ripe.net/</a> -- To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: <a href="https://mailman.ripe.net/" target="_blank"> https://mailman.ripe.net/</a><o:p></o:p> </blockquote> </div> </div> </body> </html>