[db-wg] running in whios-circles...?

Hi,

so on my self-hosted MTA I got an email [unsure about good intentions,
thus checking origin] from 82.156.114.62

Whois directed to ripe, ripe said it's iana, iana said it's ripe

[  BGP said ..... 4134 23724 45090  ]

and .....

there's a route object in APNIC:
route:          82.156.0.0/15
origin:         AS45090
descr:          Tencent Cloud Computing (Beijing) Co., Ltd
                309 West Zone, 3F. 49 Zhichun Road. Haidian District.
mnt-by:         MAINT-TENCENT-CN
last-modified:  2020-02-24T07:34:42Z
source:         APNIC

and also "inetnum:        82.156.0.0 - 82.157.255.255" (in APNIC)

So, I tend to believe that I'm on the wrong list here, because my
question turns out to be:
    can I trust whois.iana.org ?

It seems to tell me something different from what APNIC is saying.

PS:
a prefix containing IP in question is not seen in
https://www.iana.org/assignments/ipv4-recovered-address-space/ipv4-recovered-address-space.xhtml


am i right to be confused by the iana answer?
who should get 'encouraged' to change something?

Thanks,
Frank



[frank at fisi ~]$ whoisiana 82.156.114.62
[Querying whois.iana.org]
[whois.iana.org]
% IANA WHOIS server
% for more information on IANA, visit http://www.iana.org
% This query returned 1 object

refer:        whois.ripe.net

inetnum:      82.0.0.0 - 82.255.255.255
organisation: RIPE NCC
status:       ALLOCATED

whois:        whois.ripe.net

changed:      2002-11
source:       IANA

[frank at fisi ~]$ whois 82.156.114.62
[Querying whois.ripe.net]
[whois.ripe.net]
% 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

% Note: this output has been filtered.
%       To receive output for a database update, use the "-B" flag.

% Information related to '82.156.0.0 - 82.157.255.255'

% No abuse contact registered for 82.156.0.0 - 82.157.255.255

inetnum:        82.156.0.0 - 82.157.255.255
netname:        NON-RIPE-NCC-MANAGED-ADDRESS-BLOCK
descr:          IPv4 address block not managed by the RIPE NCC
remarks:        ------------------------------------------------------
remarks:
remarks:        For registration information,
remarks:        you can consult the following sources:
remarks:
remarks:        IANA
remarks:        http://www.iana.org/assignments/ipv4-address-space
remarks:        http://www.iana.org/assignments/iana-ipv4-special-registry
remarks:        http://www.iana.org/assignments/ipv4-recovered-address-space
remarks:
remarks:        AFRINIC (Africa)
remarks:        http://www.afrinic.net/ whois.afrinic.net
remarks:
remarks:        APNIC (Asia Pacific)
remarks:        http://www.apnic.net/ whois.apnic.net
remarks:
remarks:        ARIN (Northern America)
remarks:        http://www.arin.net/ whois.arin.net
remarks:
remarks:        LACNIC (Latin America and the Carribean)
remarks:        http://www.lacnic.net/ whois.lacnic.net
remarks:
remarks:        ------------------------------------------------------
country:        EU # Country is really world wide
admin-c:        IANA1-RIPE
tech-c:         IANA1-RIPE
status:         ALLOCATED UNSPECIFIED
mnt-by:         RIPE-NCC-HM-MNT
created:        2019-01-07T10:49:20Z
last-modified:  2019-01-07T10:49:20Z
source:         RIPE

role:           Internet Assigned Numbers Authority
address:        see http://www.iana.org.
admin-c:        IANA1-RIPE
tech-c:         IANA1-RIPE
nic-hdl:        IANA1-RIPE
remarks:        For more information on IANA services
remarks:        go to IANA web site at http://www.iana.org.
mnt-by:         RIPE-NCC-MNT
created:        1970-01-01T00:00:00Z
last-modified:  2001-09-22T09:31:27Z
source:         RIPE # Filtered

% This query was served by the RIPE Database Query Service version 1.101
(ANGUS)


[frank at fisi ~]$