[dp-tf] Maintaining person, role and domain objects

Hi all

I think we all agreed that this one is Ok almost as I sent it out. There
are issues around who should be allowed to create mntners and who should
be able to put data into the RIPE Database. But these are outside the
immediate scope of this proposal.

I have made one significant change to the implementation plan. I
expanded Stage 2 into 2 separate stages. This is to allow for the
problem of other people maintaining referenced data. We don't want to
stop anyone from modifying existing data, maybe until a much later time.
So I have added the point about new references.

So the implementation plan now looks like this:

Stage 1

    * No new person, role or domain objects can be created without a
"mnt-by:" attribute.
    * Any unmaintained person, role or domain object cannot be modified
without adding an "mnt-by:" attribute.
    * Any update where objects reference an un-maintained person object,
either directly or their mntner has such references, will generate a
warning message in the acknowledgement.

In this stage the acknowledgement message may include these warnings:

***WARNING: Un-maintained person object referenced [DW-RIPE]


 Stage 2

    * Any update where objects reference an un-maintained person object,
either directly or their mntner has such references, will generate a
warning message in the acknowledgement.
    * Any NEW reference to an un-maintained person object or to a mntner
which has such references, will generate an error message in the
acknowledgement and the update will fail.

In this stage the acknowledgement message may include these warnings and
errors:

***WARNING: Un-maintained person object referenced [DW-RIPE]
***WARNING: Un-maintained person object referenced [DW-RIPE] in mntner
[AARDVARK-MNT]
***ERROR: New reference to un-maintained person object [DW-RIPE]
***ERROR: New reference to un-maintained person object [DW-RIPE] in
mntner [AARDVARK-MNT]

Stage 3

    * Any update where objects reference an un-maintained person object,
either directly or their mntner has such references, will generate an
error message in the acknowledgement and the update will fail.

In this stage the acknowledgement message may include these errors:

***ERROR: Un-maintained person object referenced [DW-RIPE]
***ERROR: Un-maintained person object referenced [DW-RIPE] in mntner
[AARDVARK-MNT]

We will send this one to the community later this week. The others will
follow over the next few weeks. We don't want to send them all out at
the same time and overload people.

regards
Denis
RIPE NCC