[6bone] ip6.arpa ...

[Robert Kiessling]

Bill Manning <bmanning@ISI.EDU> writes:

> % Bill Manning <bmanning@ISI.EDU> writes:
> % 
> % > 	This is fatally flawed, as some folks will get one set of 
> % > 	answers while others will get distinctly different answers
> % > 	to the same questions, based on the age of the resolver that
> % > 	is in their endsystems.  
> % 
> % You cannot avoid that. Having the same delegations on
> % sub-e.f.f.3.ip6.arpa level does not guarantee that the eventual
> % answers are the same, since the nameserver to which it's finally
> % delgated can have different zones for ....ip6.arpa and ...ip6.int. And
> % quite often they would.
> 
> 	actually, you can. using -ONE- zone file with two $ORIGIN
> 	statements will ensure that e.f.f.3.ip6.arpa is identical
> 	to e.f.f.3.ip6.int.

You know this is not true. This only guarantees that one level of
delgation is exactly the same. For all practical purposes the RIR
proposal does the same.

In no way does this ensure that the answer to a reverse query is the
same for .ip6.arpa and .ip6.int.

We are still waiting for your example about a substantially different
answer which you claim results from the RIR proposal.

And what you mean by

|        And the simplist,               
|	fastest way to get e.f.f.3.ip6.arpa. out the door is to have
|	the IANA delegate that point to -exactly- the same server 
|	suite that hosts the e.f.f.3.ip6.int delegation

given the fact that ip6.arpa is delegated to the RIRs, and
consequently it is the RIRs who would need to make that delegation,
not IANA.

Robert