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]/
[anti-abuse-wg] Update on "abuse-c:" coverage in RIPE Database
- Previous message (by thread): [anti-abuse-wg] Update on "abuse-c:" coverage in RIPE Database
- Next message (by thread): [anti-abuse-wg] Update on "abuse-c:" coverage in RIPE Database
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Johan Åhlén
jahlen at ripe.net
Fri Dec 6 09:38:38 CET 2013
Dear Piotr, We will look into filtering the legacy resources out and approaching the holders as you suggested. Enforcing the policy however is another matter as the RIPE NCC currently does not have the mandate to do so. Kind regards, Johan Åhlén Assistant Manager, Database RIPE NCC On 6 Dec 2013, at 08:42, Piotr Strzyzewski <Piotr.Strzyzewski at polsl.pl> wrote: > On Fri, Dec 06, 2013 at 08:28:01AM +0100, Johan ??hlén wrote: > > Dear Johan > >> It is our understanding that ripe-563, "Abuse Contact Management in >> the RIPE Database", does not apply to legacy resources because they >> are not explicitly mentioned in the policy. For this reason, legacy >> resources are not part of our implementation plan. >> >> https://www.ripe.net/ripe/docs/ripe-563 > > Is there any obstacle to contact erx resource holders and ask them > politely if they are willing to voluntarily follow the procedure? > > Piotr > > -- > gucio -> Piotr Strzyżewski > E-mail: Piotr.Strzyzewski at polsl.pl >
- Previous message (by thread): [anti-abuse-wg] Update on "abuse-c:" coverage in RIPE Database
- Next message (by thread): [anti-abuse-wg] Update on "abuse-c:" coverage in RIPE Database
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]