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] Proposal: Abuse-C as a Reference
- Previous message (by thread): [db-wg] Proposal: Abuse-C as a Reference
- Next message (by thread): [db-wg] Proposal: Abuse-C as a Reference
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Niall O'Reilly
Niall.oReilly at ucd.ie
Thu May 6 14:04:30 CEST 2004
On 6 May 2004, at 12:28, Ulrich Kiermayr wrote: >> Adding a new reference attribute requires modification of primary >> objects >> (inet*num, AS-whatever-the -object-is called). If a parallel >> reference is >> already in place, I don't see that this gives us a useful return on >> effort. >> Since all primary objects of interest must already have a tech-c >> reference, >> we should better say "Because" than "If". > > Ahem. In what respect this situation is different from adding > abuse-mailbox to those primary objects? I'm supposing that primary objects come in clusters, each managed by a single NOC team, and that the NOC team is already represented in the database by the target of identical tech-c attributes in each primary. Adding a new reference to each primary requires updating each primary. For me in UCD, this means several operations, as we have a handful of inetnum objects, and just one inet6num. I expect it's not all that different at UniVie. Placing a new attribute in the common, existing tech-c object requires updating just one object. What the saving is, depends on the level of aggregation in any given case. The point is, to take systematic advantage of any existing aggregation-point, be this a PRO (person/role/org) or an IRT. ATB, Niall
- Previous message (by thread): [db-wg] Proposal: Abuse-C as a Reference
- Next message (by thread): [db-wg] Proposal: Abuse-C as a Reference
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]