March 2022 - members-discuss - mailman.ripe.net

RIPEdb registry need to be ready for separating?
by Serg Galat 01 Apr '22

01 Apr '22

Dear colleagues, I found some strange scheme - https://twitter.com/EvgeniiBender/status/1502709009408835589?s=20&t=PSGBvgc… If this is true, Russian LIR must be already registered in those structures. Can anyone confirm or disprove the existence of such events? -- Sergey

8 21

Legal compliance doubts
by Stary Bezpiek 31 Mar '22

31 Mar '22

W dniu 19.03.2022 o 06:59, Taras Heichenko pisze: > Peace. > > I am glad to see that RIPE NCC is legally clean. There are questions about humanism but of course this is not a cope of work of RIPE NCC. In my opinion - it is not. RIPE NCC claims to operate in accordance with its own policies, that are created by the community. Meanwhile, we have a selective treatment of Members in terms of payments without: a) RIPE NCC resolutions b) without annexes to contracts with users. c) policy change Neither the Agreement nor the existing policies allow for discretionary behavior like "this user may not pay, and others must" without formal authorization. Of course Ukraine as an attacked country can and must be treated with any aid, including exemption from payments, when possible. But it has to be passed by a resolution of the RIPE NCC ordinance. The resolution may contain one sentence: "We do not issue invoices to Ukrainian members until the end of the war." Vote: who is in favor? All? The End. On the other end is Russia, as a country that has been subject to sanctions. It should not be of our interest, that they cannot pay. In result, recognizing that Russia users may not pay, because they have "banking difficulties" means, that no one from Russia will pay. Without any consequences. Although they probably can pay. Letting go at this point is very unfair to other Members. I also have a difficult in payment because the Euro exchange rate is very high. Does it interest someone? -- Stary Bezpiecznik

7 11

RIPE NCC Quarterly Planning Q2 2022
by Fergal Cunningham 31 Mar '22

31 Mar '22

Dear RIPE NCC members, We have now published our Q2 2022 plans for our development teams. These are available at: https://www.ripe.net/support/documentation/quarterly-planning Our quarterly planning includes the work we will be carrying out in the next few months in: - RPKI - Learning & Development - RIPE Database - Business Applications, including the LIR Portal, Registry Services and other applications. - DNS and K-root (new this quarter) - RIPE Atlas (new this quarter) - RIPEstat (new this quarter) - RIS (new this quarter) - Information Technology and Security (new this quarter) If you have any input on our plans or want to let us know what you would like to see the RIPE NCC work on, please let us know. See the specific plans for details on where to provide input to the relevant teams. Finally, our staff will be attending RIPE 84 in Berlin (in person and online) if you want to discuss any of our services and how they should develop: https://ripe84.ripe.net/ Kind regards, Fergal Cunningham Head of Membership Engagement RIPE NCC

1 0

WARNING! attempts at delivering malware from this mailing list
by Andrzej Ława 30 Mar '22

30 Mar '22

As I was afraid Russian agents are trying to distribute malware using data from this mailing list (links to onedrive.com to download something). In last days I've received at least two spoofed e-mail pretending to be from this mailing list quoting my older posts in this mailing list - thus it has to be an attempt from someone who has access to this mailing list. The offending IPs are: 62.3.58.13 and 193.233.207.195 (originating mail IPs, both geolocated in Russian Federation) I say again: both spoofed e-mail were quoting my older mails on this mailing list and attempting to pretend to be responses to my inquiries (one "personal information" and one "you can pay here for your LIR membership"). Thus the perpetrator has to be a LIR, not just a user of those operators. What are the RIPE rules regarding LIRs trying to send other LIRs malware? -- Regards Andrzej Ława tel. 500 206 268 DAWIS IT Sp. z o.o., 05-800 Pruszków, ul. Staszica 1 NIP 5342409456 / REGON 141663620/ KRS 0000319237

2 1

Re: [members-discuss] WARNING! attempts at delivering malware from this mailing list
by Antony Gollan 30 Mar '22

