Request for Comments re: .health gTLD
This is a request for feedback, preferably sent to me directly at <
[log in to unmask] (mailto:[log in to unmask]) >
As many in the global and public health communities are aware of, there
is some ongoing controversy around the proposed creation of the global top
level (gTLD) internet domain name .health, to be owned by a private
company. ICANN is the organization responsible for the approval of gTLDs,
and awarding contracts to registry companies who will manage the registrar
companies who in turn sell domain names to the public. ICANN created about
two dozen gTLDs in the past 15 years (.com, .net, .org, etc.) and is now in
the process of rolling out another 1200-1500 gTLDs in the next 18 months.
There is a piece on the .health controversy in The Lancet, Volume 382,
Issue 9902, Page 1404, 26 October 2013
http://www.thelancet.com/journals/lancet/article/PIIS0140-6736%2813%2962215-1/fulltext
A .health gTLD would mean health related domain names would populate the
internet. Not to promote (or pick on) one product let me use neem as a
neutral example. One might find, for example, websites called neem.health,
betterneem.health, bestneem.health, neembest.health, Canadaneem.health,
Botswananeem.health, and so on.
The controversy centers on two major issues. The argument for a .health
is to create a “trusted” health domain name on the Internet, because
health is "important". This is not an issue for all new gTLDs since some,
like .lawyer, can require that lawyers and law firms meet prior
professional qualifications. This is impossible with .health. One issue is
what constitutes meeting some “trust” standards. There is a problem
here akin to false positives and false negatives in medical research. How
does one prevent unsuitable owners from getting domain names? How does one
insure that suitable website owners are not denied access to a domain name?
Another issue is, if .health did exist what are the criteria that should
govern awarding or denying a domain name, and who should administer those
policies?
.health is not alone with regard to these issues. The proposed .kosher and
.halal gTLDs are being opposed on similar grounds, and not for religious
reasons. In all cases part of the “push” to create the gTLDs is that
private business interests see the prospects of profits. Some have
suggested that mechanisms other the granting or denying a .health domain
can evolve for allowing users to assess the trustfulness of online sites
and businesses, and the multitude of health related businesses, ngo’s,
etc. can just as easily live with .com, .net, .org, etc.. They argue that
the wider risks associated with .health are not worth the private profits.
If you or your organization(s) have views on the proposed .health, either
pro or con, or want to raise further issues I would appreciate feedback. I
will compile and share feedback, and I will be attending the ICANN meetings
in Singapore in late March 2014, representing the Canadian Society for
International Health on ICANN’s NPOC and NCSG committees. Individual
gTLDs (e.g. .health, .halal, .kosher) will not be on the formal agenda of
the meetings but stakeholder based discussion and awareness raising is part
of the environment of the meetings.
Sam Lanfranco email: < [log in to unmask] (mailto:[log in to unmask])>
----------------------------------------------
"It is a disgrace to be rich and honoured
in an unjust state" -Confucius
----------------------------------------------
Dr Sam Lanfranco (Prof Emeritus & Senior Scholar)
Econ, York U., Toronto, Ontario, CANADA - M3J 1P3
email: [log in to unmask] (mailto:[log in to unmask]) Skype: slanfranco
blog: http://samlanfranco.blogspot.com (http://samlanfranco.blogspot.com)
Phone: 613 476-0429 cell: 416-816-2852
Access CANCHID archives at: https://listserv.yorku.ca/archives/canchid.html
plus CANCHID subscription management. CANCHID is a joint service of the Canadian Society for International Health < http:www.csih.org > and the Distributed Knowledge Project (York University). Queries to Sam Lanfranco <[log in to unmask]>
|
