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]/
[db-wg] denying access to RIPE DB for proven spammers
- Previous message (by thread): [db-wg] denying access to RIPE DB for proven spammers
- Next message (by thread): [db-wg] denying access to RIPE DB for proven spammers
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sergey Myasoedov
sergey at devnull.ru
Wed Sep 13 20:26:30 CEST 2023
As far as I know, ARIN implemented such limits only once (*), which helped at least for some time. Please correct me if I'm wrong. -- Kind regards, Sergey Myasoedov * https://regmedia.co.uk/2020/01/08/arin-cogent.pdf > On Sep 13, 2023, at 14:19, Ben Cartwright-Cox via db-wg <db-wg at ripe.net> wrote: > > In principal I agree with this and it makes sense, however when ARIN has done this it hasn't really made any noticeable difference. > > On Wed, 13 Sep 2023, 20:10 Sergey Myasoedov via db-wg, <db-wg at ripe.net> wrote: > Hi, > > I would like to discuss the possible changes to the RIPE Database for the LIRs or brokers sending targeted spam with proposed address resources transactions. > > As far as I know, RIPE DB T&C does not contain a statement about restricting the use of RIPE DB for those abusive traders. Should the community request the NCC to develop how to limit RIPE DB usage? > > Please feel free to comment. > > > -- > Kind regards, > Sergey Myasoedov
- Previous message (by thread): [db-wg] denying access to RIPE DB for proven spammers
- Next message (by thread): [db-wg] denying access to RIPE DB for proven spammers
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]