On 05/12/2017, 11:11, Tim Bruijnzeels via db-wg typed:
>
>
> We suggest the following solution as a basis for further discussion.
>
> 1) Remove the "origin:" authorization requirement
> the "mnt-routes:" attribute on AUT-NUM objects will no longer be useful. We
> propose that the attribute is
--- Begin Message ---
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
> issues across Internet databases by requiring
--- Begin Message ---
On 11/10/2017, 18:22, Saschatyped:
>
>
>> Question - Should the RIPE Database allow creation of ROUTE objects for non
>> RIPE resources?
This question has to be split into two to be able to be answered.
Part 1: Should RIPE DB allow creation of route/route6 objects whe
--- 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
--- Begin Message ---
On 11/10/2017, 14:09, Job Snijders via db-wgtyped:
> You
> as network operator can easily poll the APNIC or AFRINIC database.
> There are even a number of "IRR aggregation services" such as NTTCOM
> and RADB which mirror a ton of IRRs for your querying convenience.
Witho
--- 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 ---
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 ---
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
