IDN registrations are now available not only in .SU.

Beginning on September, 02, 2008 RU-CENTER offers IDN registrations in .COM and .NET.

More than 80 languages are available.

Languages that can be written in the following scripts: Latin; Greek; Cyrillic; Armenian; Hebrew; Arabic; Syriac; Bengali; Gurmukhi; Oriya; Tamil; Telegu; Kannada; Malayalam; Sinhala; Thai; Lao; Tibetan; Myanmar; Georgian; Hangul; Ethiopic; Cherokee; Canadian-Aboriginal Syllabics; Ogham; Runic; Khmer; Mongolian; Han (Japanese, Chinese, Korean ideographs) are available.

Register IDN in .COM and .NET

A partir del 8 de septiembre comenzará el período de registro escalonado de dominios que incorporará al uso de Internet en la Argentina los caracteres multilingües del idioma español y portugués, y se añadirá el subdominio “gob ar” que reemplazará al tradicional “gov ar”.

La iniciativa fue impulsada por el Gobierno Nacional a través del canciller Jorge Taiana que el 9 de abril había firmado una resolución para incorporar esta clase de denominaciones junto con la diéresis, y los acentos.

Como es sabido, Internet fue creada originalmente para permitir nombres de dominio que contuvieran solamente caracteres pertenecientes al alfabeto inglés. Las discusiones globales para modificar ese marco, de las que siempre participó Argentina, habían comenzado en 1998.

Continue reading ‘Las Webs argentinas se preparan para recibir la Ñ’ »

Following the progress on the IDN TLD allocation processes during the ICANN meeting in Paris a new area has been made available to describe IDN policy development and IDN ccTLD allocation developments under ICANN’s IDN Area: http://icann.org/en/topics/idn.

At the Paris meeting, the Board approved both of the processes described below for implementation.

  • In relation to the IDN ccTLD “fast track” process it was resolved that the Board directs staff to: “(1) post the IDNC WG final report for public comments; (2) commence work on implementation issues in consultation with relevant stakeholders; and (3) submit a detailed implementation report including a list of any outstanding issues to the Board in advance of the ICANN Cairo meeting in November 2008.”

    Fast-track IDN ccTLD Activities

  • On a related note, the ICANN Board also adopted “the GNSO policy recommendations for the introduction of new gTLDs. And further that the Board directs staff to continue to further develop and complete its detailed implementation plan, continue communication with the community on such work, and provide the Board with a final version of the implementation proposals for the board and community to approve before the new gTLD introduction process is launched.”

    New gTLD Program
    source: http://www.icann.org/en/announcements/announcement-20aug08-en.htm

Yesterday VeriSign announced that VeriSign-branded SSL Certificates now support IDN. For years I have told people that IDN stood for International Domain Name, but in preparation for our press release on this topic, I have learned that the actual term is Internationalized Domain Name. Go figure. Anyway, IDN support means that a Web site can use character sets beyond the standard ASCII in its domain name. So you could use an umlaut or a Kanji character, for example. In the long term IDN affords the opportunity for non-English Web communications to have a truer experience by using the native alphabet in domains. One of the elements that's necessary is for sites to be able to secure themselves when these domain names are in use, and VeriSign is ready to do its part in that regard.

Mountain View, Calif. – August 18, 2008 – Seven of every 10
people in the world don’t speak English, but that isn’t keeping them
from using the Internet. Now, domain name registrants and Web site operators
not only can reach users in their own language – they can also protect
their sites with Secure Sockets Layer (SSL) Certificates from VeriSign,
Inc. (NASDAQ: VRSN), the trusted provider of Internet infrastructure
services for the networked world.

VeriSign today announced that its SSL Certificates
will now support Internationalized Domain Names (IDNs). IDNs display
Web site addresses in local language characters, such as Sinitic characters
used in China, Kanji symbols from Japan, and Cyrillic characters in
Russia.

