Re: [Sidrops] inter-RIR overclaiming - discrepancy?

[Job Snijders <[e-mail]>]

Dear colleagues,

A CA subordinate to APNIC is claiming authority for 2001:7fa:11::/48
https://console.rpki-client.org/rpki.apnic.net/repository/B322A5F41D6611E2A3F27F7C72FD1FF2/UtaA4EXc6ZB4ng13cmF8YMNu0Y4.cer.html

However, according to IANA this space is managed by RIPE NCC:

	$ curl -s https://www.iana.org/assignments/ipv6-unicast-address-assignments/ipv6-unicast-address-assignments.txt | grepcidr3 -D 2001:7fa:11::/128
	 defined by the prefix 2000::/3. [RFC3513] was later obsoleted by [RFC4291]. All address
	   2001:0600::/23 RIPE NCC    1999-07-01 whois.ripe.net https://rdap.db.ripe.net/      ALLOCATED

But, RDAP queries for 2001:7fa::/32 points to APNIC:

	$ rdap --output-format json 2001:7fa::/32 | jq '.notices[0]'
	{
	  "title": "Source",
	  "description": [
	    "Objects returned came from source",
	    "APNIC"
	  ]
	}
	feather$ rdap --output-format json 2001:7fa::/32 | jq '.name'
	"APNIC-AP-IX-ASSIGNMENT"

The RIPE NCC 'online intermediate CA' appears to consciously omit
authority for this block (by poking a hole), see:
http://console.rpki-client.org/rpki.ripe.net/repository/aca/KpSo3VVK5wEHIJnHC2QHVV3d5mk.cer.html
	IP: 2001:600:: -- 2001:7f9:ffff:ffff:ffff:ffff:ffff:ffff
	IP: 2001:7fb:: -- 2001:bff:ffff:ffff:ffff:ffff:ffff:ffff

OK good - at the operational level RIPE NCC does not claim authority for
2001:7fa::/32, and APNIC does assume authority; but what gives at the
IANA level? Where is it documented that APNIC manages 2001:7fa::/32?

Kind regards,

Job