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 18:28:25 CEST 2015
Moin! On 30 Jun 2015, at 16:41, Jim Reid wrote: >> So we are talking about 12 domains. What is the hassle of keeping >> them? > > Adding cruft for cruft's sake creates needless hassles and overhead. > We should all be wary about asking the NCC to make open-ended > commitments and at the very least review those sorts of > requests/decisions from time to time. From that perspective, getting a > sense from the WG about these domain names is a good thing. That is a good argument. I like clean systems, we just have to weigh it against the effort and the possible damages. Running a couple of more domains doesn't seem like a big burden to me, a lot of people on this list host thousands or millions of domains. >> I'm pretty "confident" the new owners won't do as good things with it >> as the RIPE NCC. > > Who cares? If the domains no longer serve any useful purpose or have > no worthwhile affiliation with the NCC or the RIPE community, there > seems to be little point in keeping them. Or as was discussed a few > months ago, there would be no point rolling over their DLV keys. Since > DLV is going away, that may well be the catalyst to give some of these > crufty domains a one-way ticket to Dignitas. I don't care about DLV as you know, but I am pretty sure these will be used in abuse going forward if the RIPE NCC releases them. The RIPE NCC name has some authority when it comes to IPv4 addresses.... It seems that people are not concerned about that and that's fine with me. I might just be overly paranoid, and have certain opinions on these domain and IPv4 traders. > Holding on to these domains and continuing to maintain them "just > because" seems unwise. ICANN already has ripe.<gTLD> on a reserved > list so there is no chance of them going to an impostor. ripen.*, but not ripe(-)ncc.*. Will be interesting to see what happens to them. > Personally speaking, I do not like open-ended commitments which are > just allowed to drift. In this case, nobody appears to be sure why > these domains need to exist any more or have a good reason to hold on > to them. Romeo's asking the WG if there are good reasons, just in case > there are factors which have been overlooked. If anyone knows of such > considerations, please speak up. I did. Do whatever you want with it. If there are more people who think the NCC should drop them I'm a good democrat ;-). 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 ]