Job Snijders via db-wg wrote on 14/10/2018 11:40:
This policy proposal concerns exclusively the RIPE-NONAUTH IRR
database. If you feel strongly about the information in the "RIPE" IRR
source feel free to make a new proposal.
There's no need for a new proposal: a notification mechanism and a gra
Hi,
On Sun, 14 Oct 2018, Nick Hilliard via db-wg wrote:
Job Snijders wrote on 14/10/2018 07:48:
When an operator makes a mistake, they've made a mistake.
When someone needs to create multiple ROAs, but only publishes one - it
is an operator error. When one misconfigures things... they a
On Sun, Oct 14, 2018 at 11:32:44AM +0100, Nick Hilliard wrote:
> Job Snijders wrote on 14/10/2018 07:48:
> > When an operator makes a mistake, they've made a mistake.
>
> > When someone needs to create multiple ROAs, but only publishes one - it
> > is an operator error. When one misconfigures thin
Hi,
On Sun, Oct 14, 2018 at 12:34 PM Randy Bush via db-wg wrote:
> > once a route/route6 object in RIPE-NONAUTH becomes in conflict with a
> > RPKI ROA it should no longer exist.
>
> and once a route/route6 object in the ripe irr instance comes in
> conflict with a roa published anywhere in the r
> once a route/route6 object in RIPE-NONAUTH becomes in conflict with a
> RPKI ROA it should no longer exist.
and once a route/route6 object in the ripe irr instance comes in
conflict with a roa published anywhere in the rpki, it should no longer
exist?
randy
Job Snijders wrote on 14/10/2018 07:48:
When an operator makes a mistake, they've made a mistake.
When someone needs to create multiple ROAs, but only publishes one - it
is an operator error. When one misconfigures things... they are
misconfigured, no big deal.
operator error happens all th
