[db-wg] Proposal to remove "referral-by" attribute in "mntner" object or make it optional

On Mon, Mar 17, 2014 at 05:51:49PM +0100, Denis Walker wrote:

> I think this may be a bit over cautious for this object type. 

When none of the other participants in this thread have objections to a
'fast phase-out', I will not persue a more cautious approach for this
attribute. :-)

> The MNTNER object is not created, update or queried as often as
> operational data. And it is one of the least likely objects to be
> subject to automated scripts creating or querying & fully parsing it.
> Because of the hidden password hash, most MNTNER objects can only be
> fully accessed by an authenticated lookup in Webupdates. This takes
> care of issues surrounding a missing, previously mandatory,
> attribute.

I agree. 

> So for this object maybe we can:
> 
> -drop referral-by to an optional attribute with warning if used. Of
> course it will follow our now standard deployment process.
> -send the reminders to the DB WG after 1 and 2 months
> -deprecate the attribute fully after 2 months

Would it be possible to monitor the amount of creations/updates to MNTER
objects which contain a 'referral-by' attribute from the moment the
attribute becomes optional and generates soft warning? 

Kind regards,

Job
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 873 bytes
Desc: not available
URL: </ripe/mail/archives/db-wg/attachments/20140318/d26814f0/attachment.sig>