Dear all, Here's the meeting notes from our last call. Best, Boris *RIPE Requirements Database Task Force Meeting Notes* 26 May 2020 Attendees: Nick Hilliard, James Kennedy, Peter Koch, Bijal Sanghani, Edward Shryane, Maria Stafyla, Boris Duval DBTF BoF 1. Review RIPE meeting presentations BoF -- General Feedback The DBTF was pleased with the feedback received during the BoF and will take it into consideration for its work. The DBTF also mentioned that they might organise a new session at a later stage to help build consensus around the final document. -- IPAM The DBTF received new information regarding IPAM usage during the BoF as several options were considered to tackle this issue. The DBTF will need to explore each of these options before coming up with guidelines regarding this topic. Maria proposed to prepare an overview of the assignment/allocation registration requirements to be made in the RIPE Database to help the DBTF take a decision. -- Geolocation The DBTF discussed what to do with geolocation and looked specifically at the “geoloc:” attribute that was created in 2011. James mentioned that he could contact Maxmind as they might use this attribute operationally. -- IRT objects The DBTF would like to know more about how CERTs are using IRT objects and if they plan to use a different source of data in the future. Boris proposed to contact Mirjam Kühne from the RIPE NCC as she is in contact with CERTs. Bijal added that she will also ask Sara as she knows some of the CERTs. -- Minutes The DBTF agreed with the current minutes draft and proposed to add more information regarding the number of BoF and polls participants. Community Plenary Bijal shared that her presentation went well but regretted to have not received a lot of feedback from the community. She mentioned that it might have been due to the fact that the session was scheduled towards the end of the RIPE meeting and that the meeting was taking place online. Routing WG Nick gave his presentation about RPSL at the Routing WG during RIPE 80 and will follow up on the Routing WG mailing list to ask the community their thoughts on RPSL. 2. Survey analysis and user-requirements matrix James analysed the results from the DBTF survey and elaborated a user-requirement matrix based on the results that would help guide the DBTF work and better define challenges. Bijal thanked James for his work and agreed that it was a useful exercise to map out users and their needs. Peter mentioned that we should also not forget to keep the RIR function in mind when writing requirements. Boris added that some of the information needed to fill-in the matrix could be find in the RIPE NCC Survey 2019. James proposed that everybody in the Task Force look at the survey as it contains relevant information regarding users’ needs and views on the RIPE Database. Bijal mentioned that it would be interesting to look at older RIPE NCC Surveys to see how the membership evolved. Boris agreed to look into it. 3. Next steps The DBTF Chairs agreed to have a separate meeting to write up a roadmap that will allow the Task Force to structure the remaining work on the requirements document. The DBFT agreed to make James co-Chair to help speed things up as he is willing to invest more time and energy into the Task Force. 4. Confirm actions and next meeting. James will contact Maxmind and ask them about their usage of the RIPE Database’s geolocation data. Maria will look into RIPE policies and prepare an overview of the assignment/allocation registration requirements to be made in the RIPE Database. Boris will update the minutes according to the DBTF’s feedback and publish them on ripe.net with the recording. Boris will contact Mirjam and Bijal will contact Sara about CERTs. Nick will follow-up with the Routing WG on RPSL. Boris will explore the RIPE NCC Survey 2019 data and highlight what’s useful to the DBTF as well as looking into older surveys. The DBTF will take a look at the RIPE NCC Survey 2019. The DBTF Chairs (Bijal, Shane and James) will come up with a roadmap to advance the Task Force’s work. The next meeting will take place at the beginning of June.