Looking over that list .. 

The .int - only a very small set of organisations could register one, so 
there’s absolutely no reason to keep it if it’s not being used. 

The hyphenated domains - is there any “risk” in dropping them? I sincerely 
doubt it

As for the rest - I’ve no strong feelings either way, but holding on to a bunch 
of domains “just because” is pointless

And I wasn’t even aware that RIPE would even need to consult with the community 
or members on this kind of administrative matter . .

Regards

Michele

--
Mr Michele Neylon
Blacknight Solutions
Hosting, Colocation & Domains
http://www.blacknight.host/
http://blog.blacknight.com/
http://www.blacknight.press - get our latest news & media coverage
http://www.technology.ie
Intl. +353 (0) 59  9183072
Direct Dial: +353 (0)59 9183090
Social: http://mneylon.social
Random Stuff: http://michele.irish 
-------------------------------
Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty
Road,Graiguecullen,Carlow,Ireland  Company No.: 370845






On 30/06/2015 13:41, "dns-wg on behalf of Ralf Weber" <[email protected] 
on behalf of [email protected]> wrote:

>Moin!
>
>On 30 Jun 2015, at 14:30, Romeo Zwart wrote:
>
>> Dear colleagues,
>>
>> The RIPE NCC holds a number of domains besides ripe.net.
>>
>> Some of these domains were only registered as a "protection"
>> mechanism, which was considered good practice at the time.
>Is this considered bad practice now? Was there a policy change I missed?
>
>> We now plan to release the following domains, which are not being
>> actively used by the RIPE NCC:
>>
>> ripe-ncc.org
>> ripe-ncc.com
>> ripe-ncc.net
>> ripencc.com
>> ripencc.net
>> ripencc.org
>> ripelabs.net
>> ripen.cc
>> ripe.int
>> ipv6roadshow.com
>> ipv6roadshow.net
>> ipv6roadshow.org
>So we are talking about 12 domains. What is the hassle of keeping them?
>I'm pretty "confident" the new owners won't do as good things with it
>as the RIPE NCC.
>
>I would like to see more reasoning behind why you don't want to serve
>these 12 domains any longer.
>
>So long
>-Ralf
>
>

Reply via email to