missing aggregation opportunity

[jkroonza]

Hi,

Somewhat contrived, but given the current data for one of our peers:

jkroon@plastiekpoot ~ $ bgpq4 AS328173 -4
no ip prefix-list NN
ip prefix-list NN permit 196.250.204.0/22
ip prefix-list NN permit 196.250.204.0/24
ip prefix-list NN permit 196.250.205.0/24
ip prefix-list NN permit 196.250.206.0/24
ip prefix-list NN permit 196.250.207.0/24

This aggregates nicely to:

jkroon@plastiekpoot ~ $ bgpq4 AS328173 -4 -A
no ip prefix-list NN
ip prefix-list NN permit 196.250.204.0/22
ip prefix-list NN permit 196.250.204.0/22 ge 24 le 24

But here we can squeeze a bit more out:

jkroon@plastiekpoot ~ $ bgpq4 AS328173 -4 -A -R 23
no ip prefix-list NN
ip prefix-list NN permit 196.250.204.0/22 le 23
ip prefix-list NN permit 196.250.204.0/22 ge 24 le 24

This could become:

jkroon@plastiekpoot ~ $ bgpq4 AS328173 -4 -A -R 23
no ip prefix-list NN
ip prefix-list NN permit 196.250.204.0/22 le 24

As mentioned, somewhat contrived, I was just playing to fully understand the effects of -R and -m when I noticed this, and this probably doesn't reflect any real-world scenario. For a fact the whois and RPKI data for the specific peer is sub-optimal and incorrect.

[job]

Yes