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] Fw: [db-wg] Suggestion further validity-checking
- Previous message (by thread): [routing-wg] 2018-06 Discussion Phase (RIPE NCC IRR Database Non-Authoritative Route Object Clean-up)
- Next message (by thread): [routing-wg] Fw: [db-wg] Suggestion further validity-checking
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
ripedenis at yahoo.co.uk
ripedenis at yahoo.co.uk
Tue May 28 15:13:03 CEST 2019
Colleagues We have had a suggestion (with some support) on the DB-WG mailing list about deprecating the "holes:" attribute in ROUTE(6) objects. Perhaps the Routing WG could consider if this attribute has any value in the RIPE Database. cheersdenis co-chair DB-WG ----- Forwarded message ----- From: Nick Hilliard via db-wg <db-wg at ripe.net>To: Edward Shryane <eshryane at ripe.net>Cc: "db-wg at ripe.net" <db-wg at ripe.net>Sent: Tuesday, 28 May 2019, 13:30:30 CESTSubject: Re: [db-wg] Suggestion further validity-checking Edward Shryane via db-wg wrote on 28/05/2019 12:12: > Unfortunately, no cleanup was done when this rule was implemented, > but in recent times we try to do this. I will also contact the > maintainers of these route objects and ask them to fix the holes > attribute(s). I wonder if this key should be formally deprecated. It's used for 643 out of 302354 route: objects and 40 out of 28803 route6: objects, i.e. ~0.2% and 0.1% respectively. The complexity associated with handling it is substantial and most tools simply ignore it. Nick -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/routing-wg/attachments/20190528/a91d4a62/attachment.html>
- Previous message (by thread): [routing-wg] 2018-06 Discussion Phase (RIPE NCC IRR Database Non-Authoritative Route Object Clean-up)
- Next message (by thread): [routing-wg] Fw: [db-wg] Suggestion further validity-checking
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]