[db-wg] Foreign ROUTE objects in RIPE Database - final decision?
George Michaelson ggm at algebras.org
Tue Oct 17 23:41:06 CEST 2017
Yes, I would support these changes. Half of the concerns with APNIC resource management disappears if we cease depending on aut-num authorization for route objects. I prefer that ultimately the open maintainer method cease. But a step along the way is to mark foreign objects clearly, so their status and role can be understood. -George On Tue, Oct 17, 2017 at 9:23 AM, William Sylvester via db-wg <db-wg at ripe.net> wrote: > > > ---------- Forwarded message ---------- > From: William Sylvester <william.sylvester at addrex.net> > To: Database WG <db-wg at ripe.net> > Cc: > Bcc: > Date: Mon, 16 Oct 2017 23:22:55 +0000 > Subject: Re: [db-wg] Foreign ROUTE objects in RIPE Database - final decision? > Db-wg members, > > Now that there has been substantial discussion on this topic, I wanted to try to bring the conversation back to a more practical and actionable path forward. Clearly this is a topic where there are a lot of opinions. From seeing the discussion and receiving additional feedback, I wanted to point out some re-occurring themes and request a revised proposal for working group consideration. > > > 1) Remove the "origin:" authorization requirement. RIPE is currently the only RIR that requires this, the current implementation creates data concurrency issues across Internet databases by requiring the creation of duplicate autnums. > > 2) Flag "route:" objects for non-RIPE-managed space with "source: RIPE-NONAUTH" to identify non-authoritative data. > > > I’d like to seek input from the group; > > - Do you feel these options are straight forward and easy to understand? > - Does this provide a reasonable security posture? > - Will this make a positive impact for RIPE DB and the greater Internet? > - Do you support these concepts? > > > Thanks, > William > Db-wg co-chair > >
[ db-wg Archives ]