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/db-wg@ripe.net/
[db-wg] abuse-c on legacy resources
- Previous message (by thread): [db-wg] abuse-c on legacy resources
- Next message (by thread): [db-wg] abuse-c on legacy resources
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Nick Hilliard
nick at inex.ie
Thu May 28 22:42:15 CEST 2015
On 28/05/2015 20:08, denis walker wrote: > During the RIPE Meeting you suggested the idea of legacy resource holders > adopting the practice of referencing an abuse contact using the one > accepted method currently in use in the RIPE Database with "abuse-c:". In > terms of responsible management of internet resources I don't think anyone > could argue against all resources documented in the RIPE Database making > reference to an abuse contact via an ORGANISATION object showing who is > responsible for a resource. > > Many ideas raised at RIPE Meetings are quickly forgotten after the meeting. > How can we move this idea forward so it does not become another of those > 'good idea, but never implemented'? This will probably need a policy change, no? https://www.ripe.net/publications/docs/ripe-639 > 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. Nick
- Previous message (by thread): [db-wg] abuse-c on legacy resources
- Next message (by thread): [db-wg] abuse-c on legacy resources
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]