- db-wg - mailman.ripe.net

in-addr.arpa glue?
by Randy Bush 23 Oct '20

23 Oct '20

domain: 0.28.147.in-addr.arpa descr: RG79-147-28-0 admin-c: RB45695-RIPE tech-c: RB45695-RIPE zone-c: RB45695-RIPE nserver: rip.psg.com nserver: nlns.globnix.net mnt-by: MAINT-RGNET source: RIPE ***Error: No response from nameserver for zone 28.147.in-addr.arpa when trying to fetch glue. ***Error: Not enough data about 0.28.147.in-addr.arpa was found to be able to run tests. not aware of glue in in-addr.arpa zones does it want me to delete the 28.147.in-addr.arpa parent zone first? that seems scary. randy

3 3

New on RIPE Labs: Our Plan to Fix Country Codes - NWI-10
by Stefania Fokaeos 23 Oct '20

23 Oct '20

Dear colleagues, As part of our preparation for the implementation of NWI-10, we've written an article on RIPE Labs in which we look at our plans for fixing country codes in the RIPE Database. https://labs.ripe.net/Members/stefania_fokaeos/our-plan-to-fix-country-codes <https://labs.ripe.net/Members/stefania_fokaeos/our-plan-to-fix-country-codes> During the RIPE Database WG session next Thursday at RIPE 81 all NWIs will be discussed and if needed my colleague Ed Shryane can provide more details. Kind regards, Stefania Fokaeos RIPE NCC

1 0

MNTNER Naming : Consensus
by William Sylvester 19 Oct '20

19 Oct '20

db-wg members, The chairs of the database working group believe there is a consensus to have a standardised name format for creating new MNTNER objects. There was talk of a prefix (MNT-) or a suffix (-MNT). When creating a new standard it doesn't really make sense to introduce a standard with multiple formats. As there are currently 36347 MNTNERs that end with -MNT and 12480 MNTNERs that start with MNT-, we suggest that the standard should be to end with -MNT. We ask the RIPE NCC to take the next steps in moving this request forward, conducting an impact analysis, and proceed with implementation. Best regards. William & denis db-wg chairs

4 5

NWI reviews: NWI-3, NWI-6 consensus
by denis walker 15 Oct '20

15 Oct '20

Colleagues The author of 'NWI-6 Applicable data model not clear from contextless objects' has agreed that it can be cancelled. No one disagreed with that so the chairs agree to cancel NWI-6. It was suggested that 'NWI-3 Afrinic IRR Homing' was partly superseded by 'NWI-5 Out of region ROUTE(6) / AUT-NUM objects'. As NWI-5 is finished then NWI-3 should also be marked as finished. No one disagreed with this so the chairs agree that NWI-3 is finished. Ed, please mark NWI-3 as 'Finished' and NWI-6 as 'Cancelled'. cheers denis co-chair DB-WG

2 1

Re: [db-wg] proposal: new attribute 'geofeed:'
by Q 07 Oct '20

07 Oct '20

