[db-wg] RIPE Policy Proposal 2018-06 Aims to Delete Conflicting Non-authorative IRR Objects
- Previous message (by thread): [db-wg] RIPE Policy Proposal 2018-06 Aims to Delete Conflicting Non-authorative IRR Objects
- Next message (by thread): [db-wg] RIPE Policy Proposal 2018-06 Aims to Delete Conflicting Non-authorative IRR Objects
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Nick Hilliard
nick at foobar.org
Mon Oct 15 12:52:02 CEST 2018
On 15 Oct 2018, at 11:31, Job Snijders <job at instituut.net> wrote: > > I'm hesitant to add such things because we don't have such a > notification & grace period in BGP Origin Validation process when > processing BGP route announcements either. You don’t need one there. If there’s a problem with those you can back out the configuration and life will proceed as before. The difference between the examples you’re giving and this proposal is that - as it stands - this proposal will automatic activate a mechanism with no backout, no grace period and no warning. Nick
- Previous message (by thread): [db-wg] RIPE Policy Proposal 2018-06 Aims to Delete Conflicting Non-authorative IRR Objects
- Next message (by thread): [db-wg] RIPE Policy Proposal 2018-06 Aims to Delete Conflicting Non-authorative IRR Objects
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]