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] New on RIPE Labs: How We Will Be Validating abuse-c
- Previous message (by thread): [anti-abuse-wg] New on RIPE Labs: How We Will Be Validating abuse-c
- Next message (by thread): [anti-abuse-wg] New on RIPE Labs: How We Will Be Validating abuse-c
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Ronald F. Guilmette
rfg at tristatelogic.com
Mon Oct 15 20:55:04 CEST 2018
In message <E1gArD9-0007Bj-FW at www-apps-1.ripe.net>, Marco Schmidt <mschmidt at ripe.net> wrote: >Please allow me to provide some clarification. >... >The RIPE Policy "RIPE NCC Services to Legacy Internet Resource Holders" >states in its scope: >"[...] Any existing or future RIPE policy referring to resources shall not >apply to legacy resources unless the policy explicitly includes legacy >resources in its scope. [...]" >https://www.ripe.net/publications/docs/ripe-639#1-2-scope > >The RIPE Policy "Abuse Contact Management in the RIPE Database" does not >fulfil this requirement. > >It would require a successful policy proposal to change that. In 2016 such >proposal was made, but the proposer decided to withdraw the proposal due to >the inability to find an acceptable agreement which satisfied all parties. That's sooooo dumb. >I hope this clarifies. It does and I thank you for the clarification. Regards, rfg
- Previous message (by thread): [anti-abuse-wg] New on RIPE Labs: How We Will Be Validating abuse-c
- Next message (by thread): [anti-abuse-wg] New on RIPE Labs: How We Will Be Validating abuse-c
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]