Additional ACL prefix-generating attributes

[ipspace]

Resolving prefixes by the new linkid is something we should have. (by @DanPartelly in #3766)

@DanPartelly @jbemmel -- would it make more sense to have new attributes (linkid, vlan, role) or to reuse the prefix attribute and expand it to look up named prefixes, link IDs, link roles, and VLAN prefixes?

[DanPartelly]

I generally hate overloading, but I believe in this case, reuse of the prefix may improve user experience and make topologies easier to read.

[jbemmel]

@DanPartelly @jbemmel -- would it make more sense to have new attributes (linkid, vlan, role) or to reuse the prefix attribute and expand it to look up named prefixes, link IDs, link roles, and VLAN prefixes?

Can you show an example config? I'm having trouble visualizing what we're talking about, and looking at #3766 I do not see Dan's comment there?

[ipspace]

Can you show an example config?

Let's say you want to match the prefix of VLAN red and link with link ID abc as the source IP address in an ACL. You could either write:

routing.acl.example:
- src.vlan: red
- src.linkid: abc

or

routing.acl.example:
- src.prefix: [ red, abc ]