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]/
[db-wg] abuse-c
- Previous message (by thread): [db-wg] abuse-c
- Next message (by thread): [db-wg] abuse-c
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Marco d'Itri
md at Linux.IT
Wed Jan 14 12:55:25 CET 2004
On Jan 14, Christian Rasmussen <chr at jay.net> wrote: >Actually I kind of have the same need!.. :) But my idea would be to insert >our abuse address in the maintainer so it defaults to this one, and then >insert customer (more specific) abuse address in the inetnum.. The only If the problem is lusers who cannot choose the right address to send complaints to, then this is way too hard for them and is not a solution. Looks like we need to discuss again the requirements... >> Extend mntner template with: >> >> abuse: [mandatory] [multiple] I think many people already explained why making this mandatory would be too hard and not really useful. >Aside from my comments above I fully support this. Do we now have something >which a larger group could support?? I'm not sure. I think that so far nobody disagreed with the proposal to return IRT objects by default for inetnum and inet6num queries, which has the advantages of using what is already available and probably being easy to implement. OTOH, the RIPE DB people have not explained us yet if this is feasible. -- ciao, | Marco | [4094 coeYUCAGphQow]
- Previous message (by thread): [db-wg] abuse-c
- Next message (by thread): [db-wg] abuse-c
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]