Hi Denis, Thanks for the invite, Shane will be at the wg tomorrow and will give a quick update. Kind regards, Bijal

On 9 Oct 2019, at 20:59, denis walker <dw100uk@yahoo.co.uk> wrote:

Hi Guys

Would one of you be willing to act as a spokesperson and give a short introduction in the DB-WG session on Thursday? Just outlining who you all are and what your plans for the coming months are.

cheers denis

co-chair DB-WG

On Tuesday, 8 October 2019, 14:51:54 CEST, Bijal Sanghani <bijal@euro-ix.net> wrote:

Hi Hans Petter,

I am happy to be here and it’s nice to see a good competent list of volunteers, I look forward to working with you all :)

Please use this (bijal@euro-ix.net <mailto:bijal@euro-ix.net>) email address for me and my bio is below.

Regarding the first meeting at the coming RIPE meeting, I am there for a really short time and would appreciate it if we could meet during one of the below slots;

1. After 5pm on Tuesday 2. Wednesday breakfast 8am 3. Wednesday lunch 4. Wednesday after NCC Services wg 5. Thursday Breakfast 8am 6. Thursday during the first session (AA and IPv6)

I created a doodle to collect replies - https://doodle.com/poll/mwqnqm5e7he73mpv <https://doodle.com/poll/mwqnqm5e7he73mpv>

In terms of agenda, since the meeting is next week, here’s a first draft proposal;

1. Welcome 2. Select chairs 3. Agree systems and tools i.e. google docs / dropbox / Trello etc 4. Agree charter - any changes? 5. Agree high level requirements and next steps 6. Take aways and actions/timelines 7. Next meeting

Please let me know if I have missed anything, I look forward to seeing you next week and hope one of the time slots above works for us all.

Kind regards, Bijal

Bijal’s experience includes DNS management for DEMON Internet, Provisioning Engineer at Level 3 and Senior Operations Engineer at FLAG Telecom and Reliance Globalcom, where she was involved from the beginning to build the FLAG IP network.

In her role at Euro-IX she brings the members together to share ideas and experiences on technical, commercial and regulatory matters, and works on other IXP related projects such as the IXPDB and support programs to help IXPs in need.

Bijal has been involved with the Peering and Interconnect Community since 2003, she’s been a RIPE NCC Services Working Group Co-chair since 2005 and was elected on to the PeeringDB Board in 2017 where she currently serves as a Director.

...

On 8 Oct 2019, at 09:53, Hans Petter Holen <hph@oslo.net <mailto:hph@oslo.net>> wrote:

Thank you all for volunteering to the database task force. I have noted the following volunteers, which I believe to be a good composition:

* Peter Koch * Shane Kerr * Nick Hilliard * Bijal Sangani * Sara Marcolla * James Kennedy

I will ask the RIPE NCC to set up a web page and a publicly archived mailing-list for the Task Force.

Please confirm that you are still willing to participate and which email address you would like to subscribe to the list. Also, send us a short bio to be published on the taskforce page in order to provide transparency to the larger community.

Since the RIPE community and the database working group will potentially have to implement the findings from the working group, database working group chairs and eventually the RIPE Chair may have to evaluate consensus on the proposal, so I believe it is better for us not to be directly involved. We will of course be following the work and give advice when needed.

It would be great if you could find time to meet and select one or two chairs for the task force during the RIPE meeting. I have also set aside time on the agenda for the RIPE Community Plenary on Thursday https://ripe79.ripe.net/programme/meeting-plan/ripe-community/ <https://ripe79.ripe.net/programme/meeting-plan/ripe-community/> for the chair to present the charter, members and timeline, as well as opening for community input.

The RIPE NCC will provide reasonable administrative support if needed, and legal support, since this task force may touch upon legal obligation of the RIPE NCC.

There has been no comments to the draft charter, which I have included here for your reference.

RIPE Database Requirements Task Force

Daniel Karrenberg

*Version 1.1*

### Rationale The RIPE Database is now almost 30 years old [[ripe-13]] (https://www.ripe.net/publications/docs/ripe-013 <https://www.ripe.net/publications/docs/ripe-013> "RIPE Databases"). During all this time, the community has developed the functionality of the Database incrementally. Today some new frictions have emerged such as changing privacy requirements and the use of the RIPE DB by parties outside the traditional community, specifically law enforcement. Because of these frictions and changing needs, the community consensus about the functionality of the RIPE DB has become less obvious. Therefore it is now time to take stock and to establish a clear consensus about what functionality the RIPE DB should provide in the future.

### Charter The RIPE Database Requirements task force shall develop a RIPE document listing all the [requirements] (https://en.wikipedia.org/wiki/Requirements_engineering <https://en.wikipedia.org/wiki/Requirements_engineering> "Wikipedia") for the RIPE DB and their rationales. The task force is a small and focused drafting team of two to five persons and not a representative body. The task force will consult the RIPE community and other interested parties. Consensus building will take place in the appropriate RIPE working groups and possibly specific BoFs. The task force will regularly publish draft versions of the document.

### Document Scope The purpose of the document is to establish community consensus at the general level. The document will be the new requirements specification for the RIPE DB. It shall provide clear guidance for the evolution of RIPE DB functionality, including the removal of current functionality that is no longer required.

The document will prioritise requirements as much as possible. The document shall list the purpose of each RIPE DB function and consider the relevant privacy aspects, making the document useful in the context of privacy regulations such as the GDPR. The document shall allow easy updates as community needs change.

Software development, deployment and other implementation details are out of scope. Despite being scoped as a requirements document, the document shall not prescribe a specific engineering methodology for subsequent steps in the process.

### Methodology The RIPE Chair shall appoint the task force after a call for volunteers. Volunteers are expected to contribute significant amounts of text and to collect community feedback. The task force will regularly publish revised drafts based on this feedback. The task force may conduct BoF sessions to discuss drafts with the community.

### Time Line The task force will start its work at [RIPE 79] (https://ripe79.ripe.net/ <https://ripe79.ripe.net/> "RIPE 79, 14-18 October 2019") and produce the *first* draft by December 2019. The task force will deliver a document for last-call at RIPE 81 in October 2020. If the community does not achieve consensus by RIPE 81, the task force will give a report listing the open issues and propose a plan to resolve them.

-- Sincerely, Hans Petter Holen - hph@oslo.net <mailto:hph@oslo.net> - +47 45066054