Hi denis,
I am not sure if this feature is used or not however I think this is a
very good reason to not go forward with a clean-up (at least until we
have properly evaluated things).
We will probably have to figure out some other way to deal with
objects that are currently causing issues I
> Cross-registry queries are a fact of life. It is advisable to specify
> source lists explicitly because otherwise you can end up with all
> sorts of junk in a query
the ancient grotty code here orders the source query list per peer as it
generate phyltres, prioritiising the one they tell me
Niall O'Reilly via db-wg wrote on 30/11/2022 16:15:
If we indeed don't need a policy, I think it would be cleaner
to make this a new NWI, as adding to an NWI after implementation
work has begun seems, IMESHO, likely to cause confusion.
agreed. In terms of breakage, we're carrying a 25yo
denis walker wrote on 30/11/2022 14:26:
This is an interesting point. I know nothing about bgpq3 or peval
(even though it has been around since the beginning of time). So I
just read the documentation on GitHub for them. I never realised this
feature existed. What you have described here Nick is
On 29 Nov 2022, at 22:07, denis walker via db-wg wrote:
> I don't see that needing a policy. We can add it to NWI-19.
>
> Thoughts???
If we indeed don't need a policy, I think it would be cleaner
to make this a new NWI, as adding to an NWI after implementation
work has begun seems, IMESHO,
On Thu, 24 Nov 2022 at 16:13, Nick Hilliard via db-wg wrote:
>
> Niall O'Reilly via db-wg wrote on 23/11/2022 18:17:
> > What I have in mind is AS-NIALLSPECIAL, which I populate with a list of
> > AS numbers which I want to advertise to let others know that these
> > are to be handled in some
