Hi, Brett Carr schrieb:
As mentioned in my presentation at RIPE 54 last week we have become aware that there is an inconsistency between ipv4 and ipv6 with regard to obtaining reverse delegation.
The reverse delegation procedure listed at http://www.ripe.net/rs/reverse/reverse_howto.html has the following listed: [...] We think it would be a good idea to address this inconsistency, this could be done in several ways including but not limted to:
Make ns.ripe.net mandatory on ipv4 and ipv6 delegations Make ns.ripe.net optional on ipv4 and ipv6 delegations Discontinue the secondary service on ns.ripe.net for new delegations.
Our suggestion and preference would be to make ns.ripe.net optional on both ipv4 and ipv6 delegations.
We would welcome and encourage input from the dns community on this subject.
i support the suggestion to make it optional. Discontinuation makes no sense - i don't really think this service causes a high workload or costs too much money. Making it mandatory for ALL allocations(?) would eventually cause operational problems for the LIR/customer in some cases, not really worth the effort. ==> Make it optional for all delegations, IPv4&IPv6 as suggested if you feel any needs to change the current situation (which i don't actually consider bad either). As a service, i would like to use RIPE as 2ndary in some cases. -- ======================================================================== = Sascha Lenz SLZ-RIPE slz@baycix.de = = Network Operations = = BayCIX GmbH, Landshut * PGP public Key on demand * = ========================================================================