Re: [routing-wg] 2018-06 Discussion Phase (RIPE NCC IRR Database Non-Authoritative Route Object Clean-up)

2019-05-23 Thread Andreas Larsen
I ageee on this proposal also.


Den 23 maj 2019 15:35 skrev Ben Maddison via routing-wg :
Hi WG,


On 2019-05-22 13:29:10+02:00 routing-wg wrote:

We encourage you to review this proposal and send your comments to
routing-wg@ripe.net before 20 June 2019.


I strongly support this proposal. Although we don't have any, many of our 
customers have out-of-region objects in the db, which are often 
stale/duplicated/wrong. I welcome any steps that can be taken to clean this 
mess out without waiting around for operators to "do-the-right-thing".

Cheers,

Ben



Re: [routing-wg] 2018-06 Discussion Phase (RIPE NCC IRR Database Non-Authoritative Route Object Clean-up)

2019-05-23 Thread Ben Maddison via routing-wg
Hi WG,


On 2019-05-22 13:29:10+02:00 routing-wg wrote:

We encourage you to review this proposal and send your comments to
routing-wg@ripe.net before 20 June 2019.


I strongly support this proposal. Although we don't have any, many of our 
customers have out-of-region objects in the db, which are often 
stale/duplicated/wrong. I welcome any steps that can be taken to clean this 
mess out without waiting around for operators to "do-the-right-thing".

Cheers,

Ben



Re: [routing-wg] 2018-06 Discussion Phase (RIPE NCC IRR Database Non-Authoritative Route Object Clean-up)

2019-05-23 Thread Job Snijders
On Thu, May 23, 2019 at 15:05 Cosmin Lupu  wrote:

>
> On Wed, May 22, 2019 at 2:29 PM Marco Schmidt  wrote:
>
>> We encourage you to review this proposal and send your comments to
>>  before 20 June 2019.
>>
>
>
> do you think the ROA check should be implemented also on addition of new
> records?
>


Dear Cosmin,

Nobody can create *new* records in the RIPE-NONAUTH database. It has been
locked down when NWI-5 was completed.

This checks/deletion proposal does *not* apply to the “RIPE” IRR source.
Only in the “RIPE” database can new objects be created. When new objects
are created in the “RIPE” database the creation of the object is verified
against the owner of the IP resource, so these objects are not problematic.

I understand we are juggling around quite some subtly different
datasources, apologies for confusion.

Kind regards,

Job


> I support this proposal
>
>
>


Re: [routing-wg] 2018-06 Discussion Phase (RIPE NCC IRR Database Non-Authoritative Route Object Clean-up)

2019-05-23 Thread Cosmin Lupu
On Wed, May 22, 2019 at 2:29 PM Marco Schmidt  wrote:

> We encourage you to review this proposal and send your comments to
>  before 20 June 2019.
>


do you think the ROA check should be implemented also on addition of new
records?

I support this proposal