- db-wg - mailman.ripe.net

Update: Bogon Route objects (part 2)
by Ronald F. Guilmette 06 Aug '21

06 Aug '21

There remain a number of route objects in the AUTH data base that refer to bogon AS numbers. I would like to suggest that at the very least these should be moved to NONAUTH, but preferably deleted altogether. Use of bogon AS numbers should neither be condoned nor assisted by any RIR. I mean what is the point of having RIRs if people are just going to use whatever numbers they want, willy nilly, and without formal assignments? Also, the overwhelming majority of these route objects do not correspond to active route announcements anyway, and thus deleting them would provably have -no- operational significance. Examples: https://bgp.he.net/AS198738 https://bgp.he.net/AS8295 https://bgp.he.net/AS36879 https://bgp.he.net/AS31419 https://bgp.he.net/AS46723 ... AUTH / IPv4 (80): ----------------- 5.1.112.0/24 198738 2012-05-16 5.1.113.0/24 198738 2012-05-16 5.160.196.0/24 62280 2014-05-10 5.160.197.0/24 62280 2014-05-10 5.160.240.0/24 62280 2014-11-02 5.160.241.0/24 62280 2014-11-02 45.8.92.0/24 397796 2020-06-11 45.8.92.0/24 46723 2020-06-11 45.8.93.0/24 46723 2020-05-26 45.8.94.0/24 397796 2020-05-26 45.8.94.0/24 46723 2020-05-26 45.8.95.0/24 397796 2020-05-26 45.8.95.0/24 46723 2020-05-26 45.14.212.0/22 2209013 2019-05-09 45.95.0.0/24 46723 2020-06-11 45.95.1.0/24 46723 2020-06-11 45.95.2.0/24 46723 2020-06-11 45.95.3.0/24 46723 2020-05-30 77.246.74.0/24 37631 2015-05-29 81.52.165.0/24 36879 2013-10-01 81.52.166.0/24 36879 2013-10-02 81.52.167.0/24 36879 2013-10-02 81.52.168.0/24 36879 2013-10-02 81.52.169.0/24 36879 2013-10-02 82.98.78.0/24 394935 2016-10-26 83.136.64.0/21 8871 2020-12-29 83.216.160.0/19 31419 2011-01-03 83.216.160.0/20 31419 2011-01-03 83.216.160.0/21 31419 2011-01-03 83.216.168.0/21 31419 2011-01-03 83.216.176.0/20 31419 2011-01-03 83.216.176.0/21 31419 2011-01-03 83.216.184.0/21 31419 2011-01-03 86.110.128.0/19 31419 2011-01-03 86.110.128.0/20 31419 2011-01-03 86.110.128.0/21 31419 2011-01-03 86.110.136.0/21 31419 2011-01-03 86.110.144.0/20 31419 2011-01-03 86.110.144.0/21 31419 2011-01-03 86.110.152.0/21 31419 2011-01-03 91.102.168.0/21 8295 2006-11-17 91.102.168.0/24 8295 2020-02-25 91.102.169.0/24 8295 2020-02-25 91.102.170.0/24 8295 2020-02-25 91.102.171.0/24 8295 2020-02-25 91.102.172.0/24 8295 2020-02-25 91.102.173.0/24 8295 2020-02-25 91.102.174.0/24 8295 2020-02-25 91.102.175.0/24 8295 2020-02-25 91.107.84.0/24 202532 2019-07-08 91.220.83.0/24 46414 2010-10-28 93.92.104.0/22 1975505 2018-12-12 141.98.12.0/24 208469 2020-03-25 158.255.59.0/24 203655 2015-11-27 185.18.88.0/23 196803 2019-09-18 185.48.220.0/22 199724 2014-03-05 185.62.220.0/22 1975505 2018-12-12 185.62.221.0/24 1975505 2018-12-12 185.106.44.0/24 200968 2015-06-29 185.148.136.0/22 198738 2019-07-08 185.148.138.0/23 198738 2016-09-12 185.164.160.0/22 14076 2016-11-02 185.194.4.0/22 205740 2020-04-05 185.200.32.0/22 33431 2017-06-13 185.225.136.0/22 33431 2017-10-13 185.244.144.0/22 204634 2018-02-02 185.250.112.0/22 20180320 2019-07-25 188.92.121.0/24 40178 2020-04-01 193.33.110.0/23 42796 2012-06-28 193.110.94.0/24 16712 2021-03-18 193.135.119.0/24 46723 2020-05-30 193.201.204.0/24 14880 2007-11-23 193.201.205.0/24 14880 2007-11-23 194.99.204.0/22 36895 2006-05-04 194.165.87.0/24 21389 2012-12-10 194.201.253.0/24 25568 2014-04-08 212.68.170.0/23 20873 2013-12-20 213.156.70.0/24 20873 2005-09-06 213.156.71.0/24 20873 2005-09-06 213.228.244.0/24 31453 2005-01-04 AUTH / IPv6 (19): ----------------- 2001:678:d44:100::/64 999998 2021-02-13 2001:678:d44:200::/64 999999 2021-02-13 2a00:9700:1::/48 47497 2017-01-14 2a00:e640::/32 198738 2012-04-26 2a01:9ba0::/32 199724 2014-03-05 2a03:1960::/32 201400 2017-07-24 2a03:9c00:f::/48 210323 2019-12-18 2a03:b600::/29 46723 2019-03-14 2a07:7e40:1::/48 34676 2020-07-28 2a09:be40:3620::/48 208577 2019-08-15 2a09:f700::/29 46723 2019-03-06 2a0a:7740::/48 46076 2020-10-30 2a0b:1040::/29 31005 2017-06-04 2a0b:3e00::/32 14076 2016-11-02 2a0b:4340:a0:3ec::/64 139734 2020-03-18 2a0d:1a40:faf::/48 138987 2020-06-13 2a0e:aa07:f030::/44 132352 2019-04-26 2a0e:b107:680::/48 140540 2020-04-02 2a10:cc46:100::/44 655312 2021-06-03

