Hi guys What you are suggesting here is quite a significant change to the way the RIPE Database (and maybe IANA) works. The block 82.156/16 is not (or no longer) in the RIPE Database. There are place holder objects in the RIPE Database for non RIPE address space. All these place holder objects contain the same generic information. They state this is not RIPE address space and include links to all the other whois databases. So strictly speaking it does not refer 'back' to IANA and therefore it is not a loop. The person making the query will find the object in one of the listed whois databases. If you want the RIPE Database to provide a referral service then you are asking for the RIPE Database to become a global whois service rather than using the RIPE GRS. If this block was transferred from RIPE to APNIC then it is easy to update the placeholder at that moment to make a referral to APNIC. But what if the object is transferred again to another region? The RIPE Database would have to track all transfers, otherwise the referral may become stale information. The RIPE NCC effectively already provides this referral service with RIPE GRS. It solves this problem 100% for all RIR administered address space. Why do we need the NRO to start discussions with IANA on how to fix a problem that already has a fully implemented and working solution?
cheers denis co-chair DB-WG On Thu, 16 Sept 2021 at 00:59, Leo Vegoda via db-wg <[email protected]> wrote: > > On Wed, Sep 15, 2021 at 10:09 AM Gert Doering <[email protected]> wrote: > > 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. > > +1 > > > 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. > > +1 >
