[ris-int] Announcement: Changes to RIS Routing Beacons

------- Blind-Carbon-Copy

To: ris-users at ripe.net, ops at linx.net, sfinx at ml.renater.fr,
    tech-l at ams-ix.net, announce at nl-ix.net, tech-users at lists.gn-ix.nl,
    vixoper at vix.at, peer.tech at mix-it.net
Reply-To: ris at ripe.net
Subject: Announcement: Changes to RIS Routing Beacons
From: James Aldridge <james at ripe.net>
X-Organization: RIPE Network Coordination Centre
X-Phone: +31 20 535 4444
X-Fax: +31 20 535 4445
Date: Fri, 25 Feb 2005 13:56:38 +0100
Sender: james at x34.ripe.net

[Apologies for duplicate messages]

The RIPE Routing Information Service has made some alterations to our BGP
Routing Beacon announcements.  The main changes (since 3 February 2005) are:

*  Beacon prefixes now come from a new, larger address range 84.205.64.0/19
   (instead of 195.80.224.0/20);

*  We now announce an "anchor prefix" corresponding to each beacon;

*  For each beacon and anchor prefix there is a "pingable" target at the first
   address in the range (beaconNN.ris.ripe.net, anchorNN.ris.ripe.net).

All prefixes announced by the RIS (AS12654) are listed in the AS12654:RS-RIS
'route-set' and individual 'route' objects in the RIPE Database and are
described in more detail at
http://www.ripe.net/projects/ris/docs/beaconlist.html

RIS peers should set any maximum prefix limit to at least the number of
entries listed in the route-set (although it is unlikely that any one RRC will
ever advertise more than a small subset of these prefixes).  We would also
like our peers to treat these prefixes in the same way that they would a
customer's prefix and announce them to their other peers and upstream
providers.

If you have any questions, please contact the RIS team at ris at ripe.net.

Regards,
The RIPE NCC RIS Team

------- End of Blind-Carbon-Copy