Re: [db-wg] Foreign ROUTE objects in RIPE Database - final decision?

>> why not go the other, more positive, direction, and identify authorised >> data with RIPE-AUTH or whatever? no need to be pejorative. > > s/RIPE-NONAUTH/RIPE-OTHERRIR/ can there be cases where the source is not an rir? rfc1918 for example? s/RIPE-NONAUTH/JOB-HATES/ :) randy

Re: [db-wg] Foreign ROUTE objects in RIPE Database - final decision?

> Cc: > Bcc: > Date: Mon, 16 Oct 2017 23:22:55 + > 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

Re: [db-wg] Foreign ROUTE objects in RIPE Database - final decision?

>>> 2) Flag "route:" objects for non-RIPE-managed space with "source: >>> RIPE-NONAUTH" to identify non-authoritative data. >> >> why not go the other, more positive, direction, and identify authorised >> data with RIPE-AUTH or whatever? no need to be pejorative. > > This is not meant to be

Re: [db-wg] Foreign ROUTE objects in RIPE Database - final decision?

On Tue, Oct 17, 2017 at 05:18:55PM +, Randy Bush via db-wg wrote: > > 2) Flag "route:" objects for non-RIPE-managed space with "source: > > RIPE-NONAUTH" to identify non-authoritative data. > > why not go the other, more positive, direction, and identify authorised > data with RIPE-AUTH or

Re: [db-wg] Foreign ROUTE objects in RIPE Database - final decision?

> 2) Flag "route:" objects for non-RIPE-managed space with "source: > RIPE-NONAUTH" to identify non-authoritative data. why not go the other, more positive, direction, and identify authorised data with RIPE-AUTH or whatever? no need to be pejorative. randy

Re: [db-wg] Foreign ROUTE objects in RIPE Database - final decision?

Hi, 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

Re: [db-wg] Foreign ROUTE objects in RIPE Database - final decision?

--- Begin Message --- * den...@gmail.com (den is) [Tue 17 Oct 2017, 03:02 CEST]: 3) Consider possible, simple options to allow non RIPE resource holders to 'approve' (if not authorise) the creation of a foreign ROUTE object. This is cumbersome in practice already. Options 1 and 2 would lessen

Re: [db-wg] Foreign ROUTE objects in RIPE Database - final decision?

--- Begin Message --- Daniel Shaw via db-wg wrote: > On 17/10/2017, 03:24, William Sylvester via db-wg typed: >> > >> > >> > 1) Remove the "origin:" authorization requirement. RIPE is currently the >> > only RIR that requires this, the current implementation creates data >> > concurrency

Re: [db-wg] Foreign ROUTE objects in RIPE Database - final decision?

t; Onderwerp: Re: [db-wg] Foreign ROUTE objects in RIPE Database - final decision? Dear WG, chairs, On Mon, Oct 16, 2017 at 11:24:14PM +, William Sylvester via db-wg wrote: > Now that there has been substantial discussion on this topic, I wanted > to try to bring the conversation back t

Re: [db-wg] Foreign ROUTE objects in RIPE Database - final decision?

t; Onderwerp: Re: [db-wg] Foreign ROUTE objects in RIPE Database - final decision? Dear WG, chairs, On Mon, Oct 16, 2017 at 11:24:14PM +, William Sylvester via db-wg wrote: > Now that there has been substantial discussion on this topic, I wanted > to try to bring the conversation back t

Re: [db-wg] Foreign ROUTE objects in RIPE Database - final decision?

--- Begin Message --- Hi, Op 17 okt. 2017, om 09:53 heeft Job Snijders via db-wg het volgende geschreven: > These two options represent what currently is the lowest hanging fruit > to improve in this problem space. Funny enough, neither of these items > makes things more

Re: [db-wg] Foreign ROUTE objects in RIPE Database - final decision?

--- Begin Message --- On 11/10/2017, 17:48, Nick Hilliard via db-wg typed: > > > 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 more

Re: [db-wg] Foreign ROUTE objects in RIPE Database - final decision?

> > To: Database WG <db-wg@ripe.net> > > Cc: > > Bcc: > > Date: Mon, 16 Oct 2017 23:22:55 + > > Subject: Re: [db-wg] Foreign ROUTE objects in RIPE Database - final > decision? > > Db-wg members, > > > > Now that there has been substantial d

Re: [db-wg] Foreign ROUTE objects in RIPE Database - final decision?

wrote: > > > -- Forwarded message -- > From: William Sylvester <william.sylves...@addrex.net> > To: Database WG <db-wg@ripe.net> > Cc: > Bcc: > Date: Mon, 16 Oct 2017 23:22:55 + > Subject: Re: [db-wg] Foreign ROUTE objects in RIPE Database - final decision?

Re: [db-wg] Foreign ROUTE objects in RIPE Database - final decision?

--- Begin Message --- 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

Re: [db-wg] Foreign ROUTE objects in RIPE Database - final decision?

--- Begin Message --- On Wed, Oct 11, 2017 at 03:00:55PM +0100, Sascha Luck [ml] wrote: > 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

