On Tue, Nov 18, 2014 at 11:16:19AM +0000, Niall O'Reilly wrote: I use the simplest option. ;-)
I am not sure a request IANA to sign .int is worth doing any time soon. Signing .int will almost certainly be blocked by layer 9+ issues until long after the dust has settled on the NTIA-IANA transition. Besides, the few voices on this thread that have mentioned ripe.int appear to be asking for it to be removed, not for it to be signed in a signed TLD. I think the WG needs to reach consensus on what should be done here.
I'm reading that as a call from one of the co-chairs for (more) voices from the WG, so here's mine.
Let's have RIPE.INT removed.
+1
4/ Ripen.cc is a historical artifact. RIPE NCC is not currently using it and we are not planning any future use. Releasing the domain is an operational decision that we may take in the future.
Just kill it! IMO the domain should get removed from DLV as soon as it is prudent to do so: which probably means immediately. ripen.cc can die on its renewal date. Though these too should be consensus decisions for the WG.
Let's have RIPEN.CC removed also.
+1 Piotr -- gucio -> Piotr Strzyżewski E-mail: Piotr.Strzyzewski@polsl.pl