- db-wg - mailman.ripe.net

Re: [db-wg] geofeed issue: can't add geofeed attribute to PI /48
by Jeroen Massar 14 Feb '22

14 Feb '22

> Hi Job, Colleagues, > > On 3 Jan 2022, at 13:36, Job Snijders via db-wg <db-wg at ripe.net> wrote: > > > > ... > > I appreciate concerns about privacy, but I'm not wholly convinced > > restricting /48s from having a proper 'geofeed:' attribute is the best > > path forward. > > > > How does the working group feel about this restriction? Is it useful? > > Should it be lifted? If the latter, what would be the process? > > > I will ask our Legal team to re-examine the prefix size restriction and keep you and the DB-WG informed. > Regards Ed Shryane RIPE NCC Hi Ed, Did something come out of this? It is a very silly restriction, especially for PI /48's but also for the simple fact that one can register very small prefixes (I've done IPv4 /28 and IPv6 /56) in the actual geofeeds file. Greets, Jeroen

2 1

update on draft-spaghetti-grow-nrtm-v4-00
by Sasha Romijn 04 Feb '22

04 Feb '22

Hello all, FYI, following up on various discussions and the BoF we had on this list about NRTMv4 and NWI-12, a draft has now been submitted. If you’re interested in discussing further details of the proposed protocol, do send your questions and comments to that mailing list. Sasha Forwarded message: > From: Sasha Romijn > To: grow(a)ietf.org > Subject: [GROW] draft-spaghetti-grow-nrtm-v4-00 > Date: Fri, 04 Feb 2022 13:04:48 +0100 > > Hello, > > We’ve submitted a draft for the Near Real Time Mirroring Protocol (NRTM) version 4: https://datatracker.ietf.org/doc/draft-spaghetti-grow-nrtm-v4/ > > This document specifies a one-way synchronization protocol for Internet Routing Registry (IRR) records. The protocol allows instances of IRR database servers to mirror IRR records, specified in in the Routing Policy Specification Language (RPSL), between each other. > > NRTMv4 is intended as a replacement of current synchronization methods mainly based on FTP downloads and NRTM version 3, which have many problems that are addressed in NRTMv4. > > The need for this originated from experiences by users of IRRD v4, and discussions in the RIPE Database working group, tracked under NWI-12: > https://www.ripe.net/ripe/mail/archives/db-wg/2020-November/006720.html > > The broad strokes of this draft were previously discussed in a BoF in the RIPE Database wg, which included several operators of IRR databases, and responses were overall positive. I am also the maintainer of IRRD v4, one of the most widely used IRR database servers, and will implement it in there. > > I’m proposing this draft for adoption by this working group. I would also be happy to present it in the IETF 113 session. > > Sasha Romijn > > _______________________________________________ > GROW mailing list > GROW(a)ietf.org > https://www.ietf.org/mailman/listinfo/grow

2 1

RDAP Conformance Level "cidr0"
by Benjamin Pereto 26 Jan '22

26 Jan '22

Dear RIPE DB wg, The RDAP for querying ip and network information on rdap.db.ripe.net is really useful. Currently you support the rdapConformance level "rdap_level_0" and this is missing the CIDR or Prefix Information about the Length/Mask. Other RIR have implemented a rdap conformance level "cidr0" for this: * https://rdap.arin.net/registry/ip/9.9.9.9 * https://rdap.apnic.net/ip/1.1.1.1 with the desired information: "cidr0_cidrs": [ { "v4prefix": "1.1.1.0", "length": 24 } ] Information about the Origin ASN is also available by arin with "arin_originas0", which is also very helpful, but the format seems to be arin specific and not standardized. May I suggest to also implement the cidr0 level, or even additionally the "origin as" for the RIPE DB RDAP? Kind regards, Benjamin

2 1

RIPE Database Quarterly Planning Q1 2022
by Edward Shryane 11 Jan '22

11 Jan '22

Dear colleagues, We have now published our Q1 2022 planning for the RIPE Database: https://www.ripe.net/manage-ips-and-asns/db/quarterly-planning/ This is the second quarterly plan we have published. The previous plan for Q4 2021 is also available so you can see how we progressed and see what was completed and what will continue in Q1 2022: https://www.ripe.net/manage-ips-and-asns/db/quarterly-planning/archived-pla… If you have comments or questions around our plans, we hope you'll discuss with us on the list or you can always contact us directly at ripe-dbm(a)ripe.net. Regards, Ed Shryane RIPE NCC

1 0

Whois Release 1.102.2
by Edward Shryane 20 Dec '21

20 Dec '21

Dear Colleagues, We have deployed Whois release 1.102.2 to production to fix further vulnerabilities in the Log4j library. The only change from Whois release 1.102.1 is to update the log4j dependency from 2.15.0 to 2.17.0. Regards Ed Shryane RIPE NCC

1 0

Whois Release 1.102.1
by Edward Shryane 13 Dec '21

13 Dec '21

Dear Colleagues, We have deployed Whois release 1.102.1 to production to fix the Log4Shell vulnerability: https://www.lunasec.io/docs/blog/log4j-zero-day/ The only change from Whois release 1.102 is to update the log4j dependency from 2.14.1 to 2.15.0. We previously put a workaround in place last Friday morning to mitigate this vulnerability, we don't believe it has been exploited. Regards Ed Shryane RIPE NCC

1 0

Whois Release 1.102
by Edward Shryane 07 Dec '21

07 Dec '21

Dear Colleagues, RIPE Database release 1.102 has been deployed to the Release Candidate environment. We plan to deploy to production on Tuesday 7th December. This release includes the following main changes: * NWI-13: Geofeed (#937) * Support base64 encoded signed update messages (sent by Thunderbird 78+) (#942) * Updated "geoloc:" help text (#929) * Support IDN in outgoing mail update notifications (#888) 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 2

RIPE Database Purposes - Video presentation
by denis walker 23 Nov '21

23 Nov '21

Colleagues In advance of my presentations tomorrow, if you have a spare 15 minutes please watch the pre-recorded presentation: https://ripe83.ripe.net/wp-content/uploads/presentations/DB_WG-Denis_Walker… cheers denis co-chair DSB-WG

1 0

NWI-13: Geofeed Impact Analysis
by Edward Shryane 17 Nov '21

17 Nov '21

2 3

Agenda RIPE83 - Database Working Group
by William Sylvester 15 Nov '21

15 Nov '21

Dear Database Working Group Members, Below is the agenda for the Database Working Group for RIPE83. 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 & Cloud Migration Update– 15 mins Edward Shryane, RIPE NCC C. UI Update – 15 mins Rehan Syed, RIPE NCC D. Database Task Force Update – 15 mins Shane Kerr, Database Task Force E. RIPE Database Purposes – 10 mins Denis Walker, Co-Chair DB-WG Z. AOB (open discussion)

2 1