This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/routing-wg@ripe.net/
[routing-wg] Notification/authorisation of references to aut-num from other RPSL objects
- Previous message (by thread): [routing-wg] Notification/authorisation of references to aut-num from other RPSL objects
- Next message (by thread): [routing-wg] Notification/authorisation of references to aut-num from other RPSL objects
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Job Snijders
job at instituut.net
Wed Jun 11 16:42:59 CEST 2014
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. Kind regards, Job
- Previous message (by thread): [routing-wg] Notification/authorisation of references to aut-num from other RPSL objects
- Next message (by thread): [routing-wg] Notification/authorisation of references to aut-num from other RPSL objects
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]