[dns-wg] [RIR] Deprecation of ip6.int Scheduled for June 1, 2006

On Thu, Mar 02, 2006 at 09:19:56AM -0500, Member Services wrote:
> In August 2005, RFC 4159 Deprecation of ip6.int was published as Best 
> Current Practice. This RFC noted that maintenance of ip6.int is no 
> longer required and that the Regional Internet Registries adopt a 
> schedule for cessation of ip6.int. All the RIRs have agreed to deprecate 
> ip6.int on June 1, 2006. Further note that ARIN no longer modifies any 
> of the zones it administers under ip6.int effective December 7, 2005.
> 
> Ginny Listman
> Director of Engineering
> American Registry for Internet Numbers

and:

On Tue,  16 May 2006 11:09:10 +0200, Andrei Robachevsky wrote:
> Below is the proposed plan of ip6.int deprecation. Could you please
> check if it is detailed enough to be properly coordinated, or if it
> misses something.
> 
> Andrei
> 
> ip6.int deprecation plan
> -------------------------
> 
> Advance Work:
> 
> Contact Bill Manning at bmanning at vacation.karoshi.com and
> hostmaster at ep.net before the 25th of May and ask him to schedule the
> following:
> 
> o June 1st 12:00 GMT: Remove all delegations within the 2.ip6.int zone.
> 
> RIR Plan (common)
> 
> o May 30th 12:00 GMT: Drop TTL on authoritative NS records within the
> ip6.int zones to 3600.
> 
> o June 1st 12:00 GMT: All delegations within the ip6.int zone are
> removed. No RIR Action needed, other than checking.
> 
> o June 1st 13:00 GMT - 23:59 GMT: All RIR's remove their respective
> ip6.int zones from their servers.

........


while i noted the following:


        not all the zones or data in ip6.int are  being removed....
        so no, i am not changing the TTLs.   the delegations that
        the RIR's have asked to be removed are scheduled for automatic
        removal.   I will check on the process when i wake up roughly
        3.5 hours later.  I will be glad to send you email at that time
        to confirm removal.

--bill

.......

that being said, the RIR requested delegations have been removed from the IP6.INT
zone.  

what remains is:

# dig 2.ip6.int. axfr @::1        

; <<>> DiG 9.3.2 <<>> 2.ip6.int. axfr @::1
; (1 server found)
;; global options:  printcmd
2.ip6.int.              86400   IN      SOA     dot.ep.net. hostmaster.ep.net. 1999061700 10800 900 604800 129600
2.ip6.int.              86400   IN      NS      z.ip6.int.
2.ip6.int.              86400   IN      NS      dot.ep.net.
2.ip6.int.              86400   IN      NS      flag.ep.net.
0.0.1.0.0.2.ip6.int.    86400   IN      NS      z.ip6.int.
0.0.1.0.0.2.ip6.int.    86400   IN      NS      dot.ep.net.
0.0.1.0.0.2.ip6.int.    86400   IN      NS      flag.ep.net.
1.0.1.0.0.2.ip6.int.    86400   IN      NS      z.ip6.int.
1.0.1.0.0.2.ip6.int.    86400   IN      NS      dot.ep.net.
1.0.1.0.0.2.ip6.int.    86400   IN      NS      flag.ep.net.
2.0.0.2.ip6.int.        86400   IN      NS      z.ip6.int.
2.0.0.2.ip6.int.        86400   IN      NS      dot.ep.net.
2.0.0.2.ip6.int.        86400   IN      NS      flag.ep.net.
2.ip6.int.              86400   IN      SOA     dot.ep.net. hostmaster.ep.net. 1999061700 10800 900 604800 129600
;; Query time: 4 msec
;; SERVER: ::1#53(::1)
;; WHEN: Thu Jun  1 06:44:20 2006
;; XFR size: 14 records (messages 14)


--bill