Proposal for shutdown of ip6.int?

["Jeroen Massar" <jeroen@unfix.org>]

-----BEGIN PGP SIGNED MESSAGE-----

Hi,

Now that we have seen a RFC arise for e.f.f.3.ip6.arpa
and there apparently will be a deployment shortly,
wouldn't it be a good idea to start planning a closure
of the usage of ip6.int ?

ip6.arpa was set as a standard 2 years ago by RFC3152
which is also a BCP.

All software vendors have to do is s/ip6.int/ip6.arpa/
in their code. They don't need any fallbacks to ip6.int
thus there should be no big coding problem.
As for the existing deployments, they already knew for
2 years that this was going to happen.

To give the people in 6bone some time to create a
ip6.arpa version of their zone by doing some mv's and
reloading their nameserver and to, not forget, let
the operators of e.f.f.3.ip6.arpa create the delegations
to the pTLA's, which are going per 6/6/6 and let IANA
have some time to actually delegate the tree a date
should be picked somewhat over a year in the future.

I propose 6/6/2005 as a nice cutoff date for ip6.int.

This should give enough time to let above things happen.
People not updating in this timeframe, won't update anyways.

Greets,
 Jeroen

PS: Yes, I am still using 6bone space myself.

-----BEGIN PGP SIGNATURE-----
Version: Unfix PGP for Outlook Alpha 13 Int.
Comment: Jeroen Massar / http://unfix.org/~jeroen

iQA/AwUBQCqd2ymqKFIzPnwjEQIILwCfXAjHwxVWXRHWhpHix6LlFUumwgEAnjpS
AwC8XYmt02sXp3o7/aZ/SOVl
=V1ve
-----END PGP SIGNATURE-----