--- Begin Message ---
On Tue, 2017-07-18 at 15:26 +0200, Nick Hilliard via db-wg wrote:
>
> I am not in favour of having the RIPE database as an open-access
> database on the basis that this mixes up two sets of data,
> authoritative
> and non-authoritative, and it it is impossible for someone cas
--- Begin Message ---
On 11/08/2017, 05:14, Randy Bush via db-wg typed:
>
>>
>> databases. It's that they never have, and it's just the "way things
>> have been done". It's always ended up that they *can* support multiple
>> databases if asked to.
>
> when negotiating with a prospective pee
--- Begin Message ---
> That has proven to never really be an issue. When a network upstream
> of another network says they don't support additional databases for
> IRR, so far that has always proven to actually mean they've never
> needed to think about supporting multiple databases, and never had
--- Begin Message ---
Hi there,
On 09/08/2017, 19:34, Stefan Ideler via db-wg typed:
>
>
> As a result our route objects regardless of origin are noted in the RIPE
> database. Our upstreams use it to generate their prefix filters (and not all
> of them support multiple databases)
I won't c
--- Begin Message ---
Stefan Ideler via db-wg wrote:
> Being a member of multiple RIR's, the Ripe db is user friendly and a
> scriptable database. I don't want to divide my as-sets and prefix
> filter generation over 3 or more different database systems, with
> the additional maintenance and in som
--- Begin Message ---
Hi,
> I would like to have the IRR kept open, we have space from various
> regions and need to be able to make use of a single well known IRR in
> order to register our policies and be able to mix our ASNs with our
> space.
>This might indeed be the way forward for "I hav
--- Begin Message ---
> I would like to have the IRR kept open, we have space from various
> regions and need to be able to make use of a single well known IRR in
> order to register our policies and be able to mix our ASNs with our
> space.
There are non-RIR registries out there that can meet yo
--- Begin Message ---
* Gert Doering via db-wg [2017-07-20 09:42]:
> > > its a broken process. it inherently permits things to be said, which
> > > should not have been said.
> >
> > Time to set up a joint IRR database where only authoritative data from
> > participating RIRs is stored?
>
> Thi
oo.co.uk>, Database WG
> Bcc:
> Date: Thu, 20 Jul 2017 09:41:09 +0200
> Subject: Re: [db-wg] out of region routing in the RIPE Database
> Hi,
>
> On Tue, Jul 18, 2017 at 04:10:52PM +0200, Sander Steffann via db-wg wrote:
> > > its a broken process. it inherently permi
--- Begin Message ---
Hi,
On Tue, Jul 18, 2017 at 04:10:52PM +0200, Sander Steffann via db-wg wrote:
> > its a broken process. it inherently permits things to be said, which
> > should not have been said.
>
> Time to set up a joint IRR database where only authoritative data from
> participating
--- Begin Message ---
denis walker via db-wg wrote:
> Just for the record I have followed all previous discussions on this
> issue over many years within the RIPE community. There have been many
> (opposing) views expressed. I don't recall any consensus within the RIPE
> community to expel all, or
ann via db-wg
wrote:
>
>
> From: Sander Steffann
> Subject: Re: [db-wg] out of region routing in the RIPE Database
> Date: 18 July 2017 at 16:10:09 GMT+2
> To: George Michaelson
> Cc: Nick Hilliard , Database WG , denis
walker
>
>
--- Begin Message ---
> On 18 Jul 2017, at 17:03, Sander Steffann via db-wg wrote:
>
>
> From: Sander Steffann
> Subject: Re: [db-wg] out of region routing in the RIPE Database
> Date: 18 July 2017 at 16:10:09 GMT+2
> To: George Michaelson
> Cc: Nick Hilliard , Datab
rward.
cheersdenisco-chair DB-WG
From: Daniel Shaw via db-wg
To: Database WG
Sent: Tuesday, 18 July 2017, 16:39
Subject: Re: [db-wg] out of region routing in the RIPE Database
On 18/07/2017, 15:26, Nick Hilliard via db-wg typed:
>
>
> There are two main ways to fi
--- Begin Message ---
On 18/07/2017, 15:26, Nick Hilliard via db-wg typed:
>
>
> There are two main ways to fix this problem:
>
> 1. change all non-RIPE address space to have a different source: tag
>
> 2. remove all non-RIPE address space completely
>
> There is some previous discussion abo
6:10:09 +0200
> Subject: Re: [db-wg] out of region routing in the RIPE Database
> Hi George,
>
>> I think the previously stated position from APNIC region is clear: we
>> have problems with the logistics which permit resources from our
>> region to be included in IRR stat
--- Begin Message ---
Hi George,
> I think the previously stated position from APNIC region is clear: we
> have problems with the logistics which permit resources from our
> region to be included in IRR statements in the RIPE DB, when no formal
> check is made of permission or integrity, and we do
via db-wg wrote:
>
>
> -- Forwarded message --
> From: Nick Hilliard
> To: denis walker
> Cc: Database WG
> Bcc:
> Date: Tue, 18 Jul 2017 14:25:05 +0100
> Subject: Re: [db-wg] out of region routing in the RIPE Database
> denis walker via db-wg wr
--- Begin Message ---
denis walker via db-wg wrote:
> We would like to start off the (final?) round of discussions on this
> topic with a question. Should the RIPE Database be used as an open,
> free, global Internet Routing Registry (IRR)? If the answer is 'yes'
> then perhaps we should allow the
--- Begin Message ---
Colleagues
The DB-WG co-chairs would like to try to resolve (or close and document that as
a consensus) another long standing issue, out of region ROUTE(6) and AUT-NUM
objects in the RIPE Database (NWI-5).
We would like to start off the (final?) round of discussions on thi
20 matches
Mail list logo
