- db-wg - mailman.ripe.net

Whois Release 1.99
by Edward Shryane 21 Dec '20

21 Dec '20

Dear Working Group, RIPE Database release 1.99 has been deployed to the Release Candidate environment. We plan to deploy to production on Monday 21st December. This release includes the following main changes: * NWI-10: require -mnt suffix * Filter out sensitive information in API response on exception * Return 'invalid option supplied' on invalid version number given to --diff-version * Allow *any* CORS origin on RDAP GET requests by default (as recommended by RFC 7480). * New dummifier for RC environment * Enable TCP_NODELAY in NRTM and query connections In addition to other small improvements and bug fixes. 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

2 3

NWI-10: Phase 1 Implemented
by Stefania Fokaeos 19 Dec '20

19 Dec '20

Dear colleagues, We are pleased to announce that we have implemented Phase 1 of NWI-10: Definition of Country. The following updates took place as part of the implementation: 1. ORGANISATION objects with "org-type:" 'LIR' have been updated to include a new "country:" attribute. The Country Code displayed in this attribute is the country in which the resource holder is legally based 2. The Country Code (CC) has also been updated in the Extended Delegated Statistics file when there was a mismatch between the file and the new attribute. These resources have now as "CC" the same Country Code that is visible in the respective ORGANISATION object If you notice that your Country Code is incorrect, you can contact us. Please note that we might ask you for supporting documentation to justify the update. In the meantime, we are continuing to work towards Phase 2 of NWI-10 and will keep you updated about our progress. You can read more about our implementation plan and the different phases of NWI-10 on RIPE Labs: https://labs.ripe.net/Members/stefania_fokaeos/our-plan-to-fix-country-codes If you have any questions about the implementation of NWI-10, please send an email to <support(a)ripe.net> or <policy-implementation(a)ripe.net>. Happy Holidays and warm wishes for 2021! Kind regards, Stefania Stefania Fokaeos RIPE NCC

3 2

Weirdness in DB files
by Cynthia Revström 17 Dec '20

17 Dec '20

Hi DB-WG, I just noticed that the (at the time of writing, serial 49363913) latest aut-num split db file (possibly elsewhere too) sort of just seems to break at some point. The lines like below simply stop appearing: % Tags relating to 'AS3333' % RIPE-REGISTRY-RESOURCE Here's a section where you can see it happening: https://gist.githubusercontent.com/bitcynth/d81688c6b7587e0179d55b8324535ff… Any clue why this is occurring? or is it just a bug? - Cynthia

3 4

Domain Object Cleanup in the RIPE Database
by Edward Shryane 14 Dec '20

14 Dec '20

Dear colleagues, As mentioned in the Operational update during the DB-WG session at RIPE81, the RIPE NCC will shortly clean up (delete) domain objects without a mandatory "nserver:" attribute. This will affect approximately 1,600 domain objects in the RIPE database, which have not been updated since September 2012. We plan to notify the maintainers of affected objects today, and ask them to add "nserver:" attributes to any objects they wish to keep. We will then delete any remaining domain objects without a mandatory "nserver:" attribute in two weeks from now (on 14th December). Regards Ed Shryane RIPE NCC

1 1

Historical records... what is and isn't available
by Ronald F. Guilmette 08 Dec '20

08 Dec '20

I bumped my head on something unexpected a day or two ago, and I would now just like to ask a question, to find out if what I seemed to see was just a product of my own programming mistake, or if it is fact the way things were intended to be. So, true or false? The --list-versions and --show-version options are not supported for person:, role:, and mntner: records. To be clear I am *not* asking if the data returned when the --show-version option is applied to one of the types of records I've just listed is merely redacted of all personal information relating to natural persons. Rather, I am asking if I should in fact be expecting to get absolutely -nothing- back when/if I try to use --show-version on any of the aforementioned record types, regadless of of whether the requested historical information contains 100% personal information or alternatively, if it contains 0% personal information, or anything in between. Regards, rfg

6 9

Proposal to revert NWI-10
by Cynthia Revström 07 Dec '20

07 Dec '20

Apologies if this email is a bit impolite. >From the start NWI-10 seemed like a pointless policy to me and just a policy that was made because the db-wg wanted to make more policies. But as it has already messed up the data on my resources, I see it as a policy that messes up data and wastes time for no real advantage. Hence I suggest that we revert NWI-10 unless someone actually has a good reason for why the legal address needs to match the delegated file, and how to implement it in a non-messy way. - Cynthia

4 10

ORG-TKDS1-RIPE - VECTRA S.A. - Spam filters & abuse reporting addresses
by Ronald F. Guilmette 04 Dec '20

04 Dec '20

