On Mon, Jul 15, 2019 at 11:37 PM Job Snijders <j...@ntt.net> wrote: > Even if inter-RIR transfers were permitted, ARIN would still > operationally be responsible for all delegations under the > "0.6.2.ip6.arpa." zone. So, no issue there. [snip]
No.... that is exactly one potential issue. An entity wishing to move their networks around ought to bear costs of their moves; the RIR such as ARIN should not be subsidizing an entity's choice to move out of region and continue to keep everything nice and convenient for that resource holder by incurring extra costs against the fees paid by other still-in-region members to help facilitate the operations of some small number of 'wanting to move out' resource holders; This is not in the interests of the regional community whom its ARIN's mission to serve to be in a position of continuing to provide a Reverse DNS service to the entity that moved out after they are no longer an ARIN customer, And "fragmenting" in this manner is exactly what this forces upon ARIN. The kind of Reverse DNS Zone that is simplest for RIRs to have software, systems, and process to manage -- is one where all the NS delegations are predictable and match up exactly with database entries created by customers linked to a direct allocation or assignment. And the requirement to maintain additional, extra nameserver delegations for "transferred blocks" means designing, developing, or maintaining, systems, algorithms, and management processes which involve more ARIN staff time being used to operate, and a greater minimum complexity than the simplest form (which would meet the simpler requirements of each delegation maintained by an ARIN customer). Aside from the administrative burden that ARIN now would have to maintain an entirely additional set of delegations and database entries which are for out-of-region usage on transferred out V6 space, and have processes and people to update these entries from time to time: when the end user's downstream nameserver addresses change. To keep such a transfer in effect and reverse DNS working properly: ARIN (and therefore other ARIN members) would effectively have to also bear an ongoing cost on behalf of the foreign registrant in perpetuity without compensation for the services, because that organization will be cancelling their relationship with ARIN and/or no longer be paying any maintenance fee for that block of addresses. Meanwhile.... ARIN continues to have to maintain DNS servers with computational and bandwidth resources allocated to answering queries that come for the reverse DNS range of THAT block transferred out and maintaining a set of nameserver delegations in the reverse DNS zone for the "transferred out" address block in order to do so. And the VOLUME (total number of reverse DNS queries per day) per block varies with the usage of that block, size, etc, so it is non-predictable. ARIN likely needs that entity as a customer while delegating reverse DNS to them, in order to be be able to charge maintenance fees to compensate ARIN for costs of providing the service of answering the reverse DNS Nameserver queries. -- -JH _______________________________________________ ARIN-PPML You are receiving this message because you are subscribed to the ARIN Public Policy Mailing List (ARIN-PPML@arin.net). Unsubscribe or manage your mailing list subscription at: https://lists.arin.net/mailman/listinfo/arin-ppml Please contact i...@arin.net if you experience any issues.