discuss AT lists.opennicproject.org
Subject: Discuss mailing list
List archive
- From: gp AT gparent.net
- To: discuss AT lists.opennicproject.org
- Subject: Re: [opennic-discuss] .core TLD Proposal
- Date: Fri, 03 Feb 2017 19:28:28 +0000
- Dkim-filter: OpenDKIM Filter v2.9.2 mx-in0.gparent.org 4D0D920336
I would also suggest making a domain to hold all these subdomains. It would be better for future expansion (you can just add a subdomain to your already defined-in-the-charger reserved domain instead of having to add new entries) and it just makes more sense in general.
On 2017-02-03 14:27, Jonah Aragon wrote:
I'm not currently associated with .core. All I know about it is what's
been posted up to now on this Mailing List.
Jonah
On Feb 3, 2017 8:23 AM, "mk" <mk AT mkwia.com> wrote:
"presumably"? Aren't you one of these, so called, Tower Devs?
On 02/02/2017 22:33, Jonah Aragon wrote:
I don't think too much attention should be paid to those
necessarily. They presumably must serve some purpose and even if
they weren't listed here I'd assume Joseph would just "register"
them himself anyways, so the end result is the same.
Jonah
On Feb 2, 2017 3:37 PM, "Roman Hargrave" <roman AT hargrave.info>
wrote:
I primarily am curious about the list of reserved domains, primarily
some of them seemingly arbitrary
* citadel.core
* exertus.core
* arctarus.core
* helios.core
If these are all reserved for "backend operations" it would suggest
to me that they are in fact the
names of individual services or "machines" (as it were), which
strikes me as something that one would
prefer to use a subdomain of a more meaningful domain, e.g.
`exertus.nic.core`, `exertus.tower.core` or `exertus.central.core`
for.
On Thu, 2 Feb 2017 20:32:44 +0000 (UTC)
<josephmarsden AT towerdevs.xyz> wrote:
I’d like to start a proposal for the .core TLD on the OpenNICnetwork.
========be used by
CHARTER
========
The .core TLD, operated by CoreDomain and managed by TOWER, is to
individuals or commercial entities (individual or groups) topromote their
resource hosting (e.g virtual machine, website, file hosting) onthe OpenNIC
network. The domain should only be used for the aforementionedpurposes,
however exceptions may be granted in special cases.names may be
Use of this TLD is not a given right to any holder, and domain
revoked by the CoreDomain administration team, TOWER management orby a vote
of domain holders (henceforth known as "Members"), especiallypertaining to
violations of our policies (see Section 2).not OpenNIC
"Members" in this charter refers to owners of .core domains and
members unless otherwise noted.basis. Some
1. REGISTRATION
----------------------------
.core domains will be available on a first-come, first-serve
domains have been reserved for administrative use (see Section 6)prior to
public registration.via email.
Registrations immediately after approval will be handled manually
An automated registration system is in development and will beavailable at
register.core when it becomes available. Registrations will beavailable from
3 month to 2 year periods. All registrations will be available forfree after
approval, however, the CoreDomain administration reserves theright to raise
prices as needed to cover operating costs.domains for
2. ABUSE
---------------
TOWER will not tolerate the following behaviour, and use of our
any of the following is grounds for termination (see Section 3):charter
- Domain squatting
- Spam email delivery
- Malware distribution
- Malicious interference with computer systems
- Using the TLD for any other purpose not outlined in this
well
Our abuse policies are in line with OpenNIC's abuse policies as
(http://wiki.opennicproject.org/TLDPolicy [1] - "ObnoxiousActivity: Spam &
Cracking"), and any policies listed there apply to .on domains aswell.
CoreDomain is not a domain police force and meaningful abuseenforcement will
be reliant on members reporting. All abusive behavior should beimmediately
reported to abuse AT central.core so administration can take action.violation of
3. TERMINATION / REVOCATION
--------------------------------------------------
Domains can be immediately terminated if they are found to be in
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 anydomain
holder, 1 vote per member regardless of the amount registrationsthey hold.
Member votes are subject to policies as listed in Section 4.the OpenNIC
Domains may also be revoked by the CoreDomain administration if
membership at large moves to revoke a registration. We do notforesee a
circumstance where OpenNIC as a whole will be required to vote onthe
revocation of a .core domain, but if the need arises we willcomply with any
such vote.members of the
4. VOTING
----------------
All matters of administrative importance will be voted upon by
CoreDomain domain registry administration team. Motions will bepassed 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.dispute a
5. DISPUTES
--------------------
Trademark holders should email legal AT towerdevs.xyz if they wish to
domain. TOWER itself will revoke or transfer registrations ifordered by a
legitimate court of law, as a courtesy to that country, asapplicable to
OpenNIC's dispute policy.administration and will
6. RESERVED DOMAINS
-------------------------------------
The following domains are reserved by the CoreDomain
never be available for public registration:server
- 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 [2] – 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
- Keystore.core – Used for internal private key operations.members.
- Vote.core – Used for mass user polling.
7. AMENDMENTS AND MISC. POLICIES
-------------------------------------------------------------
Amendments to this charter may be added by a vote of .core
Additionally, the CoreDomain administration is permitted toprovide a binding
user agreement for registrations at register.core that may includepolicies
outside the scope of this charter.network and
8. FUTURE
----------------
CoreDomain and TOWER are committed to the future of the OpenNIC
will attempt to provide, in addition to the .core Tier 1 server,multiple Tier
2 DNS servers to support the OpenNIC infrastructure, free and paidweb
hosting, and free and paid file hosting.These services have nodeadline for
completion at the moment. We also wish to help in spreading theword about
OpenNIC via self promotion and joining the Public RelationsWorking Group
http://wiki.opennicproject.org/PublicRelationsWG [3].domains have
9. CONTACTS
--------------------
- CoreDomain Administration: administration AT central.core
- Abuse Reporting: abuse AT central.core (All reserved .core
the same abuse email.)and legal
- Legal Team: legal AT towerdevs.xyz (for subjects such as DMCA
action)(for
- Billing support: billing AT websites.core, billing AT files.core
premium file and website hosting)domains have the
- Webmaster: webmaster AT central.core (All reserved .core
same webmaster.)domains have
- Postmaster: postmaster AT central.core (All reserved .core
the same postmaster.)kindly provided by
====
This charter template used under license
(https://creativecommons.org/licenses/by-sa/3.0/us/ [4]) very
Jonah Aragon.(which will
Note: Our non-OpenNIC front is at https://core.towerdevs.xyz
direct users to configure their DNS settings to OpenNIC and autoredirect
them, or if they already are using OpenNIC they will automaticallybe
redirected to https://central.core for domain registrationinstructions. This
site is currently not online yet as it is undergoing the designprocess.)
suggestions for any
Thanks for reading through this proposal, we are open to
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. :/
--
Roman Hargrave
http://hargrave.info
roman AT hargrave.info
$ fortune -s linuxcookie linux cookie
"I go on working for the same reason a hen goes on laying eggs."
-- H. L. Mencken
--------
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
Links:
------
[1] http://wiki.opennicproject.org/TLDPolicy
[2] http://Www.core
[3] http://wiki.opennicproject.org/PublicRelationsWG
[4] https://creativecommons.org/licenses/by-sa/3.0/us/
--------
You are a member of the OpenNIC Discuss list.
You may unsubscribe by emailing discuss-unsubscribe AT lists.opennicproject.org
- Re: [opennic-discuss] .core TLD Proposal, (continued)
- Message not available
- Message not available
- Message not available
- Message not available
- Re: [opennic-discuss] .core TLD Proposal, JC, 02/03/2017
- Re: [opennic-discuss] .core TLD Proposal, vv, 02/03/2017
- Re: [opennic-discuss] .core TLD Proposal, vv, 02/03/2017
- Re: [opennic-discuss] .core TLD Proposal, Jonah Aragon, 02/03/2017
- Re: [opennic-discuss] .core TLD Proposal, JC, 02/03/2017
- Re: [opennic-discuss] .core TLD Proposal, josephmarsden, 02/03/2017
- Message not available
- Re: [opennic-discuss] .core TLD Proposal, Jonah Aragon, 02/02/2017
- Re: [opennic-discuss] .core TLD Proposal, mk, 02/03/2017
- Re: [opennic-discuss] .core TLD Proposal, Jonah Aragon, 02/03/2017
- Re: [opennic-discuss] .core TLD Proposal, gp, 02/03/2017
- RE: [opennic-discuss] .core TLD Proposal, Joseph Marsden, 02/03/2017
- Re: [opennic-discuss] .core TLD Proposal, Christopher, 02/03/2017
- Re: [opennic-discuss] .core TLD Proposal, JC, 02/03/2017
- Re: [opennic-discuss] .core TLD Proposal, Jonah Aragon, 02/03/2017
- Re: [opennic-discuss] .core TLD Proposal, vv, 02/04/2017
- Re: [opennic-discuss] .core TLD Proposal, Verax, 02/04/2017
- Re: [opennic-discuss] .core TLD Proposal, josephmarsden, 02/04/2017
- Re: [opennic-discuss] .core TLD Proposal, Theo B, 02/04/2017
- RE: [opennic-discuss] .core TLD Proposal, Joseph Marsden, 02/04/2017
- Re: [opennic-discuss] .core TLD Proposal, Daniel Quintiliani, 02/04/2017
- Re: [opennic-discuss] .core TLD Proposal, gp, 02/03/2017
- Re: [opennic-discuss] .core TLD Proposal, Jonah Aragon, 02/03/2017
- Re: [opennic-discuss] .core TLD Proposal, mk, 02/03/2017
- Re: [opennic-discuss] .core TLD Proposal, Jonah Aragon, 02/02/2017
Archive powered by MHonArc 2.6.19.