[ncc-services-wg] Re: [db-wg] The New "organisation object" Proposal

Hi Joao,

On 2003-08-25 14:34:18 +0200, Joao Damas wrote:
> I think this proposal is very good.
> 
> On Monday, Aug 25, 2003, at 12:27 Europe/Amsterdam, DB-News wrote:
> 
> >
> >Dear Colleagues,
> >
> >[apologies for duplicate messages]
> >
> >Following discussions at the RIPE NCC about a new Whois Database 
> >object,
> >the organisation object, we have modified the previous proposal that 
> >you
> >can find at:
> >
> >http://www.ripe.net/ripe/mail-archives/db-wg/2003/msg00013.html
> >
> >The main changes from the previous proposal are:
> >
> > - a "country:" attribute is added.
> > - "org-type:" and "org-name:" attributes are added, and 
> >"organisation:"
> >    attribute is now a NIC handle, which will be automatically assigned
> >    during the creation of the object. The motivation for this is 
> >explained
> >    in Section 3 of the proposal.
> 
> A very welcome modification. The last thing the RIPE DB needs to get 
> dragged into are trade mark disputes about object names.
> Could it be made a bit stricter and allow only for auto-generation of 
> organisation NIC handles?

Yes, this is actually the case. Quoting from Section 3 of the proposal:

  Organisation object IDs are auto-generated similar to the way person/role
  "nic-hdl:" attributes are auto-generated.  The user has to specify the ID of
  an organisation object as ORG-AUTO-<digit> during creation of the object,
  then it will be assigned an appropriate ID.  The organisation ID is assigned
  using the "org-name:" attribute of the object.  The user can specify the
  letter combination he/she prefers.  For example if the user wants TTR as the
  letter combination, in the organisation ID, then ORG-AUTO-1TTR should be 
  put into "organisation:" attribute during the creation of the object.

> > - Hierarchical names can be removed, mainly for simplicity.
> 
> I got lost on this one. Do you mean "can be removed" or "have been 
> removed"?

Oops, it's meant to be "have been removed". Sorry for that...

> > - Differing query results on the whois server introduced in section 5.
> >    According to this, the relevant organisation objects are appended 
> >to the
> >    query results (because the organisation that holds the resource is 
> >at
> >    least as important as the person/role objects mentioned in the 
> >resource object).
> 
> This is good. Also being able to disable it with '-r'.

Right, this is also in the proposal: "This behaviour can be disabled 
by using the '-r' flag in the query." in Section 5.

> 
> Will the database enforce any restrictions on the assignment of 
> org-types, so that new IANAs and new RIRs can't be created, with 
> potential for introducing confusion?

Although this is not mentioned in the proposal, yes, the DB software
will enforce restrictions.  organisation objects with type IANA, RIR, NIR
and LIR can only be created by the NCC.

> 
> I think this is a good proposal for an organisation object in the RIPE 
> Database,
> Joao

Thanks a lot for feedback,

Best regards,

-- 
Engin Gunduz
RIPE NCC Database Group