<html><head></head><body><div class="ydp20326783yahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;"><div></div>
<div>and also keep in mind what the goal of this is. Anyone can create a new PERSON/ROLE object with the same content as one of yours. In other words make an exact copy. They can then add your MNTNER and then remove theirs after making references to it. Adding an additional MNTNER doesn't require authorisation from that MNTNER. So they can still set up their data to look as if it is managed by you.</div><div><br></div><div>cheers</div><div>denis</div><div><br></div><div>co-chair DB-WG</div><div><br></div>
</div><div id="ydp377108d8yahoo_quoted_9393310032" class="ydp377108d8yahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
On Friday, 31 May 2019, 15:11:48 CEST, Cynthia Revström via db-wg <db-wg@ripe.net> wrote:
</div>
<div><br></div>
<div><br></div>
<div><div id="ydp377108d8yiv6270780151"><div><div>it wouldn't really work for maintainers, as it becomes a recursive loop. mnt-1 wants to edit mnt-2's object, mnt-2 can't add mnt-1 and mnt-1 can't add mnt-2 to mnt-ref...<div><br clear="none"></div><div>- Cynthia</div></div><br clear="none"><div class="ydp377108d8yiv6270780151yqt6272407174" id="ydp377108d8yiv6270780151yqt30920"><div class="ydp377108d8yiv6270780151gmail_quote"><div class="ydp377108d8yiv6270780151gmail_attr" dir="ltr">On Fri, May 31, 2019, 15:05 Sebastian Wiesinger via db-wg <<a shape="rect" href="mailto:db-wg@ripe.net" rel="nofollow" target="_blank">db-wg@ripe.net</a>> wrote:<br clear="none"></div><blockquote class="ydp377108d8yiv6270780151gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">* Edward Shryane via db-wg <<a shape="rect" href="mailto:db-wg@ripe.net" rel="nofollow" target="_blank">db-wg@ripe.net</a>> [2019-05-27 11:43]:<br clear="none">
> Dear Working Group,<br clear="none">
> <br clear="none">
> as mentioned at last week's DB-WG meeting, I'd like to propose extending authenticating references to other objects.<br clear="none">
> <br clear="none">
> Currently, only references to organisation objects can be protected with the mnt-ref attribute.<br clear="none">
> <br clear="none">
> However, we could extend this protection to other types of objects:<br clear="none">
> <br clear="none">
> - Abuse-c role<br clear="none">
> - Technical contact, admin contact, zone contact etc. (person/role)<br clear="none">
> - Organisation maintainer(s)<br clear="none">
> <br clear="none">
> This would prevent unauthorised references to an organisation's objects (e.g. to impersonate a third party or mis-direct abuse email).<br clear="none">
<br clear="none">
Sounds good, on the premise that this is done to the generic object<br clear="none">
type and not dependent on the usage of them.<br clear="none">
<br clear="none">
Meaning that if I put mnt-ref on a person/role you cannot reference it<br clear="none">
*anywhere* unless your maintainer is listed in mnt-ref. Same for<br clear="none">
maintainers.<br clear="none">
<br clear="none">
<br clear="none">
Regards<br clear="none">
<br clear="none">
<br clear="none">
Sebastian<br clear="none">
<br clear="none">
-- <br clear="none">
GPG Key: 0x58A2D94A93A0B9CE (F4F6 B1A3 866B 26E9 450A 9D82 58A2 D94A 93A0 B9CE)<br clear="none">
'Are you Death?' ... IT'S THE SCYTHE, ISN'T IT? PEOPLE ALWAYS NOTICE THE SCYTHE.<br clear="none">
-- Terry Pratchett, The Fifth Elephant<br clear="none">
</blockquote></div></div></div></div></div>
</div>
</div></body></html>