Archive for the 'neustar' Category

More Languages in .BIZ

Wednesday, January 23rd, 2008

We launched another round of 6 languages in .BIZ on January 16th, 2008: Finnish, Hungarian, Latvian, Lithuanian, Polish and Portuguese (press release).

While NeuStar already has many Latin-based IDN languages in its portfolio, one may wonder why we would bother making the Venn diagram so complicated. Just define a Latin script-based table and be done with it! Well, since we tend to take a more conservative approach with IDN, it is safer to have each language table contain only the characters used by that language proper and nothing else1. After all, we’re here to provide value and not to make a quick buck (at least that’s how I see it.)

1 Language is constantly evolving. Often, it is not easy trying to determine if a character used in borrowed words is well-assimilated in the culture to be considered part of the language. There are no clear rules, do we follow the guidelines from the trademark offices’ of the countries in which the language is used? Or do we follow the ccTLD registry (if we do, does it make sense for a gTLD?) Or language institutions? Thankfully, there are many great resources to draw from.

.BIZ Korean IDNs Just Launched

Monday, August 20th, 2007

The second piece of news following the localization of EchIDNA into Korean is that we have just launched Korean IDN registration in .BIZ three hours ago. I won’t divulge the numbers here but let’s just say that it far exceeded my expectations.

You may be wondering if there is any connection between our Korean launch and the localization of EchIDNA. Aside from yours truly being involved in both projects, it is purely coincidental. We have been preparing for the Korean launch for a few months, and in doing so have consulted with NIDA (National Internet Development Agency in Korea) and have adopted their language table (with 2,350 KS X 1001 Hangeul characters). The table is available here: http://www.neulevel.biz/idn/KR_Table.pdf and will be posted to the IANA Repository of TLD IDN Practices soon.

If you have a .BIZ Korean IDN and would like some free links, submit it to IDNSearch.net!

Chinese and Japanese IDN in .BIZ

Tuesday, April 24th, 2007

I just got back this morning from attending the OASIS XRI TC face-to-face meeting in San Diego with Bill Barnhill, Drummond Reed, Laurie Rae, Les Chasen, Markus Sabadello, and Marty Schleiff. A number of good things came out of the meeting, which I’ll leave for another blog because this post is about Internationalized Domain Names, not XRI.

So we just opened the flood gates for Chinese and Japanese IDNs for .BIZ. This has been my brainchild for the past half a year or so, and represents a significant step forward for our registry in terms of internationalization. As one might expect, no support for Chinese IDN is complete without bundling as specified in the JET guidelines and RFC4713.

The tricky part to supporting both Chinese and Japanese IDN within a single registry is that the two languages share a large repertoire of Han characters. While the concept of Simplified and Traditional Chinese is well-understood within the Chinese communities, Japanese generally do not use variants the same way. Two characters that may be considered variants by a Chinese user may be seen as distinct characters with different semantics from the Japanese’ point of view. To implement a registry that respects the culture and expectations of both language communities while offering a high degree of protection against homographic attack is a juggling act in itself. I dare say that NeuStar is the first unsponsored gTLD registry that Got It Right ™.

So, how does it work? Well, suppose you registered 電車.biz with the Chinese language tag, you will automatically get the simplified version of the domain, 电车.biz, placed into the DNS for you. No one can register any combination of variants of the domain, e.g. 电車.biz and 電车.biz.

What if you registered a mixed version 電车.biz, also with the Chinese tag? Well, you get that PLUS 電車.biz (traditional) and 电车.biz (simplified) giving you 3 domains in total! That is because we respect the registrant’s request, even if it looks like a mixed- traditional and simplified string. Whatever you asked for, if it doesn’t clash with another registered domain, will always be given to you.

If, however, the Japanese tag was used to register 電車.biz, that would be the only domain that you’d get. Once that is registered, other variations of the domain name in Chinese will not be allowed to register. This is a slight deviation from JPRS‘s appraoch, which treats them as distinct domains. We feel that this conservative approach offers better protection for the registrant.

So that was the skinny on our Chinese and Japanese Internationalized Domain Names offering. Is it me or do Han characters look very good with .BIZ? =)

Usual disclaimer about this being my personal opinion applies.

mod_python OpenID Access Control

Monday, January 15th, 2007

Since XRI is pretty much in bed with OpenID and NeuStar is an XRI shop, I get to play around with it quite a bit.

Here’s a little success report about using JanRain‘s mpopenid module to protect certain restricted resources served by Apache. It works somewhat like your basic HTTP authentication, but instead of returning a 401 Authorization Required response causing the browser to prompt for username and password, it redirects you to the OpenID login page. Pretty neat eh?

So, here's how we go about doing it.

My ingredients:

Following the recipes in this README file, I was able to set it up with one caveat: Python ElementTree module is a dependency of the Python Yadis library and you need to first install that.

Did I mention that you could login using an I-name?

UPDATE:

The following patch for mpopenid.py is needed to make i-name login work:

--- mpopenid-1.2.0-pre5/mpopenid.py     Tue Nov 21 20:24:53 2006
+++ mpopenid-1.2.0-pre5-wil/mpopenid.py Sun Jan 14 16:12:16 2007
@@ -157,10 +157,17 @@
         url = s.strip()
         if not url:
             continue
-        parsed = urlparse.urlparse(url)
-        if not (parsed[0] and parsed[1]):
-            url = 'http://' + url
-        urls.append(urinorm(url))
+
+        if (url[0:6].lower() == "xri://"):
+            url = url[6:] # strip "xri://"
+
+        if (url[0] not in "=@!$+"): # doesn't look like an XRI
+            parsed = urlparse.urlparse(url)
+            if not (parsed[0] and parsed[1]):
+                url = 'http://' + url
+            url = urinorm(url)
+
+        urls.append(url)

     return urls

NeuStar Launches 5 New Languages for .BIZ

Thursday, November 2nd, 2006

We launched 5 new languages for IDN in .BIZ today. They are Danish (da), Icelandic (is), Norwegian (no), Spanish (es) and Swedish (sv). Prior to this, the only language available in .BIZ was German (de), launched in October 2004.

I’d like to take this opportunity to thank DK-Hostmaster, ISNIC, NORID, NIC-SE and Cary Karp of MuseDoma for their help and advice on these tables. The work on these tables really started 2 years ago when we first had the intention to launch additional languages, so I am very proud and relieved that they made it out!

Here’s a summary of the non-ASCII characters available for registration:

Code Point Character Language Codes
U+00E0 à no
U+00E1 á is,no,es
U+00E4 ä de,da,sv,no
U+00E5 å da,sv,no
U+00E6 æ da,is,no
U+00E7 ç no
U+00E8 è no
U+00E9 é da,sv,is,no,es
U+00EA ê no
U+00ED í is,es
U+00F0 ð is
U+00F1 ñ no,es
U+00F2 ò no
U+00F3 ó is,no,es
U+00F4 ô no
U+00F6 ö de,da,sv,is,no
U+00F8 ø da,no
U+00FA ú is,es
U+00FC ü de,da,sv,no,es
U+00FD ý is
U+00FE þ is
U+010D č no
U+0111 đ no
U+0144 ń no
U+014B ŋ no
U+0161 š no
U+0167 ŧ no
U+017E ž no

If you’re looking to register a Scandinavian or Spanish domain name, visit your favourite domain registrar to get yourself one.
When you’re done and made a web site out of it, don’t forget to submit it to IDNSearch.NET!