I've been looking into PfR for optimizing inbound traffic from the internet. The two forms of adjusting the inbound traffic is BGP AS-PATH prepending and AS-PATH Community. We have a mix of ISPs that support one or the other. For the ones that support only the AS-PATH community, I'm not sure how this works under PfR. I read that out of policy will add a community up to six times to try to bring the interface back into compliance. This can't be the same community 6 times can it? Every example I see shows a single community to adjust the AS-PATH advertisement from an ISP. How do you change to community to request different levels of prepending through PfR? Our ISP has a different community depending on how many times you want to prepend your advertisement. Does PfR accept a list of communities to support this?
ISP communities:
444:1 (prepend 1)
444:2 (prepend 2)
444:3 (prepend 3)
444:4 (prepend 4)
pfr master
border 10.4.5.6 key-chain pfr
interface Ethernet0/1 external
downgrade bgp community aa:nn (community number in aa:nn format)
dinterface Ethernet0/0 internal
