I'm currently thinking about a redesign of the style of the structure prefix-lists. I think it's not that useful to identify a prefix within a prefix-list with a rule-id. Furthermore the allow or deny statements do not make that much sense.
It would be much easier to have prefix-lists in the JunOS style which is just a list a bunch of prefixes in a array.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | FEATURE REQUEST | None | T2425 Rewrite all policy zebra filters to XML/Python style | ||
| Open | FEATURE REQUEST | None | T1733 structure of prefix-lists |
@MrXermon Let's say someone is setting up BGP peering and wants to control import or export of prefixes using prefixlist. With your suggestion, how would you deny certain prefixes and accept all others? Can JunOS solve this directly with prefixlist without using route-map?