The move will bring the VeriSign Secured® Seal – the
world’s most recognized trust mark – to potentially millions more Web
sites worldwide. Now, businesses with established brand recognition
in non-Latin based scripts and languages can show visitors that their
site is secured using industry leading SSL technology.  For more
information about SSL Certificates for Internationalized Domain Names,
visit www.verisign.com/ssl-idn

VeriSign® SSL Certificates enable an essential function
for online businesses: secure information exchange. IDNs have been often
regarded as a potential phishing tool because of the similarity of some
foreign characters to Roman characters. VeriSign SSL Certificates can
help protect both site visitors and site owners, by assuring visitors
that the site they are visiting is the authentic site they meant to
visit. By improving security to build trust with consumers, site owners
can boost their visitor-to-sales conversions and lower their incidents
of abandoned shopping carts.

“Internationalized domain names are gaining traction
with the introduction of IDN-enabled browsers like Internet Explorer
7 and Firefox,” said Michael Lin, vice president of SSL product management
at VeriSign.  “Providing the latest security protection is a key
step toward achieving a globally interconnected Internet that serves
linguistically diverse populations. For its part in this effort, VeriSign
is pleased to extend the protection of VeriSign SSL Certificates to
sites using IDNs.”

Continue reading ‘VeriSign to Extend SSL Security to Web Sites with Internationalized Domain Names’ »

True global brands need a .com extension. Clearly there are obvious exceptions but for the most part, if you want to market to the world, you need a good .com. However, with all the patting on the back old-school domainers like to give themselves, you have to admit, we should have registered more country-code top-level domains and internationalized domain names. I think this is especially true for those of us that resell our names. While I was in Spain this summer, I couldn’t help but notice that most of the small and medium businesses I saw had .es ccTLDs. Many large companies marketed ccTLDs locally as well. If only I had registered 100,000 of them to sell at 1000-10,000 Euros a piece! The Domain In Spain Falls Mainly On The .es Extension Instead I sat there comfortably fooling myself that .com was all that would ever matter. This does not mean that I’m going to start buying $50,000 ccTLDs and IDNs so please don’t try and sell them to me. I just wish I had had the foresight to have gotten them early. Time and again I am hearing stories about IDNs’ revenue growing year in and year out while revenue in most other extensions are falling. This of course, is especially true in Asian countries where businesses must adopt and promote an IDN because otherwise the masses wouldn’t understand the meaning of the name. This almost makes me think .mobi names have a chance. Almost. Let me repeat that I’m not a buyer on these names at big dollars. I just think hand-registering them makes a lot of sense. As does hand registering other extensions like .mobi, .name, .asia, .info, .me, etc. Hand register the hell out of them and sell them to end-users down the line. More than anything I like the ccTLD names and I’m kicking myself in the ass for not having more of them. Fortunately, there are still many opportunities left for everyone. **Added after post went live** One thing I forgot to mention is that we are noticing it is easier to get a website ranked in Google.ccTLD if you have domain.ccTLD. In other words, Our aeiou.com customers are reporting higher traffic on their ccTLD names from the respective countries.

On Thursday 25 June the Board of Directors of the Internet Corporation for Assigned Names and Numbers (ICANN), the nonprofit corporation that coordinates the global Internet system of unique identifiers, at the closing of its 32 International public meeting in Paris, unanimously approved the introduction of Internationalized Domain Names (IDNs) in the top level of Internet addresses.

On Thursday 25 June the Board of Directors of the Internet Corporation for Assigned Names and Numbers (ICANN), the nonprofit corporation that coordinates the global Internet system of unique identifiers, at the closing of its 32 International public meeting in Paris, unanimously approved the introduction of Internationalized Domain Names (IDNs) in the top level of Internet addresses.

