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: proposal
- Previous message (by thread): [db-wg] abuse-c: proposal
- Next message (by thread): [db-wg] abuse-c: proposal
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
MarcoH
marcoh at marcoh.net
Thu Jan 29 15:50:41 CET 2004
On Thu, Jan 29, 2004 at 02:26:44PM +0000, Randy Bush wrote: > >> For some reason Shane's proposal via jabber wasn't that bad: "surpress > >> all data which is only usefulll for maintainers from the default output". > > Spot on! > > sounds nice, but two issues > > o spam response tool writers will read docs and add the opt to get > all the refs Make sure that part of the docs is surrounded by the stuff about where to find certain information...if they read the docs, they would also be able to figure out that changed: and notify: are not meant as an abuse pointer. > o it adds pain for us old operators who actually use the db to find > out who is responsible for running some chunk of net > > but no big deal either way We'll provide you with a whois-client which turns on the flag by default :) MarcoH
- Previous message (by thread): [db-wg] abuse-c: proposal
- Next message (by thread): [db-wg] abuse-c: proposal
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]