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]/
[anti-abuse-wg] [db-wg] abuse-c + org
- Previous message (by thread): [anti-abuse-wg] [db-wg] abuse-c + org
- Next message (by thread): [anti-abuse-wg] [db-wg] abuse-c + org
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Daniel Stolpe
stolpe at resilans.se
Tue Jul 2 14:01:03 CEST 2013
On Tue, 2 Jul 2013, Gert Doering wrote: > Hi, > > On Tue, Jul 02, 2013 at 11:28:31AM +0200, Gilles Massen wrote: >> My use case is to set a specific abuse-c for one autnum and inetnum, >> which is not the same as the general abuse-c of the organisation. Maybe >> I could create a 'fake' ORG in order to link to that (probably it would >> not work in my case), but that means data duplication. Allowing to >> attach the abuse-c to whatever object would solve it more nicely. The >> DBs query logic should hardly be affected as it is simply a matter of >> returning the most specific abuse-c for the object. > > I seem to remember that I stated this as well, back then, and it was > not seen as "important". > > So, yes, seconded. There is alo a strange thing here: organisation: [mandatory] [single] [primary/lookup key] org-name: [mandatory] [single] [lookup key] org-type: [mandatory] [single] [ ] descr: [optional] [multiple] [ ] remarks: [optional] [multiple] [ ] address: [mandatory] [multiple] [ ] phone: [optional] [multiple] [ ] fax-no: [optional] [multiple] [ ] e-mail: [mandatory] [multiple] [lookup key] geoloc: [optional] [single] [ ] language: [optional] [multiple] [ ] org: [optional] [multiple] [inverse key] admin-c: [optional] [multiple] [inverse key] tech-c: [optional] [multiple] [inverse key] abuse-c: [optional] [single] [inverse key] ref-nfy: [optional] [multiple] [inverse key] mnt-ref: [mandatory] [multiple] [inverse key] notify: [optional] [multiple] [inverse key] abuse-mailbox: [optional] [multiple] [inverse key] <- mnt-by: [mandatory] [multiple] [inverse key] changed: [mandatory] [multiple] [ ] source: [mandatory] [single] [ ] Multiple abuse-mailboxes. role: [mandatory] [single] [lookup key] address: [mandatory] [multiple] [ ] phone: [optional] [multiple] [ ] fax-no: [optional] [multiple] [ ] e-mail: [mandatory] [multiple] [lookup key] org: [optional] [multiple] [inverse key] admin-c: [optional] [multiple] [inverse key] tech-c: [optional] [multiple] [inverse key] nic-hdl: [mandatory] [single] [primary/lookup key] remarks: [optional] [multiple] [ ] notify: [optional] [multiple] [inverse key] abuse-mailbox: [optional] [single] [inverse key] <- mnt-by: [mandatory] [multiple] [inverse key] changed: [mandatory] [multiple] [ ] source: [mandatory] [single] [ ] One single. The one in "role" is the one that counts. Why don't we allow multiple addresses there? And yes. What it leads to is you have to create several org objects in order to get more than one (or different) abuse-mailboxes. Best Regards, Daniel Stolpe _________________________________________________________________________________ Daniel Stolpe Tel: 08 - 688 11 81 stolpe at resilans.se Resilans AB Fax: 08 - 55 00 21 63 http://www.resilans.se/ Box 13 054 556741-1193 103 02 Stockholm
- Previous message (by thread): [anti-abuse-wg] [db-wg] abuse-c + org
- Next message (by thread): [anti-abuse-wg] [db-wg] abuse-c + org
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]