The board endorsed the IDNC Working Group Report on recommendations for the introduction of Internationalized Domain Names, to expand the world’s Domain Name System and to work on adapting it to accommodate Country Code Top Level Domain Names (ccTLDs) in scripts other than Latin, such as Arabic, Cyrillic or Devanagri, and ideographic writing systems, such as Japanese, Korean or Chinese.This process is a major improvement in the development of the Internet as a global information and communication tool as it will enable multi-script addressing and therefore ensure access to millions of users who are currently deprived of this core resource of Knowledge Societies due to language constrictions.

Background
In September 2006 ICANN Board charted a multi-stakeholder working group on Internationalized Domain Names (IDNC WG) to develop and report on feasible methods that would enable the introduction, in a timely manner and in a way that ensures the continued security and stability of the Internet, of a limited number of “non-contentious” IDN ccTLDs, associated with the ISO 3166-1 list of two-letter country codes (such as .fr for France or .jp for Japan). The introduction of a limited number of IDN ccTLDs under the recommendations of this Working Group, popularly known as “fast track” mechanism, must not pre-empt the ultimate long-term policy outcomes of the IDN cc Policy Development Process (ccPDP).

Building from UNESCO’s Leading role in the WSIS implementation, the Organization participated at the first two phases of the Internet Governance Forum (IGF). At the second IGF in Rio de Janeiro in November 2007, UNESCO, ITU and ICANN organized a joint workshop on “Multilingualism in Cyberspace” where the three organizations committed themselves to cooperatively develop international standards for building a truly multilingual Internet including Internationalized Domain Names (IDNs).

Continue reading ‘ICANN approves the introduction of internationalized domain names’ »

Recently we teamed up with the Non-Commercial Users Constituency (NCUC) to express our concern to ICANN that the rights and needs of end-users are taken into account in the discussion of Internationalized Domain Names (IDN). Namely, IDNs are to be seen as a technical measure to allow for multi-lingual direction navigation of the Internet and not used as a tool to control access, impose censorship or limit freedom of expression online. Ultimately, each and every one of us, privileged enough to participate in the ICANN process in some way shape or form, does (or should) endeavor to represent the needs of the Internet end-users around the globe, and not simply our own political, or commercial self interest. I don’t purport to have the solution, but I think it is incumbent on all of us, especially those in the decision making capacity to simply ask the question: “Is this right for the welfare of the Internet user?”

Since the topic of Internet control is quite relevant these days, I wanted to post the full letter to ICANN.

Post by Alexa Raad, CEO, .ORG, The Public Interest Registry, Inc.

* * *

July 29, 2008

Dr. Paul Twomey, President

ICANN

4676 Admiralty Way, Suite 330

Marina del Rey, California 90292-6601

Dear Dr. Twomey:

Re: A Statement on Internationalized Domain Name Implementation

The deployment of Internationalized Domain Names (”IDN”) should be seen as a technical measure to allow for multi-lingual use of the internet, and not used as a tool by governments to control access, impose censorship or limit freedom of expression online.

In developing IDN policy, ICANN is urged to carefully distinguish the true needs of Internet users from the interests of those who might claim to represent them politically.

If ICANN solely considers a government’s claims for specific IDN needs and pays insufficient attention to the needs of users, it may enable governments to restrict end-users’ access to the Internet by imposing on them a specific language and script. An oppressive government might exert control over Internet access by adopting laws or pricing policies that limit end user accessibility to Internet content outside a specific IDN. In such a case, the implementation of an IDN string would impede rather than enhance Internet accessibility. We must ensure that IDN implementations do not make it easier for an oppressive government to censor and control user access.

It is critical that ICANN consider the specific IDN needs of end-users and also the potentially oppressive results that IDN implementation might have for some end-users. If some governments wrongfully manipulate IDN implementation as a means of validating their oppressive control of Internet users, then implementing such IDN strings will fail to fulfill the duty of ICANN to be a steward of the administration of the Internet and protector of the Internet user.

