On May 14, 2007, at 10:20, Jørgen Hovland wrote:
I hope this does not become mandatory, only optionally or discontinue it. A very few amount of LIRs would have to send a zonefile in the size of (2^96 ) * 32 * 4 * 20 bytes to ns.ripe.net if it becomes mandatory.
Let's step back. Slave service for reverse zones was something the NCC has been doing since the dawn of time. In the early days, connectivity was sometimes erratic, bandwidth was limited, lame delegations were common and DNS skills were worse than they are today. It made sense to have a robust and stable DNS platform and the NCC was in the position to provide that service. That was then. But this is now. The environment has changed. And there's less reliance on reverse DNS lookups these days too, even more so in an IPv6 world. So the questions for the WG should be IMO: * Is there value in having the NCC provide DNS service for big/ important reverse zones? * If the answer to the above question is yes, under what conditions? ie What do we mean by big or important? * If the answer is still yes, should this service be compulsory or optional? And under what conditions would optional use become compulsory and vice versa? * If the answer to the orginal question is no, what, if anything, does the NCC do about things like lame delegations for reverse zones and the operational problems these cause the NCC?