- db-wg - mailman.ripe.net

Re: [db-wg] Cleanup of route(6) objects in the RIPE NONAUTH database using unregistered space
by denis walker 26 Apr '21

26 Apr '21

Thanks for the input Cynthia. As you are one of the few people who regularly comment on DB issues at the moment, maybe you could take a look at the request for feedback from the DB Task Force recently. Any comments would be appreciated, who knows it may even start a discussion :) cheers denis co-chair DB-WG On Sun, 25 Apr 2021 at 13:03, Cynthia Revström <me(a)cynthia.re> wrote: > > imo an NWI seems unnecessary unless we want it for purposes of referencing back to in the future. > > -Cynthia > > On Wed, Apr 21, 2021, 04:02 denis walker via db-wg <db-wg(a)ripe.net> wrote: >> >> Colleagues >> >> How do you want to proceed with this suggestion? Do we have support >> for deleting these ROUTE(6) objects for deregistered space and where >> the objects were created before registration? Does anyone have any >> objections to this as an ongoing cleanup? >> >> Do we even need an NWI or can we just ask the NCC to go ahead with it? >> >> cheers >> denis >> co-chair DB-WG >> >> On Thu, 11 Mar 2021 at 15:07, Edward Shryane via db-wg <db-wg(a)ripe.net> wrote: >> > >> > Dear colleagues, >> > >> > In response to the recent discussion on "196.52.0.0/14 revoked, cleanup efforts needed", I'd like to propose a regular automated cleanup of route(6) objects in the RIPE-NONAUTH database using unregistered space. >> > >> > Regards >> > Ed Shryane >> > RIPE NCC >> > >> > >> > >> > Problem Definition >> > ------------------ >> > When an RIR deregisters IPv4/IPv6 address space, any route(6) objects in the RIPE-NONAUTH database using that address space are not cleaned up (deleted). >> > >> > >> > Solution Definition >> > ------------------- >> > Once a day, compare route(6) IPv4/IPv6 prefixes in the RIPE-NONAUTH database against the combined delegated stats from all RIRs. >> > >> > Only route(6) prefixes that are "allocated" or "assigned" in any RIRs delegated stats should remain in the RIPE NONAUTH database. If a prefix is "available" or "reserved" then it is considered to be unregistered, and any associated route(6) objects will be eligible for deletion. >> > >> > If a prefix is partially "available" or "reserved" then it is also considered to be unregistered. >> > >> > If a prefix is not listed in any RIRs delegated stats, that prefix is skipped. >> > >> > The origin AS status is not considered, only the IPv4/IPv6 prefix. >> > >> > If a newly unregistered prefix is discovered, first allow a grace period of 1 week. This allows time for mistakes in the delegated stats to be corrected. >> > >> > After 1 week, contact the route(6) maintainer(s) to notify them that the route(6) object will be deleted. >> > >> > After a further 2 weeks, delete the route(6) object. >> > >> > A maintainer can request the RIPE NCC to exclude a route(6) prefix from deletion (for example, the deregistration of the prefix is being disputed). For any excluded prefixes, any associated route(6) objects will not be deleted. >> > >> > >> > Impact Analysis >> > ------------------ >> > There are approximately 738 routes (out of 56,230) in the RIPE-NONAUTH database using a prefix with status "available" or "reserved" in an RIRs delegated stats, which will be eligible for deletion. >> > >> > There are approximately 94 route6's (out of 1,564) in the RIPE-NONAUTH database using a prefix with status "available" or "reserved", so also eligible for deletion. >> > >> > There are approximately 64 routes and 37 route6's with a prefix not listed in any RIR's delegated stats. These will not be affected. >> > >> > When this cleanup is implemented, the backlog of route(6) objects eligible for deletion will be processed at the same time, leading to a large amount of emails to affected maintainers. Once this backlog is processed, the number of route(6) objects affected is expected to be low. >> > >> > >> > >>

1 0

input from community???
by denis walker 22 Apr '21

22 Apr '21

