Discuss mailing list

[Matthias Merkel <matthias AT boltn-hosting.com>]

I was informed about this but I wasn't sure if it was used already. Looks like we have to wait 3 months then (until our Tier 2 server is 3 months old). We planned to keep it online pretty much forever anyways but it's just annoying wait time. If it's a policy I guess we have to comply with it though so we will wait with the vote until the 20th of February 2018. I would still like to continue this discussion though as we can improve a lot of things until then.

About the policies: We are working on that and are gonna update the community on that.

Matthias Merkel

On Mon, Nov 20, 2017 at 2:27 PM, Jonah Aragon <jonah AT triplebit.net> wrote:

My main issue is that your policies don’t seem very clearly defined. I’d try to work out exact terms on what does and doesn’t constitute abuse, etc. 

Also, you should know we just passed some new policies regarding the creation of TLDs. If you didn’t notice you should review it (I’ll include it below) since it isn’t posted to the wiki yet. 

This document loosely follows RFC 2119 in defining the following keywords used throughout:

- “MUST”, “SHALL”, “REQUIRED”: Indicates the definition is an absolute requirement, with no exceptions.

- “MUST NOT”, “SHALL NOT”: Indicates the definition is an absolute prohibition, with no exceptions.

- “SHOULD”, “RECOMMENDED”: Indicates there may be valid reasons to ignore a particular item, but you should understand and carefully weigh the full implications of ignoring the item before proceeding.

- “SHOULD NOT”, “NOT RECOMMENDED”: Indicates there may be valid reasons in which a particular behavior is acceptable or useful, but the full implications should be understood and carefully weighed before proceeding with any behavior described with these labels.

- “OPTIONAL”: Indicates a behavior is truly optional, and may or may not be implemented.

SECTION II: Proposing a TLD

BEFORE you begin a proposal, you MUST meet the following requirements:

- You MUST have an operational Tier 1 DNS server. This server must mirror the root data of the root “.” zone and all the zone data for each OpenNIC TLD. This server MUST pass the Tier 1 server test: http://report.opennicproject.org/t2log/t1.php

- You MUST have a website accessible at www.opennic.[TLD] with the following information:

- A copy of your charter (detailed below in this document)

- Information on how to register a new domain

- Administrative contacts

- You MUST accept and process emails to the following addresses, and they must be listed on your website detailed above.

- hostmaster@opennic.[TLD] — SHOULD be delivered to the DNS administration team for your TLD.

- abuse@opennic.[TLD] — SHOULD be delivered to your abuse handling team (dealing with spam, malware, or other charter violators)

- webmaster@opennic.[TLD] — SHOULD be delivered to the web presence team for your TLD.

- You MUST publish and enforce a charter, which satisfies the following requirements:

- Your charter MUST clearly explain the purpose of your TLD (possibly including a brief description and/or examples of domains and content to be hosted)

- It MUST include a description of content that will not be allowed on your domain (for example: trademarked names, malware hosts)

- It SHOULD NOT conflict with existing OpenNIC policies.

- It SHOULD include descriptions on how amendments to your charter will be handled. If no amendment clauses are included, changes will be handled in accordance to the current OpenNIC voting policies.

Additionally, you MUST meet the following requirements before proposing your TLD to the community:

- You MUST have operated a Tier 2 DNS server continuously for at least 3 months, and said DNS server MUST be in operation while your TLD is being considered.

- You should keep this DNS server in operation following the approval of your TLD.

- You MUST have a process for users to register domains. Domain registrations SHOULD be provided free of charge, and an automated domain registration system is RECOMMENDED.

- You SHOULD have an administration team gathered. Your team can consist of as many people as needed, or a single person, but it MUST be able to handle DNS Administration, Webmaster Related, and Abuse Report requests effectively.

OPTIONALLY: You may wish to informally request feedback from the community and experienced members before pushing your TLD proposal to a formal discussion. While not required, it can help you prepare for your TLD proposal by satisfying some requests the community has before official judging.

- Consider starting a discussion on the #opennic IRC channel on Freenode to get faster feedback from some experienced members of the community. Make sure you stick around on the channel throughout the discussion to answer any questions some may have.

- You can also start a new thread on the Mailing List with a brief description of your TLD, ensuring it is clear this is just an informal discussion on the matter. Make sure you are available to answer questions and take advice from the community, which you may be able to implement either technically or in your charter before a formal discussion.

After you have satisfied ALL of the above requirements, you may proceed to submit your TLD for formal discussion and a vote.

Start a discussion by sending an email to the Mailing List, with the subject line: “[DISCUSSION] ‘.{TLD}’ Proposal” (replacing {TLD} with your namespace). This email MUST include the following:

- A copy of the charter, which may be pasted in-line, linked to, or attached as a PDF. If you choose to link to your charter, it MUST be accessible from a location other than your www.opennic.tld homepage, as no community members will be able to access that site prior to your TLD being approved.

- The IP address(es) of your Tier 1 server(s) that will be added following the approval of your TLD.

- Your OpenNIC Member username.

NOTE: DO NOT send this email as a reply to another thread. You MUST start a discussion thread by sending a new message to discuss AT lists.opennicproject.org.

After a minimum of 7 days following your discussion thread, you may begin a vote. A vote may be started by sending a new email (NOT a reply) to the Mailing List with the subject: “[VOTE] ‘.{TLD}’”

The email MUST include the following:

- A deadline for votes, at least 7 days following the post date of your thread. This should be a clear date and time (in UTC).

- A linked or attached final copy of the charter.

Thanks!

Jonah

On Nov 20, 2017, at 7:06 AM, Matthias Merkel <matthias AT boltn-hosting.com> wrote:

We wanted to request feedback for our .tut TLD. After we have collected feedback and done appropriate changes suggested by the community we will open the voting for the TLD.

About us

We are a hosting company with the goal to help innovation and provide affordable and reliable hosting. We also have a NIC project in collaboration with a German grammar school. The NIC's TLDs are mostly subdomains with nameservers delegated down using NS DNS records. Now we also want to expand to OpenNIC TLDs. Our first OpenNIC TLD is planned to be .tut. We are also operating a Tier 2 server (ns1.by.de.dns.opennic.glue) with more planned to come soon.

Charter

.tut is a TLD for tutorial sites and other types of websites with educational goal.

Registration

Registration has not started yet but we are accepting manual preregistrations via email at matthias AT boltn-hosting.com. Automated preregistration will start soon. Registration can be done by any individual

Price

Registration is generally provided free of charge. The BoltN NIC reserves itself the right to make exceptions to this rule however this right is not usually used.

Abuse

We do not take down sites related to whisteblowing or similar content but we do take down domains hosting child pornography, spam or malware.

I'm looking forward to your feedback.

Matthias Merkel

CTO

BoltN Hosting

https://boltn-hosting.com

--------
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