[j-nsp] Community based prepends.

[Pedro Roque Marques]

pr at isprime.com (Phil Rosenthal) writes:

> Hello.
> 
> As this topic has been raised in the autonomous-system thread, We are 
> planning on implementing community-based prepends for bgp customers, 
> which given the featureset available today, I think requires different 
> export policies for every peer.

Wouldn't a common export policy do the trick ?

community prepend-my-1 10458:1;
community prepend-my-2 10458:2;
community prepend-customer-1 10458:3;
community prepend-customer-2 10458:4;

policy-statement common-export {
    term a {
	from community prepend-my-1;
	then as-path-prepend "10458";
    }
    term b {
	from community prepend-my-2;
	then as-path-prepend "10458 10458";
    }
    term c {
	from community prepend-customer-1;
	then as-path-expand last-as;
    }

    term d {
	from community prepend-customer-2;
	then as-path-expand last-as count 2;
    }
    [...]
}

Or do you have different requirements ?

  Pedro.