Discuss mailing list

[Jonah Aragon <jonaharagon AT gmail.com>]

I don't think the intent of OpenNIC in general is to limit the amount of choices, even if some use cases overlap. The more choices we have the better, by your logic we should just drop all our other TLDs because .o covers all usages as a "general purpose namespace."

.core has uses not necessarily within hosting. Technical blogs, tutorials, DNS services, etc could also fall within the purpose and would be a good addition to the network. I don't see it as self promotional at all, outside of premium added services, which ModernTLD (.o) and I believe .pirate also plan to provide (possibly more, those were what I thought of off hand).

We should try to expand OpenNIC to cover as many use cases as possible to be a viable addition to the internet :)

Jonah

On Feb 2, 2017 3:26 PM, "Daniel Quintiliani" <danq AT runbox.com> wrote:

.libre is for promoting non-commercial use of the Internet, which includes use of OpenNIC
.o is for promoting use of OpenNIC

.core's charter would supposedly promote hosting services on OpenNIC, perhaps the sponsor's own hosting services (he has a large amount of "reserved domains" unusual for OpenNIC TLDs)

And regardless of whether there's a commercial interest involved in the TLD, we don't need a dozen random TLDs for "promoting use of OpenNIC" as .libre and .o are fine. If this company wants that kind of customization I suggest FreeNIC instead.

--

-Dan Q

On Thu, 2 Feb 2017 15:08:18 -0600, Jonah Aragon <jonaharagon AT gmail.com> wrote:

