So need to form a policy to make RIPE members informed about any requests, and enforce it to be included into RIPE NCC rules of conduct.


Best regards,

Ivan Kazmin


¬°¬ä: members-discuss <members-discuss-bounces@ripe.net> ¬à¬ä ¬Ú¬Þ¬Ö¬ß¬Ú Max Tulyev <maxtul@netassist.ua>
¬°¬ä¬á¬â¬Ñ¬Ó¬Ý¬Ö¬ß¬à: 26 ¬à¬Ü¬ä¬ñ¬Ò¬â¬ñ 2020 ¬Ô. 13:04:20
¬¬¬à¬Þ¬å: members-discuss@ripe.net
¬´¬Ö¬Þ¬Ñ: Re: [members-discuss] Injection of false RPKI ROAs
 
Dear Maxi,

technically - yes, they can.

For me, that is the main disadvantage of any centralized PKI system.

On 23.10.20 14:37, Maxi wrote:
> Dear fellow Members,
> Dear RIPE Team,
>
> We currently discuss a somehow strange thing.
>
> Could the RIPE NCC be forced to inject false ROAs (e.g. for censorship)?
> If so, is there any legal framework for it?
>
> Does the RIPE NCC have any information on attempts?
>
> Best,
> Maxi
>
> Impressum:
> Zeug e.K.
> Hochstra©¬e 15
> 92637 Theisseil
>
> Inhaber: Maximilian Schieder
>
> Telefon: 015678 572314
> E-Mail: maxi@zeug.co <mailto:maxi@zeug.co>
>
> Registergericht:
> Amtsgericht Weiden in der Oberpfalz Registernummer:
> HRA 2907
>
>
>
>
> _______________________________________________
> members-discuss mailing list
> members-discuss@ripe.net
> https://lists.ripe.net/mailman/listinfo/members-discuss
> Unsubscribe: https://lists.ripe.net/mailman/options/members-discuss/maxtul%40netassist.ua
>

_______________________________________________
members-discuss mailing list
members-discuss@ripe.net
https://lists.ripe.net/mailman/listinfo/members-discuss
Unsubscribe: https://lists.ripe.net/mailman/options/members-discuss/i.kazmin%40corpsoft24.ru