- db-wg - mailman.ripe.net

About rpki
by Cunchang Huang 22 Jun '23

22 Jun '23

I now need to get the expiration time of the rpki we set, how can I get it Cunchang Huang

1 0

NWI-14 Authenticating References to Objects
by denis walker 19 Jun '23

19 Jun '23

Colleagues The chairs propose creating NWI-14 for expanding the optional use of the "mnt-ref:" attribute to protect objects from accidental or intentional mis-representation of responsibility. See slide 14 of this presentation for the problem definition: https://ripe78.ripe.net/presentations/129-RIPE78-Operational-Update.pdf We ask the RIPE NCC to add NWI-14 to the list. cheers denis co-chair DB-WG

3 4

Whois Release 1.107
by Edward Shryane 19 Jun '23

19 Jun '23

Dear colleagues, RIPE Database release 1.107 has been deployed to the Release Candidate environment. We plan to deploy to production on Monday 19th June. This release includes the following main changes: * NWI-14: added mnt-ref: attribute to person, role, mntner, irt object types * Sign NRTMv4 notifications * Full text search fixes * Limit resource lookups in RDAP organisation entity requests * Allow any characters in local part of SSO auth: email addresses * Fixed country: attribute validation * Include country: attribute in organisation split file The release notes are on the website: https://apps.db.ripe.net/docs/21.Release-Notes.html#ripe-database-release-1… 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

Sponsored ASNs AccountOwner's in extended delegate file don't move with sponsor
by Ben Cartwright-Cox 15 Jun '23

15 Jun '23

I'm not 100% sure if this is the correct place to report/discuss this quirk I've come across, but db-wg is the closest I have, so here it goes. In (what I call) the RIPE delegate file https://ftp.ripe.net/ripe/stats/delegated-ripencc-extended-latest Sponsored ASNs have slightly funny behaviour. For ASNs that are sponsored, the account owner UUID is always the ASN that sponsored the ASN first. If sponsorship is moved, the account owner UUID does not change. However given (as far as I understand) sponsored ASNs are PI resources, surely they should get the same treatment as the IPv4 and IPv6 entries (in that the PI holder has their own accountowner uuid) What do we think? Is this behaviour of being sticky to the original sponsor account UUID a bug? Should sponsored ASNs have their own account UUID? Have I completely misunderstood what any of this file means? I ask most of this because my own system bgp.tools allows you to quickly lookup resources by account, and for my own production ASN: $ curl -s https://ftp.ripe.net/ripe/stats/delegated-ripencc-extended-latest | grep 206924 ripencc|GB|asn|206924|1|20170411|allocated|b786bde2-1363-44c5-aec3-5ac65ee325e6 It shows all of the remaining ASNs that were originally registered by the now defunct LIR: https://bgp.tools/rir-owner/b786bde2-1363-44c5-aec3-5ac65ee325e6 Cheers Ben Cartwright-Cox

2 3

NWI update
by denis walker 24 May '23

24 May '23

Colleagues In the past we have done an NWI update as a presentation during the RIPE Meeting. However, as there is usually very little movement on most NWIs, the presentations are not very informative. This time we will present the update as an email and ask for any questions in the AOB at the end of the WG session on Thursday afternoon. NWI-2 Historical queries No comments since RIPE 85 NWI-4 Assigning a full allocation One comment today expressing a preference for the combined primary key (prefix/status) rather than simply changing the status. This allows separate objects for the allocation and the assignment with their own information and references. NWI-12 NRTMv4 In progress, for more details see: https://github.com/mxsasha/nrtmv4/ NWI-13 Geofeed Legal review posted to list last week. The RIPE NCC will discuss internally how to tighten up the wording of the proposed purpose text. The RIPE NCC Executive Board will need to approve the change to the Terms & Conditions to accept the new purpose. Then geofeed should be usable without the previous legal restrictions. NWI-14 Extending use of mnt-ref Implementation in progress by RIPE NCC NWI-16 Using RIPE Database as an IPAM solution No comments since RIPE 85 NWI-15,17,18 Task Force recommendations No comments cheers denis co-chair DB-WG

1 0

Re: [db-wg] Agenda RIPE86 - Database Working Group - REVISED
by William Sylvester 16 May '23

16 May '23

Here is the revised agenda for the Database Working Group for RIPE86. If you would like to present, have questions, comments, or requested changes please let the chairs know. Best regards, William & Denis DB-WG Chairs A. Introduction - 10 min * Welcome * Scribe * Jabber * Chairs & Succession Planning * Agenda B. Operational Update– 20 mins Edward Shryane, RIPE NCC C. Managing the RIPE DB – 20 mins Denis Walker, Co-Chair DB-WG D. Use Cases of the RIPE Database – 15 mins Maria Stafyla, Co-Chair DB-WG Z. AOB (open discussion)

1 0

Agenda RIPE86 - Database Working Group
by William Sylvester 14 May '23

14 May '23

Below is the agenda for the Database Working Group for RIPE86. If you would like to present, have questions, comments, or requested changes please let the chairs know. Best regards, William & Denis DB-WG Chairs A. Introduction - 10 min * Welcome * Scribe * Jabber * Chairs & Succession Planning * Agenda B. NWI Update – 20 mins Denis Walker, Co-Chair DB-WG C. Operational Update– 20 mins Edward Shryane, RIPE NCC D. Geofeed Discussion – 15 mins Maria Stafyla, Co-Chair DB-WG Z. AOB (open discussion)

2 1

Proposed Service Criticality Form
by Edward Shryane 12 May '23

12 May '23

Dear Colleagues, During RIPE 84 in May, we discussed the Service Criticality Framework. We mentioned that we would like the Database Working Group's input on the criticality rating for the RIPE Database. Thank you to the Co-chairs for asking the working group for input in July with the original form: https://www.ripe.net/ripe/mail/archives/db-wg/2022-July/007527.html Since we have yet to receive any feedback so far, we plan to share our proposed completed form with the working group on Monday, 12 December. We hope that this will invite more input. Regards Ed Shryane RIPE NCC

3 4

chair selection
by denis walker 20 Apr '23

20 Apr '23

Colleagues The process for selecting chairs and terms of office is documented here https://www.ripe.net/participate/ripe/wg/active-wg/db/database-wg-chair-sel… Accordingly, Denis's term of office expires at RIPE 86. If anyone is interested in joining the team please contact db-wg-chairs(a)ripe.net over the next two weeks. cheers William and denis co-chairs DB-WG

1 1

Whois Release 1.106.1
by Edward Shryane 19 Apr '23

19 Apr '23

Dear Colleagues, RIPE Database release 1.106.1 has been deployed to the Release Candidate environment. We plan to deploy to production on Wednesday 19th April. This release includes the following main changes: * NWI-12 NRTMv4 improvements (snapshot, deltas, notification files) * Updated Zonemaster client to match API Changes (used for domain object validation) * Redirect RDAP reverse domain queries to the authoritative source * Fix hightlight issue with dot in Elasticsearch (used by Full Text Search API) 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