Routing Certification Beacons
In January 2011, the RIPE NCC will announce the production launch of the resource certification system which is documented in more detail here: http://www.ripe.net/certification/
In order to assist network operators and other interested parties in the successful deployment of resource certification technology, we made some extensions to the BGP beacons which we provide as a part of the Routing Information Service (RIS).
The routing certification beacons are intended to provide prefixes with known fixed states so that network operators and engineers can test that their router configurations treat such prefixes in the desired manner. We also anticipate that visibility measurements against these beacons will enable researchers to measure uptake and penetration of certification technology as it become more commonplace.
In addition to the existing beacon prefixes , we are now announcing:
1) Two prefixes with a valid Route Origin Authorization (ROA) object:
There are pingable addresses within these ranges, these exist in DNS as cert-valid.ris.ripe.net which resolves to:
184.108.40.206 and 2001:7fb:fd02::1
2) Two prefixes with valid ROA object, but where the origin AS (AS12654) is different than that listed in the ROA (AS196615)
There are pingable addresses within these ranges, these exist in DNS as cert-bad-origin.ris.ripe.net which resolves to:
220.127.116.11 and 2001:7fb:fd03::1
In addition to the above, we continue to announce stable anchor prefixes from the same location. These prefixes have no ROAs associated with them. They have pingable addresses in DNS as cert-none.ris.ripe.net.
The full list of RIS beacon prefixes, their characteristics and functions is available via our website here .
We hope that this extension to the RIS will prove useful to members of our community, and we invite feedback and comments to enable us to refine and improve this service.