- db-wg - mailman.ripe.net

Updated Full Text Search API
by Edward Shryane 23 Jun '23

23 Jun '23

Dear Colleagues, In the Whois 1.107 release, we have made some improvements to the Full Text Search API and also to the backend Elasticsearch implementation. We have also improved the API documentation: https://apps.db.ripe.net/docs/11.How-to-Query-the-RIPE-Database/02-Web-Quer… If you prefer using the web interface to Full Text Search, it is still available: https://apps.db.ripe.net/db-web-ui/fulltextsearch If you have any suggestions for improvements or find any issues, please let me know. Regards Ed Shryane RIPE NCC

1 0

RIPE Database Quarterly Planning Q3 2023
by Edward Shryane 23 Jun '23

23 Jun '23

Dear colleagues, We have published our next quarterly plans for the RIPE Database on our website: https://www.ripe.net/manage-ips-and-asns/db/quarterly-planning In this quarter, we will continue to work on publishing the source code to our web application and move the RIPE Database documentation to a new interface. By sharing these plans with you, we want to inform you of the ongoing developments on the RIPE Database and get your feedback on other work items you would like us to focus 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

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 15 May '23

15 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

-T
by Randy Bush 12 Apr '23

12 Apr '23

i just want to fetch the domain object [ actually, what i would love is to fetch all domain objects with mnt-by: MAINT-RGNET but one step at a time ] ryuu.rg.net:/Users/randy> telnet -4 whois.ripe.net 43 Trying 193.0.6.135... Connected to whois.ripe.net. Escape character is '^]'. % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf -T domain 150.180.198.in-addr.arpa % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '150.180.198.in-addr.arpa' domain: 150.180.198.in-addr.arpa descr: RG79-198-180-151 admin-c: RB45695-RIPE tech-c: RB45695-RIPE zone-c: RB45695-RIPE nserver: rip.psg.com nserver: nlns.globnix.net ds-rdata: 54446 8 2 3b1fdae94f0e47d280e23ad1b62fb1451d98f29f66863420d6a3d0f5fa2f1037 mnt-by: MAINT-RGNET created: 2016-03-16T18:42:51Z last-modified: 2023-04-07T16:00:58Z source: RIPE person: Randy Bush address: RGnet OÜ address: Sakala tn 7-2 address: Tallinn address: EE-10141 address: Estonia phone: +33 7 67 97 33 30 nic-hdl: RB45695-RIPE mnt-by: MAINT-RGNET created: 2019-05-20T12:22:32Z last-modified: 2019-12-12T06:06:38Z source: RIPE % This query was served by the RIPE Database Query Service version 1.106 (BUSA) Connection closed by foreign host. so maybe it wants the option at the end? ryuu.rg.net:/Users/randy> telnet -4 whois.ripe.net 43 Trying 193.0.6.135... Connected to whois.ripe.net. Escape character is '^]'. % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf 230.83.192.in-addr.arpa -T domain % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '230.83.192.in-addr.arpa' domain: 230.83.192.in-addr.arpa descr: RG79-192-83-230 admin-c: RB366-ARIN tech-c: RB366-ARIN zone-c: RB366-ARIN nserver: rip.psg.com nserver: nlns.globnix.net ds-rdata: 142 8 2 1e1f841e69f79afa0c6775647e90597c88dbe7121867473700b7a51c358d9045 mnt-by: MAINT-RGNET created: 2016-03-16T18:42:51Z last-modified: 2016-03-16T18:42:51Z source: RIPE person: Randy Bush address: RGnet, LLC address: 5147 Crystal Springs address: Bainbridge Island, WA 98110 address: United States phone: +1 206 356 8341 fax-no: +1 206 973 2762 nic-hdl: RB366-ARIN mnt-by: MAINT-RGNET created: 1970-01-01T00:00:00Z last-modified: 2019-12-12T06:03:49Z source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.106 (SHETLAND) Connection closed by foreign host. clue bat appreciated randy

3 3

More specific INET6NUM for IPv6 PI
by Tobias Fiebig 04 Apr '23

04 Apr '23

