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 ]
denis
ripedenis at yahoo.co.uk
Fri May 29 15:06:05 CEST 2015
Hi Nick On 29/05/2015 14:47, Nick Hilliard wrote: > On 29/05/2015 13:33, denis wrote: >> I am not against policy change if that is the only way forward. But let me >> just throw a quick question back at you. If someone manages (legacy) >> resources and have customers using some of these resources and all this is >> documented in the RIPE Database and one of those customers 'could' cause >> abuse, does it not make sense to advertise an abuse contact? Isn't this >> just good management of resources? > in theory, advertising this is a good thing and won't do any harm. In > practice people will continue to use their old templates as before and > won't bother changing things unless there's some impetus to do so. > > The LRH community is receptive to the idea of good stewardship of > resources, so I don't see why they wouldn't be interested in mentioning > legacy resources in the "Abuse Contact Management in the RIPE Database" > document. So are you suggesting that ripe-563 policy is amended to include legacy resources? cheers denis > > Nick > -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/db-wg/attachments/20150529/8f1616d9/attachment.html>
- 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 ]