As the Internet becomes ubiquitous, nothing is more critical than ensuring the security and stability of the Domain Name System (”DNS”). ICANN is urged to verify that the operator of any new IDN TLD be fully committed and legally bound to maintaining an Internet that is open, interoperable and globally accessible. Inherent in ensuring adherence to this principle is the need to consider the proposed Internet Registry practices of any new IDN TLD operator. Criteria should be developed to ensure that any new registry operator will not reduce Internet freedom or impose burdensome restrictions, whether political or economic, on Internet users.

Respectfully submitted,

Alexa Raad

CEO, .ORG, The Public Interest Registry, Inc.

Dr. Milton Mueller

Chair, ICANN Non Commercial Users Constituency

cc: Denise Michel, VP of Policy Development, ICANN

John Jeffrey, General Counsel, ICANN

Kurt Pritz, Senior VP, Services, ICANN

Craig Schwartz, Chief gTLD Registry Liaison, ICANN

El Ministerio de Relaciones Exteriores aprobó los signos en castellano y portugués en la registración de los nombres de dominio de internet de la Argentina.

La Resolución 616/2008 del Ministerio, que apareció hoy publicada en el Boletín Oficial, establece que “se incorporan los caracteres multilingües pertenecientes al idioma español y portugués, para la registración de nombres de dominio de Nivel Superior Argentina (.AR).” y que la resolución se toma en base al “Decreto 267 del 6-4-2005; la resolución ministerial 2226 del 8-8-2000 que aprueban las Reglas para la Registración de Nombres de Dominio en Internet” en el país.

Entre los considerandos de la resolución se incluyen que “se ha producido un significativo aumento en la cantidad de registraciones de nombres de dominio” y que “es necesario actualizar el servicio que brinda NIC Argentina, teniendo en consideración los intereses de la República en el plano regional e internacional”.

Además, que “la intención del Gobierno Argentino es fortalecer la identidad cultural, permitiendo a las distintas comunidades locales de Internet, el registro de nombres de dominio incorporando caracteres multilingües propios del

español, idioma oficial de nuestro país”, y que el sistema “IDN (Internationalized Domain Names) permite la utilización de caracteres multilingües posibilitando, entre otros, la inscripción correcta de nombres de dominio según las reglas de los idiomas español y portugués”.

También que se resolvió incorporar “los caracteres del idioma portugués en atención a la pertenencia de la República Argentina al Mercado Común del Sur, que tiene como base fundamental de coincidencias la búsqueda de la ampliación de los respectivos mercados nacionales, a través de la integración y a efectos de acelerar procesos de desarrollo económico y social”.

Por otra parte, “en tal orden de ideas, la oportunidad amerita también reconsiderar la utilización del subdominio .gov.ar, que tiene por origen el subdominio genérico basado en el idioma inglés que distingue la palabra government, incorporando .gob.ar, en directa alusión al vocablo gobierno del idioma español”, incluye la resolución.

source: http://www.gobiernoelectronico.org/node/6419

Domains using the full character spectrum aren’t really supported well in browsers, partly due to security issues… so entering something like bücherei.com (the German word for library) will resolve into what is called a punycode address, namely xn--bcherei-n2a.com. This kinda ruins it for serious uses, but still, there’s domains out there using more than just ASCII letters… and some even use the graphical symbols part of Unicode:

  • This one showing the female symbol is still under construction: www.♀.com
  • The self-proclaimed “manliest domain on the internet” is for sale: www.♂.com
  • A page load error for heart-dot-com: www.♥.com
  • The eternal forces of yin-yang are for sale: www.☯.com
  • The right-facing swastika returns a page educating on the traditionally Hindu/ Buddhist/ good luck symbol: www.卐.com
  • The copyright character resolves to a parked page titled “protectyourbrand.com”: www.©.com
  • A smiley leads to the personal homepage of Daniel Früh from Switzerland: www.☺.com
  • The sun can’t be found: www.☼.com
  • A musical note leads to the personal homepage of… Daniel Früh again: www.♫.com
  • The omega character is the self-proclaimed Future Home of The Omega Project: www.Ω.com

source: http://blogoscoped.com/archive/2008-07-24-n24.html