[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 ]
Niall O'Reilly
niall.oreilly at ucd.ie
Thu Jan 29 15:19:12 CET 2004
On 29 Jan 2004, at 14:57, Ulrich Kiermayr wrote: > [ Niall O'Reilly wrote ] >> Do we need a new machinery for this? If a role or person object >> acquires >> a new inverse-key relationship, I would find it reasonable to alert >> the >> 'mnt-by:' and 'notify:' targets as a matter of course. I don't see >> the >> value in defining new attributes just to cover this. > > Hmm, I'd prefer the protection from that to happen instead of: Bad Guy > does something -> You hear from it -> You have to persuade the > RIPE-NCC to do something against it (Because you can't do it yourself, > since you do _not_ maintain the object where the reference is in). Right. I should have thought of that. For " ... alert the 'mnt-by:' and 'notify:' targets ... " read " ... alert 'mnt-by:' and 'notify:' targets, and block the update pending their confirmation ... ". MfG Niall
- 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 ]