[db-wg] [routing-wg] Solving the issue of rogue ROUTE objects in the RIPE Database

Dear working groups,

A small clarification.

> On 11 Nov 2015, at 14:52, denis <ripedenis at yahoo.co.uk> wrote:
>> 
>> So, with the caveat about automated deletion of objects that we do
>> have concerns with, we think we could implement the above as an
>> intermediate solution. We would also like to point out that we can
>> build on this step by step. E.g. we can start disallowing route
>> objects for Afrinic resources and direct people to the Afrinic IRR,
>> while still applying the above strategy for resources from other
>> regions.
> 
> From what I understood from Gert and Randy's comments it is a user's choice where to put a ROUTE object and there seem to be some reasons why they sometimes choose to put it in the RIPE Database. Is there some specific policy now that prohibits ROUTE objects in the RIPE Database for AFRINIC resources?

No, there is no such policy. I was referring to the "Afrinic IRR Homing Project" and how it could fit this model. RIPE NCC and Afrinic were asked to work on a proposal for this. We will present it during the DB WG session at the RIPE Meeting (next week), and I believe it's best to discuss this in more detail then. But to be absolutely clear: we would only implement after working group discussion and consensus called by the chairs. The same applies obviously for other proposals and suggestions mentioned in this thread.


Kind regards,

Tim Bruijnzeels
Assistant Manager Software Engineering
RIPE NCC Database Group