Discuss mailing list

[Verax <verax AT 8chan.co>]

For what it matters, FurNIC is technically not part of OpenNIC, just a
peer.  So what arrangements we have for them should not necessarily be
taken as precedent for OpenNIC TLDs.

Secondly, I'm surprised no one has questioned TOWER before this.  It's
also not been brought up by the proposer, which seems to be a touch out
of order to me.

From the proposer's email (josephmarsden AT towerdevs.xyz), towerdevs.xyz
seems to be the group in question, which is comprised of Joseph Marsden,
Jonah Aragon, and 2 other psuedoanonymous parties.

I feel that that information should have been disclosed at the start,
not dug up by me.

I also take issue with a few parts of the charter.  I won't get into the
pricing bit or the reserved domains, as others have already covered that.
        First is that the use case for .core is extremely specific and
ambiguously worded.  The promote clause implies that it is only for
advertising purposes, and the purpose statement as a whole can be
interpreted in a number of ways.
        "TOWER" has heavy administrative power over the proposed .core, but is
never clearly defined in the document.  This is definitely not
acceptable.  At the bare minimum a link to the website is in order.
(Yes, I know the domain is in there, however each time it's listed, it's
for other reasons)
        Some of your contact emails use towerdevs.xyz, others use .core
domains.  There should be a .core AND an ICANN domain for each contact.

And finally, it's not really a complaint, but please clean up the
commas.  There are a number that are redundant, and if you're not going
to use Oxford commas then don't use multi-clause sentences.

Regards,
Verax

vv AT cgs.pw wrote:
> I would like to see Mister TOWER post to the ML
> if he's going to be part of this. ;)
> 
> It's quite likely that I don't understand something
> here, but I see OpenNIC as a community, and the
> idea of having some hidden entity behind an
> application for a TLD just seems off the mark.
> 
> ~ Ole
> 
> 
> On Fri, 03 Feb 2017 23:45:05 +0000
> Jonah Aragon <jonaharagon AT gmail.com> wrote:
> 
>> Speculating here, as I'm not associated with CoreDomain,
>> but here's what I've been led to believe:
>>
>> Re Point 1: I think the whole "exceptions may be granted
>> by a member super-majority vote of at least 60%" is
>> implied by the other section that mentions that, since
>> that is the only(?) party authorized to make the
>> exceptions in the first place.
>>
>> 2: I think you're correct, it sounds like TOWER
>> "owns"/manages CoreDomain. Not sure if that needs to be
>> made clearer in the charter or if it matters when it
>> comes down to it, either way it's the same. It sounds
>> like TOWER exists to resolve legal issues, possibly
>> similar to how Fellig e.V. operates FurNIC. Clearly at
>> least one TLD on OpenNIC operates in a similar manner.
>>
>> What JC brought up has little to do with .core it seems,
>> and it sounds like he might be moving to a different TLD
>> anyways, so it's really a non-issue.
>>
>> Jonah
>>
>> On Fri, Feb 3, 2017 at 5:31 PM Christopher
>> <weblionx AT gmail.com> wrote:
>>
>>> The section "The domain should only be used for the
>>> aforementioned purposes, however exceptions may be
>>> granted in special cases." seems especially vague. If
>>> it spelled out reasons for exceptions, even if it was
>>> just something like, for example: "exceptions may be
>>> granted by a member super-majority vote of at least
>>> 60%".
>>>
>>> I also don't get why "CoreDomain administration team"
>>> and "TOWER management" are separate but given power. It
>>> should be either one or the other. If the CoreDomain
>>> administration team is wholly owned by TOWER, then it
>>> should be spelled out as such.
>>>
>>> You also have a reference to ".on" in there at the end
>>> of section 2.
>>>
>>> With the issue raised by JC, along with the ones I have
>>> mentioned above, I would be very hesitant to vote yes
>>> on this TLD.
>>>
>>>
>>> On Fri, Feb 3, 2017 at 4:06 PM, Joseph Marsden
>>> <josephmarsden AT towerdevs.xyz> wrote:  
>>>> I'll consider placing some of the backend-reserved
>>>> and miscellaneous  
>>> domains under a generalized subdomain. Maybe
>>> backend.core (for example arctarus.backend.core). If
>>> you were wondering, these are codenames for our
>>> internal file hosting and media sharing services - they
>>> are not visited normally and would simply redirect you
>>> to central.core. (excluding citadel.core).  
>>>>
>>>> -----Original Message-----
>>>> From: discuss-request AT lists.opennicproject.org
>>>> [mailto:  
>>> discuss-request AT lists.opennicproject.org] On Behalf Of
>>> gp  
>>>> Sent: 03 February 2017 7:28 PM
>>>> To: discuss AT lists.opennicproject.org
>>>> Subject: Re: [opennic-discuss] .core TLD Proposal
>>>>
>>>> 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 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 [1] -
>>>>>>> "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 [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  
>>>>>> 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
>>>>>>> [3].
>>>>>>>
>>>>>>> 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/
>>>>>>> [4]) 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. :/  
>>>>>>
>>>>>> --
>>>>>> 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  
>>>>
>>>>
>>>>
>>>> --------
>>>> 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
>

Attachment: signature.asc
Description: OpenPGP digital signature