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: 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
Fri Feb 6 15:26:45 CET 2004
On Fri, Feb 06, 2004 at 01:02:42PM +0000, Niall O'Reilly wrote: > > On 6 Feb 2004, at 12:45, MarcoH wrote: > > >Sounds good, but what do you consider 'primary objects', as in what > >templates will be modified to allow for abuse-mailbox and/or abuse-c ? > > Sorry, I should have made this clearer. > > I'm thinking of inet*num, aut-num as 'primary'; person, role, mntner > as 'indirect'. This would involve extending 6 templates for > 'abuse-mailbox' > and 3 templates for 'abuse-c'. Ppl may think of others. To get this clear you mean this ? inetnum abuse-c abuse-mailbox inet6num abuse-c abuse-mailbox aut-num abuse-c abuse-mailbox mntner abuse-mailbox person abuse-mailbox role abuse-mailbox Looks fine to me...the best of both worlds, although we might consider to also extend irt with the abuse-mailbox and allow abuse-c to refer to an irt object ? But maybe I'm opening another can of worms here. Grtx,
- 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 ]