[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 ]
Cynthia Revström
me at cynthia.re
Thu Jul 8 09:04:01 CEST 2021
Hi Hank, As Ed mentioned earlier in the thread all of those except AS23456 are already blocked. -Cynthia On Thu, Jul 8, 2021, 08:14 Hank Nussbacher via db-wg <db-wg at ripe.net> wrote: > 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 > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.ripe.net/ripe/mail/archives/db-wg/attachments/20210708/25715d44/attachment.html>
- 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 ]