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/[email protected]/
[members-discuss] [ncc-services-wg] Update of RIPE NCC Procedural Document
- Previous message (by thread): [members-discuss] [FORTIMAIL: prawdopodobny spam] Re: [ncc-services-wg] Update of RIPE NCC Procedural Document
- Next message (by thread): [members-discuss] [ncc-services-wg] Update of RIPE NCC Procedural Document
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Nikolay Gorstkin
nikolay.gorstkin at gmail.com
Thu Apr 4 10:03:16 CEST 2019
Dear Piotr, Yes, you are right. I was wrong of course — regards, Nikolay Gorstkin > 4 апр. 2019 г., в 10:54, Piotr Strzyzewski <Piotr.Strzyzewski at polsl.pl> написал(а): > > On Thu, Apr 04, 2019 at 10:40:01AM +0300, Nikolay Gorstkin wrote: > > Dear Nikolay, > >> Considering the latest offers from the RIPE NCC about BGP hijacks, >> this is similar to how government structures (RKN) operate in Russia. > > If you are referring to 2019-03 policy proposal, I would like to stress > that this is discussed in the RIPE (not RIPE NCC) Anti-Abuse WG. Please, > do not confuse RIPE and RIPE NCC. > > Piotr > > -- > Piotr Strzy�ewski > Silesian University of Technology, Computer Centre > Gliwice, Poland
- Previous message (by thread): [members-discuss] [FORTIMAIL: prawdopodobny spam] Re: [ncc-services-wg] Update of RIPE NCC Procedural Document
- Next message (by thread): [members-discuss] [ncc-services-wg] Update of RIPE NCC Procedural Document
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]