[db-wg] Implementation proposal descr line

Tim,

On Tue, 20 Oct 2015 12:23:02 +0200
Tim Bruijnzeels <tim at ripe.net> wrote:

> Implementation proposal:
> ========================
> 
> = Change "descr:" to an 'optional multiple' attribute

Makes sense.

> Technically this change is not hard to do on the server side, but can
> impact users of the database because there may be no "descr:"
> attribute, and this can affect parsers.

Yes.
 
> Because this can have an impact on automated systems the RIPE NCC
> will announce this change ncc-announce at ripe.net, and use a longer
> week staging period in the Release Candidate environment allowing
> users to test and update their systems.

Reasonable, although I'm sure most users will discover this only after
the first object without a "descr:" attribute appears and their scripts
explode in colorful ways. ;)

> = Clean up existing "descr:" attributes where RIPE NCC enforced the
> organisation name
> 
> The RIPE NCC will remove the "descr:" attributes that it has been
> enforcing.

I have no strong preference here. I don't see a huge motivation for the
removal, but I'm not against this.
 
> = Add "descr:" to allocation object editor in LIR Portal
> 
> So that LIRs can edit this themselves.

Makes sense.

> = Stop setting the "descr:" on new allocations or assignments done by
> the RIPE NCC
> 
> We will leave "descr:" blank. It can be edited by the LIR or end-user
> later.

Presumably a blank "descr:" does not get added to the object?

Cheers,

--
Shane