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/db-wg@ripe.net/

[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 ]

Christoffer Hansen (Lists) netravnen+lists at gmail.com
Tue Oct 16 10:26:47 CEST 2018

Den 16-10-2018 kl. 03:56 skrev denis walker via db-wg:
> (...) So should we also be promoting
> the RIRs authoritative IRRs over commercial IRRs so that ROUTE objects
> can all be created with proper authorisation?

In my mind. It makes sense if commercial IRRs were never born. And
databases of route(6) objects was hosted by the RIRs.
Which would then validate any attempts for creating route(6) objects is
actually done by an authorised entity.

But then ... history ... :sigh:

-Christoffer

• 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 ]