[ncc-services-wg] [db-wg] Phasing out the LIR Portal object editors

On 21/04/2016 10:32, Alex Band wrote:
> Dear colleagues,
>

> The way we intend to do this involves a couple of steps. The first
> step is to use business rules to determine which attributes you can
> change, and which ones can only be changed by the RIPE NCC. For
> example, in an inetnum for an allocation only the RIPE NCC can change
> the range, but you can change the admin-c and tech-c.

I would like to know how the RIPE NCC can change the range on an 
INETNUM. This is the primary key and it has not been possible to change 
the primary keys at least for the last 15 years.

btw...has the Communications Department abandoned its standards on how 
to specify object types and attributes in documents and announcements 
now? I presume this was reviewed by COMMS...that's one of the reasons 
you have such a large, expensive department isn't it, to maintain 
professional standards?

cheers
denis

>
> Kind regards,
>
> Alex Band Product Manager RIPE NCC
>