[db-wg] Cross registry authentication BOF - rough notes
- Previous message (by thread): [db-wg] Cross registry authentication BOF - rough notes
- Next message (by thread): [db-wg] re-evaluate route-object authorisation model
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Job Snijders
job at ntt.net
Wed May 13 11:06:11 CEST 2015
Hi all, On Tue, May 12, 2015 at 08:45:18PM +0200, denis wrote: > Why are you only considering long term, complex solutions that seem to > have no agreement? Please strive to be excellent, the above sentence is neither constructive nor true. > There is a simple and quick option. Let me say it again in a few > lines. > > - Suppose we drop the requirement for ASN auth on ROUTE creation. This very option was presented as one of the possibilities during the BoF session, labeled "Direction C": https://ripe70.ripe.net/presentations/70-cross-registry-bof_ripe70.pdf > If you don't want to drop the ASN auth option simply extend the > notification/acceptance process to the ASN resource holder for non > RIPE ASNs. We still don't need copies in the RIPE Database. Interesting ideas. Let us discuss this idea in a new mail thread. Kind regards, Job
- Previous message (by thread): [db-wg] Cross registry authentication BOF - rough notes
- Next message (by thread): [db-wg] re-evaluate route-object authorisation model
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]