- ripe-db-requirements-tf - mailman.ripe.net

Notes from 22 October 2020 Meeting
by Boris Duval 29 Oct '20

29 Oct '20

Dear all, Here's the meeting notes from our last call. *RIPE Requirements Database Task Force Meeting Notes* 22 October 2020 Meeting Attendees: Boris Duval, James Kennedy, Shane Kerr, Peter Koch, Sara Marcolla, Bijal Sanghani, Maria Stafyla, Edward Shryane Agenda: 1. Draft Document The task force reviewed the current draft document before publication. -- Publishing the Legal Address of Legal Persons The task force discussed this recommendation and decided to ask the community for feedback during the BoF. Also, the task force pointed out that the purpose for this recommendation needed to be clearer and more specific. -- Reverse Domain Name System (rDNS) The task force agreed to keep this requirement in the document and develop the text at a later stage. -- Personal Data and PERSON Objects Edward Shryane gave more information about the use of personal data in the RIPE Database and mentioned that there was still a huge amount of PERSON objects being created. The task force agreed that PERSON objects were not a requirement of the RIPE Database but mentioned that they needed more time and feedback from the community on this subject and more generally on the use of personal data in the database. 2. DBTF BoF The task force agreed to only talk about the following recommendations during the BoF as there will be limited time: *Resource registration requirements *Contact information *Legal address 3. Next Call The next call will take place in November 2020.

1 0

RIPE Database Requirements Task Force – Second Draft Published
by Bijal Sanghani 23 Oct '20

23 Oct '20

Dear colleagues, Since RIPE 79, the RIPE Database Requirements Task Force is working on a document to provide new requirements specification for the RIPE Database. We have now published our second draft and invite you to share your input on this mailing list and during our BoF that will take place Monday, 26 October from 16:00-17:00 (UTC+1). We apologies for the slight delay on the publication of this second draft. - https://www.ripe.net/participate/ripe/tf/rdb-requirements-tf/the-ripe-datab… We will try to build consensus on the document and discuss open issues with the community during the BoF. Please note that you don’t need to register for the RIPE meeting to participate to the BoF. A link to join the BoF on Monday is available at: https://ripe81.ripe.net/programme/meeting-plan/bof/#mon11 <https://ripe81.ripe.net/programme/meeting-plan/bof/#mon11> Best Regards, Bijal Sanghani

1 0

Notes from 15 October 2020 Meeting
by Boris Duval 22 Oct '20

22 Oct '20

Dear all, Here's the meeting notes from our last call. *RIPE Requirements Database Task Force Meeting Notes* 15 October 2020 Meeting Attendees: Boris Duval, Nick Hilliard, James Kennedy, Shane Kerr, Peter Koch, Sara Marcolla, Bijal Sanghani, Maria Stafyla Agenda: 1. Draft Document The task force reviewed the current draft document. -- Structure The task force agreed on the following plan: · What is the RIPE Database? · The difference between the RIPE Database and the RIPE Registry · Why are we reviewing the RIPE Database functionality now? · Requirements · Recommendations · Terminology · Relevant Policies and Documents -- What is the RIPE Database? There was some references and elements missing in the current draft. For example, Peter suggested to include that the RIPE Database was originally used by many Domain Name Registries as their ccTLD authoritative registry database. This illustrates that some data was migrated out of the database in the past. -- The difference between the RIPE Database and the RIPE Registry The task force discussed the type of data contained in the RIPE Database and how its usage is regulated. -- Requirements The task force discussed which recommendations and requirements should be included in the document. There was a debate around the use of personal data in the RIPE Database and whether or not the legal address of legal persons should be disclosed. Other topics discussed included historical data, routing requirements and the use of PERSON objects. -- Text to be developed The current draft is not complete as some parts will require more time to be written. This will be indicated in the draft. -- Timeline The task force agreed to do its best to publish the draft before RIPE 81. 2. DBTF BoF The task force agreed to schedule another call to plan its upcoming BoF. 3. Next Call The next call will take place on Thursday, 22 October 2020.

1 0

DBTF Working Draft
by Boris Duval 19 Oct '20

19 Oct '20

Hi all, Please find attached the current DBTF working draft. The task force will published its second draft later this week. Cheers, Boris

1 0

Notes from 28 September 2020 Meeting
by Boris Duval 05 Oct '20

05 Oct '20

