I also would like the work to deprecate ASN auth for ROUTE creation, and the associated foreign object tagging to distinct source: work to be a discrete item (or pair of items) and not "glommed" into a collection of other things. Because there are two other RIR who run variants of the RIPE-NCC code, we have downstream consequential issues in the integration of patches into our own codebase (we're forked. it turned out to be too hard to maintain a single code tree) and its simpler if this stuff is done logistically in smaller tractable chunks. cheers -george On Wed, Oct 25, 2017 at 10:16 PM, den is via db-wg <db-wg@ripe.net> wrote:
Hi Job
Good point and I agree.
cheers denis co-chair DB WG
On 25 October 2017 at 14:13, Job Snijders <job@instituut.net> wrote:
Dear Denis,
On Wed, Oct 25, 2017 at 2:08 PM, den is via db-wg <db-wg@ripe.net> wrote:
Putting together several points from today:
-dropping ASN auth for ROUTE creation -wanting to know as precisely as possible who made a change -updating MNTNER objects by email -previous discussions on personal auth (which was also mentioned today)
maybe we could do a wider review on the auth model and build all these points into it...just a thought...
While I appreciate any efforts to improve both security and the end-user experience, I do not see the need to lump "deprecate ASN auth for ROUTE creation" is a broader project and thereby risking that it'll never get done. It is a concise, incremental change in the model and we should treat it as such.
Kind regards,
Job