[6bone] Fwd: BCP 80, RFC 3681 on Delegation of E.F.F.3.IP6.ARPA

[Jeroen Massar]

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

Bob Fink [mailto:bob at thefinks.com] wrote:

<SNIP>

> Marc Blanchet is readying the servers as we speak to make this happen.

Nice ;)

RFC3152 Section 2 mentions:
8<--------
   In this context, 'deprecate' means that the old usage is not
   appropriate for new implementations, and IP6.INT will likely be
   phased out in an orderly fashion.
- -------->8

Can we start setting a phase-out date on ip6.int too ?
Eg 6/6/2004, that way vendors *will* see where ip6.arpa isn't
used yet. All ISP's can easily upgrade to ip6.arpa trees in
the mean time. 4 months should be enough to change the string
in the resolver code from ip6.int to ip6.arpa and there won't
be anyone saying that because they use it for production they
need to do regression testing especially as the ip6.int tree
was already made obsolete in August 2001, that is 2+ years ago.

For people moving over in the next couple of weeks, one
can employ a DNAME, eg:

8.b.7.0.1.0.0.2.ip6.int. 7200   IN      DNAME   8.b.7.0.1.0.0.2.ip6.arpa.
e.5.c.5.c.0.e.f.f.f.7.2.0.9.2.0.e.1.0.0.3.0.0.0.8.b.7.0.1.0.0.2.ip6.int. 0 IN CNAME e.5.c.5.c.0.e.f.f.f.7.2.0.9.2.0.e.1.0.0.3.0.0.0.8.b.7.0.1.0.0.2.ip6.arpa.
3.0.0.0.8.b.7.0.1.0.0.2.ip6.arpa. 86400 IN SOA  nsauth1.bit.nl. hostmaster.bit.nl. 2004011901 28800 7200 604800 86400
;; Received 250 bytes from 2001:7b8:3:2c::53#53(nsauth1.bit.nl) in 38 ms

Greets,
 Jeroen

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

iQA/AwUBQA5duimqKFIzPnwjEQJZkACgtlWV3VqjTNdWeVenPPdAsrRH1xgAn3QL
ZI+RXrBBy1M+yRwHQK/RSWk5
=xABg
-----END PGP SIGNATURE-----