Colleagues Over recent months several important issues have been raised on this mailing list. We have seen comments from maybe 1 or 2 people to some of them. No comments at all to others. We appreciate that covid issues affect many businesses in many ways. So perhaps some of you have far more important issues to deal with than the RIPE Database. It is very difficult for the chairs to see consensus with only a couple of comments. The DB Task Force has also asked for feedback on a number of issues to help them finalise their recommendations. With 3 weeks to the RIPE Meeting and 2 weeks to the DBTF bof, if any of you have some spare moments to review any of the issues raised over the past months it really would help if you can offer some feedback, even better if that promotes some real discussion. cheers denis co-chair DB-WG

1 0

Call for Presentations / DRAFT Agenda RIPE82 - Database Working Group
by William Sylvester 22 Apr '21

22 Apr '21

Dear Working Group Members, Below is the proposed agenda for the Database Working Group for RIPE82. If you would like to present please submit your content as soon as possible to the chairs. If you have any questions, comments, or requested changes please let the chairs know. Best regards, William & Denis DB-WG Chairs A. Introduction - 5 min * Welcome * Scribe * Jabber * Agenda B. Operational Update RIPE Database – XX mins Edward Shryane, RIPE NCC C. Geofeeds – YY mins Massimo Candela, NTT D. YOUR PRESENTATION HERE – ZZ mins Community Member, RIPE Community E. NWI - Open Proposals – 5 mins Z. AOB (open discussion)

1 0

Whois Release 1.100
by Edward Shryane 22 Apr '21

22 Apr '21

