Your IP Address is: 13.59.82.167
Tip: try using "quotes around your search phrase"
You're viewing an archived page. It is no longer being updated.
Draft Minutes from Database WG - RIPE 67
Thursday, 17 October, 11:00 – 12:30
WG Chairs: Wilfried Woeber, Nigel Titley, Ulf Kieber
Scribe: Nigel Titley
Welcome
The presentation is available online at:
https://ripe67.ripe.net/presentations/321-DB_WG_Presentation_rev_7.pdf
Operational Report
The RIPE Database has been rewritten in Java. Now 2500 unit and integration test and 1500 end to end tests. Previously there were none. Currently about 430 queries per second
Software Release Management and TEST Database
Proper release management system now in place and being tuned. Main improvement is to add real data to the test system. Major releases which will encompass feature development and will include a test period. Minor releases will be bug fix only and will have an immediate deployment.
The TEST Database code is open source and the code base is on Github. Users are now contributing to code. You can run a local instance for experimentation.
Rudiger Volk made a short presentation on minimum requirements for the RIPE Database software update process. The presentation is available online at:
https://ripe67.ripe.net/presentations/320-rv-RIPE-DB-requirements.pdf
Points included:
Documentation
The RIPE Database documentation needs a major update. It is difficult to search and not necessarily all available in one place. The Database Team will work with the Communications Department to make this more useful.
Survey
Resiliency
Hot node is now online in Stockholm. The database is the first service that has been made available.
Action Points
Things "in the pipeline"
Unresolved Features
Upcoming Features
Functionality and/or restrictions by components
Policy or business logic interactions
Coordination/input with/from other Working Groups.
The presentation is available online at:
https://ripe67.ripe.net/presentations/324-self-published-geo_RIPE67.pdf
Existing system used by Google to allow network providers to publish geo data.
Allows rapid updates especially for networks that move around.
It was noted from the floor that prefixes are much easier to handle than address ranges.
It was noted that there are already mechanisms to allow the registration of geolocation data.
Presentation on infrastructure GeoLoc by the RIPE NCC in MAT Working Group.
Abuse information (RV) One thing that is still missing is documentation to suggest what information should be sent to the abuse-c contact and what the abuse contact should expect. Response from the RIPE NCC is that this has been specifically discussed and the Abuse Contact management task force specifically decided not to be prescriptive. This is really an issue for the Anti-Abuse Working Group to sort out.
Note to the Working Groupthat the question of Working Group chair appointment and retirement is being considered by the Working Group Chairs' collective and that input from the Working Group is very welcome
A note from Alexander Azimov who has completed an analysis of route policy data and found it to be generally very poor. He asked whether we should be verifying or deleting this data. It was suggested that this should be referred to the Routing Working Group