Your IP Address is: 54.242.75.224
Tip: try using "quotes around your search phrase"
You're viewing an archived page. It is no longer being updated.
RIPE Meeting: |
56 |
Working Group: |
Database |
Status: |
Final |
Revision Number: |
1 |
Actions from previous meetings
AP54.3 Mandatory MNT-BY.
Code is completed but two issues which means that before can be deployed much more rigorous testing needed to be done.
Ongoing
AP54.7 rev-srv deprecation.
Needs a database schema change. Will be released at the same time as AP54.3.
Ongoing
AP54.4
White pages. New org-type and will be maintained by WG-Chairs.
AP54.6
Clean up unref'ed person objects.
Started. 400k remain. Same problem as AP54.3. Start by implementing AP54.4. Monitor object weekly from outside DB and remove if unreferenced for 3 weeks.
Ongoing
AP55.1
Add mnt-irt to LIRportal.
This is not possible at the moment. It has been added to the rewrite schedule for the portal which will take place late this year or early next.
Ongoing
Future of RIPE DB DB
Team would like to pause and reflect and decide on how the database should change to reflect current requirements.
Task-Force on Data Protection Issues
Summary report will be presented tomorrow in the plenary
Contact Data Quality/Requirements Discussion
Nothing appropriate for the moment
Resource Certification Project
The point was raised that the CA-TF work was a focus for actions by lawful authority to remove items from the database. Would we want to record all such actions. This is properly the domain of the DP-TF and some progress on similar topics has already been made.
[AP56.1 DP-TF] To consider the action to be taken when legal authority requests the removal of data from the database, and in particular whether records of such actions should be recorded. It was noted that 2008-04 will result in more ROA data for the DB using data derived from the certification effort.
Using ripe-whois and our experimental syncronization trial
General enthusiam for the work done. The improvements in speed are partly due to the original code being some 7 years old. This gives further impetus to the RIPE DB team to be allowed time to think and reflect on the database re-write.
None
None