discuss AT lists.opennicproject.org
Subject: Discuss mailing list
List archive
- From: Jonah Aragon <jonaharagon AT gmail.com>
- To: discuss <discuss AT lists.opennicproject.org>
- Subject: Re: [opennic-discuss] .core TLD Proposal
- Date: Thu, 2 Feb 2017 20:59:13 -0600
He would be if there was any possibility at all that anyone here could know about his projects and his idea to use ".Core". I know Joseph and can with 100% certainty state that he didn't know of JC's idea and that it is a complete coincidence, Joseph's used "Core" as a part of projects in the past as completely unrelated developments.
That being said, I agree there should be another thread discussing how to resolve the issue, or JC could email Joseph directly to work out a solution.
Jonah
On Feb 2, 2017 8:55 PM, <vv AT cgs.pw> wrote:
JC,
Are you suggesting there is something "not quite
right" about this? To me if there is a person
working on a .core TLD and then someone else comes
up and wants to register a .core TLD would not
be a coincidence. Perhaps start another thread
about this particular issue.
~ Ole
On Thu, 2 Feb 2017 20:21:37 -0600
JC <jc AT motorsports-x.com> wrote:
> Might I mention that my idea for this domain was also
> heavily server based.
>
>
> This is very frustrating.
>
> On Feb 2, 2017 8:18 PM, "JC" <jc AT motorsports-x.com> wrote:
>
> > I. Discussed opening this .core Domain with jonah a
> > Few weeks ago.. And since have been working on getting
> > other aspects of my plan into place... Which include
> > design and. Maufactufing (and is taking a ton of effort
> > and time.) Which I do for a Living.
> >
> > My planned use of .Core calls for a completely open
> > issuance process with no fees Required for use.
> >
> > I can only ponder the coincidence of this timing.
> >
> >
> > I vote no.
> >
> >
> >
> > On Feb 2, 2017 8:11 PM, <vv AT cgs.pw> wrote:
> >
> >> When people mention "operating costs" it's always
> >> a flag for me. It comes across as someone relying
> >> on mom and dad to pay their five dollars a month
> >> (or far less) and mom says no. Seriously, there
> >> are no "operating costs" of significance and it
> >> is childish to be discussing OpenNIC in those
> >> terms. Sorry to bring this forward, but I feel
> >> that somebody had to. :)
> >>
> >> ~ Ole
> >>
> >> On Thu, 2 Feb 2017 21:34:39 +0000
> >> mk <mk AT mkwia.com> wrote:
> >>
> >> > As far as I can see, the words "reserves the right to
> >> > raise prices as needed to cover operating costs" are
> >> > still there. Still NO.
> >> >
> >> >
> >> > On 02/02/2017 21:21, Joseph Marsden wrote:
> >> > >
> >> > > I’ve clarified a few things in my previous
> >> > > conversation with Jonah and Daniel, not CoreDomain
> >> > > nor TOWER is allowed to make any profit
> >> > > from .core, by design. The main profiting activity
> >> > > will be premium web and file hosting, alongside
> >> > > our free web and file hosting (although that’s
> >> > > certainly not the purpose of .core).
> >> > >
> >> > > .core is a wide spanning TLD that’s intended to be
> >> > > used for activities related to servers, server
> >> > > hosting, and file hosting.
> >> > > >Just updated the charter to reflect things, now a
> >> > > >YES vote of at least 60%
> >> > > of CoreDomain users is required to raise operating
> >> > > costs at any time.
> >> > > >
> >> > >
> >> > > >I’ve also posted the operating charter publicly
> >> > > >so any changes can be made
> >> > > more easily.
> >> > >
> >> > > >
> >> > >
> >> > > >https://towerce-my.sharepoint.com/personal/josephmarsden_
> >> towerdevs_xyz/_layouts/15/guestaccess.aspx?docid=05f1140
> >> 1594b64852a61a0e3091ef2918&authkey=AW4f0J-G1uREgKiVblRRWx
> >> o&expiration=2017-03-04T21:12:18.000Z
> >> > >
> >> > > *From:*discuss-request AT lists.opennicproject.org
> >> > > [mailto:discuss-request AT lists.opennicproject.org]
> >> > > *On Behalf Of *mk *Sent:* 02 February 2017 9:17 PM
> >> > > *To:* discuss AT lists.opennicproject.org
> >> > > *Subject:* Re: [opennic-discuss] .core TLD Proposal
> >> > >
> >> > > I vote NO on ".core" as long as "the CoreDomain
> >> > > administration reserves the right to raise prices
> >> > > as needed to cover operating costs."
> >> > >
> >> > > On 02/02/2017 20:32, josephmarsden AT towerdevs.xyz
> >> > > <mailto: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 toabuse AT central.core
> >> > > <mailto: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
> >> > > emaillegal AT towerdevs.xyz
> >> > > <mailto: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 <http://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
> >> > > <mailto:administration AT central.core>
> >> > >
> >> > > - Abuse Reporting:abuse AT central.core
> >> > > <mailto:abuse AT central.core> (All reserved .core
> >> > > domains have
> >> > >
> >> > > the same abuse email.)
> >> > >
> >> > > - Legal Team:legal AT towerdevs.xyz
> >> > > <mailto:legal AT towerdevs.xyz> (for subjects such as
> >> > > DMCA and legal
> >> > >
> >> > > action)
> >> > >
> >> > > - Billing support:billing AT websites.core
> >> > > <mailto:billing AT websites.core>,billing AT files.core
> >> > > <mailto:billing AT files.core> (for
> >> > >
> >> > > premium file and website hosting)
> >> > >
> >> > > - Webmaster:webmaster AT central.core
> >> > > <mailto:webmaster AT central.core> (All
> >> > > reserved .core domains have the
> >> > >
> >> > > same webmaster.)
> >> > >
> >> > > - Postmaster:postmaster AT central.core
> >> > > <mailto: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
> >> > > athttps://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 tohttps://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
> >> > > <mailto: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
> >> > > emailingdiscuss-unsubscribe AT lists.opennicproject.org
> >> > > <mailto: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.open nicproject.org
> >>
> >>
--------
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
- Re: [opennic-discuss] .core TLD Proposal, Jonah Aragon, 02/02/2017
- Message not available
- RE: [opennic-discuss] .core TLD Proposal, Joseph Marsden, 02/02/2017
- Re: [opennic-discuss] .core TLD Proposal, mk, 02/02/2017
- Re: [opennic-discuss] .core TLD Proposal, vv, 02/03/2017
- Re: [opennic-discuss] .core TLD Proposal, JC, 02/03/2017
- Re: [opennic-discuss] .core TLD Proposal, JC, 02/03/2017
- 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, JC, 02/03/2017
- 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, mk, 02/02/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
- Re: [opennic-discuss] .core TLD Proposal, koobifluxe, 02/06/2017
- Re: [opennic-discuss] .core TLD Proposal, Jonah Aragon, 02/06/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, 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.