Hi Elad, > Not everyone will add the "geofeed" value and the geolocations in the csv will not validated by a 3rd party and may also be not up to date. It is a fair point that not everyone will use this, but I think a significant enough number will to warrant addition. On the point of validation it would be perhaps advisable for the RIPE DB to verify the reachability of the file (as with rDNS setup), but I don't think further validation is within scope. > I suggest to make the csv creation (of each INETNUM object) automatic and hosted by RIPE NCC Ggood suggestion, not everyone will want to use their own webserver for this, and a simple service provided by RIPE would help improve adoption, however I'm not sure that people who can't host a CSV file should really be dealing in this anyway. > RIPE NCC can use all the current ATLAS Probes in order to check the physical location of each ip This feels like a guess at best, and providing guesswork as authoritative information is hardly a sensible idea. Overall this proposal gets a +1 from me, and due to this purposefully light nature of the geofeed standard itself I don't think RIPE NCC should add too much to it. Thanks, Q Director [image: https://as207960.net] <https://as207960.net> <https://www.youracclaim.com/badges/4570b2d1-947f-426a-832d-d0e4bf445267/pub…> https://as207960.net AS207960 Cyfyngedig Phone: +44 29 2010 2455 (ext 601) Fax: +44 29 2010 2455 Address: 13 Pen-y-lan Terrace, Caerdydd, Cymru, CF23 9EU

1 0

NWI reviews: NWI-6 Applicable data model not clear from contextless objects
by ripedenis＠yahoo.co.uk 07 Oct '20

07 Oct '20

Colleagues This is the last of the NWIs from 4 years agohttps://www.ripe.net/ripe/mail/archives/db-wg/2016-June/005272.html For this one I am not even sure what is being asked for and I don't agree with some of the points in the problem statement. Maybe Job can expand on it. Any comments appreciated... cheersdenis co-chair DB-WG

2 1

RIPE Database Requirements Task Force BoF, 26 October 2020
by Bijal Sanghani 07 Oct '20

07 Oct '20

Dear colleagues, The RIPE Database Requirements Task Force (DBTF) will organise its second BoF on Monday, 26 October 2020 from 16:00-17:00 (UTC+1) via Meetecho. During this BoF, the DBTF will present its latest draft and invite participants to provide feedback on the document. The Meetecho link to join the BoF will be shared one week before the event at: https://ripe81.ripe.net/programme/meeting-plan/bof/ <https://ripe81.ripe.net/programme/meeting-plan/bof/> We look forward to discussing the future of the RIPE Database with you! Kind regards, Bijal Sanghani on behalf of the DBTF

1 0

Whois Release 1.98
by Edward Shryane 01 Oct '20

01 Oct '20

Dear Working Group, RIPE Database release 1.98 has been deployed to the Release Candidate environment. We plan to deploy to production on Thursday 1st October. This release includes the following main changes: * NWI-11 Punycode Internationalized Domain Names in email addresses. * Return remark in RDAP response when abuse-mailbox validation has failed. * RDAP CORS changes * RDAP invalid syntax exception * A deleted object may be matched in the fulltextsearch index (fixed) 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

1 1

NWI reviews: NWI-3 - Afrinic IRR Homing
by ripedenis＠yahoo.co.uk 01 Oct '20

01 Oct '20

Dear Colleagues This is another 4 year old task about 'encouraging' the transfer of ROUTE(6) objects for Afrinic resources from the RIPE Database to the Afrinic Database.https://www.ripe.net/ripe/mail/archives/db-wg/2016-May/005241.html Is this still an ongoing task? Is there anything more that needs to be done from the RIPE region to complete this Task? Or can we consider this task as completed now? My feeling is that it was superceeded by 'NWI-5 Out of region ROUTE(6) / AUT-NUM objects', which is marked as 'Finished'https://www.ripe.net/ripe/mail/archives/db-wg/2016-May/005245.html As always, your comments are appreciated... cheersdenis co-chair DB-WG

5 7

WHOIS Referrals for transferred number resources
by Ronald F. Guilmette 01 Oct '20

01 Oct '20

I have been writing a modest little software tool recently that seeks to ferret out the identity of the "top level" registrant organization for any given assigned IPv4 address. In this context by "top level" I mean the entity that obtained the relevant IP address assignment directly, either from one of the five regional Internet registries or else from some subserviant national Internet registry. This softare tool always starts by querying whois.iana.org in order to obtain a first-order referral to one of the WHOIS servers belonging to of the five regional Internet registries... usually and often the correct one that actually holds the desired information. Due to various inter-region transfers that have taken place over time however, the first-order referral given by whois.iana.org is often simply wrong, and it is really some other WHOIS server of some other one of the five regional Internet registries that actually contains the information sought. Conveniently, in the case of the ARIN WHOIS server and the APNIC WHOIS server, even in those cases where these respective WHOIS servers do not contain the data sought, e.g. due to some inter-region transfer, these WHOIS servers are at least helpful enough to provide in their responses explict referrals to the proper regional Internet registry WHOIS server where the desired data can in fact be obtained. I would like to request that NCC staff administering the RIPE WHOIS data base likewise incoroprate some such helpful explicit referral text into the WHOIS responses for all number resources where whois.iana.org believes that the resources are under the administration of RIPE, but where in fact the number resources in question have been transferred to some different region. During the early testing of my small software tool I have already encountered a number of such cases. In each of these cases I had to sort out the problem by hand -- I had to ferret out the correct RIR WHOIS server by other means, the responses from whois.ripe.net being of no help whatsoever in this regard, and I then had to program in some "manual overide" work-arounds in my code in order to deal with these cases: 51.79.0.0/16 51.81.0.0/16 51.161.0.0/16 51.162.0.0/17 51.222.0.0/16 151.101.0.0/16 151.139.0.0/16 151.164.0.0/16 151.190.0.0/16 185.105.7.0/24 185.150.189.0/24 185.150.190.0/23 185.171.208.0/22 194.204.192.0/18 I have some faith and hope that the community, the members, and the staff of the RIPE region will wish to be at least as helpful with repect to this WHOIS referral issue as their North American and Asia/Pacific counterparts. Given the expected increases in inter-regional transfers it seems that the time is... well... ripe, to address this small but consequential issue within the data base. Regards, rfg

2 3