3 4

Update: Bogon Route objects
by Ronald F. Guilmette 05 Aug '21

05 Aug '21

It would appear that we may have acquired a few new bogon route objects within 41/8 which I believe is 100% AFRINIC space. I can only guess that this is most likely due to some fresh reclamations recently performed by AFRINIC. Note that I am still including the questionable routes relating to the 192.31.196.0/24 and 192.88.99.0/24 blocks which have been discussed here previously, as well as some of the IPv6 routes that some people have also suggested should fall into the "questionable" category. (If I could get some further clarity on RIPE NCC's official position on the questionable bits, that would be helpful.) NONAUTH / IPv4: --------------- 41.217.128.0/19 37034 2018-09-04 41.217.144.0/20 37034 2018-09-04 41.217.144.0/21 37034 2018-09-04 192.31.196.0/24 112 2018-09-04 192.88.99.0/24 1101 2018-09-04 192.88.99.0/24 12816 2018-09-04 192.88.99.0/24 12871 2018-09-04 192.88.99.0/24 15598 2021-02-25 192.88.99.0/24 1741 2018-09-04 192.88.99.0/24 1835 2018-09-04 192.88.99.0/24 20640 2018-09-04 192.88.99.0/24 21416 2018-09-04 192.88.99.0/24 25192 2018-09-04 192.88.99.0/24 25308 2018-09-04 192.88.99.0/24 2847 2018-09-04 192.88.99.0/24 29076 2018-09-04 192.88.99.0/24 29259 2018-09-04 192.88.99.0/24 29432 2018-09-04 192.88.99.0/24 29632 2018-09-04 192.88.99.0/24 3243 2018-09-04 192.88.99.0/24 3344 2018-09-04 192.88.99.0/24 35244 2018-09-04 192.88.99.0/24 39326 2018-09-04 192.88.99.0/24 43097 2018-09-04 192.88.99.0/24 50113 2018-09-04 192.88.99.0/24 5408 2018-09-04 192.88.99.0/24 5413 2018-09-04 192.88.99.0/24 680 2018-09-04 192.88.99.0/24 8473 2018-09-04 192.88.99.0/24 8903 2020-11-18 NONAUTH / IPv6: --------------- 2001::/32 1101 2018-09-04 2001::/32 12816 2018-09-04 2001::/32 12871 2018-09-04 2001::/32 1741 2018-09-04 2001::/32 21155 2018-09-04 2001::/32 25192 2018-09-04 2001::/32 25308 2018-09-04 2001::/32 25525 2018-09-04 2001::/32 29259 2018-09-04 2001::/32 29432 2018-09-04 2001::/32 44980 2018-09-04 2001::/32 57801 2018-09-04 2001:4:112::/48 112 2018-09-04 2002::/16 1101 2018-09-04 2002::/16 12871 2018-09-04 2002::/16 15598 2021-02-23 2002::/16 1741 2018-09-04 2002::/16 1835 2018-09-04 2002::/16 20640 2018-09-04 2002::/16 21416 2018-09-04 2002::/16 25192 2018-09-04 2002::/16 25308 2018-09-04 2002::/16 2847 2018-09-04 2002::/16 29259 2018-09-04 2002::/16 29432 2018-09-04 2002::/16 29632 2018-09-04 2002::/16 3344 2018-09-04 2002::/16 35244 2018-09-04 2002::/16 39326 2018-09-04 2002::/16 43097 2018-09-04 2002::/16 5413 2018-09-04 2002::/16 559 2018-09-04 2002::/16 680 2018-09-04 2002::/16 8473 2018-09-04 2002::/16 8903 2018-09-04 2011:4188::/48 12880 2018-09-04

2 1

Bogon cleanup -- Current anomalies
by Ronald F. Guilmette 24 Jul '21

24 Jul '21

According to information given to me by Edward Shryane <eshryane(a)ripe.net>, the cleanup of bogon route objects which made reference to bogon IP address space should have been completed the night before last. My latest analysis suggests that a few such route objects escaped the net and are still present within the NONAUTH data base. These route objects are summarized below. I'd appreciate it if others would take a look at these and tell me if they think that these route objects should or should not be present within the data base. Note that both batches of bogon routes given below are really rather curious due to the fact that nearly all of the routes have the exact same last-modified date (2018-09-04) and a great many of them refer either to the 192.88.99.0/24 IPv4 block, which is apparently reserved by RFC 3068, or to some IPv6 block which is *not* clearly related to RFC 3068. I am frankly not sure what to make of any of these, but I do suspect that they are all invalid, because no RIR has assigned any of the relevant IP space to any resource member. NONAUTH / IPv4 routes (36): --------------------------- 41.217.128.0/19 37034 2018-09-04 41.217.144.0/20 37034 2018-09-04 41.217.144.0/21 37034 2018-09-04 41.242.84.0/22 37609 2018-09-04 170.56.0.0/16 15854 2018-09-04 170.56.0.0/16 702 2018-09-04 192.31.196.0/24 112 2018-09-04 192.88.99.0/24 1741 2018-09-04 192.88.99.0/24 29259 2018-09-04 192.88.99.0/24 2847 2018-09-04 192.88.99.0/24 12816 2018-09-04 192.88.99.0/24 3344 2018-09-04 192.88.99.0/24 20640 2018-09-04 192.88.99.0/24 5408 2018-09-04 192.88.99.0/24 1835 2018-09-04 192.88.99.0/24 8473 2018-09-04 192.88.99.0/24 15598 2021-02-25 192.88.99.0/24 1101 2018-09-04 192.88.99.0/24 12871 2018-09-04 192.88.99.0/24 680 2018-09-04 192.88.99.0/24 25192 2018-09-04 192.88.99.0/24 35244 2018-09-04 192.88.99.0/24 39326 2018-09-04 192.88.99.0/24 5413 2018-09-04 192.88.99.0/24 25308 2018-09-04 192.88.99.0/24 3243 2018-09-04 192.88.99.0/24 29076 2018-09-04 192.88.99.0/24 29632 2018-09-04 192.88.99.0/24 8903 2020-11-18 192.88.99.0/24 21416 2018-09-04 192.88.99.0/24 43097 2018-09-04 192.88.99.0/24 29432 2018-09-04 192.88.99.0/24 50113 2018-09-04 192.107.242.0/24 394784 2018-09-04 204.144.127.0/24 40142 2018-09-04 205.166.145.0/24 394784 2018-09-04 NONAUTH / IPv6 routes (37): --------------------------- 2001::/32 1101 2018-09-04 2001::/32 12816 2018-09-04 2001::/32 12871 2018-09-04 2001::/32 1741 2018-09-04 2001::/32 21155 2018-09-04 2001::/32 25192 2018-09-04 2001::/32 25308 2018-09-04 2001::/32 25525 2018-09-04 2001::/32 29259 2018-09-04 2001::/32 29432 2018-09-04 2001::/32 44980 2018-09-04 2001::/32 57801 2018-09-04 2001:4:112::/48 112 2018-09-04 2002::/16 1101 2018-09-04 2002::/16 12871 2018-09-04 2002::/16 15598 2021-02-23 2002::/16 1741 2018-09-04 2002::/16 1835 2018-09-04 2002::/16 20640 2018-09-04 2002::/16 21416 2018-09-04 2002::/16 25192 2018-09-04 2002::/16 25308 2018-09-04 2002::/16 2847 2018-09-04 2002::/16 29259 2018-09-04 2002::/16 29432 2018-09-04 2002::/16 29632 2018-09-04 2002::/16 3344 2018-09-04 2002::/16 35244 2018-09-04 2002::/16 39326 2018-09-04 2002::/16 43097 2018-09-04 2002::/16 5413 2018-09-04 2002::/16 559 2018-09-04 2002::/16 680 2018-09-04 2002::/16 8473 2018-09-04 2002::/16 8903 2018-09-04 2011:4188::/48 12880 2018-09-04 2c0f:f260::/32 36924 2018-09-04

7 16

consensus on AS23456
by denis walker 13 Jul '21

13 Jul '21

Colleagues Whilst part of the discussion continues, there does seem to be a consensus on adding AS23456 to the reserved list maintained by the RIPE NCC. This would prevent anyone creating a ROUTE(6) object with AS23456 as the origin. The chairs also recognise the consensus to not delete or modify any set objects that reference AS23456. This is in line with past views not to purge set objects when an AUT-NUM object is deleted for any reason. The chairs therefore ask the RIPE NCC to add AS23456 to the RIPE Database reserved list. Regards William & denis co-chairs DB-WG

3 2

Re: [db-wg] Further cleanup (was: RIPE NONAUTH route(6) objects
by Ronald F. Guilmette 13 Jul '21

13 Jul '21

Job Snijders <job(a)sobornost.net> wrote: >Should the database server software impose brittle restrictions >on that field? No, not worth the headache. I never suggested any changes to the data base software. I have merely suggested that *existing* route objects that make reference to bogon ASNs should be deleted from the data base, just as is already and currently being done in the case of those route objects that make reference to bogon IP space. The overwhelming majority of these "bogon-ASN" route objects are quite obviously leftovers that just never got cleaned up... some having languished unattended in the data base for as much as 20 years or more (and even some of the people who put those there originally are no doubt dead by now). We are in agreement in our (idealistic?) hops that someday RPKI will make all of these issues moot. By for today, there is no good reason not to remove the decades long accumulation of rust. It isn't doing anybody any good, and I fear it is an active enticement to mischief makers, of which the Internet has an over-supply these days. Regards, rfg

4 7

RIPE NONAUTH route(6) objects using unregistered space cleanup - deployment *today*
by Edward Shryane 08 Jul '21

08 Jul '21

Dear colleagues, The implementation of the cleanup of RIPE NONAUTH route(6) objects using unregistered space is now complete, we plan to deploy to production *today*. This means that the cleanup job will run for the first time tonight. * Each night, all RIPE NONAUTH route(6) objects with an unregistered prefix ("available" or "reserved" in delegated stats) are selected. * If a prefix remains unregistered for 1 week, notify the maintainers of any related route(6) objects. * The maintainer can ask to make an exception, not to delete a route(6) object. * Otherwise, after a further 2 weeks, delete the route(6) objects. See the solution definition for more details: https://www.ripe.net/ripe/mail/archives/db-wg/2021-March/006876.html Note for now, the AS origin status is *not* considered. Please discuss further whether this should be included. If you have any feedback, please let us know. Regards Ed Shryane RIPE NCC

9 31

Whois Release 1.101
by Edward Shryane 01 Jul '21

01 Jul '21

Dear Working Group, RIPE Database release 1.101 has been deployed to the Release Candidate environment. We plan to deploy to production on Thursday 1st July. This release includes the following main changes: * Switch RIPE database to UTC timezone (all timestamps will be in UTC and all timestamps specify the 'Z' timezone) * Display an error on NRTM if client is blocked by ACL limit (#812) * Added rewrite rules to embedded Jetty (#801) * RDAP nameserver queries always return Not Implemented (#811) * Updated dependencies *Additionally* some operational changes will also be made to the production environment on 1st July: * Remove support for TLS versions 1.0 and 1.1 on HTTPS connections * The IETF has formally deprecated these TLS versions, now only versions 1.2 and 1.3 are recommended. * Remove insecure TLS cipher algorithms * TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA * TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA * TLS_DHE_RSA_WITH_SEED_CBC_SHA * TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA * TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA * Remove HTTP redirects for whois.ripe.net and www.db.ripe.net * HTTP requests to these hosts will no longer redirect to https://apps.db.ripe.net but will return 400 Bad Request. * Remove HTTP redirects for the legacy Whois REST API * The legacy Whois REST API was retired in 2015, a temporary redirect to https://rest.db.ripe.net will be removed. * HTTP requests to the legacy API at http://apps.db.ripe.net/whois/lookup/ripe will return 400 Bad Request. Please check your Whois client in case you are affected by these changes. 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

Removie ALL bogus route objects from BOTH data bases
by Ronald F. Guilmette 21 Jun '21

21 Jun '21

I guess I'll try this again, since I don't recall seeing either any ascent nor any pushback the last time I tried to raise this point here. Al long as those bogus route objects that refer to bogon IP address space are being removed from the data, why not also remove all of the equally bogus route objects that refer to bogon AS numbers? I hope that I'm not actually the only one who sees the wisdom in cleaning up the whole mess that currently exists in the RIPE data bases. There are, at present, on the order of about 80 or so bogus route objects in the "regular" data base that refer to bogon AS numbers, and there are, give or take, about 1,500 of such bogus route objects currently within the (separate) RIPE-NONAUTH data base. Is anyone passionately in favor of keeping all of this useless and potentially fraudlent or misleading garbage in the data base? If not, then why not clear it all out? I mean seriously, the RIRs data bases are *supposed* to be the definitive guides to who has what and who may use what. And yet RIPE is, in effect, tacitly -appproving- of the use of bogon AS numbers. So I need to ask: Why? Regards, rfg

1 0

Removal of bogon route objects
by Ronald F. Guilmette 15 Jun '21

15 Jun '21

Friends, As previously discussed, the decision was made awhile back to remove from the data base all RIPE-NONAUTH route objects which refer to currently unallocated IP space: https://www.ripe.net/ripe/mail/archives/db-wg/2021-May/006952.html In recent days I stumbled upon one such object that was still present in the data base. Upon seeing that object, I necessarily assumed that it was most likely not a "one off", and that it probably had siblings. In the spirit of trying to help out, and after a fair bit of fooling around on my part, I managed to concoct a rather simple method for finding all such bogon route objects that remain in the data base, and I wrote a small Perl script to do that exact thing. A copy of the script may be obtained here, for anyone who may be interested: https://pastebin.com/raw/LsvZ05tX Notes: *) The script assumes the presence of two external programs and their presence on the user's current $PATH, i.e. the widely used wget progarm, and also John Levine's version of a thing called grepcidr, sources for which may be obtained here: https://github.com/jrlevine/grepcidr3 *) The initial line of the script may have to be adjusted depending on the location, in the filesystem, of your local Perl interpreter. *) The script computes its results based upon the following two input data files, both of which are automagically fetched by the script using wget: https://www.nro.net/wp-content/uploads/delegated-stats/nro-extended-stats ftp://ftp.ripe.net/ripe/dbase/ripe-nonauth.db.gz (It is my understanding that each of these is updated on a daily basis.) *) The script DOES NOT verify that the entirety of any given RIPE-NONAUTH route object in fact refers to bogon space. Rather the script only checks to see whether or not the first IPv4 address of each current RIPE-NONAUTH route object does or does not refer to current bogon space. If it does, then the entire IPv4 CIDR of the route object is printed to stdout. *) Assuming that the script is installed as "ripebogonroutes" and in one's path, it may be invoked simply as: ripebogonroutes > bogon-route-cidrs *) At present there are 55,964 RIPE-NONAUTH objects in the data base. Of these, the first address of 857 of them refers to current bogon space. It is my fervent hope that the corresponding RIPE-NONAUTH route objects will be removed from the data base as soon as reasonably practical. Regards, rfg

6 18

RIPE-NONAUTH route object anomalies
by Ronald F. Guilmette 14 Jun '21

14 Jun '21

It appears that, by and large, the route objects currently present within the ripe-nonauth.db.gz file refer either to bogons (which I've already provided a list of) or else they refer to out-of-region IP address blocks. The latter group seems at least explainable. The former group I am hoping will disappear from the data base soon. Checking now however I find there are a very small number of anomalous route objects within the latest edition of the ripe-nonauth.db.gz file, i.e. ones that refer to in-region IP blocks: 192.124.252.0/22 192.70.0.0/17 192.76.32.0/21 192.108.160.0/20 I'm not sure how these should be made to go away, but I wish they would. They offend my personal sense of fastidiousness, and I don't like unexplainable mysteries. Note that the RIPE-NONAUTH route object 192.76.32.0/21 appears to have some counterpart route objects for sub-blocks of that /21 and these sub-blocks route objects are *not* marked as RIPE-NONAUTH, suggesting that there is no compelling reason for the 192.76.32.0/21 route object to be marked as RIPE-NONAUTH. The same sort of syndrome appears to apply also in the case of the 192.124.252.0/22 RIPE-NONAUTH route object, i.e. in this case also there appear to be valid non-RIPE-NONAUTH route objects in the data base for sub-blocks of 192.124.252.0/22, which begs the question: Why is the 192.124.252.0/22 markes as RIPE-NONAUTH? Regards, rfg

3 5