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] Adding "::" notation to RIPE DB
- Previous message (by thread): [routing-wg] Adding "::" notation to RIPE DB
- Next message (by thread): [routing-wg] Adding "::" notation to RIPE DB
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
James Bensley
james at inter.link
Sun Nov 13 13:54:33 CET 2022
From: routing-wg <routing-wg-bounces at ripe.net> on behalf of Cynthia Revström via routing-wg <routing-wg at ripe.net> Sent: 11 November 2022 01:54 To: routing-wg at ripe.net Subject: Re: [routing-wg] Adding "::" notation to RIPE DB ... These tweets[1] from Ben Cox who many of you might know really highlights another issue with recursive as-sets. (Essentially, there are as-sets that are recursively so big as to include more AS's than exist in the DFZ. To me feels like you might as well just ignore the filter entirely and just always accept in such a case.) [1]: https://twitter.com/Benjojo12/status/1578417574790205441 -Cynthia ________________________________________ Hi Cynthia, AFAICT this is expected and valid behaviour. There will always be more ASNs registered than actually being used. Also, there is no one DFZ view. It looks different in different parts of the world/Internet, some of the ASNs will be visible only in certain locations. This is normal operating procedure in my opinion. Cheers, James.
- Previous message (by thread): [routing-wg] Adding "::" notation to RIPE DB
- Next message (by thread): [routing-wg] Adding "::" notation to RIPE DB
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]