June 2020 - ripe-db-requirements-tf

Database Usage Survey Results
by Boris Duval 16 Nov '21

16 Nov '21

Dear colleagues, We just closed the Database usage survey and collected 206 responses. Please find the survey results attached to this email. Thank you all for your input! Along with other sources of data, this feedback is really valuable to the current DBTF work. We plan to collate the open questions results and send them to the mailing list as soon as possible. Best, Boris Duval RIPE NCC

2 1

Notes from 15 June 2020 Meeting
by Boris Duval 23 Jun '20

23 Jun '20

Dear all, Here's the meeting notes from our last call. Best, Boris *RIPE Requirements Database Task Force Meeting Notes* 15 June 2020 Attendees: Nick Hilliard, James Kennedy, Peter Koch, Sara Marcolla, Bijal Sanghani, Edward Shryane, Maria Stafyla, Boris Duval 1. Run through actions from last meeting James followed up with Maxmind and other stakeholders about their usage of the geolocation attributes. The feedback he received confirmed that a lot of stakeholders are using this geolocation data for operational matters and that we could therefore consider geolocation as a secondary function of the RIPE Database. He also pointed out that best practices on how to manage this data would be useful. Maria started to look into different RIPE Policies (IPv4, IPv6 and AS Number) and will prepare an overview for the DBTF that also includes more information about historical data. Boris and Sara shared that CERTs were using the data stored in the RIPE Database and didn’t plan to move it out. Sara proposed to survey CERTs to get a better understanding on how they are using this data. Boris analysed past RIPE NCC surveys and shared relevant highlights with the DBTF. He will send an email with his findings to the Task Force. James informed the group that results from the RIPE NCC survey and the DBTF survey directly overlap on areas for improvement, i.e. data accuracy (enforce data checks and validation), and ease of use (requests that the user interface could be improved were common, and there were also many comments suggesting improvements to search functionality). Nick followed up with the Routing Working Group and shared that although he received some feedback, it was not enough to decide what to do with RPSL. The DBTF agreed to look at the Internet Routing Registry instead of RPSL to widen the scope and help drafting more high-level requirements. 2. Reminder of the DBTF’s Charter 3. Goals of the document The DBTF Chairs (James, Bijal and Shane) agreed on goals to help and guide their work on the requirements document: - Outline current functions of the RIPE Database - Address common, overarching issues experienced by today’s users - Define how changes should be made to the RIPE Database in the future 4. Next steps The DBTF will focus on refining the functions/requirements in the document with justifications and will try to identify overarching issues and suggestions where possible. The DBTF decided to pair up to facilitate this work and will divide the workload as follow: - Provide registration information of Internet number resources - James, Peter - Facilitating communication about usage of the resources. - Sara, Bijal - Publishing routing policies by network operators (RIPE IRR) + The RPKI Database - Nick, Shane 5. Confirm actions and next call Maria will send an overview of the information she found in RIPE policies that will help the DBTF advance its work. Boris will send relevant data from past RIPE NCC Survey. The DBTF will work on improving the draft document by working in pairs on a specific topic. The next DBTF call will take place on Wednesday, 1 July 2020.

1 0

DBTF BoF Minutes
by Boris Duval 08 Jun '20

08 Jun '20

Dear all, The minutes and recording of the RIPE Database Requirements Task Force (DBTF) BoF are now available at: https://www.ripe.net/participate/ripe/bof/dbtf-bof Thank you to all attendees for their active participation and inputs. Best, Boris Duval Communications Officer RIPE NCC

1 0

Notes from 26 May 2020 Meeting
by Boris Duval 05 Jun '20

05 Jun '20

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.

1 0