120 likes | 260 Views
RIPE Database Operations Update. Olaf Kolkman RIPE NCC <olaf@ripe.net>. Outline. Database statistics Database development Development plans. Facts and Figures. 1.8 M objects, 41% inetnum, 47% person 25 q/s on average, spikes of 100 q/s 4 updates/min, 18% inetnum, 75% person
E N D
RIPE Database Operations Update Olaf Kolkman RIPE NCC <olaf@ripe.net>
Outline • Database statistics • Database development • Development plans
Facts and Figures • 1.8 M objects, 41% inetnum, 47% person • 25 q/s on average, spikes of 100 q/s • 4 updates/min, 18% inetnum, 75% person Object counts, query loads, etc. available on-line: http://www.ripe.net/db/dbconstat http://www.ripe.net/db/mrtg/whois.html • 110,000 query users on average
Database Contents inetnum +84,668 (13%) person +70,105 (9%) inet6num +460 (70%)
Query rate and objects returned Number of objects/day 5,700,000 Query rate, weekly av 25 q/s Still 30% public, 70% contact...
Database developments: Whois server • Improved query processing • More helpful, consistent results • Additional server information available, -q types • Limit number of concurrent connections from IP • Some protection from DoS (less against DDoS)
Database developments:Webupdates • Web updates in production • Allows addition, modification, deletion through WWW • Built on sync-updates back-end • No PGP support • Does not bypass security restrictions • Secure updates possible in PKI framework… http://www.ripe.net/webupdates https://www.ripe.net/webupdates
Database developments:IPv6 query proxy • IPv6 queries supported • Proxy server • Supports queries externally now, while IPv6 monitored • Client source available • Full presentation in IPv6 Working Group • Slides soon to be available from the meeting page
Future Plans • New update processing • Improved reporting (fuller, clearer reports & error information) • Input processing revisited • RPSLng • Server support for IPv6 and multicast RPSL objects & attributes • IRRToolSet support • Unreferenced person/role cleanup process • Update processing semantic changes • Mostly for consistency and protection, will go to list soon!