2Robert How does it help to get rid of commercial IRRs? It's only RIPE policy, it doesn't work like GPDR. :)
2Job There is only one good thing about mistakes - if you can fix it. Here if one fails to properly configure ROAs it may lead to ongoing operational problems, that can't be fixed even after fixing ROAs, since RIPE-NONAUTH database is locked. I think, that it's ok to delete route objects that conflict with ROAs only if you are able to create new. Otherwise, the only winning party will be commercial IRRs. пн, 15 окт. 2018 г. в 17:29, Alexander Azimov <a...@qrator.net>: > 2Robert > How does it help to get rid of commercial IRRs? It's only RIPE policy, it > doesn't work like GPDR. :) > > 2Job > There is only one good thing about mistakes - you can fix it. > Here if one fails to properly configure ROAs it may lead to ongoing > operational problems, that can't be fixed even after fixing ROAs, since > RIPE-NONAUTH database is locked. > I think, that it's ok to delete route objects that conflict with ROAs only > if you are able to create new. Otherwise, the only winning party will be > commercial IRRs. > > пн, 15 окт. 2018 г. в 17:06, Robert Heuvel via db-wg <db-wg@ripe.net>: > >> Hi, >> >> Where can we express our support for this RIPE Policy proposal? >> We think it is a great idea and gets rid of commercial IIRs where you can >> register just about anything which is or is not yours... >> >> Robert Heuvel >> atom86 (AS8455) >> >> Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum >> >> > > -- > | Alexander Azimov | HLL l QRATOR > | tel.: +7 499 241 81 92 > | mob.: +7 915 360 08 86 > | skype: mitradir > | visit: radar.qrator.net > -- | Alexander Azimov | HLL l QRATOR | tel.: +7 499 241 81 92 | mob.: +7 915 360 08 86 | skype: mitradir | visit: radar.qrator.net