Dear all, Here's the meeting notes from our last call. Best, Boris *RIPE Requirements Database Task Force Meeting Notes* 28 September 2020 Attendees: Boris Duval, Nick Hilliard, James Kennedy, Sara Marcolla, Bijal Sanghani, Maria Stafyla, Edward Shryane Agenda: 1. Draft Document Sara and Bijal's draft still need to be reviewed by the DBTF. Nick and Shane will meet in the coming week to discuss their draft and make progress. James and Peter had several meetings since the last DBTF meeting and made progress on their draft. Everybody will share their draft and comments with the task force before 9 October. Maria clarified that the RIPE Database provides access to the public parts of the RIPE Registry. She added that the other parts of the RIPE Registry were out of scope for the task force. Maria, Ed and Boris offered to help out with the document’s structure and to fill existing knowledge gaps in the document. The DBTF is aiming to publish its new draft one week before the DBTF BoF to allow enough time for review. 2. DBTF BoF The DBTF will take place on Monday, 26 October from 16:00-17:00 (UTC+1). The BoF will be announced via the relevant mailing lists and will take place via Meetecho. It is already advertised on the RIPE 81 website: https://ripe81.ripe.net/programme/meeting-plan/bof/ The purpose of this BoF is to discuss the task force’s draft with the community and start building consensus around the document. 3. Summary from the meeting with the RIPE Chair (Mirjam Kühne) The RIPE Chairs (James, Bijal and Shane) met with the RIPE Chair (Mirjam) on 14 September 2020. Timeline update After discussing with the RIPE Chair, the task force decided to revise its original timeline and to set RIPE 82 as the new deadline to hand over the final document. This is now reflected on the DBTF charter’s page: https://www.ripe.net/participate/ripe/tf/rdb-requirements-tf External Communication As the public mailing list is currently closed, the RIPE Chair asked the task force if it was possible to let external messages from the community through the list when relevant. The task force agreed. 4. Next Call The next call will take place in two weeks.

1 0

Notes from 7 September 2020 Meeting
by Boris Duval 14 Sep '20

14 Sep '20

Dear all, Here's the meeting notes from our last call. Best, Boris *RIPE Requirements Database Task Force Meeting Notes* 7 September 2020 Attendees: Boris Duval, Nick Hilliard, James Kennedy, Shane Kerr, Peter Koch, Sara Marcolla, Bijal Sanghani, Edward Shryane Agenda: 1. Draft Document Sara and Bijal worked on the ‘facilitating communication about usage of the resources’ requirement with some feedback and suggestions from the RIPE NCC. The DBTF will review their text and discuss it at the next meeting. Peter and James will meet this week to work on their draft and send it to the task force before 18 September. Nick and Shane met a few weeks ago and started their draft. They will also send it to the task force before 18 September. Boris reminded the task force that the RIPE NCC can support them in reviewing the drafts and providing additional information if needed. 2. Q&A Session The task force discussed planning a Q&A session ahead of the RIPE meeting to answer community questions. 3. Next Call The next call will take place at the end of September.

1 0

Notes from 27 July 2020 Meeting
by Boris Duval 30 Jul '20

30 Jul '20

Dear all, Here's the meeting notes from our last call. Best, Boris *RIPE Requirements Database Task Force Meeting Notes* 27 July 2020 Attendees: Boris Duval, Petrit Hasani, Nick Hilliard, Peter Koch, Bijal Sanghani, Edward Shryane, Maria Stafyla Agenda: 1. Run through actions from last meeting Ed sent information about the RIPE Database's language attribute. Maria sent an overview of relevant policies and procedures regarding the RIPE Database requirements. 2. Presentation about ARCs Petrit Hasani from the RIPE NCC gave a presentation to the task force about ARCs (Assisted Registry Checks) and answered their questions. Here are some of the takeaways from the discussion: ARCs participants are picked at random from a list of RIPE NCC members and these checks are mandatory. However, you can also volunteer to participate to an ARC. All ARC procedures were created by the RIPE NCC. ARCs can last between 5 min to 1 hour depending on members’ needs. ARCs are non-exhaustive checks of a member’s data, it helps members learn about policies and procedures. ARCs are not intended to make the RIPE Database 100% correct. 3. Next steps The task force will continue to work on the requirements document and plan a longer review session after the summer holidays. The task force will review Maria’s document on relevant policies and procedures. Petrit will send more information and statistics about ARCs. 4. Confirm actions and next call The next call will take place in September.

1 0

Notes from 14 July 2020 Meeting
by Boris Duval 21 Jul '20

21 Jul '20

Dear all, Here's the meeting notes from our last call. Best, Boris *RIPE Requirements Database Task Force Meeting Notes* 14 July 2020 Attendees: Boris Duval, Peter Koch, Sara Marcolla, Bijal Sanghani, Edward Shryane Agenda: 1. Run through actions from last meeting Boris sent an overview of relevant data from past RIPE NCC surveys. Maria is working on compiling a list of relevant policies and procedures. The DBTF worked on editing and refining the RIPE Database's purposes. 2. Review/Discuss document Bijal and Sara shared their work on the “Facilitating communication about the usage of the resources” purpose. The DBTF gave feedback on the content and clarified the language when needed. During the review, the DBTF mentioned that they would need to know more about the ARC (Assisted Registry Check) procedure. Ed proposed to invite one the RIPE NCC staff in charge of running ARCs to the next call, so that they can explain their work to the DBTF. The DBTF agreed. 3. Next steps The DBTF will continue their work on editing the RIPE Database’s purposes. Sara and Bijal will integrate the feedback they received during the call in their current draft. Ed will ask a RIPE NCC colleague in charge of running ARCs to join the next call. Ed will send information about the RIPE Database's language attribute. Maria will send an overview of relevant policies and procedures. 4. Confirm actions and next call The next call will take place during the last week of July.

1 0

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