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] Further cleanup (was: RIPE NONAUTH route(6) objects using unregistered space cleanup - deployment *today*)
- Previous message (by thread): [db-wg] Further cleanup (was: RIPE NONAUTH route(6) objects using unregistered space cleanup - deployment *today*)
- Next message (by thread): [db-wg] Further cleanup (was: RIPE NONAUTH route(6) objects using unregistered space cleanup - deployment *today*)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hank Nussbacher
hank at interall.co.il
Thu Jul 8 08:14:20 CEST 2021
On 08/07/2021 00:29, Nick Hilliard via db-wg wrote: > Edward Shryane via db-wg wrote on 07/07/2021 15:05: >> So 23456 is*not* excluded, but it can be if the DB-WG agrees. > > just to be clearer: AS23456 should be included in the list of ASNs which > cannot be used as the origin. > > Any objects which refer to it should be flagged for deletion. > > Nick Why single out 23456 when there are many other ASNs such as those listed here: https://en.wikipedia.org/wiki/Autonomous_system_(Internet)#ASN_Table In the same way we would not allow 10.0.0.0 to appear as an inetnum in the DB, so too numerous private use and reserved ASNs should not appear in the DB. Regards, Hank
- Previous message (by thread): [db-wg] Further cleanup (was: RIPE NONAUTH route(6) objects using unregistered space cleanup - deployment *today*)
- Next message (by thread): [db-wg] Further cleanup (was: RIPE NONAUTH route(6) objects using unregistered space cleanup - deployment *today*)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]