[ripe-db-requirements-tf] Notes from 18 December 2020 Meeting
- Previous message (by thread): [ripe-db-requirements-tf] Notes from 9 December 2020 Meeting
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Boris Duval
bduval at ripe.net
Wed Dec 23 10:39:10 CET 2020
Dear all, Here's the meeting notes from our last call. *RIPE Requirements Database Task Force Meeting Notes* 18 December 2020 Meeting Attendees: Boris Duval, Shane Kerr, Peter Koch, Sara Marcolla, Edward Shryane, Maria Stafyla Agenda: 1. Questionnaire Review The task force continued to review the questionnaire that will be sent out to the community in January to collect feedback on the current draft. One of the main challenges is how to best frame questions, so that the task force gets qualitative feedback from the community. Nick and Shane will look into coming up with questions for the routing requirements section. The task force will fine-tune the questionnaire and finalise it during their next call in January 2021. 2. Timeline Review The task force reviewed and agreed on the following timeline: 18 January 2021: DBTF to finalise questionnaire (sign off) 25 January 2021: Publication and promotion of the questionnaire 8 February 2021: End of questionnaire + discussing result and asking clarifying questions to the community 8 March 2021: Publication of an intermediate draft including feedback from the community 17 March 2021: 3rd BoF (if needed) to discuss the new draft and build consensus on potential open issues 12 April 2021: Publication of the final draft and last call for comment 3 May 2021: Final draft accepted and listing open issues (if any) 3. DB-WG discussion on historical data The task force mentioned the recent discussion about the use of historical data in the DB-WG mailing list: https://www.ripe.net/ripe/mail/archives/db-wg/2020-December/006737.html As historical data is addressed in the questionnaire, the task force will ask the community for more feedback on this topic. 4. Editing the current draft The task force will look at the current draft and see if it needs to be updated based on the feedback already received from the community (especially the routing requirements section). 5. Diagram review Boris presented a diagram representing the relationships between the RIPE Registry, the RIPE Database, the RIPE IRR and the RPKI Database (see attachment). The task force gave his feedback and mentioned that it will be good to include this overview in the final draft. Peter added than having a second more detailed diagram might be useful for internal use to shed some light on some of the data relationships between the different parts of the RIPE Database. 6. Next Meeting The next meeting will take place in January 2021. -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/ripe-db-requirements-tf/attachments/20201223/ce6a7bec/attachment-0001.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: clip_image001.png Type: image/png Size: 57124 bytes Desc: not available URL: </ripe/mail/archives/ripe-db-requirements-tf/attachments/20201223/ce6a7bec/attachment-0001.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: Message signed with OpenPGP URL: </ripe/mail/archives/ripe-db-requirements-tf/attachments/20201223/ce6a7bec/attachment-0001.sig>
- Previous message (by thread): [ripe-db-requirements-tf] Notes from 9 December 2020 Meeting
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]