--- Begin Message ---
I think its time to stop disrespecting external source of authority on
this. You argued for a position based on the desire of RIPE entities
needing to import foreign objects into their RPSL But you did not
address the far larger body of people who are exposed to risks from
--- Begin Message ---
On Wed, 11 Oct 2017 at 16:52, Sascha Luck [ml] via db-wg
wrote:
> On Wed, Oct 11, 2017 at 11:30:06AM -0300, Carlos M. Martinez wrote:
> >IMHO, any idea that starts with “Let´s create a central X” is doomed from
> the start.
> >
> >We must think along other
--- Begin Message ---
On Wed, Oct 11, 2017 at 11:30:06AM -0300, Carlos M. Martinez wrote:
IMHO, any idea that starts with ???Let??s create a central X??? is doomed from
the start.
We must think along other lines.
Maybe "central" was the wrong word to use. Think a DB that every
RIR provides a
--- Begin Message ---
IMHO, any idea that starts with “Let´s create a central X” is
doomed from the start.
We must think along other lines.
/Carlos
On 11 Oct 2017, at 11:21, Sascha Luck [ml] via db-wg wrote:
From: Sascha Luck [ml]
--- Begin Message ---
Sascha Luck [ml] wrote:
> How does this fact falsify the fact that cross-RIR route: objects
> exist? Those have to be in *some* irrdb and as long as a
> cross-RIR irrdb doesn't exist, part of the data will be
> non-authenticated...
it doesn't say anything about cross-RIR
--- Begin Message ---
> Also, what would the distinguisher be for eg. a route: with prefix
> from RIPE and ASN from ARIN?
thanks to the inability to inter-region transfer as-nums, that is
exactly my situation :)
randy
--- End Message ---
--- Begin Message ---
On Wed, Oct 11, 2017 at 02:46:54PM +0100, Nick Hilliard via db-wg wrote:
Job Snijders wrote:
I think this touches upon an incredibly important question: how do we
distinguish between garbage and properly authenticated "route:"
objects covering RIPE-managed space?
and