[6bone] ip6.arpa ...

[Bill Manning]

% Hallo.
% 
% I have seen that the ip6.arpa delegation is now in place, but the
% e.f.f.3.ip6.arpa is not. Following a statement I picked up at RIPE44
% in Amsterdam a month ago, I believe that the RIRs are held to keep
% the nameservers in their control.
% 
% May I suggest opening up dot.ep.net for slave transfers from ns.ripe.net
% so that RIPE may copy the zone nightly, rewrite all the ip6.int into ip6.arpa
% and create a duplicate tree for e.f.f.3.ip6.arpa ?
% 
% groet,
% Pim
% -- 

	several issues raised at the last RIPE mtg w/ Andrei are:
	) zone consistancy.  the delegations in 3ffe should be
	  identical, regardless of the anchor point. the RIR
	  proposal is to have the data -differ- between the 
	  two anchor points.  The proper way forward would be
	  to use $ORIGIN to anchor the same zone in two places.
	  The reason you need to do this is that there is nearly
	  a decade of deployed resolvers that will only look in
	  ip6.int for data and it will take a decade or more to
	  have those resolvers expire.
	) the zone transfers should be protected by TSIG. I have
	  not been able to successfully work with RIPE on getting
	  TSIGS in place.  I have been able to do so with both APNIC
	  and ARIN. I've not had dealings w/ LATNIC yet.
	) IPv6 transport capability. ARIN does not have v6 capability.
	  RIPE has only sporadically supported v6 although I hope 
	  the current efforts will be stable.  APNIC has had stable
	  v6 capability for several years now.  LATNIC has v6 experise
	  but I've not been able to get closure on their operational
	  stance.
	) previous email to the 6bone list have suggested that 
	  the same servers be used for both e.f.f.3.ip6.int and e.f.f.3.ip6.arpa
	  and I think this is a sound stratagy.

	So what I proposed to Andrei to take back to the RIRs was the 
	following:

        Recognise that the data published for 3ffe:: should be identical
	regardless of anchorpoint.  Plan for an active migration plan
	from industry/user nameservers to RIR nameservers for this delegation,
	based on the capability of the RIRs to support native IPv6 and
	TSIG. 

	I've not heard back from Andrei or anyone else on this proposal.
	I intend to work with the RIRs, starting with APNIC, to migrate
	the 3ffe:: zone to RIR servers.

--bill
	
	
--bill
Opinions expressed may not even be mine by the time you read them, and
certainly don't reflect those of any other entity (legal or otherwise).