|
|
 |
RE: [enum-wg] Name "ripe" in the e164.arpa zone
-
To: "Jim Reid" jim@localhost, "Anand Buddhdev" anandb@localhost
-
From: "brett" brett@localhost
-
Date: Thu, 17 Jan 2008 19:50:55 +0100
> -----Original Message-----
> From: enum-wg-admin@localhost [ ] On Behalf
Of
> Jim Reid
> Sent: Thursday, January 17, 2008 3:55 PM
> To: Anand Buddhdev
> 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?
Hmmm don't think I would define it as a bug as it is I believe intended
behaviour.
> I wonder what will happen if the ITU one day decides
> that "ripe.e164.arpa" should be delegated to someone....
Don't think this would cause a problem would it, as this is only a TXT
record I think it could quite happily co-exist with some NS records.
I do take your point though Jim and I'm sure if the community members
feel strongly enough the NCC would consider looking into how difficult
it would be to remove this record from the e164.arpa zone
Brett (Speaking as a NON NCC person)
|
|
 |
 |