Hi I would say forget IANA, forget RDAP and if you don't know which region a resource may be in use the RIPE GRS service. The mirrors are updated daily so you will get an accurate answer for the resource wherever it is today. cheers denis co-chair DB-WG On Wed, 15 Sept 2021 at 19:09, Gert Doering via db-wg <db-wg@ripe.net> wrote:
Hi,
On Wed, Sep 15, 2021 at 08:49:27AM -0700, Leo Vegoda via db-wg wrote:
The CSC focuses on naming and not numbering issues. That said, rather than making a complaint, it might be more helpful to decide what the desired future state is and then ask the RIRs to work on that with the IANA team. In general, they'll make changes to the way they deliver services to the numbering community when the NRO makes a request.
My take on this is: referrals MUST NOT loop.
That is, if IANA points me to the RIPE NCC, and the network got moved *elsewhere*, the RIPE NCC should have a referral to "elsewhere", and not point "back to IANA".
Ideally, IANA should point to the final RIR right away.
(I see the "use RDAP, not whois" comment as sort of confusing - if the data source is good, the query method should not matter, and if the data source is bad, it definitely won't matter. If RDAP gives a proper referral and whois gives a bad one, the server needs to be fixed - but that's not a *protocol* issue)
Gert Doering -- LIR contact and whois user -- have you enabled IPv6 on something today...?
SpaceNet AG Vorstand: Sebastian v. Bomhard, Michael Emmer Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279