This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/

[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
Sun Oct 14 23:27:28 CEST 2018

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 grace 
period can be built into either the proposal or else the operating 
procedure.

Some of these old route objects have been there for many years. Another 
couple of weeks isn't going to cause a huge amount of harm.

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 ]