At the moment ripe.e164.arpa is needed they will made a fix for it, making a fix before that moment isn't needed if you ask me. With kind regards, Met vriendelijke groet, Mark Scholten Stream Service Web: http://www.streamservice.nl/ E-mail: mark@streamservice.nl NOC: http://www.mynoc.eu/ NOC e-mail: noc@streamservice.nl Tel.: +31 (0)642 40 86 02 KVK: 08141074 BTW: NL104278274B01 ----- Original Message ----- From: "Jim Reid" <jim@rfc1035.com> To: "Anand Buddhdev" <anandb@ripe.net> Cc: <enum-wg@ripe.net> Sent: Thursday, January 17, 2008 4:55 PM Subject: Re: [enum-wg] Name "ripe" in the e164.arpa zone On Jan 17, 2008, at 14:56, Anand Buddhdev wrote:
The tools that transfer these zonelets rely on this extra piece of information in the TXT record for consistency checks. Similarly, AfriNIC, ARIN and APNIC also generate zones for their /8 allocations with records named "afrinic", "arin" and "apnic".
The e164.arpa zone does not really need this "ripe" record in it, since it is not shared among the registries in any way. However, because the e164.arpa zone is generated automatically from the RIPE Database by the same tools, it automatically receives this extra name. Currently, there is no way to stop the zone receiving this extra entry. But it has no negative effect on the zone or on ENUM operations.
Hmmm. This smells like a bug. Why are the DNS provisioning tools for e164.arpa generating data that isn't needed and inserting that data into the DNS? I wonder what will happen if the ITU one day decides that "ripe.e164.arpa" should be delegated to someone....