Defines for mixed IPv6/IPv4

[Jeroen Massar]

> On 24 Jan 2024, at 11:08, Maria Matejka <maria.matejka at nic.cz> wrote:
> 
> 
> 
> On 24 January 2024 08:53:19 CET, Jeroen Massar via Bird-users <bird-users at network.cz> wrote:
>> 
>> 
>>> On 23 Jan 2024, at 14:13, Nico Schottelius via Bird-users <bird-users at network.cz> wrote:
>>> 
>>> 
>>> Hello bird users,
>>> 
>>> I am wondering how you handle matching both IPv6 and IPv4 prefixes
>>> efficiently.
>>> 
>>> We have tons of blocks in our config like these:
>> 
>> Generate the configs.
> 
> Not only that, please split IPv6 and IPv4 filters, at least if these are prone to frequent changes.
> 
>> Especially when doing IRR filtering, one simply lets bgpq4 generate the filters
>> and then drop those definitions into a bird include file, and generate the peers parts too.
> 
> When doing IRR filtering, please export it as JSON and load it through RTR mechanism. We support multiple ROA tables and this is exactly the use case for it

Mmm... do you mean IRR data (what bgpq4 generates from RPSL) or RPKI data (what rpki-client generates from ROAs) ?

As yes, RPKI data we generate into a JSON file and then pass that to a RTR which serves it up to bird; but IRR data becomes filter statements ("bgpq4 -b" ;) )

Greets,
 Jeroen