At 11:25 10/06/2014 +0000, Job Snijders wrote:
I propose we dub the attribute for nice alignment with existing attributes:
notify-on-ref: <email-address> optional, multi-valued
Works for me.
Questions:
- do you want a notification each time an object is updated and has a reference to your object?
No.
- or do you only want notifications when a reference inititally is added to an object? (spares you a daily mailbomb for daily updated objects)
Yes.
- do you want a notification when the reference is removed from an object?
Yes.
- In what classes do you want to set a notify-on-ref attribute? (I think initially aut-num, as-set, rs-set)
Agree.
- do we want the notify-on-ref email addresses to be set to unread@ripe.net upon NRTM/ftp export?
No opinion.
Regarding authorisation, for me requiring authorisation to reference a given object is a bridge too far at this point in time. Quite some operators automatically generate an autnum, route-sets & as-sets on a daily basis to reject their policy, and I don't see an easy way to make this a painless adventure. Let's first do notifications and based on those experiences look further. ok?
Yup. -Hank
Kind regards,
Job