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]/
[routing-wg] ASN reference cleanup
- Previous message (by thread): [routing-wg] [db-wg-chairs] ASN reference cleanup
- Next message (by thread): [routing-wg] [training] RIPE NCC Webinars - new dates
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Roger Jørgensen
rogerj at gmail.com
Sat May 17 23:05:05 CEST 2014
On Wed, May 14, 2014 at 10:28 AM, Rob Evans <rhe at nosc.ja.net> wrote: > Folks, > > For any RPSL lovers among you that weren't at the Address Policy WG meeting > this morning, the topic of cleaning up referenced AS numbers came up again. > There are about ~2,000 16 bits ASNs that have been returned, but are still > referenced in the import/export lines of other aut-num objects, either > directly or via as-sets. Do anyone have any number on the scale of the problem as in how many out of those ~2000 are only referred to a few times, or maybe just internal referred toward another returned ASN? I would guess that there are some of those that are referred to more than others, and others have very few and easy to figure out the scope of. I know this will very likely be a manual process to verify this but the job probably has to be done sooner or later. -- Roger Jorgensen | ROJO9-RIPE rogerj at gmail.com | - IPv6 is The Key! http://www.jorgensen.no | roger at jorgensen.no
- Previous message (by thread): [routing-wg] [db-wg-chairs] ASN reference cleanup
- Next message (by thread): [routing-wg] [training] RIPE NCC Webinars - new dates
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]