[routing-wg] 2018-06 New Policy Proposal (RIPE NCC IRR Database Non-Authoritative Route Object Clean-up)
- Previous message (by thread): [routing-wg] 2018-06 New Policy Proposal (RIPE NCC IRR Database Non-Authoritative Route Object Clean-up)
- Next message (by thread): [routing-wg] 2018-06 New Policy Proposal (RIPE NCC IRR Database Non-Authoritative Route Object Clean-up)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Tom Smyth
tom.smyth at wirelessconnect.eu
Tue Oct 16 14:03:30 CEST 2018
Im happy with the proposal, again I think the prior notification + graceperiod suggestion makes sense +1 Thanks TOm Smyth On Tue, 16 Oct 2018 at 12:57, Tore Anderson <tore at fud.no> wrote: > > * Marco Schmidt > > > A new RIPE Policy proposal, 2018-06, "RIPE NCC IRR Database Non-Authoritative Route Object Clean-up", is now available for discussion. > > > > The goal of the proposal is to delete an non-authoritative object stored in the RIPE IRR, if it conflicts with an RPKI ROA. > > I've read the policy proposal and I think it makes sense. > > I see some respondents in db-wg asking for a notification of an upcoming > deletion followed by a grace period. That's a reasonable ask, considering > that a deletion of a RIPE-NONAUTH object is irreversible. > > In any case, +1. > > Tore >
- Previous message (by thread): [routing-wg] 2018-06 New Policy Proposal (RIPE NCC IRR Database Non-Authoritative Route Object Clean-up)
- Next message (by thread): [routing-wg] 2018-06 New Policy Proposal (RIPE NCC IRR Database Non-Authoritative Route Object Clean-up)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]