Home / Blogs

Presenting a Way Forward: Step-by-Step and ICANN’s New gTLD Process

I read this to the ICANN Board Thursday morning, in Sydney, after more prep work than I care to recall. If you don’t know that the DAGv3 is delayed, or what the IRT is, this is a good time to bush up on current ICANN state.

Good morning. My name is Eric Brunner-Williams, and I am speaking to you on behalf of the initial signatories of the Step-by-Step proposal. I represent one of the signatories as the principal of the native, aboriginal, and indigenous cultural and linguistic Top-Level Domain (TLD) project, one of many similar efforts to preserve living languages and cultures.

Along with linguistic and cultural and city and regional TLD projects, we have started the Step-by-Step proposal.

We held a workshop on Monday which was well attended and we have had discussions with the relevant stakeholders, which are continuing.

After detailed discussions with many interested stakeholders, I am now presenting the Step-by-Step proposal to you, the board.

The Step-by-Step proposal is an early window, nothing more, and nothing less. We are convinced that while the still unresolved issues are relevant, a fair number of applicants fall under the RADAR and do not affect these open issues.

Applicants seeking to enter this early window should commit to the highest level of protection regarding these open issues:

• credible registration and compliance policies,
• recognition of legitimate protection of ip rights, and
• anti-phishing mechanisms,

through a shared binding code of conduct, implemented on a scalable platform.

The Step By Step proposal, while allowing some applications to move forward, harms none.

An early window tests the system.

Stakeholders having legitimate concerns about open issues, will be able to flag applications which do not conform to their standards, removing those applications from the early window.

Linguistic and cultural, regional and city applications mentioned in the draft of this proposal are examples. The early window is would be open to any application which is willing to commit to the higher levels of protection I mentioned previously.

We invite discussion with the board and the ICANN community. An online fora is available at stepbystep.tel.

And of course we invite discussion from the CircleID community as well.

The initial signatories are:

.NAI, Native, Aboriginal & Indigenous (languages and cultures)
.QUEBEC, PointQuébec
.BCN, The City of Barcelona
.CYM, dotCYM Cyf. (Welsh language and culture)
.EUS, PuntuEus Elkartea (Basque language and culture)
.GAL, Asociación PuntoGal (Galician language and culture)
.BZH, Association pointBZH (Brittany / Breton language and culture)
.LAT, Latin-American and Caribbean Federation for Internet and Electronic Commerce
and
.BERLIN, .HAMBURG & .KÖLN
and
CORE.

There are subsequent signatories, and question(s) from members of the Board. I’ll provide these shortly.

There was a question from the Board, which I’ll add here from the transcript shortly.

By Eric Brunner-Williams, Mathematician

Filed Under

Comments

Comment Title:

  Notify me of follow-up comments

We encourage you to post comments and engage in discussions that advance this post through relevant opinion, anecdotes, links and data. If you see a comment that you believe is irrelevant or inappropriate, you can report it using the link at the end of each comment. Views expressed in the comments do not represent those of CircleID. For more information on our comment policy, see Codes of Conduct.

CircleID Newsletter The Weekly Wrap

More and more professionals are choosing to publish critical posts on CircleID from all corners of the Internet industry. If you find it hard to keep up daily, consider subscribing to our weekly digest. We will provide you a convenient summary report once a week sent directly to your inbox. It's a quick and easy read.

Related

Topics

IPv4 Markets

Sponsored byIPv4.Global

New TLDs

Sponsored byRadix

DNS

Sponsored byDNIB.com

Domain Names

Sponsored byVerisign

Brand Protection

Sponsored byCSC

Threat Intelligence

Sponsored byWhoisXML API

Cybersecurity

Sponsored byVerisign