Based on my experience, if one is reporting spam to most typical networks, the network operators generally like to actually -see- the spam being reported. Thus, I always include a copy. It is Good that RIPE resource holders now all have abuse reporting addresses in their WHOIS records. It is also Good that RIPE NCC is now checking these abuse reporting contact email addresses to insure that they actually function, at least minimally. What is un-good, in my opinion, is for any network to have an abuse reporting address set up with *content based* anti-spam filters. To illustrate this point, I have recently received a spam from an IP address that is currently being routed by AS29314 - Vectra S.A., located in Poland. I duly forwarded a full copy of that spam to the abuse reporting address provided in the RIPE WHOIS for AS29314, i.e. abuse(a)vectra.pl. That message was rejected with the following SMTP reject message: <abuse(a)vectra.pl>: host smtp.vectra.pl[88.156.64.22] said: 554 Spam. Email Session ID: 86748699 (in reply to end of DATA command) Given that outcome, I now feel compelled to locally blacklist all IP space associated with ORG-TKDS1-RIPE (VECTRA S.A.) until such time as some kind soul provides the operators of this network with some education on the topic of how to operate an abuse reporting address. The space in question is as follows: 31.11.128.0/17 31.22.96.0/21 31.135.168.0/21 37.8.192.0/18 37.77.152.0/21 46.36.224.0/19 62.122.112.0/21 77.222.224.0/19 78.31.152.0/21 78.31.209.0/24 78.88.0.0/16 82.139.0.0/18 83.143.40.0/21 83.143.136.0/21 83.243.104.0/21 88.156.0.0/16 89.151.0.0/18 91.192.76.0/22 91.230.159.0/24 91.230.162.0/23 91.230.164.0/22 91.231.116.0/23 91.238.232.0/22 93.105.0.0/16 94.231.48.0/20 95.160.0.0/16 109.107.0.0/19 109.197.56.0/21 109.197.64.0/21 109.241.0.0/16 178.235.0.0/16 185.51.180.0/22 192.166.120.0/23 193.108.228.0/23 193.201.18.0/23 194.54.188.0/22 195.26.72.0/22 195.28.170.0/23 195.95.170.0/24 195.191.162.0/23 195.225.92.0/22 195.242.252.0/22

1 0

Fwd: Multi tenancy in a LIR?
by denis walker 20 Nov '20

20 Nov '20

Hi Hank Your scenario is not clear. When you say "each has their own resources", how did they get those resources? Were they separate LIRs that have received allocations, have there been mergers, were they all allocated to the parent organisation's LIR and distributed to sub organisations? Or do you mean they each want to have their own resources? As far as the database is concerned, address space resources allocated to the parent organisation's LIR can be distributed to sub organisations as LIR-PARTITIONED or ALLOCATED-BY-LIR. The sub organisations can separately manage their resources. If you want exclusive management control by the sub organisations you can set the MNTNER attributes accordingly. But ultimately they are still the parent organisations resources. They could be reclaimed by the parent organisation. The organisation reference in the allocations will always be the parent organisation that was allocated the resources by the RIPE NCC. That cannot be changed. cheers denis co-chair DB-WG On Thu, 19 Nov 2020 at 16:28, Hank Nussbacher via db-wg <db-wg(a)ripe.net> wrote: > > Can a LIR account handle multi-tenancy? > > > What if you had a parent organization and a few sub-organizations and each has their own resources (ASN + inetnum) that they wish to manage independently (objects, RPKI, etc) without the other sub-organizations of parent organization able to affect the resources. > > Is that at all possible or is the only solution to create a new LIR account? > > > Thanks, > Hank > Caveat: The views expressed above are solely my own and do not express the views or opinions of my employer

3 5

Multi tenancy in a LIR?
by Hank Nussbacher 19 Nov '20

19 Nov '20

2 1

Problem definition for new NWI (12?) - NRTM service
by Stavros Konstantaras 19 Nov '20

19 Nov '20

Dear db-wg community, Please find below the problem definition for the (upcoming) NWI-12 item as we have discussed it and envisioned it for this project. Problem definition: Back on October 2019 during the RIPE 79 meeting in Rotterdam, we discussed about the need to move forward with a next generation of NRTM service. Upon the completion of NWI-9 and the lifting of the legal restrictions, we can now proceed to design the new solution. As we discussed preciously, the version 3 of the current NRTM solution is not suitable anymore for network operations on 2020. A summary of the reasons are: -Is a Telnet based protocol, thus: • No keep alive mechanism is adopted, • It provides plain text/unencrypted transport of data -The bootstrap process is not always trivial and sometimes is slow -Long time synchronisation is complicated and users need to re-synchronise after a couple of weeks. -No well specified protocol (There is just a PDF doc that describes it) For all the reasons above (and reasons that we might have not think about yet but you are welcome to share), it becomes a necessity for the community to proceed with a new implementation that will be easily adopted by modern tools and last for the years to come. I hope the above text is sufficient for the db-wg chairs to kick off the process and the community to share its feedback. Best regards, Stavros Konstantaras | Sr. Network Engineer | AMS-IX M +31 (0) 620 89 51 04 | T +31 20 305 8999 ams-ix.net

4 3