[ris-int] Prepending experiment: meaning of communities

Hi James,

here is a hopefully less confusing meaning of the communities we're 
planning to use:

> 12654:10x : Prepend AS12654 x times to AS16150 (RRC07), AS1299 (RRC10), AS6762 (RRC14)
> 12654:20x : Prepend AS12654 x times to AS5400 (RRC07), AS9026 (RRC10), and AS6939 (RRC14)
> 12654:30x : Prepend AS12654 x times to AS13237 (RRC07), AS12779 (RRC10), and AS2914 (RRC14)
> 
> 12654:199 : Don't announce to AS16150 (RRC07), AS1299 (RRC10), or AS6762 (RRC14)
> 12654:299 : Don't announce to AS5400 (RRC07), AS9026 (RRC10), or AS6939 (RRC14)
> 12654:399 : Don't announce to AS13237 (RRC07), AS12779 (RRC10), or AS2914 (RRC14)

The route-map I gave you is out of date and uses 12654:40x instead of 
12654:x99, but the principle is the same.

So for example, announcing 84.205.73.0/24 to RRC07 with a community 
value of "12654:199 12654:202 12654:301" should result in RRC07 
announcing nothing at all to AS16150, "12654 12654" to AS5400, and 
"12654 12654 12654" to AS13237.

Since cow announces three different prefixes RRC07, RRC10, and RRC14, 
this should give us complete control over who we announce to and how 
much we prepend to each upstream. As far as we can see, these RRCs only 
have three peers giving transit for the beacon prefixes, but perhaps we 
need an explicit rule that denies the routes to anyone else...

Do you think all this makes sense and could actually work?



Cheers,
Lorenzo

P.S. I attach the setup diagram in powerpoint format for the benefit of 
others on the list.

-- 
Lorenzo Colitti                          lorenzo at ripe.net
Network Engineer                           +31-20-5354471
RIPE NCC                                     www.ripe.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: setup.ppt
Type: application/vnd.ms-powerpoint
Size: 51200 bytes
Desc: not available
URL: <https://www.ripe.net/ripe/mail/archives/ris-int/attachments/20060502/1fab9d1c/attachment.ppt>