30 Mar '22

Dear Andrzej, Thank you for your email. We have also noticed this and we recently sent an announcement to the membership: https://www.ripe.net/ripe/mail/archives/ncc-announce/2022-March/001563.html Members can always alert us to potential security incidents at <security(a)ripe.net>. Kind regards Antony Gollan Communications Team Manager RIPE NCC **** > As I was afraid Russian agents are trying to distribute malware using data from this mailing list (links to onedrive.com to download something). > In last days I've received at least two spoofed e-mail pretending to be from this mailing list quoting my older posts in this mailing list - thus it has to be an attempt from someone who has access to this mailing list. > The offending IPs are: > 62.3.58.13 > and > 193.233.207.195 > (originating mail IPs, both geolocated in Russian Federation) > I say again: both spoofed e-mail were quoting my older mails on this mailing list and attempting to pretend to be responses to my inquiries (one "personal information" and one "you can pay here for your LIR membership"). Thus the perpetrator has to be a LIR, not just a user of those operators. > What are the RIPE rules regarding LIRs trying to send other LIRs malware? > -- > Regards > Andrzej Ława > tel. 500 206 268 > DAWIS IT Sp. z o.o., 05-800 Pruszków, ul. Staszica 1 > NIP 5342409456 / REGON 141663620/ KRS 0000319237

1 0

Re: [members-discuss] RIPEdb registry need to be ready for separating?
by Andrzej Ława 24 Mar '22

24 Mar '22

W dniu 15.03.2022 o 11:52, Daniel Kalchev pisze: >> So please convince me what is the better course of action. > > You essentially want someone else to take responsibility for your own choices and actions. Sorry, but what have you got against an open debate, weighing options and considering multiple aspects of an issue by multiple people from multiple points of view? I am not an omniscient super-genius - nobody is (duh!) - thus a calm debate weighing all the options considering all available data is the best way to evaluate what is the best solution. Wouldn't you agree? > This might, or might not work. It never works long term. What might work or not? A debate? It seems calm debate considering all options and facts is the best long term solution. > The Internet community has been working for decades to keep the Internet unified, and especially the IP and DNS registries be unique and unambigous. I know that. Yet there we are - in a situation where governments want to enforce their own DNS entries. > This is by far not the first time we face such callenge… all previous times were caused > by friendly enterpreneurs from “our side”. It was stopped at great cost (manhours spent > of thousands of people worldwide to talk it over). Unfortunately some entities are not capable of talking honestly and in good faith. > There is nothing wrong in Russia setting up their own “mirror” of any registry. > As long as we do not cut them from the “original” this is ok and might be for > the benefit of everybody. Actually, some European countries have been doing this > ever since we had Internet — you probably just didn’t know. The problem is those are not mirrors - those are fakes. I.e. the Polish regulation (supposedly only to be used to block only gambling sites but is implemented as an administrative decision without any judiciary oversight) is frighteningly similar to what Russia is planning to do with their DNS "mirrors". Not a big problem over here as it is easy for any end user to circumvent... until the government blocks all "foreign" DNS systems (i.e. forces all ISPs to block access to any foreign DNS). > Internet registries are not about politics. If you want your registry to stay stable > and not be “fixed” after the next elections, just stay away from politics. This can’t be stressed enough. Please explain that not to me but to the Russian (and sadly not just Russian) government. > Filtering penetration attempts is an entirely different topic, nothing to do with RIPE (as registry). > Everyone does it. It happens all the time and has not increased following recent events. Not only this, > but most of those “Russian and Chinese” computers are just victims of someone hacking them. > Not only that someone might not be Russian or Chinese, but since these are automated scripts they might not even know they attack you in particular. Suuuuure. > The right thing to do here is for the RIPE NCC to continue to work with the Russian registries, to make sure they are not diverging. Unfortunately if their government decides they want to diverge - there's nothing we can really do, can we? -- tel. 500 206 0268 DAWIS IT Sp. z o.o. z siedzibą w Pruszkowie Adres: ul. Staszica 1, 05-800 Pruszków KRS 0000319237 I NIP 5342409456 I REGON 141663620

