This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/members-discuss@ripe.net/
[members-discuss] RIPEdb registry need to be ready for separating?
- Previous message (by thread): [members-discuss] RIPEdb registry need to be ready for separating?
- Next message (by thread): [members-discuss] RIPEdb registry need to be ready for separating?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Andrzej Ława
andrzej.lawa at dawis-it.pl
Fri Mar 18 23:52:16 CET 2022
>>> 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? > > Well.. our governments appear to want that Russia gets isolated and diverge. > What can we do? Change our governments? You don't seem to get it - it is the Russian government that is implementing steps to get isolated and diverged - among others - from RIPE database. So please stop with posing questions based on fiction and express your honest opinion and arguments what would be the best course of action here and now in real world to maintain the network operation and neutrality in the face of what Russia is doing or attempting to do. Frankly what you wrote makes me lean toward the total cut-off solution because they seem to plan an unilateral/partial cut-off anyway and cut-off on our part would at least make hack attempts and messing up data with false information much more difficult for them. But I'm still open to be swayed one way or another by solid arguments what would be better for efficient operation of our Internet infrastructure having in mind that If I had to choose between (a) our network working reliably and safely and (b) being connected with Russia I will definitely vote for the (a) option. -- 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
- Previous message (by thread): [members-discuss] RIPEdb registry need to be ready for separating?
- Next message (by thread): [members-discuss] RIPEdb registry need to be ready for separating?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]