Skip to Content.
Sympa Menu

discuss - Re: [opennic-discuss] ICANN now has a .free gTLD

discuss AT lists.opennicproject.org

Subject: Discuss mailing list

List archive

Re: [opennic-discuss] ICANN now has a .free gTLD


Chronological Thread 
  • From: kevin <krattai AT gmail.com>
  • To: discuss AT lists.opennicproject.org
  • Subject: Re: [opennic-discuss] ICANN now has a .free gTLD
  • Date: Sat, 03 Dec 2016 21:05:26 -0600

wow!

OK, this is more than just a "good fight" on principle.

Has anyone read the Amazon .free TOS?

http://nic.free/pdf/FREE-en-ConditionsOfUse.pdf

"COPYRIGHT
All content included in or made available through any Site, such as
text, graphics, logos, button icons, images, audio clips, digital
downloads, data compilations, and software is the property of ARSI or
its content suppliers and protected by United States and international
copyright laws. The compilation of all content included in or made
available through any Site is the exclusive property of ARSI and
protected by U.S. and international copyright laws"

I say we hold strong to .free

Kevin

On Sat, 2016-12-03 at 20:49 -0600, kevin wrote:
> Yes, yes, that I know, Jeff. :)
>
> What I was specifically speaking to was that ICANN could then sell
> off .OSS and .pirate and all the others and what will we do ...?
> Scramble to find a new .tld ?
>
> Of course, I'm speaking from a principle point of view when I saw we
> ignore .free, for the reasons I spoke.
>
> At the end of the day, if everyone with a .free is willing to move over
> to a .lib(re/er), then ... hey ... no biggie. :D
>
> Kevin
>
> On Sat, 2016-12-03 at 19:37 -0700, Jeff Taylor wrote:
> > On 12/03/2016 07:16 PM, kevin wrote:
> > > As for ICANN, they could simply look at all OpenNIC tlds and grab them
> > > for ICANN use.
> >
> > Actually that's not true. We generate our own root zone for opennic,
> > and that script forces opennic TLDs to take precedence and override any
> > conflicting ICANN domains. So even in our current situation where
> > Amazon's .free has made it into the ICANN root, we opennic users still
> > have full access to our existing domains. The only way for the ICANN
> > TLD to get into our root zone is if I remove the references to opennic's
> > TLD first. If we voted to create our own .com zone, we could do it
> > because we maintain full control of the zone files used by opennic from
> > top to bottom. If we wanted to maintain ICANN's .com zone, but replace
> > google.com with our own domain, we could do that too.
> >
> > In case you don't realize it, I wrote the scripts and have been
> > maintaining opennic's root zone for a number of years. Most people
> > never hear about this because for the most part everything runs smoothly
> > and your queries always return the results that you expect (yes there
> > have been some hiccups and I do what I can to try to make the scripts
> > more bulletproof when something breaks). If I had ever betrayed that
> > trust, you can bet that everyone would have known about it!
> >
> > However the point is that the root zone is an absolutely critical piece
> > of the DNS infrastructure, and changes to the root can have significant
> > affects on how you see the whole internet. We can shape that view
> > however we want, and ICANN cannot simply reserve our existing TLDs and
> > shut us down. The initial purpose of opennic was to show that ICANN
> > does not HAVE to be the ones in control of the internet, and that anyone
> > can set up a DNS service to do the same thing as them, but without the
> > huge costs. We've been here for over 16 years and have a world-wide
> > presence. They may try ignore us, but the proof is here that ICANN is
> > not actually as important as they would like to think.
> >
> > --------
> > You are a member of the OpenNIC Discuss list.
> > You may unsubscribe by emailing
> > discuss-unsubscribe AT lists.opennicproject.org
>

--
http://ca.linkedin.com/in/kevinrattai/

https://plus.google.com/+KevinRattai/

https://community.spiceworks.com/people/kevinrattai




Archive powered by MHonArc 2.6.19.

Top of Page