- db-wg - mailman.ripe.net

RIPE Database Quarterly Planning Q2 2023
by Edward Shryane 21 Mar '23

21 Mar '23

Dear colleagues, We have published our quarterly plans for Q2 2023 for the RIPE Database: https://www.ripe.net/manage-ips-and-asns/db/quarterly-planning In this quarter, we will work on the NWI-12 NRTMv4 implementation, publishing the source code to our web application and opening the Full Text Search API to end users among other items. We hope that by providing these plans, we can better inform the community of the ongoing developments on the RIPE Database and get feedback on our work. The goal of our quarterly planning is to communicate the work we’re doing for the coming months, get your input and start a discussion on other developments we should work on. If you have comments or questions around this, we hope you'll let us know on the list or you can always contact the DB team directly at ripe-dbm(a)ripe.net . Regards Ed Shryane RIPE NCC

1 0

Discussion and Decision making in the DB-WG
by denis walker 08 Mar '23

08 Mar '23

Colleagues I would like to clarify a couple of points here in case anyone has doubts. I often get heavily involved in some discussions on the mailing list. I sometimes have strong views and probably come across as quite pushy. But I always present arguments to support my viewpoint. I am not one of those who make a bold headline and then disappear behind a rock, expecting you to just accept my comment. Of course I am not always right. I am happy to hear from anyone who (partially) disagrees with me or others as long as you offer some arguments to support your viewpoint. I also like to hear from people who (partially) agree with me or others. We don't get a lot of people joining discussions on this mailing list. That's one of the reasons I reply to many comments to try to keep the discussion alive. Sometimes someone makes a comment, no one responds and the conversation dies. But on the other hand, by replying to many of the comments, some people may see me as talking over you. It is a fine line to get it right. The bottom line is, if more people were involved in discussions, expressing a range of supported views, I could say less or even shut up. To make decisions it is always better to have multiple views. When it comes to decisions, if I have been heavily involved in a discussion I always step back from the final decision. In those cases William will make the decision. So just because I am a co-chair and push a particular view does not mean it is a done deal. It really would help if more people expressed opinions on these issues we try to develop... cheers denis co-chair DB-WG

1 0

Set default maintainer on locked inetnum resources
by Edward Shryane 06 Mar '23

06 Mar '23

Dear colleagues, From time to time, the RIPE NCC gets requests from LIRs to unlock their PA assignments that have RIPE-NCC-LOCKED-MNT as mnt-by. These inetnums are locked due to the deprecation of the NONE authentication scheme in 2004: https://www.ripe.net/publications/news/announcements/deprecation-of-the-non… A total of 438 ASSIGNED PA AND 13 LEGACY inetnums have both this maintainer, and a responsible LIR organisation referenced in a less-specific inetnum. The DB team wishes to update these inetnums with the responsible LIR's default maintainer, so they can be maintained by the LIR without needing to contact the RIPE NCC. We will inform the affected maintainers. Please let me know your comments. If there are no objections, I'd like to implement this in the coming weeks. Regards Ed Shryane RIPE NCC

3 6

recording ROV enforcement
by Tomas Hlavacek 03 Mar '23

03 Mar '23

Dear colleagues, In the last few years we saw numerous experiments that strove to identify networks that enforce ROV. These works came not only from the scientific community but also from the industry, which indicates that many different parties are interested in this question and are willing to work to get the answer. This brings me to the question whether there is any structured and machine-readable way that the networks and IXPs can use to publish the fact that they enforce ROV? It seems that the logical place for this would be IRR and therefore I am off-topic here, but since I am not aware of any previous efforts to extend the RPSL for this particular purpose and I can imagine reasons against it, I was wondering if there is something else, possibly in the non-IRR part of the RIPE DB or somewhere else? Best regards, Tomas

3 3

RIPE-NONAUTH AS-SET bug fix
by denis walker 20 Feb '23

20 Feb '23

Colleagues There is some support for the idea that if AUT-NUM objects in RIPE-NONAUTH authorise the creation of AS-SET objects, these set objects will also be in RIPE-NONAUTH. There is also support for this to be considered as a bug from the implementation of 'NWI-5 Out of region ROUTE(6)/AUT-NUM objects'. So existing AS-SET objects whose creation was authorised by one of these RIPE-NONAUTH ASNs can be moved to RIPE-NONAUTH as part of a bug fix. Does anyone have any objections to such a 'bug fix'? cheers denis co-chair DB-WG On Thu, 1 Dec 2022 at 19:34, Nick Hilliard <nick(a)foobar.org> wrote: > > Cynthia Revström wrote on 30/11/2022 22:59: > > I am not sure if this feature is used or not however I think this is a > > very good reason to not go forward with a clean-up (at least until we > > have properly evaluated things). > > We will probably have to figure out some other way to deal with > > objects that are currently causing issues I think. > > the "feature" is used, yes. Some providers have customers in different > RIR service regions. Some organisations have address space registered > in different RIR service regions. It's impossible to avoid in many > situations. > > What's important right now is to close off the option to create new > unqualified as-set names, and to move the existing qualified non-RIPE > ASxxxx:as-set objects from source: RIPE to source: RIPE-NONAUTH. > > Denis was correct that this was a bug during the implementation of NWI-5 > (not ripe-731 which I mistakenly quoted). > > After that, we can afford to spend a bit of time looking at potential > clean-up options. There are 1590 empty as-set objects. 700 of these > haven't been updated in the last 5 years, and some going back 20 years. > > I wouldn't lose too much sleep about deleting empty as-sets. Contact > people, set a timeout, and then delete. Worst case, people can > reference new, qualified as-sets. > > Nick >

4 8

