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] Removal of bogon route objects
- Previous message (by thread): [db-wg] Removal of bogon route objects
- Next message (by thread): [db-wg] Removal of bogon route objects
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Ronald F. Guilmette
rfg at tristatelogic.com
Mon Jun 14 00:30:55 CEST 2021
In message <ca608a29-078d-e4be-33bf-15432f37964e at foobar.org>, Nick Hilliard <nick at foobar.org> wrote: >Edward Shryane via db-wg wrote on 11/06/2021 08:35: >> In total I found 825 route objects and 57 route6 objects with >> unregistered prefixes, and which are now eligible for deletion. > >Taking both non-merger transfers and unregistered / reserved prefixes >into account, I figure 1555 ipv4 prefixes and 59 ipv6 route objects: Now I'm confused. My understanding was that the plan was -just- to remove route object that referenced bogon space. Assuming that that is the current plan, then Ed's results and mine are in reasonably close agreement with regards to the number of IPv4 route objects that need to be purged, i.e. some 800+. Your figure is nearly double that, so obviously, you are fishing out a rather different set of IPv4 route objects than Ed and I are. Not saying you're wrong. Just saying that now I'm a bit confused about the actual scope of this cleanup project. Regards, rfg
- Previous message (by thread): [db-wg] Removal of bogon route objects
- Next message (by thread): [db-wg] Removal of bogon route objects
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]