[db-wg] Suggestion further validity-checking
- Previous message (by thread): [db-wg] Suggestion further validity-checking
- Next message (by thread): [db-wg] Suggestion further validity-checking
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Piotr Strzyzewski
Piotr.Strzyzewski at polsl.pl
Tue May 28 14:37:08 CEST 2019
On Tue, May 28, 2019 at 01:36:45PM +0200, Job Snijders via db-wg wrote: > On Tue, May 28, 2019 at 1:31 PM Nick Hilliard via db-wg <db-wg at ripe.net> wrote: > > > > 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. > > +1 for deprecation of "holes:" key. +1 Piotr -- Piotr Strzyżewski Silesian University of Technology, Computer Centre Gliwice, Poland
- Previous message (by thread): [db-wg] Suggestion further validity-checking
- Next message (by thread): [db-wg] Suggestion further validity-checking
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]