- db-wg - mailman.ripe.net

Re: [db-wg] NWI-10 Definition of Country
by Arash Naderpour 01 Nov '19

01 Nov '19

Hi, I'm new to DB-WG, but want to express my opinion in this regard, from problem definition: "Historically the country code was used to refer to the location of the network" There are plenty of organization out there that are already set their network and firewalls rules to use country code value in delegation file as reference to the location of the network. Changing the rule to to something new, will cause problem for clients and providers, so I don't think it is a good idea, country code in delegation file can be synced with the country code for resource object in RIPE DB. A new attribute in organization object refers to where the resource holder is legally based is totally fine, but having the same value in delegation file can break networks and services. Regards, Arash Naderpour Parsun Network Solutions

1 0

country attribute in aut-num
by Cynthia Revström 23 Oct '19

23 Oct '19

Hello, I ran into an issue today that was the inability to have a country attribute in the aut-num object, despite having a country code in the delegated file. I would like to see it added to WHOIS. - Cynthia

4 5

Apologies for the accidental email
by Fallon Albrecht 23 Oct '19

23 Oct '19

Dear working group, I apologise for the accidental email that was sent out, it was meant to be an internal feature request. Sorry for spamming you. Fallon

1 0

Re: [db-wg] [swe-database] Implementation -K Flag Request
by Fallon Albrecht 23 Oct '19

23 Oct '19

Hi Ed, I have some feature requests: 1. To have a perma link option for full text search. 2. If a SSO account is associated with the mnt-by of the inetnum and they query the allocation that they also can see all the more specific objects. 3. If the SSO account is a Ripe NCC email address and you login that the functionality “do not retrieve related objects” is disabled. That is’t for now. Thank you! Fallon > On 23 Oct 2019, at 11:20, Valentino Dijkstra <vdijkstra(a)ripe.net> wrote: > > Hi Ed, > > Thank you for the reply. > > That is ok for us, in case we are receiving any other future request I will let you know. > > Cheers, > > Valentino > > >> On 22 Oct 2019, at 17:21, Edward Shryane <eshryane(a)ripe.net> wrote: >> >> Thanks Valentino, >> >> I added a story to the DB team's backlog for this feature request: "db-web-ui: Support the --primary-keys/-K flag on the Query Page" (https://jira.ripe.net/browse/DB-2659) >> >> We are busy with other work, but we'll review when we're next working on new website functionality. >> >> The DB team doesn't need a "feature request" tag in Zendesk (unless CS needs it), as we're tracking everything in one place (Jira) already. >> >> Just send us the request and I'll add it to our backlog. You can then close the Zendesk ticket. >> >> We add a ticket # to the story (or bug) in Jira, so we remember to contact the user again once it's done. >> >> Regards >> Ed >> >> >> >> >>> On 22 Oct 2019, at 16:40, Valentino Dijkstra <vdijkstra(a)ripe.net> wrote: >>> >>> Dear Team, >>> >>> >>> In the last couple of weeks we did not receive any particular future request. >>> >>> The only request came from ticket 219462 requesting to have the -K flag implemented in order to >>> retrieve all the route objects related to a certain range. >>> >>> Also I will make sure that we will have a “future request” tag in the DB queue so it will be easy to retrieve the tickets in the future. >>> >>> Let me know if this can be done in a short period of time. For further questions feel free to contact me. >>> >>> Cheers, >>> >>> Valentino >>> CS_______________________________________________ >>> swe-database mailing list >>> swe-database(a)ripe.net >>> https://intlists.ripe.net/mailman/listinfo/swe-database >> >

1 0

Set Default Maintainer on all Top-level Resources
by Edward Shryane 22 Oct '19

22 Oct '19

Dear Colleagues, as presented during the DB-WG session at RIPE 79, we wish to extend the "Default Maintainer" functionality for LIR organisations. Firstly, to set the Default Maintainer (with an mnt-by: attribute) on *all* top-level resources (where the org: reference is the LIR itself): - IPv4 and IPv6 allocations (the current behaviour) - ASNs - IPv4 and IPv6 assignments - IPv4 LEGACY resources Secondly, to automatically (re-)set the Default Maintainer on a nightly basis, on *all* top-level resources: - Fix inconsistencies due to manual updates - Add the default maintainer (with an mnt-by: attribute), and remove other user maintainer(s) Please let me know of any feedback or questions you may have. Regards Ed Shryane RIPE NCC

3 4

Cleanup Locked Person Objects - Implementation Plan
by Edward Shryane 21 Oct '19

21 Oct '19

