Perhaps a good place to start would be to get APE and WIX to implement a
common policy, and then those that peer at those locations are likely to
follow suit.
-----Original Message-----
...
Another thing I've also been thinking about is community attributes.
Using it to turn on remote blackholing with upstreams is useful, and we
saw at NZNOG the approach to communicate enhancements or variations of
that. But lowest common denominator suggests that using an agreed set of
community attributes (which works for everyone) to convey stuff is
something that should be worked on first.
So, combining an agreed set of local_pref's and some community
attributes might be the basis of building a broader, and faster exchange
between participants.
Community String Attributes
1000 Route is locally-originated, and should be exported
1000 Route is locally-originated, but should be suppressed towards peers
1002 Route is a blackhole route
1100 Route was learnt from a customer
1200 Route was learnt from a peer
1300 Route was learnt from a backbone
1400 Route was learnt from a transit provider (domestic/international)
Local Preference Values
130 - locally-originated
120 - customers
110 - peers
90 - backbone
85 - domestic
80 - international
...
