On Wed, Jun 11, 2014 at 06:20:51PM +0300, Hank Nussbacher wrote: > At 14:42 11/06/2014 +0000, Job Snijders wrote: > >On Wed, Jun 11, 2014 at 05:15:54PM +0300, Sander Steffann wrote: > >> >> I think stripping/changing the notify-on-ref mail might hinder this. It > >> >> would be materially useful to preserve it, should exported IRR state be > >> >> used at another site aggregating data, to contact the prime information > >> >> manager. > >> > > >> > To contact the owner of a resource there are other mechanisms (abuse-c, > >> > admin-c, contact-c, etc). I would deem the notify-on-ref email address > >> > only relevant for communication between the registry and the email > >> > address being notified. It should not concern others who is notified > >> > when a resource is referenced. > >> > >> So how about notifying an ASN holder in the RIPE region about a policy > >> reference bring changed in the APNIC database? > > > >Today that would not be trivial.. It would not be aligned with current > >behaviour that RIPE mirrors or monitors other registries and their > >objects. > > Let's start someplace. Once the other RIRs see how great and wonderful > notify-on-ref is inside the RIPE region in 2015, they will implement it as > well (2016-2018), and then by 2019, the other RIRs will have to get > together and decide how to mirror and monitor the references between each > other. > > Rome wasn't built in a day.
*Reviving old thread* Is there a volunteer who wants to write up a specification/requirements text for discussion on [email protected], and after consensus we can ask RIPE NCC to implement this feature? Kind regards, Job