> I forgot how touchy some people are around here about charging for domains.
> It's allowed and you could if you want, but I'd have to recommend you
> saying you'll provide registrations for free forever. It calms some people
> down ;) you can make money from other services like what you mentioned
> anyways.
>
> Re: Dan -- .core seems to have a different purpose from .o/.libre (also we
> (.o) don't provide SSL certs, as we're working on an official OpenNIC Root).
>
> Jonah
>
>
> On Feb 2, 2017 3:05 PM, "Joseph Marsden" <josephmarsden AT towerdevs.xyz>
> wrote:
>
> TOWER and CoreDomain are totally different things... Give me a second to
> clarify this.
> The .core domain is not used solely to advertise a company's products, but
> can be for a much wider use, like people who want to host servers, store
> files, etc. In other words, .core is all about servers, to be short!
>
> TOWER and CoreDomain will always be kept separate except for legal issues
> such as DMCA requests which need to legally be handled by TOWER. The
> operating costs is only for costs required to run CoreDomain servers and
> does in no way relate to TOWER. The main profit-making activity for us will
> come from our future premium web and file hosting services.
>
> Hope this clears up the issue!
>
> -----Original Message-----
> From: discuss-request AT lists.opennicproject.org [mailto:
> discuss-request AT lists.opennicproject.org] On Behalf Of Daniel Quintiliani
> Sent: 02 February 2017 8:51 PM
> To: discuss <discuss AT lists.opennicproject.org>
> Subject: Re: [opennic-discuss] .core TLD Proposal
>
> .free/.libre and the new .o have the same exact purpose in their charters
> and don't claim "the right to raise prices to cover operating costs".
> Methinks "TOWER CoreDomain" is a company trying to misuse OpenNIC to
> promote Web hosting services. .free/.libre and .o have the same promotional
> purposes and at no cost (IIRC .o charges for SSL certificates and the
> like). I vote No on ".core" and any other TLD used solely to advertise a
> company's products.
>
> --
>
> -Dan Q
>
> On Thu,  2 Feb 2017 20:32:42 +0000 (UTC), <josephmarsden AT towerdevs.xyz>
> wrote:
>
> > I’d like to start a proposal for the .core TLD on the OpenNIC network.
> > ========
> > CHARTER
> > ========
> >
> > The .core TLD, operated by CoreDomain and managed by TOWER, is to be
> > used by individuals or commercial entities (individual or groups) to
> > promote their resource hosting (e.g virtual machine, website, file
> > hosting) on the OpenNIC network. The domain should only be used for
> > the aforementioned purposes, however exceptions may be granted in special
> cases.
> > Use of this TLD is not a given right to any holder, and domain names
> > may be revoked by the CoreDomain administration team, TOWER management
> > or by a vote of domain holders (henceforth known as "Members"),
> > especially pertaining to violations of our policies (see Section 2).
> >
> > "Members" in this charter refers to owners of .core domains and not
> > OpenNIC members unless otherwise noted.
> >
> > 1. REGISTRATION
> > ----------------------------
> >
> > .core domains will be available on a first-come, first-serve basis.
> > Some domains have been reserved for administrative use (see Section 6)
> > prior to public registration.
> >
> > Registrations immediately after approval will be handled manually via
> email.
> > An automated registration system is in development and will be
> > available at register.core when it becomes available. Registrations
> > will be available from
> > 3 month to 2 year periods. All registrations will be available for
> > free after approval, however, the CoreDomain administration reserves
> > the right to raise prices as needed to cover operating costs.
> >
> > 2. ABUSE
> > ---------------
> >
> > TOWER will not tolerate the following behaviour, and use of our
> > domains for any of the following is grounds for termination (see Section
> 3):
> >
> > -      Domain squatting
> > -      Spam email delivery
> > -      Malware distribution
> > -      Malicious interference with computer systems
> > -     Using the TLD for any other purpose not outlined in this charter
> >
> >
> > Our abuse policies are in line with OpenNIC's abuse policies as well
> > (http://wiki.opennicproject.org/TLDPolicy - "Obnoxious Activity: Spam
> > & Cracking"), and any policies listed there apply to .on domains as well.
> > CoreDomain is not a domain police force and meaningful abuse
> > enforcement will be reliant on members reporting. All abusive behavior
> > should be immediately reported to abuse AT central.core so administration
> can take action.
> >
> > 3. TERMINATION / REVOCATION
> > --------------------------------------------------
> >
> > Domains can be immediately terminated if they are found to be in
> > violation of our policies by the CoreDomain administration or TOWER
> > management, and a notice will be sent to the registrant of the
> > offending domain. Domains can also be terminated via a member vote.
> > Membership is granted to any domain holder, 1 vote per member regardless
> of the amount registrations they hold.
> > Member votes are subject to policies as listed in Section 4.
> >
> > Domains may also be revoked by the CoreDomain administration if the
> > OpenNIC membership at large moves to revoke a registration. We do not
> > foresee a circumstance where OpenNIC as a whole will be required to
> > vote on the revocation of a .core domain, but if the need arises we
> > will comply with any such vote.
> >
> > 4. VOTING
> > ----------------
> >
> > All matters of administrative importance will be voted upon by members
> > of the CoreDomain domain registry administration team. Motions will be
> > passed by a simple majority of votes (50% + 1). The CoreDomain
> > administration, and the higher TOWER management, holds the right to
> > veto any member votes, in order to retain control of .core operation.
> >
> > 5. DISPUTES
> > --------------------
> >
> > Trademark holders should email legal AT towerdevs.xyz if they wish to
> > dispute a domain. TOWER itself will revoke or transfer registrations
> > if ordered by a legitimate court of law, as a courtesy to that
> > country, as applicable to OpenNIC's dispute policy.
> >
> > 6. RESERVED DOMAINS
> > -------------------------------------
> >
> > The following domains are reserved by the CoreDomain administration
> > and will never be available for public registration:
> >
> > -     Register.core – Domain registration site.
> > -     Central.core – Administration and management site.
> > -     About.core – Overview site, CoreDomain hub.
> > -     Admin.core – CoreDomain administration site.
> > -     Websites.core – For future web hosting.
> > -     Secure.core – Future SSL certificates.
> > -     Nic.core – Reserved for redirection.
> > -     Opennic.core – Reserved for redirection.
> > -     Www.core – Reserved for redirection.
> > -     Files.core – Future file hosting site.
> > -     Citadel.core – Reserved.
> > -     Exertus.core – Reserved for backend operations.
> > -     Arctarus.core – Reserved for backend operations.
> > -     Helios.core – Reserved for backend operations.
> > -     Deepsector.core – Reserved for special operations.
> > -     Meta.core – Internal server operations and control.
> > -     Example.core – Example web page
> > -     Test.core – Test web page, is a blank page on the DNS server
> > -     Keystore.core – Used for internal private key operations.
> > -     Vote.core – Used for mass user polling.
> >
> > 7. AMENDMENTS AND MISC. POLICIES
> > -------------------------------------------------------------
> >
> > Amendments to this charter may be added by a vote of .core members.
> > Additionally, the CoreDomain administration is permitted to provide a
> > binding user agreement for registrations at register.core that may
> > include policies outside the scope of this charter.
> >
> > 8. FUTURE
> > ----------------
> >
> > CoreDomain and TOWER are committed to the future of the OpenNIC
> > network and will attempt to provide, in addition to the .core Tier 1
> > server, multiple Tier
> > 2 DNS servers to support the OpenNIC infrastructure, free and paid web
> > hosting, and free and paid file hosting.These services have no
> > deadline for completion at the moment. We also wish to help in
> > spreading the word about OpenNIC via self promotion and joining the
> > Public Relations Working Group http://wiki.opennicproject.
> org/PublicRelationsWG.
> >
> > 9. CONTACTS
> > --------------------
> >
> > -     CoreDomain Administration: administration AT central.core
> > -     Abuse Reporting: abuse AT central.core (All reserved .core domains have
> > the same abuse email.)
> > -     Legal Team: legal AT towerdevs.xyz (for subjects such as DMCA and legal
> > action)
> > -     Billing support: billing AT websites.core, billing AT files.core (for
> > premium file and website hosting)
> > -     Webmaster: webmaster AT central.core (All reserved .core domains have
> the
> > same webmaster.)
> > -     Postmaster: postmaster AT central.core (All reserved .core domains have
> > the same postmaster.)
> >
> > ====
> >
> > This charter template used under license
> > (https://creativecommons.org/licenses/by-sa/3.0/us/) very kindly
> > provided by Jonah Aragon.
> >
> > Note: Our non-OpenNIC front is at https://core.towerdevs.xyz (which
> > will direct users to configure their DNS settings to OpenNIC and auto
> > redirect them, or if they already are using OpenNIC they will
> > automatically be redirected to https://central.core for domain
> > registration instructions. This site is currently not online yet as it
> > is undergoing the design process.)
> >
> > Thanks for reading through this proposal, we are open to suggestions
> > for any changes.
> >
> > Joseph Marsden
> > Root Administrator at CoreDomain and Director at TOWER
> > IRC: CitadelCore
> > Email: josephmarsden AT towerdevs.xyz
> >
> > Sorry if this got sent as a duplicate... I think Outlook broke. :/
> >
> >
> > --------
> > 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
>
>
> --------
> 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