Dear Colleagues, As presented during the DB-WG session at RIPE 79, we will shortly begin to cleanup locked person objects in the RIPE database. We will select person objects maintained by RIPE-NCC-LOCKED-MNT, which are referenced by inetnum allocations or assignments, and re-assign them to the resource maintainer. The goals of this cleanup are: - Align with RIPE-730 Policy - “Registration data (range, contact information, status etc.) must be correct at all times (i.e. they have to be maintained).” - Align with GDPR - assign responsibility for contact details to the correct maintainer - Cleanup 90% of locked person objects in the RIPE database (the remainder will be cleaned up separately) We will implement this cleanup as follows: - Announce to ncc-announce, ncc-services-wg and db-wg beforehand - Perform the cleanup one LIR at a time - Email the affected LIR and assignment maintainers beforehand to explain the change, including a list of planned updates - Set the locked persons mnt-by to the assignment maintainer, where we are sure of a link between them (e.g., if the objects were originally created together, and if the assignment maintainer has not changed since (this applies to two thirds of all locked persons)). - Otherwise, set the locked persons mnt-by to the LIR maintainer (for one third of all locked persons). - Email the LIR and assignment maintainers afterwards, and ask them to validate the contact details on their resources. Please let me know of any feedback or questions you may have. Regards Ed Shryane RIPE NCC

1 0

Agenda RIPE79 - Database Working Group
by William Sylvester 10 Oct '19

10 Oct '19

DB-WG Members, Here is our agenda for the RIPE meeting next week. Best regards, DB-WG Chairs A. Introduction - 5 min * Welcome * Scribe * Jabber * Agenda B. Operational Update RIPE Database – 20 mins Edward Shryane, RIPE NCC C. DB Requirements Tast Force Update – 5 mins D. NWI-8 LIR’s SSO Authentication Groups Demonstration – 5 mins Mahesh Aggrwal, RIPE NCC E. NWI-3 RIPE-NONAUTH perspective, still needed? – 15 mins Job Snijders, NTT F. NWI-9 In-Band Notification Mechanism – 15 mins TBD G. NWI - Open Proposals – 15 mins Z. AOB (open discussion)

1 0

GDPR and the RIPE Database
by Edward Shryane 08 Oct '19

08 Oct '19

Dear Working Group, as mentioned in last week's DB-WG meeting, we will shortly be implementing the following changes: - Do not include personal data in historical queries (notify, e-mail, address attributes). - Do not include person/role references in historical queries (admin-c, tech-c, ping-hdl, zone-c). A legal review found we should not return historical contact details, as they may contain personal data, which is not in line with the purpose of the RIPE database or data protection legislation. For background, Maria Stafyla from RIPE NCC Legal presented on this topic at RIPE 76: https://ripe76.ripe.net/presentations/101-GDPR-Database-WG-RIPE-76.pdf Regards Ed Shryane RIPE NCC

4 8

NWI-10 Definition of Country
by ripedenis＠yahoo.co.uk 08 Oct '19

08 Oct '19

Colleagues The DB-WG chairs have agreed to create "NWI-10 Definition of Country". This is an issue that has been debated many times over many years and needs a solution. The Solution Definition below is based on a presentation made at RIPE 78 by the RIPE NCC. There has been very little discussion on this since RIPE 78 so perhaps we can have a final round of pros and cons over this next week and then see if we have a consensus. cheersdenis co-chair DB-WG NWI-10 Definition of Country Problem DefinitionThere is no clarity for the meaning of the country code attribute in the RIPE Database and the Extended Delegated statistics. This creates confusion and inconsistencies. Historically the country code was used to refer to the location of the network. Until recently this location was, in most cases, identical to the legal presence of the resource holder. However, in recent years there has been a growing number of resource holders that have, for various reasons, their legal presence in one country, but the network located in another country. There is also a growing number of out-of-region members resulting in an increase in requests to update the country code in the Extended Delegated Statistics for different purposes (e.g. commercial). While the country code attribute in the RIPE Database can be updated directly by the resource holder, the Extended Delegated Statistics are maintained by the RIPE NCC and they were created as part of a joint effort from the RIRs with a specific purpose. Solution Definition1. The country code for resource objects in the RIPE Database should remain as it is currently, ie the resource holder remains responsible for maintaining this attribute and deciding what the country code should be, according to whatever criteria best suits their needs. 2. A new attribute should be added to the ORGANISATION object, which contains a country code that refers to where the resource holder is legally based. The RIPE NCC would be responsible for this field and would only make updates to this field after being provided with documentation that proves the resources holder is legally-based in another country. This would essentially be the same process for updating an organisation's legal name currently. 3. The new country code value in the ORGANISATION object would then be reflected in the Extended Delegated Statistics – so that this file will show where the holder of a resource is legally based and will not make any claims about where the resources are being used. This will ensure the Extended Delegated Statistics file is consistent with those published by the other RIRs. This may mean there is a greater divergence between the country code contained in resource objects in the RIPE Database and those listed in the statistics file. As the country code in the resource objects only has meaning to the resource holder, which should be made clear, this should not be a problem.

9 13

Synchronising Users from the LIR Portal to the Default Maintainer in the RIPE Database
by Edward Shryane 23 Sep '19

23 Sep '19

Dear colleagues, Following a request by the Database Working Group earlier this year, we have implemented a new feature to synchronise users from the LIR Portal to the Default Maintainer in the RIPE Database. More information can be found in the Labs article: https://labs.ripe.net/Members/ed_shryane/synchronising-users-from-the-lir-p… The discussion by the DB-WG was defined as the Numbered Work Item NWI-8 : https://www.ripe.net/manage-ips-and-asns/db/numbered-work-items We plan to deploy this new feature to production next Monday, 23rd September. Regards, Ed Shryane RIPE NCC

1 1