Discuss mailing list

[Maiyannah Bishop <maiyannah.bishop AT postactiv.com>]

Personally, I'm in favour of keeping .free and letting ICANN explain to people why there's collisions.
Are we going to just roll over the moment ICANN takes up a TLD that conflicts?  Because if so, then we may as well not even bother with operating, because we'll be dead the moment they reopen gTLD applications next year.
-mb

On 2016-12-03 22:14, Jonah Aragon wrote:

I'm strongly in favor of .libre, and I don't see a reason it would be used by ICANN really (and that hasn't stopped us before, I can see a good use case with a lot of our TLDs that haven't been used). .liber is also good but I feel like some people may not have heard of liber as opposed to libre which is in more popular use, and think it's a misspelling.

I guess I don't really have an alternate proposal, just wanted to show support for .libre, it seems the best alternative that would be aligned with .free's policies based on name alone.

I'd like to add I don't support numbers in TLDs for usability reasons. I don't think they would fall in popular use, especially when similar letter-only domains exist as an alternative (.free vs .fr33). That's just my opinion though, I wouldn't use it but perhaps others don't think the same.

Jonah

On Sat, Dec 3, 2016 at 9:04 PM Jeff Taylor <shdwdrgn AT sourpuss.net> wrote:

As Jonah mentioned in the other thread, it would be best for us to go
ahead and plan ahead for the worst.  Based on the comments so far,
nobody wants to just drop our existing domains under .free, so we will
move forward with the assumption that we will either be ignoring the new
ICANN zone, or we will be transferring our domains to a new zone.

In the event that we migrate to a new TLD, lets start discussing what we
would like to use.  So far "libre" (French) and "liber" (Latin) have
both been proposed.  Libre is a more mainstream term and thus has more
of a potential to also be snagged up by ICANN in the future.  Does
anyone else have suggestions they want to propose?
Going off of RFC3696, section 2, valid TLDs may contain standard letters
(A-Z), numbers (0-9), or hyphens (-).  The TLD may NOT start or end with
a hyphen, nor may it be completely numeric.  So as an example, we could
legally create a new TLD with the name .fr33. Please keep these rules in
mind when submitting your suggestions for a new TLD.


--------
You are a member of the OpenNIC Discuss list. You may unsubscribe by emailing discuss-unsubscribe AT lists.opennicproject.org

--------
You are a member of the OpenNIC Discuss list. 
You may unsubscribe by emailing discuss-unsubscribe AT lists.opennicproject.org

Attachment: signature.asc
Description: OpenPGP digital signature