[dp-tf] Quadlogy of person proposals

Dear Denis,

Thank you for the nice work! Overall, I think it is very good.

I have a couple of comments below:

>    Clean up of unreferenced person objects

> Targeting 'loose' mntner objects will catch the mutually
 > referencing pairs. There may be many more of these when it
 > is required to maintain person objects. In this case we will
 > only target the person/mntner object pairs. To include role
 > objects implies person/role/mntner groups with many more
 > references. This is too complicated to handle within the
 > scope of this one time cleanup process.

You do not need the role objects to make things complicated.

Actually the mntner-person "pairs" can cause you some more headache
as well. Consider the case:

mntner1: admin-c: p1 tech-c: p2
p1: mnt-by: mntner2
p2: mnt-by: mntner3
mntner2: admin-c: p1 tech-c: p2
mntner3: admin-c: p1 tech-c: p2

You have here five objects that reference each other, but nothing
else. Of course, this can be made as complex as you wish:

mntner1: admin-c: p1
p1: mnt-by: mntner2
mntner2: admin-c: p2
p2: mnt-by: mntner3
mntner3: admin-c: p3
p3: mnt-by: mntner4
...
mntner"n": admin-c: p"n"
p"n": mnt-by: mntner1

Do I miss something?


> Changes to objects

> Add a "not-ref:" attribute to person/role objects. This
 > indicates that the person/role object is not referenced
 > and the date when it last became unreferenced. ...

Is it not the date when it _first_ became unreferenced
(i.e. when you first noticed it is unreferenced)?



> A user can apply to have their person object linked to
 > the white pages. They should select the category and contact
 > the moderator. The user needs to send their full person object
 > to the moderator. This should either include the plain text
 > password or be a signed message providing the authentication
 > to modify this person object. ...

I think this is what Elmar objected to as well... (Never send
passwords to somebody else.)


> Requests for additional white pages categories can be sent
 > to Customer Services at RIPE NCC. These requests will be
 > forwarded to the WG chairs mailing list for approval.
 > If approved the RIPE NCC will create the new organisation
 > object, update the web page and notify the moderator.

I think you mean _appoint_ a moderator. (Once appointed, he/she
will be have to be notified as well, of course.)



>   Authentication for referencing of person and role objects

I think I would call this _authorization_ rather than authentication.
This applies to the other uses of this term throughout this document.




>   Structuring of address attributes in person, role and organisation objects


> Stage 2
> 
>     * Whenever a person/role/organisation object is modified with only "address:"
 > attributes an error message will be added to the acknowledgement.
>     * Whenever a person/role/organisation object is referenced with only "address:"
 > attributes an error message will be added to the acknowledgement and the update
 > will fail.

Delete the word "only" in the two bullets above, as you either have "address:"
attribute(s) or the other set, not both.

I hope this helps.

Please let me know if I misunderstood something, or if what I was trying to say is
not clear enough.

Best regards,
Janos