About RIPE | Contact  | Search | Sitemap    
Homepage RIPE  
RIPE Community Mail Archives
search  
     
RIPE Navigation Ends
About RIPE Maillists
Maillists Archive
Global Lists
Non Active Lists
RIPE NCC Navigation Ends
Next Section
<<< Chronological >>> Author Index    Subject Index <<< Threads >>>

Re: [ipv6-wg@localhost] 9/9/2004 IP6.INT Removal (Was: 9/9/2006 :ip6.int shutdown?)

  • To: Jeroen Massar < >
  • From: Andrei Robachevsky < >
  • Date: Thu, 22 Jul 2004 12:11:34 +0200
  • Cc: Kurt Erik Lindqvist < >
  • Organization: RIPE NCC

Jeroen, all,

Jeroen Massar wrote:
[ Cross-post, to get everybody in sync,
Other messages in this thread can be found at:
http://www.ripe.net/ripe/mail-archives/ipv6-wg/2004/msg00089.html ]

On Thu, 2004-07-22 at 09:58, Kurt Erik Lindqvist wrote:


On 2004-07-22, at 09.43, Jeroen Massar wrote:


But indeed, if there is concensus or not 9/9/2004 and ip6.int is gone
for me.
I vote for 9/9/2004 and getting rid of it properly. Maintaining two reverse threes will create more problems than it will solve.

Take your pick:

http://unfix.org/~jeroen/archive/drafts/draft-massar-v6ops-ip6int-removal-00.html
http://unfix.org/~jeroen/archive/drafts/draft-massar-v6ops-ip6int-removal-00.txt
http://unfix.org/~jeroen/archive/drafts/draft-massar-v6ops-ip6int-removal-00.xml

Short, quick and easy.
If no comments are risen for 16:00 today I'll submit this as an ID.


We were discussing possible ways of ip6.int phaseout with other RIRs, and one approach was presented at the last RIPE meeting in May (http://www.ripe.net/ripe/meetings/ripe-48/presentations/ripe48-dns-reverse-ipv6.pdf). It is a bit less radical than yours.

Description of the plan is attached.


Greets,
 Jeroen

Regards,

Andrei

--
Andrei Robachevsky
RIPE NCC

IP6.INT Phaseout Plan

   To deprecate usage of IP6.INT tree for reverse DNS and enable smooth
   transition to IP6.ARPA a process with 3 milestones is proposed:


   Milestone 1. Stop creating new and modifying existing delegations in
                IP6.INT tree.
   
   Starting from January 1, 2005 new delegations SHOULD NOT be created and
   existing resource records will be modified. This applies to the
   IP6.INT zone itself as well as to all child zones down the tree.

   Creation of new delegations in IP6.INT zone for 6bone address space was
   effectively stopped on January 1, 2004 as no new pseudo TLA's can be
   allocated according to the 6bone phaseout plan [RFC3701]. For the address
   space allocated to the RIRs by IANA it means that new allocations will not
   be reflected in the IP6.INT zone. 
 
   These measures will inevitably degrade the quality of delegations in
   IP6.INT tree, gradually increasing pressure for developers and
   administrators to migrate to use of IP6.ARPA as the only reverse
   delegation tree.



   Milestone 2. Remove all existing delegations from the IP6.INT tree.

   Starting from June 6, 2006, all delegations will be deleted from the
   IP6.INT zone and its child zones down the tree. This will effectively
   obsolete IP6.INT reverse delegation tree.

  
   Milestone 3. Remove IP6 delegation from the "INT" gTLD.

   Recommend to the IETF to direct IANA to remove the delegation of the
   obsolete "IP6" child zone from the "INT" gTLD. Since Milestone 2 effectively
   obsoletes IP6.INT zone this can be done at the same time, on June 6,
   2006.
   

  • Post To The List:
<<< Chronological >>> Author    Subject <<< Threads >>>
 

Next Section
     About RIPE | Site Map | LIR Portal | About the RIPE NCC | Contact | © RIPE Community. All rights reserved.
RIPE.NET Homepage LIR Portal RIPE Community