This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/routing-wg@ripe.net/
[routing-wg] Implementation of "pingable:" attribute in the RIPE Database
- Previous message (by thread): [routing-wg] Prefix hijacking possibility
- Next message (by thread): [routing-wg] How much traffic goes to unallocated address space?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Denis Walker
denis at ripe.net
Mon Feb 21 13:50:59 CET 2011
[Apologies for duplicate emails] Dear Colleagues, The RIPE NCC has implemented the "pingable:" and "ping-hdl:" attributes according to the specification in RFC 5943. They can now be used in ROUTE and ROUTE6 objects in the RIPE Database. RFC 5943 describes the syntax and explains how to use them: http://tools.ietf.org/html/rfc5943 The "pingable:" addresses are already active for beacons, anchors and debogon routes announced by the RIPE NCC Routing Information Service (RIS). For an example of how these are announced, see the ROUTE object for 84.205.81.0/24. For more information about RIS beacons and anchors, please see: http://www.ripe.net/data-tools/stats/ris/ris-routing-beacons Regards, Denis Walker Business Analyst RIPE NCC Database Group
- Previous message (by thread): [routing-wg] Prefix hijacking possibility
- Next message (by thread): [routing-wg] How much traffic goes to unallocated address space?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]