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 14:56:46 CET 2004
On Thu, Jan 29, 2004 at 02:42:10PM +0100, Ulrich Kiermayr wrote: > From the user's viewpoint yes, from the viewpoint of having to maintain > the objects, I'd prefer a reference, because if the mailbox changes, you > just have to maintain 1 Object and not n (for arbitrary positive > integers of n) Therefore my proposal to also allow for it on the mntner object and optionally modify the database server to return the maintainer when the attribute is not present on the inetnum, but one of the maintainers carries it. Can somebody from Ripe give some insigth in how much work would be involved on the various suggestions made, like adding attributes, complete objects and or modifying the default behaviour of the server ? 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 ]