Heho, for some unrelated reasons I have been thinking about more specific INET6NUM objects for IPv6 PI assignments that still list the same organization but detail a specific purpose of the more specific to aid, e.g., debugging and information sharing. As this is a relatively quick thought that crept up to my brain (I don't want to request or suggest anything; More interested in understanding the current situation), i'd really appreciate some input, mainly to understand where i might have missed some context. With best regards, Tobias # Description The following might, for example, be the use of a /48 PI assignment: 2001:db8:1234::/48 2001:db8:1234::/52 - Public Internet Infrastructure 2001:db8:1234::/56 - Network; Loopbacks, transfer etc. 2001:db8:1234:100::/56 - Infrastructure PoP1 (mail, web, DNS) 2001:db8:1234:200::/56 - Infrastructure PoP2 (backup, DNS) 2001:db8:1234:f000::/52 - Office France 2001:db8:1234:f000::/56 - Office (infra) France 2001:db8:1234:f100::/56 - Office (wired) France 2001:db8:1234:f200::/56 - Office (wifi) France 2001:db8:1234:f300::/56 - Office (guest wifi) France 2001:db8:1234:d000::/52 - Office Germany 2001:db8:1234:d000::/56 - Office (infra) Germany 2001:db8:1234:d100::/56 - Office (wired) Germany 2001:db8:1234:d200::/56 - Office (wifi) Germany 2001:db8:1234:d300::/56 - Office (guest wifi) Germany Dedicated INET6NUM objects could be useful for: - The per-office-country /52 to properly attribute geoloc and direct to the right (local) role contacts (noc.fr(a)example.com vs. noc.de@) - Indicate that the internal office wifis have a /64 on each client - Indicating the status of the guest wifis and a different abuse department, as they--containing externals--might have to be handled differently, and there is no prefix delegation (PI requirements) - Creating objects for pop1/pop2 infra networks (noc.infra@, detailing use for public-facing/DMZish systems) - Creating objects providing additional information on more specifics that may show up in traceroutes - ... In all cases, the ORG of the objects would remain the same as that of the assigned /48. This is currently not possible in the DB as: - There is no fitting status:, and ASSIGNED PI can not use by LIR/end- user MNTs - The creation of more specific INET6NUM objects is not allowed in general Arguments against allowing more specifics below PI are: # The org should just request one PI per pop/use (infra/de/fr) Here, I would argue, that this does not necessarily conform to address space conversation; Technically, the /48 is enough for this specific org. Also, while RIPE 738 2.6 notes that assignments should only be made for _specific_ purposes, it explicitly lists some of the use-cases and splits described above. Furthermore, when requesting PI, the ability to use more specifics from a /48 is a common argument why only a /48 can be provided to one end-user with multiple pops. Similarly, requesting multiple /48s increases the numbering overhead for the end-user, and even if one larger-than /48 assignment was made (which is a discussion out-of-scope and for another wg here), the issue of creating more specifics for the /48s would remain the same. # Policy forbids it I am actually not sure whether ripe-738 actually forbids this. Reading Sec. 2.6, I only see a restriction to specific purposes (see above) and a restriction of more specifics being 'sub-assigned to other parties', which is reiterated in the preamble of Sec. 7. In my reading, though, that does not mean that an assignee could not create more specific INET6NUM to more accurately document the extend of the specific use of the assignment, as long as the ORG remains the same. -- Tobias Fiebig M tobias(a)fiebig.nl

4 3

ORGANISATION country code
by denis walker 23 Mar '23

23 Mar '23

Colleagues We have a number of outstanding issues from RIPE 85 so let's start with NWI-10. Ed said in his update, "Country code is now editable in organisations without co-maintained resources" I think this is a really bad idea. The country codes entered into ORGANISATION objects by the RIPE NCC are well defined, verified and maintained by the RIPE NCC. If we allow users to edit this field in other ORGANISATION objects, the values they enter will be undefined, unverified and meaningless. Just like the country code in resource objects. I don't think we should allow more meaningless data to be added to the RIPE Database. Even worse, we are mixing well defined data with meaningless data in the same attribute in the same object. This will end up with some people trusting all of this data and some people not trusting any of it...confusion. I suggest we don't allow users to enter any data into this attribute and remove any data that may have already been entered. If there is a need for resource holders to enter a country code in ORGANISATION objects set up for end users, then let's define a specific attribute for that with a well defined meaning. Your thoughts are welcome... cheers denis co-chair DB-WG

11 36

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