[db-wg] AUT-NUM authorization on ROUTE(6) objects
- Previous message (by thread): [db-wg] AUT-NUM authorization on ROUTE(6) objects
- Next message (by thread): [db-wg] AUT-NUM authorization on ROUTE(6) objects
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Edward Shryane
eshryane at ripe.net
Tue Aug 27 11:52:49 CEST 2019
Hi Hank, DB-WG, > On 25 Aug 2019, at 19:47, Hank Nussbacher via db-wg <db-wg at ripe.net> wrote: > > Didn't we also say that route object creation should generate an alert to AS origin admin-c or tech-c? > > -Hank > > Yes, this change was documented at the time in the NWI-5 impact analysis: https://www.ripe.net/manage-ips-and-asns/db/impact-analysis-for-nwi-5-implementation <https://www.ripe.net/manage-ips-and-asns/db/impact-analysis-for-nwi-5-implementation> "One of the consequences of dropping the ASN authentication requirement is that the ASNholder might not be aware of the creation of a ROUTE(6) object that shows them to be the originator. This consequence will be mitigated by sending a notification email to the notify email address of the ASN. The "notify" attribute is optional. If the ASN does not have a "notify" attribute set, we will not send a notification email." I will update the database documentation to include this. Regards Ed Shryane RIPE NCC -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.ripe.net/ripe/mail/archives/db-wg/attachments/20190827/b3d8751c/attachment.html>
- Previous message (by thread): [db-wg] AUT-NUM authorization on ROUTE(6) objects
- Next message (by thread): [db-wg] AUT-NUM authorization on ROUTE(6) objects
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]