|
|
|
assignment policy is documented in:
RIPE NCC members can request AS Numbers using the
form available in the LIR Portal or at:
****************************************************
Information about the RIPE Database can be found at:
http://www.ripe.net/db/index.html
****************************************************
You may use communities to control outgoing information
via the route server. The meaning and order of evaluation is
important.
block of announcement of a route to a certain peer 0:peer-as
announcement of a route to a certain peer 6695:peer-as
block of announcement of a route to all peers 0:6695
announcement of a route to all peers 6695:6695
There are additional communities for controlling announcements.
6695:65000 peer is using bad netmask (80.81.192.0/24)
6695:65001 peer is using bad netmask (80.81.193.0/24)
6695:65003 prefix is injected at DE-CIX1
6695:65004 prefix is injected at DE-CIX2
6695:65005 prefix is injected at DE-CIX3
6695:65006 prefix is injected at DE-CIX4
6695:65281 set community NO-EXPORT
Please take care when setting 0:x communities as this changes
the local-preference:
community local-preference
--------------------------------
0:6695 0
0:x, x!= 6695 50
else or nothing 100
For more information pls contact peering@de-cix.net or see
http://www.de-cix.net
The above information was collected from whois.ripe.net, using
object "AS6695" on July 15, 2010
|
