[anti-abuse-wg] [db-wg] Options for extending "abuse-c:"
- Previous message (by thread): [anti-abuse-wg] [db-wg] Options for extending "abuse-c:"
- Next message (by thread): [anti-abuse-wg] Working Group Charter
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Piotr Strzyzewski
Piotr.Strzyzewski at polsl.pl
Thu May 15 15:24:07 CEST 2014
On Mon, May 12, 2014 at 05:32:19PM +0200, Denis Walker wrote: Dear Denis > Again you are right. The abuse contact is not special. It only seems > special because we have applied the principles of the database model to it. > These principles are sadly missing from so many other areas of the data. > > Although it has been forgotten after 10+ years the basic database model is > - an organisation is the core of your data. That organisation has human > resources and Internet resources. The human resources are grouped into > roles and these roles manage the Internet resources. That is it in a > nutshell. It sounds simple, but so many layers have been built on and > around these principles, that the original principles have been partially > lost. > > That core organisation is anyone/thing that manages (some aspect of) an > Internet resource. If it is an outsourced 24/7 team, an abuse handler or an > End User doing their own routing. There should be an ORGANISATION object to > identify them. Everything else hangs off that object. So, do we have to start thinking about making admin-c/tech-c of INET(6)NUM (and others) optional and then deprecated at some point in time? Do we have to start thinking about moving whole contact details to the ORGANISATION objects? Piotr -- gucio -> Piotr Strzyżewski E-mail: Piotr.Strzyzewski at polsl.pl
- Previous message (by thread): [anti-abuse-wg] [db-wg] Options for extending "abuse-c:"
- Next message (by thread): [anti-abuse-wg] Working Group Charter
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]