Dear Working Group, RIPE Database release 1.100 has been deployed to the Release Candidate environment. We plan to deploy to production on Thursday 22nd April. This release includes the following main changes: * Separate email address and leading/trailing space during Punycode conversion (#782) * Use status index during update validation (#725) * Fixed aut-num attribute managed flag in lookup and search response (#749) * Added client flag to API for proxying requests (#728) * RDAP nameserver not implemented (#711) * Fixed delete object bug (#723) In addition to other small improvements and bug fixes. The release notes are on the website: https://www.ripe.net/manage-ips-and-asns/db/release-notes/ripe-database-rel… More information on the Release Candidate environment can be found on our website: https://www.ripe.net/manage-ips-and-asns/db/release-notes/rc-release-candid… Please let us know if you find any issues with this release in the RC environment. Regards Ed Shryane RIPE NCC

1 1

Cleanup of route(6) objects in the RIPE NONAUTH database using unregistered space
by Edward Shryane 21 Apr '21

21 Apr '21

Dear colleagues, In response to the recent discussion on "196.52.0.0/14 revoked, cleanup efforts needed", I'd like to propose a regular automated cleanup of route(6) objects in the RIPE-NONAUTH database using unregistered space. Regards Ed Shryane RIPE NCC Problem Definition ------------------ When an RIR deregisters IPv4/IPv6 address space, any route(6) objects in the RIPE-NONAUTH database using that address space are not cleaned up (deleted). Solution Definition ------------------- Once a day, compare route(6) IPv4/IPv6 prefixes in the RIPE-NONAUTH database against the combined delegated stats from all RIRs. Only route(6) prefixes that are "allocated" or "assigned" in any RIRs delegated stats should remain in the RIPE NONAUTH database. If a prefix is "available" or "reserved" then it is considered to be unregistered, and any associated route(6) objects will be eligible for deletion. If a prefix is partially "available" or "reserved" then it is also considered to be unregistered. If a prefix is not listed in any RIRs delegated stats, that prefix is skipped. The origin AS status is not considered, only the IPv4/IPv6 prefix. If a newly unregistered prefix is discovered, first allow a grace period of 1 week. This allows time for mistakes in the delegated stats to be corrected. After 1 week, contact the route(6) maintainer(s) to notify them that the route(6) object will be deleted. After a further 2 weeks, delete the route(6) object. A maintainer can request the RIPE NCC to exclude a route(6) prefix from deletion (for example, the deregistration of the prefix is being disputed). For any excluded prefixes, any associated route(6) objects will not be deleted. Impact Analysis ------------------ There are approximately 738 routes (out of 56,230) in the RIPE-NONAUTH database using a prefix with status "available" or "reserved" in an RIRs delegated stats, which will be eligible for deletion. There are approximately 94 route6's (out of 1,564) in the RIPE-NONAUTH database using a prefix with status "available" or "reserved", so also eligible for deletion. There are approximately 64 routes and 37 route6's with a prefix not listed in any RIR's delegated stats. These will not be affected. When this cleanup is implemented, the backlog of route(6) objects eligible for deletion will be processed at the same time, leading to a large amount of emails to affected maintainers. Once this backlog is processed, the number of route(6) objects affected is expected to be low.

2 1

RIPE Database Requirements Task Force BoF, 5 May 2021
by Bijal Sanghani 15 Apr '21

15 Apr '21

Dear all, The RIPE Database Requirements Task Force (DBTF) will organise its third BoF on Wednesday, 5 May 2021 from 16:00-17:30 (UTC+2) via Zoom. During this BoF, the DBTF will present its latest recommendations and discuss open issues. More information and joining details are available at: https://www.ripe.net/participate/ripe/tf/rdb-requirements-tf/bof-5-may-2021 Kind regards, Bijal on behalf of the DBTF

1 0

RIPE Database - Historical Information
by Bijal Sanghani 14 Apr '21

14 Apr '21

Dear colleagues, As part of our work in the RIPE Database Requirements Task Force (DBTF), we are trying to understand if providing historical data is one of the requirements the RIPE Database must fulfil. Currently some attributes are filtered out to limit the exposure of unnecessary personal data. If providing historical data is a requirement the RIPE Database must fulfill, we will recommend the RIPE NCC to examine if additional filtering can be applied to limit further the unnecessary exposure of personal data in attributes that are not meant to contain personal data. We are looking specifically for arguments pro or against this recommendation. We’ll then discuss each argument with the task force and make a decision. Kind regards, Bijal on behalf of the DBTF

3 3

RIPE Database - Legal Address
by Bijal Sanghani 14 Apr '21

14 Apr '21

Dear colleagues, As part of our work in the RIPE Database Requirements Task Force (DBTF), we are trying to evaluate if we should recommend that the RIPE NCC publish the legal address of resource holders in the RIPE Database. It will include everybody that is directly receiving resources from the RIPE NCC. This information is already stored in the RIPE Registry but not available in the RIPE Database. However it’s good to note that since the implementation of NWI-10, a new attribute was added to the ORGANISATION object with the Country Code for the country in which the resource holder is legally based. As a reminder, this is our current recommendation: “The task force recommends that the legal address of resource holders who are legal persons be published in the RIPE Database. This will clarify which organisation holds which Internet number resources and ensure quick action from incident responders such as CSIRTs and LEAs in case of abuse.” The task force is aware that there are legal and technical constraints attached to this recommendation. The main challenge is to find a system that can clearly separate natural and legal persons across our service region, so that the privacy of natural persons in the RIPE Database is respected. This also includes corner cases such as SMEs using their home addresses as their legal addresses. We are looking specifically for arguments pro or against this recommendation. We’ll then discuss each argument with the task force and make a decision. Kind regards, Bijal on behalf of the DBTF

3 2

RIPE Database - PERSON Objects
by Bijal Sanghani 14 Apr '21

14 Apr '21

Dear colleagues, As part of our work in the RIPE Database Requirements Task Force (DBTF), we are trying to understand where there is a requirement to keep allowing PERSON objects to be created. We have received arguments for both pro and against this and we propose the following recommendation: promote ROLE objects instead of PERSON objects but still make it possible for users to create PERSON objects. We want to recommend the RIPE NCC to implement stricter checks and measures to prevent users from unknowingly entering personal data in both object types. We are looking specifically for arguments pro or against this recommendation. We’ll then discuss each argument with the task force and make a decision. Kind regards, Bijal on behalf of the DBTF

1 0

Comments on RIPE Database requirements progress
by denis walker 09 Apr '21

09 Apr '21

Colleagues For the benefit of those who don't often check the mail archives of the RIPE Database Task Force there have been 4 meetings in February and March with 3 sets of minutes published so far on their mail archive which can be found here: https://www.ripe.net/ripe/mail/archives/ripe-db-requirements-tf/ The chairs really appreciate the work done by the TF and acknowledge that it is a long and complex task. I have read through these last sets of minutes and feel some things need to be clarified. It may just be language but the minutes suggest the TF has or will make decisions on a number of items, rather than decisions on their recommendations for these items. As it says in their charter "The task force is a small and focused drafting team of up to six persons and not a representative body....Consensus building will take place in the appropriate RIPE working groups". Up to now there has been very little discussion in any working group and certainly no consensus on any of the issues raised as yet. I see the TF making a number of very important recommendations which can then be discussed publicly in appropriate WGs to see if there is a consensus. Let me try to clarify or question some specific issues from recent minutes. I am doing this here, rather than privately with the TF as I have done in the past, as I feel more public discussion is needed on this document the TF is producing. "The task force also discussed what will happen after their final report is published. They agreed that the implementation of the requirements could be delegated to the relevant working groups but mentioned that it will be up to the RIPE Chair team to decide what to do next with it." This implies that the requirements, as suggested by the TF, 'will be' implemented and that the implementation details 'could be' delegated to WGs. The requirements and recommendations themselves, from the TF, need to be discussed in WGs to see if the community even agrees with them. That needs to happen before any discussion on possible implementation. "Ed asked if the task force was considering to make a recommendation regarding assignments as it seems to drive the creation of a lot of unmaintained objects (especially PERSON objects). The task force replied that they were working on a recommendation dealing with assignments but didn’t reach a final decision yet." Firstly it should not be possible to create any unmaintained objects in the database now. If creating assignments is causing too much personal data to be entered into the database it may be the issue of personal data that needs to be addressed. The issue of assignments (whether or not they are needed) should not be confused with that of personal data. These two issues should be considered completely separately. "They [TF] also decided to only publish a final draft ahead of RIPE 82 and skip the publication of an intermediate draft." This is unfortunate as it again reduces community discussion and the chances for the community to offer any feedback to the TF to be incorporated into the final draft. "The task force discussed Randy and Denis’s recent comments on the db-wg mailing list about NWI-2 [historical data]. Ed mentioned that this was one final call from Denis to see if there are any interest from the community to move NWI-2 forward. As the task force is already working on this topic, Ed proposed to inform the db-wg that they can close NWI-2. The task force agreed." The NWIs are action points on the DB-WG. It is for the co-chairs to decide on these action points based on discussion and consensus by the WG members. The issue of historical data queries has been on and off the agenda of the WG for a number of years. I am sure the members of the DB-WG will have more to say yet on this issue. There have been many individual comments. The key to resolving this issue is to get all interested parties to discuss it, openly, at the same time. "The task force decided to keep the current baseline [registration] information data" I presume you mean 'the TF recommends keeping...'. There has been no discussion in any WG on changing this registration data so no consensus either way as yet. "The task force didn’t get enough information and arguments from the questionnaire survey results to decide whether or not the legal address of resource holders should be published in the RIPE Database. The task force will therefore ask the community via email to get more feedback on this topic before making a decision." Again this is an important issue which cannot be decided behind closed doors, based on private comments to a non representative body. There are some major issues in this list of points. In an open, transparent, bottom up, community driven industry these issues can only be decided by open discussion and consensus within WGs. We all welcome the recommendations put forward by the TF but they are by no means final decisions on these issues. They will be the starting points for open, public discussion leading to community consensus. In the meantime, please feel free to comment on and discuss publicly on this WG mailing list any issues regarding the TF draft requirements document which can be found here https://www.ripe.net/participate/ripe/tf/rdb-requirements-tf/the-ripe-datab… cheers denis co-chair DB-WG

3 2