Whois Release 1.106
by Edward Shryane 20 Feb '23

20 Feb '23

Dear Colleagues, RIPE Database release 1.106 has been deployed to the Release Candidate environment. We plan to deploy to production on Monday 20th February. This release includes the following main changes: * NWI-19 Implement AS-SET NONAUTH source (#1169) * Implement RDAP "networks" and "autnums" elements in RDAP entity response (#1103) * RDAP Flat model, don't return as-block (#1125) * RDAP Refactor rdap errors (#1124) * RDAP Events and notices (#1112) * NRTMv4 changes (#1166, #1156, #1099) * Improve AS-SET documentation (#1147) 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

Newbie-ish type of questions
by Hank Nussbacher 08 Feb '23

08 Feb '23

As a LIR we want to extract all records for which we are registered as mnt-by. We tried: https://apps.db.ripe.net/db-web-ui/query?searchtext=-i%20mnt-by%20ISOC-MNT but it appears there is some limit at which point all results are blocked for an undetermined time. Also, we don't want to do copy/paste but rather would like that ability to download or API or script the results. Any clue? We also like the app: https://stat.ripe.net/widget/address-space-hierarchy but again here we didn't find a method to download/script/API the results. Any clue? Thanks, Hank

5 4

The RIPE Database needs your attention...
by denis walker 08 Feb '23

08 Feb '23

Colleagues We still have many outstanding issues, some of which have been on and off the table for years. We cannot make any progress on them as we do not have the attention of enough people in the community. It will be good if we can clear up some of these issues before the next RIPE meeting. For that to happen we need more of you to volunteer to focus a little bit of your attention on database issues over the coming months. The database may not be your highest priority, but it is still an essential tool for many LIR's business and a fundamental part of the whole registry system. If you can PLEASE offer a few moments of your attention over the coming months we can wrap up many of these outstanding issues. Often people who agree with a suggestion, or have no preference, say nothing. We need you to say something so we know you agree or don't disagree. It is not good to declare consensus based on only 3 people commenting. Maybe we can start with the recent conversation about country codes. If you look back over the DB-WG mailing list for January we more or less have a couple of people supporting and one objecting to my suggestions. My suggestions for the community to consider are these: 1/ The country: attribute in ORGANISATION objects is only used to specify the legal address country of organisations (including individuals) holding internet resources and is tied to the country values in the extended delegated stats file. These values are maintained by the RIPE NCC. This is what the community agreed to when they accepted the implementation plan for NWI-10. 2/ The country: attribute in ORGANISATION objects cannot be set by users to meaningless, undefined values for other reasons, as this was not in the agreed implementation plan. 3/ The country: attribute in INET(6)NUM objects is made optional. 4/ We define the optional country: attribute in INET(6)NUM objects to be used for geolocation purposes only 5/ If included, this country code will signal that all the addresses covered by this range/prefix are used within the geographical boundary of the country value. 6/ The geofeed: attribute can be used where a block of addresses are used in multiple countries or if more fine grained details are needed. 7/ An optional country: attribute could be added to the AUT-NUM object if anyone feels it necessary to specify a geolocation for an ASN. As always your thoughts are welcome... cheers denis co-chair DB-WG

1 0

ASNs present in a few AS-SETs in RIPE
by Peter Potvin 30 Jan '23

30 Jan '23

Hello, It has come to our attention that a couple of our newly-allocated ASNs are present in a few AS-SETs within the RIPE database which we should not be present in, and we are unsure how to successfully get them removed from these AS-SETs. If someone could please let us know how we can get them removed, that would be appreciated. Regards, Peter Potvin | Executive Director ------------------------------------------------------------------------------ *Accuris Technologies Ltd.* 56A Mill St E, Unit #470, Acton, ON L7J 1H3 Canada Email: peter.potvin(a)accuristechnologies.ca Office: +1 (877) 352-6105 Network Operations Centre: +1 (877) 321-1662

3 2

Re: [db-wg] ORGANISATION country code
by Ángel González Berdasco 24 Jan '23

24 Jan '23

Hello Denis Sorry to ask but, how is this country code used / what their meaning when it is entered by RIPE NCC itself? It appears to me that the challenge on "what to place" would be the same. Regards -- INCIBE-CERT - Spanish National CSIRT https://www.incibe-cert.es/ PGP keys: https://www.incibe-cert.es/en/what-is-incibe-cert/pgp-public-keys ==================================================================== INCIBE-CERT is the Spanish National CSIRT designated for citizens, private law entities, other entities not included in the subjective scope of application of the "Ley 40/2015, de 1 de octubre, de Régimen Jurídico del Sector Público", as well as digital service providers, operators of essential services and critical operators under the terms of the "Real Decreto-ley 12/2018, de 7 de septiembre, de seguridad de las redes y sistemas de información" that transposes the Directive (EU) 2016/1148 of the European Parliament and of the Council of 6 July 2016 concerning measures for a high common level of security of network and information systems across the Union. ==================================================================== In compliance with the General Data Protection Regulation of the EU (Regulation EU 2016/679, of 27 April 2016) we inform you that your personal and corporate data (as well as those included in attached documents); and e-mail address, may be included in our records for the purpose derived from legal, contractual or pre-contractual obligations or in order to respond to your queries. You may exercise your rights of access, correction, cancellation, portability, limitationof processing and opposition under the terms established by current legislation and free of charge by sending an e-mail to dpd(a)incibe.es. The Data Controller is S.M.E. Instituto Nacional de Ciberseguridad de España, M.P., S.A. More information is available on our website: https://www.incibe.es/proteccion-datos-personales and https://www.incibe.es/registro-actividad. ====================================================================

2 1