discuss AT lists.opennicproject.org
Subject: Discuss mailing list
List archive
- From: kevin <krattai AT gmail.com>
- To: discuss AT lists.opennicproject.org
- Subject: Re: [opennic-discuss] .on TLD Proposal
- Date: Thu, 17 Nov 2016 21:22:48 -0600
- Archived-at: <https://lists.opennicproject.org/sympa/arcsearch_id/discuss/2016-11/1479439368.14425.1.camel%40kevin-Pavilion-17>
- List-archive: <https://lists.opennicproject.org/sympa/arc/discuss>
- List-id: <discuss.lists.opennicproject.org>
Out of curiosity, why must the TLD be .on as that is a sticking point.
Could it not be .onic or similar?
Kevin
On Fri, 2016-11-18 at 03:12 +0000, Jonah Aragon wrote:
> The RFC you linked states "There are a set of what are called
> "top-level domain names" (TLDs). These are the generic TLDs (EDU, COM,
> NET, ORG, GOV, MIL, and INT), and the two letter country codes from
> ISO-3166."
>
> It's my understanding that it's like how all squares are rectangles
> but not all rectangles are squares: All ISO-3166 2 letter codes are 2
> letter TLDs, but all 2 letter TLDs don't necessarily have to be listed
> in the ISO-3166 specification, and they don't necessarily have to be
> ccTLDs. ICANN may be limiting gTLD registrations to 3 letters and
> above on the *off-chance* a new country code is created, but I don't
> believe IETF or OpenNIC has any prohibitions on their creation outside
> of country-code usage, and I don't think my proposal has to be changed
> at this time.
>
>
> Perhaps OpenNIC needs a policy change if you really think it's an
> issue?
>
> On Thu, Nov 17, 2016 at 8:57 PM Tim Groeneveld <tim AT timg.ws> wrote:
>
> https://tools.ietf.org/html/rfc1591
>
>
>
>
> ---- On Fri, 18 Nov 2016 13:20:58 +1100
> jonaharagon AT gmail.com wrote ----
>
>
> Could you try to find that RFC? The only specification
> I could find mentioned that all ISO 3166-1 codes were
> to be used as ccTLDs, but I couldn't find anything
> specifically stating all 2 letter domains were
> reserved for ccTLDs, regardless of whether or not they
> a part of that standard.
>
>
> Additionally, OpenNIC has the .oz domain currently
> in-use, and seems to peer with New Nations which
> primarily uses two letter TLDs. As far as I can tell
> there's no OpenNIC policy prohibiting TLDs like these,
> since they don't interfere with any domain on ICANN's
> root DNS servers.
>
> On Thu, Nov 17, 2016 at 7:53 PM Jacob Bachmeyer
> <jcb62281 AT gmail.com> wrote:
>
> The concept seems good, but the name needs to
> be changed. ISO-3166
> provides the list of country codes and the
> only requirement on country
> codes is that they are two letters. As I
> understand it, IETF reserved
> all two-letter TLDs as ccTLDs before ICANN
> ever existed, but I do not
> know in which RFC this was declared off the
> top of my head.
>
> We should not add two-letter TLDs.
>
> Jonah Aragon wrote:
> > I would like to start a proposal for a .on
> TLD on the OpenNIC network:
> >
> > ========
> > CHARTER
> > ========
> >
> > The .on TLD, operated by the dotON
> administration, is to be used by
> > commercial and non-commercial entities
> (individual or groups) to
> > promote themselves on the OpenNIC free
> network. This domain is
> > intended to be used in a general sense, akin
> to .com in the ICANN
> > network, and as such has a very general use
> case and little
> > restrictions on registration.
> >
> > Use of this TLD is not a given right to any
> holder, and domain names
> > may be revoked by the dotON administration
> team 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 .on domains and not
> > OpenNIC members unless otherwise noted.
> >
> > 1. REGISTRATION
> > ----------------------------
> >
> > .on 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.on 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 dotON administration
> > holds the right to raise prices as needed to
> cover operating costs.
> >
> > 2. ABUSE
> > ---------------
> >
> > dotON will not tolerate the following
> behavior, 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
> >
> > 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. dotON 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 register.on
> > <mailto:abuse AT register.on> 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 dotON
> administration, 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 dotON
> 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 .on 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 dotON domain registry. Motions will
> be passed by a simple
> > majority of votes (50% + 1). The dotON
> administration holds the right
> > to veto any member votes, in order to retain
> control of .on operation.
> >
> > 5. DISPUTES
> > --------------------
> >
> > Trademark holders should email
> trademarks AT register.on
> > <mailto:trademarks AT register.on> if they wish
> to dispute a domain.
> > dotON 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
> dotON administration and
> > will never be available for public
> registration:
> >
> > - register.on - Primary .on registration
> website
> > - www.on <http://www.on> - Redirects to
> register.on
> > - nic.on - Redirects to register.on
> > - dot.on - dotON administration, presently
> redirects to register.on
> > - search.on - Will be hosting an
> OpenNIC-wide search engine
> > - opennic.on - Reserved
> >
> > 7. AMENDMENTS AND MISC. POLICIES
> >
>
> -------------------------------------------------------------
> >
> > Amendments to this charter may be added by a
> vote of .on members.
> > Additionally, the dotON administration is
> permitted to provide a
> > binding user agreement for registrations at
> register.on that may
> > include policies outside the scope of this
> charter.
> >
> > 8. FUTURE
> > ----------------
> >
> > dotON is committed to the future of the
> OpenNIC network and will
> > attempt to provide, in addition to the .on
> Tier 1 server, Tier 2 DNS
> > servers to support the OpenNIC
> infrastructure, a search engine for the
> > network, email services, SSL services (under
> a self-hosted root CA).
> > 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
> > --------------------
> >
> > - dotON Administration: admins AT dot.on
> > <mailto:admins AT dot.on>
> (hostmaster AT opennic.on
> > <mailto:hostmaster AT opennic.on> forwards
> here)
> > - Abuse Reporting: abuse AT register.on
> > <mailto:abuse AT register.on> (abuse AT opennic.on
> > <mailto:abuse AT opennic.on> forwards here)
> > - Webmaster: jonah AT dot.on
> <mailto:jonah AT dot.on> (webmaster AT dot.on
> > <mailto:webmaster AT dot.on>,
> webmaster AT opennic.on
> > <mailto:webmaster AT opennic.on> forwards here)
> >
> > ====
> >
> > Thanks for reading through this proposal, we
> are open to suggestions
> > for any changes.
> >
> > Jonah Aragon
> > IRC: jonaharagon on #opennic
> >
>
> ------------------------------------------------------------------------
>
>
>
> --------
> 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
--
http://ca.linkedin.com/in/kevinrattai/
https://plus.google.com/+KevinRattai/
https://community.spiceworks.com/people/kevinrattai
--------
You are a member of the OpenNIC Discuss list.
You may unsubscribe by emailing discuss-unsubscribe AT lists.opennicproject.org
- [opennic-discuss] .on TLD Proposal, Jonah Aragon, 11/17/2016
- Re: [opennic-discuss] .on TLD Proposal, Jacob Bachmeyer, 11/17/2016
- Re: [opennic-discuss] .on TLD Proposal, Jonah Aragon, 11/17/2016
- Re: [opennic-discuss] .on TLD Proposal, Tim Groeneveld, 11/17/2016
- Re: [opennic-discuss] .on TLD Proposal, Jonah Aragon, 11/17/2016
- Re: [opennic-discuss] .on TLD Proposal, kevin, 11/17/2016
- Re: [opennic-discuss] .on TLD Proposal, Jonah Aragon, 11/17/2016
- Re: [opennic-discuss] .on TLD Proposal, kevin, 11/17/2016
- Re: [opennic-discuss] .on TLD Proposal, Draago D. Bellasys, 11/18/2016
- Re: [opennic-discuss] .on TLD Proposal, Jonah Aragon, 11/18/2016
- Re: [opennic-discuss] .on TLD Proposal, Daniel Quintiliani, 11/18/2016
- Re: [opennic-discuss] .on TLD Proposal, Maiyannah Bishop, 11/18/2016
- Re[2]: [opennic-discuss] .on TLD Proposal, spaesani, 11/19/2016
- Re: [opennic-discuss] .on TLD Proposal, Jonah Aragon, 11/17/2016
- Re: [opennic-discuss] .on TLD Proposal, kevin, 11/17/2016
- Re: [opennic-discuss] .on TLD Proposal, Aaron J. Angel, 11/18/2016
- Re: [opennic-discuss] .on TLD Proposal, Jonah Aragon, 11/18/2016
- Re: [opennic-discuss] .on TLD Proposal, Jacob Bachmeyer, 11/18/2016
- Re: [opennic-discuss] .on TLD Proposal, Jonah Aragon, 11/17/2016
- Re: [opennic-discuss] .on TLD Proposal, Tim Groeneveld, 11/17/2016
- Re: [opennic-discuss] .on TLD Proposal, Jonah Aragon, 11/17/2016
- Re: [opennic-discuss] .on TLD Proposal, Jacob Bachmeyer, 11/17/2016
Archive powered by MHonArc 2.6.19.