Re: [db-wg] Foreign ROUTE objects in RIPE Database - final decision?

;d...@c4inet.net> > Cc: Database WG <db-wg@ripe.net>, denis walker <ripede...@yahoo.co.uk> > Bcc: > Date: Wed, 11 Oct 2017 15:06:04 + > Subject: Re: [db-wg] Foreign ROUTE objects in RIPE Database - final decision? > > On Wed, 11 Oct 2017 at 16:52, Sascha L

Re: [db-wg] Foreign ROUTE objects in RIPE Database - final decision?

--- 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

Re: [db-wg] Foreign ROUTE objects in RIPE Database - final decision?

--- 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

Re: [db-wg] Foreign ROUTE objects in RIPE Database - final decision?

net> To: denis walker <ripede...@yahoo.co.uk> Cc: Database WG <db-wg@ripe.net> Subject: Re: [db-wg] Foreign ROUTE objects in RIPE Database - final decision? Date: October 11

Re: [db-wg] Foreign ROUTE objects in RIPE Database - final decision?

--- 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

Re: [db-wg] Foreign ROUTE objects in RIPE Database - final decision?

--- 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 ---

Re: [db-wg] Foreign ROUTE objects in RIPE Database - final decision?

--- 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

Re: [db-wg] Foreign ROUTE objects in RIPE Database - final decision?

--- Begin Message --- Question - Should the RIPE Database allow creation of ROUTE objects for non RIPE resources? >> >> yes > > then how can we use the traditional irrdb to distinguish between address > blocks which have been authenticated by the ripe ncc and those which > have not.

Re: [db-wg] Foreign ROUTE objects in RIPE Database - final decision?

--- Begin Message --- Randy Bush via db-wg wrote: >> > Question - Should the RIPE Database allow creation of ROUTE objects >> > for non RIPE resources? > > yes then how can we use the traditional irrdb to distinguish between address blocks which have been authenticated by the ripe ncc and those

Re: [db-wg] Foreign ROUTE objects in RIPE Database - final decision?

--- Begin Message --- > But this time we do need numbers. voting, eh? > Question - Should the RIPE Database allow creation of ROUTE objects > for non RIPE resources? yes randy --- End Message ---

Re: [db-wg] Foreign ROUTE objects in RIPE Database - final decision?

--- Begin Message --- On Tue, Oct 10, 2017 at 18:33 Sander Steffann via db-wg wrote: > Hi, > > > In any case, given that we have no proper global registry, and we have > > lots of cross-region routes ("addresses from RIR A, AS number from RIR > B"), > > we need to find a way to

Re: [db-wg] Foreign ROUTE objects in RIPE Database - final decision?

--- Begin Message --- Hi, > In any case, given that we have no proper global registry, and we have > lots of cross-region routes ("addresses from RIR A, AS number from RIR B"), > we need to find a way to document these properly. My preference would be to start such a global registry. I would

Re: [db-wg] Foreign ROUTE objects in RIPE Database - final decision?

--- Begin Message --- Sascha Luck [ml] via db-wg wrote: > Not allowing > "foreign" resources in the ripedb denies the reality that there > will always be RIPE-allocated prefixes originated from > non-RIPE-assigned ASNs and vice versa. Not true - you can easily run a whois query on whois.radb.net

Re: [db-wg] Foreign ROUTE objects in RIPE Database - final decision?

--- Begin Message --- Hi, On Mon, Oct 09, 2017 at 03:48:43PM +0200, denis walker via db-wg wrote: > Question - Should the RIPE Database allow creation of ROUTE objects for non > RIPE resources? I wonder if this is the right question to ask, or we should step back and ask the question what

Re: [db-wg] Foreign ROUTE objects in RIPE Database - final decision?

--- Begin Message --- On 09/10/2017 18:22, denis walker via db-wg wrote: C -Hank --- End Message ---

Re: [db-wg] Foreign ROUTE objects in RIPE Database - final decision?

--- Begin Message --- personal opinion: I don't care as a programmer. company's opinion: A - all our network resources are routed solely through our RIPE-AutNum. -- velia.net Internetdienste GmbH * Hessen-Homburg-Platz 1 * D-63452 Hanau Geschäftsführer: Franz G. Köhler, Arek Akilli * AG Hanau

Re: [db-wg] Foreign ROUTE objects in RIPE Database - final decision?

--- Begin Message --- Hello Denis, WG On Mon, 2017-10-09 at 15:49 +0200, denis walker via db-wg wrote: > A: Yes the RIPE Database should allow creation of ROUTE objects for > non RIPE resources. If this is the answer then we can look at how to > make the data more trusting in the short term (and

Re: [db-wg] Foreign ROUTE objects in RIPE Database - final decision?

--- Begin Message --- A On Mon, Oct 9, 2017 at 21:48 denis walker via db-wg wrote: > Colleagues > > This has been discussed many times with many views expressed. We are sure > lots of you are bored with commenting on this issue. Unfortunately no > consensus has yet been found.