[db-wg] The New "organisation object" Proposal

Engin,

>> 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.

Yes, I read it, what I mean is whether you would consider eliminating 
the part about choosing letters. This is only an identifier and it 
would be good if people could think about it as just that, with no 
naming implications.

>
>>
>> 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.

Cool. One more question, though it is really not DB related in itself, 
but more policy: Will org objects be created when LIRs are created? If 
so, will existing LIRs automatically get an org object?

Joao