> Generally it's sensible practice to filter on source: attributes, as
> there is a good deal
... of unfinished emails on the internet.
Also, of junk stored in a bunch of irrdbs, some of which have ended up
as unmaintained toxic dumping grounds for route objects.
Nick
Randy Bush wrote:
> peval() does not look at source:. and thanks, don't tell a whole lot of
> folk to change software.
it does if you tell it to:
% peval -s RIPE AS-BLAH
Generally it's sensible practice to filter on source: attributes, as
there is a good deal
> and you know that the point of m
On 4/5/2018 2:27 PM, Nick Hilliard via db-wg wrote:
Randy Bush via db-wg wrote:
and we are supposed to use the high quality ripe irr as authoritative
data for routing validation?
the current plan is to re-mark all out-of-region route / route6 / autnum
objects with source: RIPE-NONAUTH and to di
>> and we are supposed to use the high quality ripe irr as authoritative
>> data for routing validation?
>
> the current plan is to re-mark all out-of-region route / route6 /
> autnum objects with source: RIPE-NONAUTH and to disable creation of
> these objects in future. Unless something has been
Randy Bush via db-wg wrote:
> and we are supposed to use the high quality ripe irr as authoritative
> data for routing validation?
the current plan is to re-mark all out-of-region route / route6 / autnum
objects with source: RIPE-NONAUTH and to disable creation of these
objects in future. Unless
> We're back to this again... more of our space is being hijacked using
> a RIPE IRR entry:
>
> route: 108.160.128.0/20
> descr: 2nd route
> origin: AS19529
> mnt-by: ADMASTER-MNT
> created: 2017-11-15T17:41:46Z
> last-modified: 2017-11-15T17:41:46Z
> sou
We're back to this again... more of our space is being hijacked using a
RIPE IRR entry:
route: 108.160.128.0/20
descr: 2nd route
origin: AS19529
mnt-by: ADMASTER-MNT
created: 2017-11-15T17:41:46Z
last-modified: 2017-11-15T17:41:46Z
source: RIPE
denis walker via db-wg wrote:
> Perhaps after the RIPE NCC implements the agreed actions on foreign
> ROUTE objects, it would be a good idea to do a (one time?)
> cleanup/review of all foreign ROUTE objects in the RIPE IRR. Find the
> contact details in the appropriate RIR Database for all non RIPE
; cheers
> denis
> co-chair DB WG
>
>
> --
> *From:* Job Snijders via db-wg
> *To:* Brian Rak
> *Cc:* db-wg@ripe.net
> *Sent:* Thursday, 9 November 2017, 17:53
>
> *Subject:* Re: [db-wg] Getting fraudulent entries removed
>
> D
: Thursday, 9 November 2017, 17:53
Subject: Re: [db-wg] Getting fraudulent entries removed
Dear Brian,
It appears that RIPE NCC is lacking a clear and expedient procedure to
remedy unauthorised route object creation. I'd be happy to volunteer to
work with the RIPE NCC to develop a procedure
Den 2017-11-09 kl. 17:22, skrev Brian Rak via db-wg:
> Hi,
>
> We've run into an issue where an unknown malicious party appears to
> have hijacked some of our IP space. They created entries in the RIPE
> database that they are using to actually get this space announced.
> What's even worse is the
On 11/9/2017 11:52 AM, Job Snijders wrote:
Dear Brian,
It appears that RIPE NCC is lacking a clear and expedient procedure to
remedy unauthorised route object creation. I'd be happy to volunteer to
work with the RIPE NCC to develop a procedure that aligns with industry
standards on how to veri
Dear Brian,
It appears that RIPE NCC is lacking a clear and expedient procedure to
remedy unauthorised route object creation. I'd be happy to volunteer to
work with the RIPE NCC to develop a procedure that aligns with industry
standards on how to verify abuse reports like these and resolve them in
13 matches
Mail list logo
