[ncc-services-wg] Re: [db-wg] Proposal - Maintaining person, role and domain objects

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

The proposal from Denis for moving towards assigning a mntner for all
person, role and domain objects seems to me very clear, and entirely
practicable to implement. Two questions:


1. How will RIPE NCC decide when to move to the next stage?

2. I think it is logically possible for objects in a stagnant part of
the database to escape stages 1, 2 and 3 because they are rarely or
never involved in update traffic.
Have we any idea how large a collection of such objects will remain,
and might there be a stage 4 during which action is taken on them?


I suspect both questions depend on some more statistics. Some of them
will only become available as the transition goes on, and I do not
know how to design them anyway.

Rodney Tillotson, JANET-CERT
+44 1235 822 255.


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

> Stage 2
>
>   * Any update where objects reference an un-maintained person
>     object, either directly or through a mntner with 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.

> Stage 3
>
>   * Any update where objects reference an un-maintained person
>     object, either directly or through a mntner with such
>     references, will generate an error message in the
>     acknowledgement and the update will fail.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGeoZczHL8ns8C6+kRAr7pAKDT+FtlcGYvJsBXAJVuluLjJvROMACfThuW
IEIgZFvjpzU6IRK5RlubDBs=
=83pz
-----END PGP SIGNATURE-----