Discuss mailing list

[Jonah Aragon <jonah AT triplebit.net>]

Hello!

Your proposal looks good, well-written. I’ll give it a longer look when I have more time, but this sounds like a great project. 

If you didn’t know already, I just wanted to remind you that we just passed some new policies regarding the creation of TLDs. If you didn’t notice you should review it (I’ll include the relevant portion below) since it isn’t posted to the wiki yet. The main thing is that you’ll need to have operated a Tier 2 server for 3 months. This is mainly to show commitment to the project and make sure you can keep a server online for a fairly long term period of time. If you don’t already operate one I’d suggest starting now, that way by the time you finish building the infrastructure for your TLD and other programs you’ll already meet that requirement. 

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 28, 2017, at 3:20 PM, <hacktivist AT keemail.me> <hacktivist AT keemail.me> wrote:

Hi comunity,

For begin, please excuse our english. We're from francophone zone. We even
think about creating and boosting the francophone OpenNIC community soon.

We are LECOCYT. A TEAM of passionate people about technology and the spirit of
free software. We currently operate in the Republic of Benin (West Africa) and
we are formalized as a company named LECOCYT SARL. We provide services based
on Open Source Software to particulars and professionnals.

We founded a local community with goal to share tech knowledge and open source
spirit with  african  people in particulary and the rest of the world in
general. Often we provide free tech-class for beginners through our comunity
in our local areas.  We also fight for fundamental liberties and adheres to
web neutrality  and every tech-concept which bring positive change in this
domain. We think OpenNIC is an awesome project and we want to do our best to
bring it to the highest level in Africa and Benin in particular.

Our proposal is to create the dot BEN extension.

Despite technological evolution in the world, the situation in Africa and
Benin in particular does not favour free access to Internet resources and the
creation of websites under the ccTLD ".BJ".

dot BEN is the ccTLD (country code Top-Level Domain) custom made for the
Beninese people, which is estimated at about 10,000,000 inhabitants on the
African continent.  dot BEN is a free alternative to the traditional dot BJ,
which is not open, has many constraints and does not facilitate technological
development on this side of the continent. As this problem is recurrent in
Africa, the ccTLD dot BEN is intended to be a development tool for Benin in
particular and for Africa in general. Opening Africa to the world and
encouraging cultural mix through the dot BEN ccTLD is our vision.

To vvande's question : "How will your users learn to reconfigure their
networking software so this will work?" on the OpenNIC IRC Channel, we're
actually developping a cross platform OpenNic browser and also DNS Overider.
We'll release all the job when we finish to the public under Open Source
Licence. The software will be downloadable for Linux/Unix, Mac OS, Windows,
Android and Iphone. We also plan to create a web site accessible via ICANN DNS
as an entry point for beginners people to explain the whole OpenNic concept
and how to benefit from the dot BEN extension. We currently have our own
network of people all over the country who will be in charge of promoting
OpenNic to the general public in order to get as many people as possible to
join us and democratize OpenNic.

There a many people in Africa who want better and open technologies without
censors and our goal is to bring this dream to reality. LECOCYT plan also to
launch a competitive free email service like ProtonMail or TutaNota,
accessible for all to get a free web email box under the "dot BEN" ccTLD

We invite all members of the community to express their opinion on the
proposal to create the dot BEN extension. Your comments and opinions are
welcome.


Here is our charter proposal:

***************************************************

Registrant Criteria

Registrations are available to all entities such as persons, partnerships,
corporations, non-profits, etc. It is recommended, though not required, that
an entity register one domain and have others, such as specific promotions and
so forth, underneath their existing registration. Registrants will be allowed
to register as many domains as they wish, within reason and subject to network
and administrative resources, server support, etc.


General Policies

By default and intention, the .BEN ccTLD includes the OpenNIC general policies
against spamming from registered domains and that the registry is run by its
members, who are domain holders. Domain registrations will be accepted on a
first-come first-served basis. Since commercial interests can be involved,
trademarks will be honoured. Disputes will be handled under the .BEN dispute
policy. Proven violation of .BEN policies will result in the immediate
suspension of the domain name. No domain name will be suspended, barring
exceptional circumstances, on the basis of a complaint or dispute alone.


Domain Disputes

As a general rule, a domain may only be disputed by the holder of a trademark
registered before the domain in question was registered. Disputes must first
be brought to both the .BEN Hostmaster and the registrant of the disputed
domain. The registrant will be contacted and given a chance to respond. In the
event the registrant does not make an initial response within 14 days, the
domain may be released or, if in the opinion of the .BEN ccTLD team the
dispute is not clear-cut, the matter will be referred to a vote by the .BEN
membership. Since legal issues are involved, the .BEN ccTLD will abide by the
decisions of a court of competent jurisdiction. Obtaining proof of a trademark
claim or seeking such a court decision will be the responsibility of the
entity seeking the dispute.


Notes

Trademarks are honoured only to ensure the commercial viability of the .BEN
TLD. The dispute policy is intended to be a democratic balance between the
needs of a commercial registrant and the rights of a domain holder.


http://www.opennic.ben

hostmaster AT opennic.ben
webmaster AT opennic.ben
abuse AT opennic.ben


***************************************************



Extra Notes :

We are thinking in the LECOCYT community about several concepts to be
implemented in the near future to accelerate the widespread adoption of
OpenNIC. At a time when everyone must be concerned about their privacy and
their future in a world of domination and thousands of connected objects.


Special Thanks :

We thank all the OpenNIC comunity, the IRC channel members in particulary
vvande for his retroaction and his questions. We also thank all contributors
from any side.

--------
You are a member of the OpenNIC Discuss list.
You may unsubscribe by emailing discuss-unsubscribe AT lists.opennicproject.org