This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[dns-wg] RIPE NCC domain registrations
- Previous message (by thread): [dns-wg] RIPE NCC domain registrations
- Next message (by thread): [dns-wg] RIPE NCC domain registrations
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Ralf Weber
dns at fl1ger.de
Tue Jun 30 14:41:40 CEST 2015
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
- Previous message (by thread): [dns-wg] RIPE NCC domain registrations
- Next message (by thread): [dns-wg] RIPE NCC domain registrations
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]