3 4

LIR invoices for Ukrainian companies
by Max Tulyev 14 Mar '22

14 Mar '22

Hi All, as you now there is a huge russian military invasion in Ukraine. The communications, especially Internet access, is one of the most important things during this time. Unfortunately, almost all ISPs facing with a financial impact of war because of non-payment crisis. A thousand of Euros is a huge money now even for big companies. I think it is a good idea to support Ukrainian ISPs and postpone payments for LIR for them until the end of the war. Please, do support of this proposal. Thank you all!

42 47

Annual contribution payment options
by Alexey S. Berezhnev 11 Mar '22

11 Mar '22

Dear colleges, I would like to discuss the possibility to pay up RIPE NCC bills (annual contribution, to be more specific) in other currencies, than EURO. I can assume, as per the latest actions of the currency regulator - Central Bank of Russia, there is a chance that outgoing payments in EURO will be either impossible, or will be performed with double conversion with high commission at each step for Russian LIR holders. This will double the expense, of Russian LIRs. Not to mention, that payments made by sponsoring LIR significantly exceed regular contribution for an obvious reason. Therefore, I suggest the following measures to be discussed. 1. Break payments into quarters for Russian LIRs, and yet perhaps, we will overcome the limits set by central bank until Sept 9, 2021 2. Make it possible for the annual contribution to be made USD, etc. by prevailing cross-rate. 3. Evaluate the possibility to accept cryptocurrency (ETH, BTC, and etc). This post is totally about financial problems to be discussed, and therefore I kindly ask other members to avoid any political statements in this thread. -- ------ Alexey S. Berezhnev Office: +7 495 973 21 25

9 13

A request to terminate ENOG
by Töma Gavrichenkov 11 Mar '22

11 Mar '22

Peace, (which is my usual greeting message, always was, and will ever be, — because the only thing I've always valued the most is peace) As the Programme Committee Chair of the Eurasian Network Operators Group (ENOG), I, hereby, with all due respect, request that the RIPE Executive Board formally dissolve ENOG and cancel all the potential future meetings indefinitely. Rationale: ENOG was founded in 2011 per the decision of the RIPE Executive Board, and it was assumed to be incorporating Ukrainian, Russian, Belarusian, Armenian, Azerbaijanian, and many other regional communities in the hope of building a better shared Internet space among the communities. In view of the recent events (if not even the prior events), the said "ENOG community" does not exist anymore, and in no way it could be clear to the Programme Committee how to arrange a programme for all the distinct and divided communities colloqually recognized as ENOG at the time. Technically, under normal circumstances, a request like this should've gone through a voting process in the PC; however, we currently have several PC members under ongoing _missile attacks_, and I therefore don't believe it is sane to arrange any vote in the PC. Additionally, at the moment, being a Russian citizen, I don't believe I should assume there's a consensus in the entire RIPE Service Region to still invest trust in me, without further due diligence, to hold any official community position in the RIPE community; therefore, I hereby step down as the PC Chair. It's now up to the members of the RIPE NCC Executive Board to decide on future actions, and I urge the RIPE NCC Executive Board to act. It is entirely up to the RIPE NCC Executive Board to consider any future alignments to replace ENOG. Stay safe. -- Töma

31 50

Reply: Re: Annual contribution payment options
by alex 10 Mar '22

10 Mar '22

Crypto currency is being widely used at ip exchanges. Why would RIPE NCC avoid them? > Hi, > > On Thu, Mar 10, 2022 at 01:10:58AM +0300, Alexey S. Berezhnev wrote: > > 3. Evaluate the possibility to accept cryptocurrency (ETH, BTC, and etc). > > I strongly reject any use of proof-of-work based cryptocurrencies > in the RIPE NCC context (or anywhere else, but do not get to vote there). > > Gert Doering > -- LIR representative > -- > 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

4 3