{"id":353,"date":"2010-06-21T03:09:10","date_gmt":"2010-06-21T03:09:10","guid":{"rendered":"http:\/\/rigf.asia\/?page_id=353"},"modified":"2024-01-25T06:49:59","modified_gmt":"2024-01-25T06:49:59","slug":"aprigf-roundtable-june-16th-2010-session-2","status":"publish","type":"page","link":"https:\/\/event.rigf.asia\/2010\/aprigf-roundtable-june-16th-2010-session-2\/","title":{"rendered":"APrIGF Roundtable \u2013 June 16th, 2010: Session 2"},"content":{"rendered":"

Diversity: Challenges and Opportunities for Internationalized Domain Names<\/span>
\n________________________________________________________________________<\/p>\n

REAL TIME TRANSCRIPT: Diversity: Challenges and Opportunities for
\n Internationalized Domain Names
\n APrIGF
\n 11:15-12:30, Wednesday 16 June 2010
\n Hong Kong<\/p>\n

DISCLAIMER: Due to the inherent difficulties in capturing a live
\n speaker’s words, it is possible this realtime transcript may
\n contain errors and mistranslations. An edited version of the
\n realtime transcript which amends the inherent errors, will
\n be posted later. LLOYD MICHAUX and APrIGF accept no
\n liability for any event or action resulting from the
\n contents of this transcript.<\/p>\n

________________________________________________________________________<\/p>\n

Welcome back, this session is about challenges or
\nopportunities for internationalised domain names, can I
\nknow invite Professor Izumi Aizu to start the session
\nand introduce the panel speakers for us.<\/p>\n

This will be an interesting session, the overall
\nteam is diverse theme.<\/p>\n

As many speakers already said Asia and Pacific has
\nlarge earth sort of different groups of economy, ethnic
\nreligious language, whatever.<\/p>\n

Diversity sounds great, but to make it work, in this
\nworld, is not sometimes so great. It’s often blood,
\nsweat and tears.<\/p>\n

Today, I would like to pick up together with you,
\nthe one cased called internationalised domain name, IDN.<\/p>\n

It’s just a case study. It’s not the end by itself.<\/p>\n

We are very happy to have very interesting line up
\nand speakers.<\/p>\n

Actually, we have to speakers will give you
\ninteresting presentations, followed by case reports,
\nfrom those TLDs, who have successfully introduced or
\ngoing to introduce their IDNs on both in the CC space as
\nwell as in the case of DotAsia, the G space.<\/p>\n

Before going into that, I really would like to thank
\nall the people who made this whole forum possible and
\nalso the Hong Kong’s wonderful hosts.<\/p>\n

But without further ado, I would like to start from
\nsay 20 years ago or 15, the origin of the
\ninternationalised domain name.<\/p>\n

Can we, whilst the story starts from there.<\/p>\n

>>Tan Tin Wee: Thank you very much. Good morning, thank
\nyou.<\/p>\n

Thank you for the invitation for me to come here as
\ncontroversial statements and as Director General says,
\nstir it up and to come here as the first Asian Pacific
\nregional IGF.<\/p>\n

Thank you to all of you, old friends, comrades in
\nthe internet, colleagues.<\/p>\n

So it’s puzzling to me, as a professor in the
\nmedical school at the National University of Singapore,
\nand as the deputy head in the Department of
\nBiochemistry, and a pioneer of biometrics, that whenever
\nI get dragged out of the woodwork to an internet policy
\nit tends to raise eyebrows both ways, particularly shock
\namongst my internet colleagues to find a fake
\nunqualified misfit like myself to actually be in their
\nmidst.<\/p>\n

Indeed, why would a biochemist be involved in the
\ninternet, I mean, championing global multilingualisation
\nof the internet at that.<\/p>\n

Indeed, the generosity and camaraderie of friends
\nI have made in championing many initiatives as pioneer
\ndoctor of innovator technologies in the early 90s,
\na late comer, but made up for good time, from WAIS,
\ngopher, remember CU see me, or slip or PPP, and of
\ncourse WWW, how about VRML, music mark up notation
\nlanguage, I was involved in that, PO box mail forwarding
\nfor biochemist, it must be quite a challenge, internet
\nfor the hearing impaired, the visually handicapped,
\nmultilingual content, Java in 1995, internet 2 to the
\ngrid and cloud computing of today.<\/p>\n

Yes, the friendship of many friends here and
\ncolleagues have made up for all the pain and financial
\nloss and collateral damage suffered as the victim of
\ninnovation, suppression, not unlike that which Keith
\nDavidson alluded to in the previous session, the
\ngovernments might be complicit in, particularly the kind
\nof subtle suppression associated with the origins of
\nIDNs in the late 1990s, which, of course, I stand guilty
\nof inventing.<\/p>\n

So please forgive me in advance if I’m too blunt in
\nmy independent and unfettered comments and hopefully
\nmoderated by the kindness of Izumi and hopefully not too
\nbiased in my comments on IDNs origins.<\/p>\n

This, of course, is an old story, but a new and
\nlonger way of presenting it to be sure, eating into your
\nlunchtime, I’m sure.<\/p>\n

So let me present you a new good script for reality
\nTV, perhaps.<\/p>\n

IDN is the acronym for initialised domain names.<\/p>\n

The origins of IDN is indeed in Asia and it is quite
\nappropriate for this first AP Regional Internet
\nGovernance Forum.<\/p>\n

To at least have a few words mentioned about IDN, if
\nnot an entire session.<\/p>\n

The reason why domain names have to be
\ninternationalised is because it’s been and still is
\nnatively in the ASCII range of Latin characters, the so
\ncalled LDH, letters digits and hyphen. So make it
\nsupport and visual representation of all the languages
\nof the world in the global internet, we have had to
\nresort to the process of internationalising the domain
\nname system.<\/p>\n

This, of course, did not come easy, nor was it the
\nrationale for doing it obvious to the powers that be 12
\nyears ago, some say even now, especially when it was
\n1998 when we first started it in Asia.<\/p>\n

So it was said, let them all learn English. That
\nwas the mantra.<\/p>\n

Let them bridge the digital divide themselves.<\/p>\n

I mean, if you want to use the internet, which we
\nhave labelled and fought very hard to create and unify,
\nit’s just like if you want to write computer programme
\nor publish a scientific programme or fly a plane, you
\ncan jolly well my friend reminded us as the of analogy
\nI used 10 yearss ago while trying for the difficult IDN
\nmovement. Based on the IDN system, which had built and
\ntested in Asia in 1998.<\/p>\n

The paraphrase story goes.<\/p>\n

If the internet were invented not by Al Gore, but by
\na bunch of programmers from Thailand, who chose the Thai
\ncharacter set as the basis for rendering easily
\nmemorable strings indeed of a bunch of four IP address
\nnumbers, would anyone of us here except our Thai reading
\nfriends be able to use the would be able to be use to
\ninternet?<\/p>\n

Surely we could write an email in English, but we
\nwould have to memorise the email address of our friends
\nin the Thai alphabet.<\/p>\n

And over the phone, to keep in touch, OK, because
\nI’m reachable at this Google email address in Thai
\ncharacters and here, let me write it down for you and
\ndon’t forget to load your Thai keyboard on your qwerty
\ncomputer or else you would not be able to reach me.<\/p>\n

Or perhaps come to my Facebook and blog site in
\nEnglish, but you would have to navigate here in this
\nseries of Thai alphabets, otherwise you will be locked
\nout.<\/p>\n

This is the kind of linguistic barrier endured by
\nthe millions of non native English speaking non Latin
\ncharacter using people every day today. Ever since the
\nweb became popular in their regions, more than 15 years
\nago.<\/p>\n

Back in the summer of 1993, when Mark Anderson and
\nEric by that at NCSA got hold of WWW code from Tim Lee
\nand released the graphical interface to the web, and
\nopened the floodgates of the internet. The rest was
\nhistory.<\/p>\n

Or was it?<\/p>\n

The earliest web browser could not support
\nmultilingual characters. Neither could your favourite
\npine emailer from a terminal innovation that was seven
\nbit clean. But we could scan images of Chinese
\ncharacters for instance and put them on-line as web
\nimages. So in 1994, as early as that, we were one of
\nthe first few to put Chinese characters on-line as
\nimages.<\/p>\n

We used a converter to convert the Chinese encodings
\nand turn them into images.<\/p>\n

Why wait? We asked.<\/p>\n

By 1995, we were able to make use of the earliest
\nversion of unicode to turn unpopular unicode encodings
\ninto give I imagines, in the summer of 1995, when goes
\nLing released Java, we were the first few to build an
\nimage convert engine and later a gentleman have input
\nengine by end of 1995, we were able to lawn multilingual
\ncharacters on the web site, putting on multilingual
\ncontent was the key priority. For the global masses.<\/p>\n

By 1996, we even helped our Sri Lankan friends build
\na try listening wall website, perhaps to soothe ethnic
\ntensions.<\/p>\n

By 1997, multilingual support began to come on
\nboard, thankfully, a few years after netscape when IPO
\nin 1995 and Microsoft released internet explorer.<\/p>\n

They had to cater for the small but certainly
\ngrowing demand in the internet communities especially in
\nthe Far East.<\/p>\n

By the first quarter of 1998, it became clear to me
\nthat the bottleneck now was not the content, but it was
\nat the labels and the addresses. The domain names in
\nyour web address or in your email address.<\/p>\n

We had to figure out a way to solve this divisive
\nroadblock.<\/p>\n

The digital divide that was looming ahead.<\/p>\n

Why wait indeed?<\/p>\n

There was no way the IETF at that time could
\ncountenance the change the installed base of domain name
\nDNS servers that could read to make it read unicode or
\nany of its UTF transformations. To make it backwards
\ncompatible with ASCII.<\/p>\n

Nor was it likely that any of the Asians working in
\nAsia for multilingual internet able to penetrate
\na tightly knit club of internet engineers highly
\nproticktive of their precious bay they that was making
\na global debut. This was back in 1998. Today I hear we
\nare going IETF is going to Beijing soon.<\/p>\n

But this was after the victorious fight against the
\nOSI from the late 1990s as to 1994, you know,
\nreminiscent of the so-called standard war that we are
\nfamiliar with VHS, Betamax, TCP\/IP over OSI.<\/p>\n

As Daniel was quoted as saying, it was totally
\nirrational to make the international R&D community wait
\nfor international standards.<\/p>\n

He was saying that we should adopt TCP\/IP over OSI
\nat that time.<\/p>\n

This was especially when UNIX was built with TCPIP
\nand all one needed was a UNIX box and a modem and
\neveryone who wants to be connected can be connected.<\/p>\n

Why wait, the argument went.<\/p>\n

But for us, it was different.<\/p>\n

After that kind of bloody network war, no one had
\nthe stomach for anyone who wanted to touch the
\nfundamental infrastructure of the TCPIP internet that
\nthe DNS system had to affect.<\/p>\n

So the accepted wisdom was that you cannot support
\nmultilingual characters for domain names and you should
\nnot, because it has to be a machine readable label which
\nengineers far and wide can read, besides, it wouldn’t
\nwork, they said.<\/p>\n

Now, I didn’t know that, did I? I was a Cambridge
\nbiochemist, a UCL biotechnologist and an Edinburgh
\nmolecular biologist working in the Department of
\nBiochemistry at the National University of Singapore.
\nBut seconded to run the internet service provider of
\nSingapore in 1994 and asked to run the Internet Research
\nand Development Unit, I was pretty naive, wasn’t I?<\/p>\n

After I sold the ISP for 2.5 million for on behalf
\nof the university in 1995, they gave me 2 million bucks,
\nhere, you go do more internet research.<\/p>\n

I had to deliver results. I couldn’t wait. So
\nI went through the invention of IDNs, demonstrated
\nresults then. Perhaps now, hopefully, with a global
\noutcome.<\/p>\n

That was in 1998, around about March to May, when
\nI got my programmers to build a proxy domain name system
\nto convert multilingual characters in whatever language
\nencodings and get them converted into backwards
\ncompatible as I can.<\/p>\n

With dug around around found Martin desk at
\nWorldwide Web Consortium, having newly moved from
\nuniversity of Zurich across to Japan and he had taken up
\na dare by his network engineer friends and showed on
\npaper that his UTF5 conversion, this was in 1996, could
\nsupport a seven bit clean DNS system. This was first
\ndescribed when he was in the university of Zurich and
\nthe internet drafts which I downloaded yesterday. I’ll
\nshow that. This was back in 1996.<\/p>\n

This was of course shortly after France was and his
\nteam set up the A list technologies. You remember that.
\nSet up standards for multilingual HTML and
\ninternationalisation of the URL, RFC2070. But neither
\nMartin nor France was got around to having it I prettied
\nin a working model. France what was busy with Alice
\ntechnologies for translation and multilingual content,
\nand Martin was starting up in Worldwide Web Consortium.<\/p>\n

So my team and I in the internet R&D unit at the
\nuniversity of Singapore put the whole thing together,
\nthe first as a proxy solution.<\/p>\n

We also adapted the view row level domain name of
\nthe hidden ZLD of Martin’s design, which still today
\nChina has been using for .China and .com in Chinese,
\nsince the IDNA standards emerged in 2003, under licence
\nfrom our university spin off company which we set up
\nback then, which is of course still surviving today,
\ndespite the decade of delays by groups of people
\nI loosely attribute as the so-called ICANN process.<\/p>\n

Our investors put in US$4 million and then 20
\nmillion and just about lost it all.<\/p>\n

At that time, I also served as the newly elected
\nchairman of the Asian Pacific networking group, APNG,
\nfrom 1997 to 1999, because the same group that set up
\nAPNIC as a project first run by David Conrad and now by
\nPaul Wilson, very successfully.<\/p>\n

We also set up APTLD, if you recall. Of course, the
\nfailed WWTLD too.<\/p>\n

You can tell from the logo of APTLD that it was
\nquite unprofessionally done, with PowerPoint and
\na screen grab, because I too ran their first website
\nAPTLD.org and WWTLD.org and Korea and he had to have
\na logo, a nice little logo and that was the fastest
\nI could use, draw an elliptical blog and stick in the
\nwords APTLD and have some shading and then stick in the
\nwords.<\/p>\n

I’m impressed that he hasn’t changed, still there.<\/p>\n

Until that time, Asia was actually playing catch up
\nto Europe, which was also catching up on the Amranet, to
\nthe NSF transition in the US. We all bought into the
\ninternet as the global information infrastructure.<\/p>\n

This seemed to be our only contribution.<\/p>\n

As chairman of APNG, I had set up several chairman’s
\ninitiatives and research decisions, one for disability
\naccess and the other was, of course, multi-ling wall
\ndomain names.<\/p>\n

Being a lean outfit APNG was, whatever
\nI commissioneded I had to deliver it myself.<\/p>\n

So to cut a long story, why wait? We had to get
\nAsia to contribute technological advanced to the
\ninternet rather than wait pass civil to receive new
\ntechnologies from the west as early technology adopters.<\/p>\n

But this contribution was not to be. We faced
\nnumerous obstacles and as we now know, a 12 year delay.
\nThese were political roadblocks mostly, not really
\nengineering, since the IDNs that trumpeted worldwide
\ntoday with star fish power is still very much the same
\nIDNA standards which is very much fundamentally the same
\nbackward compatibles aski compatible encoding system we
\nhad a full implementation of by 1998.<\/p>\n

So why did we have to wait?<\/p>\n

First ira magcy that was tasked by president Bill
\nClinton to go around the world to get everyone to buy
\nthis idea that vice-president gore was the inventor of
\nthe internet, I just here, and to make the US preeminent
\nin internet technologies and put in place industry led
\nmechanisms, private sector mechanisms, to manage its
\noperation, namely the names and the numbers and to get
\nthe industry to run it rather than have government
\ninterfere.<\/p>\n

So he went round the world with Esther, the first
\nchair of ICANN, to sell a watered down white paper,
\nremember the IFWP? This was after the green paper reply
\nto the IHAC’s GTLD MOU was shot down by upset people
\nfrom the European theatre.<\/p>\n

So in the summer of 1998, we were there building our
\nIDN systems while the whole world was engrossed with the
\ninternational forum of the white paper, internet
\ngovernance was making its circuits, starting from Geneva
\nand wended it way to Singapore in August 1998, where we
\nnaively showed ICANN delegates our wonderful system to
\nbridge the linguistic barrier of the digital haves and
\nhave knots.<\/p>\n

The US Government was on tense bring looking for
\na new private stack holder led organisation to perform
\nthe role of internet governance.<\/p>\n

This was the big global fight they were talking
\nabout. White paper versus all comers. No time for puny
\nfolks solving digital divide props while they were
\npreoccupied with that struggle.<\/p>\n

The IDN people have to wait. That is what this in
\nfact origin of the IDN in 1998 illfated to be coincident
\nwith the less than legitimate birth of the ICANN tainted
\nby the same brush of illegitimacy that ICANN was at that
\ntime shrouded in, from its inception and some say still
\ntoday.<\/p>\n

Obviously IDN was ignored by 1998 for good reason.
\nIt had to be obviously they were busy with the survival
\nof the global information infrastructure in the throws
\nof struggling with its governance processes.<\/p>\n

These were the important issues of the day.<\/p>\n

IDN was deemed without commercial worth in 1999, we
\nproved it by commercialising I DNS into I DNS net
\ninternational and received the $4 million investment and
\nlater $20 million investment from investor which
\nI mentioned earlier.<\/p>\n

Meanwhile, over IDN companies with their own
\nsolutions were also being invent and and re-invented
\nfrom Jason powerful less in Australia, the first
\nsuperannuation.net to Edmon Chung’s net ca, back in
\nthose days, to Wah lid tout’s patents to the many that
\nsubsequently emerged, from teeth tier’s real names,
\nremember that one, Thai URLs, netpyia and other IDN
\nmimics to alternative roots to host these IDNTLDs.<\/p>\n

Those were the heady days. One hellfire of foment
\nand fiery interest in domain names or mimics in your own
\nlanguage by the dot-com boom of 2000, but hang on.
\nWait. IDN, you have no standards. Wait. So I sent my
\nstudent James Tseng, who was transferred from ANU back
\nto NUS, returned to in 1999 to work on IDNs and for the
\ncompany I DNS.net. Of course, the rest was history.
\nAfter four years of engineering squabbles and internet
\nare you lidge house wars, we all settled in 2003 on
\na set of standards, technical RFC standards collectively
\ncalled the IDNA, to push the backward compatibility to
\napplication level and that A in IDNA was the application
\nlevel solution as opposed to the server solution that we
\nhad in those early days.<\/p>\n

But wait, what about the policy and the governance
\nand the stakeholder process?<\/p>\n

What are you doing about that? So all these tech
\nknow be able was going on. We formed out of Asia in
\nSeoul 2000 the multilingual internet names consortium.
\nArguably the first global internet organisation
\noriginated out of Asia.<\/p>\n

In order to drive the governance processes related
\nto IDNs, as Asia’s contribution, if IHC and GTHL and got
\nredaled by the US locomotive, MINC was a pushover. Not
\neven with ITU blessings of sorts to co-host workshops in
\n2001 with PIPO and later with UNESCO in 2006, we
\ncouldn’t bet into the serious radar screen of ICANN
\nfallacy.<\/p>\n

We formed Arabic internet name consortium, Chinese
\ndomain name names, the joint engineering taskforce of
\nChina, Japan, Korea and Taiwan agreed of all things to
\nCJK internationalisations, to no avail.<\/p>\n

ICANN was just too preoccupied to countnance any
\nchange to the root, other than what was clearly liketive
\nand under their control.<\/p>\n

Once the IANA function was subordinated to ICANN
\nuntil this year when ICANN proclaimed full IDNs at the
\nTLD level, as a historic blessing brought to you by Tina
\ndam and the ICANN team let by rod, the new ICANN COE
\nfrom homeland security. Seven years it took for IDNA
\nstandards to reach this stage, this historic stage,
\nwhere we now are able to enjoy the fruits of IDN
\ntechnology.<\/p>\n

Seven years for IDN standards to be agreed before it
\ncleared ICANN’s multitude of internal processes before
\nit made a global rollout as Ram Mohan here, somewhere,
\nwould testify.<\/p>\n

They worked very, very, very hard. The ICANN
\nprocesses, the test beds, the IDN2LDs, et cetera, Ram
\nwill tell you about the engineering policy and political
\nrigour it went through.<\/p>\n

So much so at the end, instead of an Asia originated
\nIDNs with registries and registrars from Asia running
\ntheir own IIDNs as their own invention, it will probably
\nbe somebody else that will reap the first fruits.<\/p>\n

For after all, haven’t we all learnt English in the
\nlast 10 years who are waiting for go do to turn up and
\nwe have bridged the linguistic digital divide ourselves
\nalready. In fact, it is beneficial to learn English
\nthese days.<\/p>\n

We now have to pay back perhaps maybe 185,000 bucks,
\nhopefully with less ICANN discounts, just to check out
\nthe domain names in our languages OK or not, in case it
\nwere confusingly similar to the untrained westerner eye.<\/p>\n

True, what doesn’t kill us makes us stronger. But
\nit is not an invitation to kill us, please.<\/p>\n

It is a call for fair play.<\/p>\n

It is a call for legitimacy of internet self
\ngovernance of the people who own their languages.<\/p>\n

Perhaps some might say it’s a call for recompense.
\nThose who have lost money.<\/p>\n

I hope edmoney, you didn’t lose too much money in
\ntech ca.<\/p>\n

It’s a call for probity and honesty in our public
\ncommunications and to eschew over computer rant claims
\nfor undue credit for somebody else’s original work.<\/p>\n

Without a doubt, the origin of IDNs is in Asia. It
\nis our little but perhaps significant contribution for
\nenjoying the benefits of internet technology which we
\nhave adopted from the west.<\/p>\n

It is also our little attempt, our earnest attempt
\nto participate in the process of building and evolving
\nthe internet architecture through proper internet
\ngovernance processes, to serve a global need, which is
\nobviously taken over by ICANN processes these days.<\/p>\n

This was the original goal of IDNs, to play
\na rightful role in the development of solutions and
\ninnovations for our own problems which does not impact
\non the rest of the world because we made it backwards
\ncompatible and we were totally sold and supportive to
\nthe idea of a unique root under ICANN’s control, some
\nsay monopolistic control.<\/p>\n

We now have to press our patents on various patents
\nof IDNs and I think Edmon, you might have a few, right?<\/p>\n

Seek injunctive relief or retrospective royalties?
\nDo we want to get even with a few cents per domain name
\nof royalty and use of intellectual property with the
\nwhich pioneered or do we have to be pushed to create
\na global all termtive competitive root because the
\nexcesses of monopoly and absolute power are checked?
\nOnly time and perhaps IGF will tell.<\/p>\n

Meanwhile, worldwide wait, please. Thank you.<\/p>\n

>>Izumi Aizu: Thank you. I’m sure there are many diverse
\nviews on the diversity of IDN, from the floor, we will
\nwelcome you to make commentaries or comments later, but<\/p>\n

without further ado, I would like to introduce Prof Xue
\nHong, now representing Chinese Domain Name Users
\nAlliance and Prof Hong worked very hard within the ICANN
\nprocess when we were in the colleagues of advisory
\ncommittee. So she will tell what it takes to make the
\nIDN a reality within the IDN process.<\/p>\n

>>Xue Hong: Thank you the organiser. Thank you for having
\nme here and thanks the chair, Izumi Aizu. This is
\na wonderful opportunity for me to learn from all
\nexperts, especially from this region.<\/p>\n

I want to specially thanks Prof Tan whois very
\ninsightful and visionary presentation on the history and
\ntheories of IDNs. The last part is the most inspiring.
\nIt sounds like Martin Luther King’s I have a dream. The
\ndifference is we all have this dream, especially for
\nnon-English speakers, IDN is really going to be real,
\nafter so many policy and technical difficulty, is in
\npolicy and technical contours, eventually it’s going to
\nbe very real, we should really cherish the opportunity
\nwe are having right now, but I’m not going to repeat
\ndiscussion of ICANN and IDNs. for most of us, we are
\nactually in the ICANN process and IDN does not make much
\nsense for us to repeat that part, but yesterday,
\nMr Kummer, secretary general of IGF, mentioned one
\nissue, that is he used IDN as an example of the impact
\nof IGF on the global policy making, very good point.<\/p>\n

So went through what is being discussed on IGN at
\nIGF, a kind of stocktaking, what has been talking about
\nat IGF. This is different forum, apart from ICANN, but
\nis also an IDN. So that will be interesting idea. So
\nlet’s have a little review of IGF discussion.<\/p>\n

At IGF, they follow the principle of WSIS.<\/p>\n

A. Among this principle is language diversity
\nmultilingualism. So at IGF, IDN issues were primarily
\ndiscussed and the main session of diversity. Apart from
\nthat, the other main session on access, on the critical
\ninternet resources are also the relevant forums for IDN
\ndiscussion.<\/p>\n

I went through all the four IGF meetings held in
\ndifferent places. This is inaugural rating IGF held in
\nAthens. Now you can see that I cannot really see on
\nthat screen, it’s too far away for me.<\/p>\n

At Athens, IDN was identified as a nexus of
\ntechnology and policy issues.<\/p>\n

And people agree it is important to keep the balance
\nbetween language community’s involvement in decision
\nmaking about code points and maintenance of stability
\nand security of the internet.<\/p>\n

Second IGF, discussion move on. IDN was still an
\nintensefully discussed issue, but more people reached
\nthe limit of IDNs, especially in creating local contents
\nand caveats of causing phishing and other security
\nproblems.<\/p>\n

It was also mentioned IDN would need to cooperate
\nwith other application technologies, such as emails and
\nE address books to make IDN to be really useful.<\/p>\n

This is the third and fourth IGF. It seems
\ndiscussion on IDN went deeper into the diversity
\nconsideration of IDN management, which is really timely
\nfor ICANN’s fast-track add-in ccTLD and new gTLD
\nprogramme. We suspect this diversity of management on
\none hand, it was mentioned that new gTLD and regional
\nTLD reflecting local values, culture and history would
\nbe managed by people from the relevant countries and
\nregions.<\/p>\n

On the other hand, it was mentioned that the
\nimportance to introduce competition in selection of
\nregistry to run the new ITLDs.<\/p>\n

Now a few key issues I highlight. After reviewing
\nIGF. The first one I summarise as multi-stakeholderism.
\nThe second one I summarise as management issue of IDN.
\nThe last but not least, I have summised as access
\nissues, security and stability issue.<\/p>\n

Back to multi-stakeholderism, not only based on
\nprinciple of IGF practices, but also the reality of the
\ninternet. Multi-stakeholder is the only way for the
\nglobal policy making.<\/p>\n

There is no single sovereign state can govern the
\ninternet. There is no single law can really regulate
\nthe internet. There is no single international
\norganisation have the wide mandate to cover all the
\nissues on the internet and on IDN.<\/p>\n

So we have to involve all the stakeholders. All the
\nrelevant stakeholders are here listed on the screen.
\nThe first group I have listed as regulators, not the
\npolicy setting group, but also the technical group such
\nas ICANN. ICANN is not treaty organisation, it’s not an
\ninter-government all organisation, but obviously its is
\nmaking policy, very important policy, especially to
\nIDNs.<\/p>\n

The second group I summarise is industries and
\nservice providers. The registries, registrars, of
\ncourse they are making policies, they should be
\ninvolved. The last but not least is user group.
\nI labelled here as language community. IDNs as Prof Tan
\nvery wisely mentioned, is for the people who are really
\nused the native scripts, they are not the people who
\nwill really can be really frank for English. They are
\nthe people that need the script to access internet
\neffectively.<\/p>\n

I have summarised here the two statement made by the
\nchair summary in Hyderabad IGF. Users groups and here
\nis language community is actually salient for the IGF
\ndiscussions, so they are not kind of outsiders or
\nobservers, they are really stakeholder groups.<\/p>\n

Through the multi-stakeholder dialogue on IDN, I can
\nsee three levels for this multi-stakeholderism.<\/p>\n

The first level is for the efficiency.<\/p>\n

Think about this is issue on the internet, this is
\nan IDN, it’s highly complicated issue, even for the
\ninformation, it is difficult to go through stakeholder
\ngroup, by stakeholder group. Party by party, the one
\nIGO to another IGO. For the efficiency, would be better
\nto get everybody on the same room, on the same page, in
\nthe same room, so that’s for efficiency, but it’s
\nsuperficial level.<\/p>\n

We want deeper, we can see this is for acceptance.<\/p>\n

Everybody on the same page will take about the same
\nissue, even through the rough consensus, it will enhance
\nthe acceptability of the policy.<\/p>\n

But eventually, I want to emphasise the last but the
\nmost important value of multi-stakeholderism, that is
\nlegitimacy.<\/p>\n

Why we are making global policies? As an
\ninternational lawyer, I’m specially concerned the lack
\nof global law in the international law system, now we
\nhave an international law, but they are territorially
\nbased and enforced. There is no really global law. But
\nwe are now making global policies. Why are they
\nlegitimate and why are they enforced in why ICANN is
\nmaking a policy and IGF should be enforced in any part
\nof the world? The only legitimate reason is that
\neverybody involved and everybody agreed. I guess it is
\nreally new form of global democracy.<\/p>\n

Of course, maybe different from the traditional
\nrepresentative voting democracy.<\/p>\n

The second part I have summised is management. Even
\nat IGF, people have gone into the details of how to
\nmanage IDNs, very interesting and insightful. I can see
\nthree critical issues on management. First, how to
\nchoose IDN strings. Second, how to choose IDN
\nregistries operators. Thirdly, how to decide
\nregistration policies. Whether the registration should
\nbe open for all or is only limited within the language
\ncommunity, limited to that screen or we will allow mixed
\nscripts ITMs or whether we should consider other sorts
\nof morality or public order issues, to restrict certain
\nnames.<\/p>\n

Less are the very critical issues. That is why Paul
\nlast night mentioned IDN is more critical issue, this
\nmore critical internet resources. So it is more
\ncritical.<\/p>\n

What my concern, I’m not going to go through the
\ndetails of ICANN dialogue, it is very complicated, I be
\nthere is one issue that is so aware, especially to other
\npeople researching international law and global policy
\nand global governance, that is think about IDN is
\ndifferent from as ci domains. For as I can domain, as I
\ncan default governance power after the white paper. At
\nthat time, most sovereign states were not prepared to
\ngovern the internet and domain name system. It is very
\nmuch technical and irrelevant to policy, but for IDN,
\nover 10 years, ICANN has been working on this for 10
\nyears and many things happen in these 10 years.<\/p>\n

For many country who are really interested in IDN,
\nin these 10 years, they enacted laws.<\/p>\n

Their local laws effective in their territory.
\nThese law governing the strings of IDN, especially top
\nlevel strings. They govern the manager and operator of
\nthe IDN strings and they govern the registration policy.<\/p>\n

So I do see a critical issue I hope I ICANN
\nstakeholder would take note athat. We should avoid the
\nin fact scenario of clash of government, the territorial
\nlaws and the rules and the norms of the global
\ngovernance, how to reconcile these two strings of
\ngovernance that is very, very critical issue.<\/p>\n

But I do note that ICANN’s fast-track ccTLD it seems
\nthe first test of this IDN governance is going on quite
\nwell. I know Chris is here. He knows everything about
\nthis fast track. What’s the father of this. So far, so
\ngood.<\/p>\n

For fast-track, the string must be a meaningful
\nrepresentation of the ccTLD territory name.<\/p>\n

That’s well accepted.<\/p>\n

Following the principle and the operator, it could
\nbe the present registry of ccTLD or new registry as far
\nas supported by the local governments and local language
\ncommunity.<\/p>\n

A very good policy.<\/p>\n

The third one is generally flexible on the
\nregistration policy, but they must conclude contract
\nwith ICANN, even though it will be a light contract.<\/p>\n

So that is the practice right now. Fast-track
\nccTLD. I have raised generally smooth, but for the
\ngTLDs will be very, very critical.<\/p>\n

It seems many states sort of believe the kind of
\nownership over the top level strings in their language.<\/p>\n

So I wonder what would be the solution on that.<\/p>\n

It is a public order issue, would be adjudicated
\nthrough a resolution policy.<\/p>\n

The last point is security and stability issue.<\/p>\n

Of course, we want to prevent and punish the cyber
\ncrime, especially phishing. IDN fishing is a critical
\nand bad problem that cause terrible harm, especially for
\non-line banking and also we want prevent user confusion,
\neven though it is not a crime, we should think about
\npeople could be confused in IDN string.<\/p>\n

This is an interesting, I share one example, is from
\nBulgaria. Bulgaria file an application to ICANN, you
\ncan see the string, the left, that’s actually a Cyrillic
\nscript. They believe that is most representative string
\nfor their CCTLT territory name in their native script.<\/p>\n

But unfortunately, it seems very much similar to
\n.BR, that is ccTLD in ASCII for Brazil.<\/p>\n

So now we see this is highly complicated issue. For
\nIDN confusing similarity, normally we think about two
\nissues. One, whether it is confusing I will similar.
\nIn that language community, if it is Chinese character,
\nwe think about whether it is confusing to Chinese and
\nsecondly, we think about whether it is confusingly
\nsimilar to the relevant or language community. Say even
\nthough it is ID. In this Chinese character, it could be
\nconfusingly similar to Japanese, because we share many
\nscripts.<\/p>\n

But this is the third level. We have to think about
\neven though this is not a really relevant language
\ncommunity, we have to think about the user confusion at
\nthe global level, very complicated. Last but not least
\nis IP issue. You may be wondering why spell lek actual
\nproperty security and stability issue, because if we do
\nnot protect intellectual property, they won’t let us
\nstabilise the governance of IDN.<\/p>\n

IP industry very powerful. It’s not only powerful
\nICANN is powerful in the world, they are making their
\nown interest secured in all the policy setting forum.
\nWe can see the bad example of actor and couple of other
\nshowings on this strings in last thing I want to
\nmention, I was reminded by Prof Tan’s mentioning of the
\npatents on IDN I was not prepared on this point, but
\nit’s an IP professor, I’m so impressed by this issue,
\nthose technical pioneers, they are so unselfish, they
\ngive up to enforce their patent rights, that’s terrific.
\nBut I heard, unfortunately, some techies are prepared to
\nenforce their patent rights and it has been included in
\nthe IDN standards. I must say, this is highly
\ndangerous. This is really will danger the security and
\nstability of enforcement of IDN and their enforcement is
\nnot fair, even by law, because it is kind of violation
\nof the standards setting policy. They violate the
\ndisclosure obligation. They should disclose, I have
\npatent here and you want to include my patent in the IDN
\nstandards, I either give up my patent rights or I give
\nup my role charging rights.<\/p>\n

My conclusion is IGF is a unique global forum for
\nIDN discussions. It can discuss anything about IDN, not
\nonly the things that can be discussed in ICANN and even
\nthe thing they not been discussed in ICANN, but is very
\nimportant for IDN, not only on technologies, but also on
\npolicies.<\/p>\n

I hope IGF could be producing more deliverable
\noutput on the IDN policies.<\/p>\n

Of course, IGF is not a decision-making forum and
\nnever attempt to be such a forum, but according to the
\nrecent message from UN, it is not harm to produce more
\nadvices or recommendations on IDN issues to the
\nstakeholder groups and other international forums.<\/p>\n

That’s my presentation. Thank you very much.<\/p>\n

>>Izumi Aizu: Thank you Professor Hong for your very
\ninsightful interesting and forward looking intervention.<\/p>\n

Now you may see why we chose IDN as a best topic to
\ntalk about in diversity from this region.<\/p>\n

From origin to making reality, now the task of
\ncarried by these speakers. With the help of APTLD,
\nbecause we have difficulty in selecting the speakers,
\nbecause so many ccTLDs in Asian Pacific are going to
\nintroduce or introducing the IDNs. So which one to
\nselect was a challenge, but anyway, there are three case
\nreports or four.<\/p>\n

Also, gTLD.Asia, but which order. Is China ready?
\nShariya Haniz Zulkifli, please, from Malaysia.<\/p>\n

>>Izumi Aizu: Unfortunately, I give only five minus
\nminutes.<\/p>\n

>>Shariya Haniz Zulkifli: Hi again.<\/p>\n

Again, it’s to talk about Malaysia’s experience with
\nregards to IDN and I do feel that what we have gone
\nthrough is obviously very different from some of the
\nother countries. I’m assuming that some, most of you,
\nhave been to Kuala Lumpur. I’m sure you would have
\nnoticed that our signposts are in Roman alphabets.<\/p>\n

The issue that we have for IDN as I mentioned, is
\nnot the same way as it is for Hong Kong, China, Japan,
\net cetera.<\/p>\n

But we do have other scripts that communities use.
\nWe have a multiracial community. This is why we are
\nthinking of introducing IDNs to .my.<\/p>\n

That was a bit of context setting.<\/p>\n

There are three scripts that we are looking at.<\/p>\n

Jawi, which is a subset of the Arabic script,
\nChinese and Tamil characters.<\/p>\n

Again, this is a reflection of the communities that
\nexist in Malaysia.<\/p>\n

The target date for IDN launch in Malaysia and for
\nus it is at the second level, is in December this year
\nand we feel that it will benefit many Malaysians, in
\nparticular those communities that use these three
\nscripts widely.<\/p>\n

Just a bit more updates, we have our policy
\ncommittee still ongoing. They’re meeting again next
\nmonth in July, so that should have a few more
\ninteresting items for us, in particular whether we are
\ngoing to use a mix of traditional and simplified Chinese
\nthat’s still up in the air for us.<\/p>\n

We are very excited for June, because we are
\nactually conducting a survey to see the preparedness or
\nreadiness of Malaysians in accepting and using IDNs, so
\nI hope to have an update on this actually at our next
\nAPTLD meetings.<\/p>\n

Who are the policy committee members? I expect to
\nhear a few groans from the floor, it is headed by a law
\nprofessor.<\/p>\n

A cross-section, cyber security, other lawyers, we
\nwork very closely with our national standards body and
\nalso a few representatives from the ISPs.<\/p>\n

Whatever policy documents that are formed would have
\nto go to the regulator MCMC for them to endorse or
\nsupport.<\/p>\n

The IDN test bed is on, so if you would like to take
\na look, that’s the URL. These slides will be provided
\nto the secretariat. It also has our virtual keyboards.<\/p>\n

Some information on milestones again, you can take
\na look at them, if you’re interested.<\/p>\n

What I do want to point out here is that as far as
\nthe top level domain IDNs are concerned, we are still
\ntaking a much closer look at this. As I explained,
\nthere are three scripts that we are looking at. So we
\nare still reviewing this and we’ll keep you posted.<\/p>\n

That’s the second level implementation plan, in
\nthree languages.<\/p>\n

This is a screenshot of our virtual keyboard.<\/p>\n

For the Jawi keyboard we worked again closely with
\nthe standards Malaysian, for Chinese and Tamil, it was
\nmore readily available.<\/p>\n

.my domain registry submitted our Jawi language
\ntable in June to IANA, so we are still waiting for some
\nfeedback.<\/p>\n

I do need to stress that we have very much looked to
\nother ccTLDs, other countries for guy dances. Of
\ncourse, there are others who have pioneered this, so for
\nJawi, which is a subset of Arabic, we have looked to
\nSaudi Arabia and the Middle East. For Tamil, India has
\nbeen a strong source and of course for Chinese, CTNC.<\/p>\n

In fact, for Chinese and Tamil, we will probably
\njust adopt these existing tables.<\/p>\n

Some examples of our websites, these are Chinese
\nwebsites for the Malaysian market.<\/p>\n

Tamil, Jawi, et cetera.<\/p>\n

Just to share with you that local content
\ndevelopment is very important for Malaysia.<\/p>\n

There was some information on Dr Sharil’s slides
\nyesterday on what MCMC is doing to push the development
\nof local content. There are also other grants given out
\nby other development agencies, such as the multimedia
\ndevelopment corporation.<\/p>\n

Of course, content is a key growth area for national
\npolicies.<\/p>\n

Just to quickly wrap up with impact of IDN,
\nobviously because there is this content in the local
\nscripts, obviously having the local script at the domain
\nname level will complete the process.<\/p>\n

We hope that this will further enhance the ties
\nbetween the cultural groups in Malaysia.<\/p>\n

Some of the language professors were very excited
\nabout IDN, because it meant that this would share our
\nMalaysian, I was going to say peculiarities, but unique
\nwords in how we express ourselves and share this
\nglobally.<\/p>\n

For me personally, I feel that translation will
\nbecome very, very important to bridge these various
\nscripts and I’m very happy to read a few days ago that
\nthe education ministry is considering looking into
\nmaking Mandarin and Tamil compulsory in national
\nschools, so they are looking into that.<\/p>\n

If this creates new employment opportunities in
\nstudents and languages and linguistics, all the better.<\/p>\n

The Chinese, Indian and Middle East markets are very
\nimportant to Malaysian businesses, so we hope that IDNs
\nwill help facilitate this as well.<\/p>\n

Thank you.<\/p>\n

>>Izumi Aizu: Just one quick question, I’m sorry, Shariya,
\ndo you have any target date for introduction?<\/p>\n

>>Shariya Haniz Zulkifli: It has to be by December 2010.<\/p>\n

>>Izumi Aizu: That’s short.<\/p>\n

While waiting for the projector to be connected,
\nlet’s see. How many of you guys plan to register your
\ndomain in IDN? Could you raise your hand? Have you
\nseriously considered it yourself will plan to register
\nyour IDN domain name?<\/p>\n

Not too many yet. It’s sort of a certain question,
\nbut hope that we’ll see more hard next year regional
\nIGF.<\/p>\n

But without further delay, Ms Tulika Pandey from
\nIndia, the Ministry of Information Communication
\nTechnology. Very diverse country of India. How many
\nIDNs do you need? It’s interesting question.<\/p>\n

>>Tulika Pandey: Good afternoon, everybody. I would first
\nlike to take this opportunity to thank the organisers
\nfor organising this Asian Pacific so soon and so well
\nthat it has brought representation from almost all of
\nour countries, which is in Asian Pacific.<\/p>\n

I would like to thank Izumi Aizu for giving me this
\nopportunity to talk about the diverse situation in case
\nof IDNs in India.<\/p>\n

I have decided not to let technology be a hindrance
\nto my quick run through of what it implies for us in
\nIndia.<\/p>\n

Most of you by now are by heart aware of India
\nhaving 22 languages supported by 11 scripts and we have
\naround 2,000 dialects.<\/p>\n

So the issue of IDN implementation, so the effort
\nfor us for IDN implementation would really be very
\ncomplex.<\/p>\n

We have around four major language families. Out of
\nthese 22, we have the representation that you can see,
\nthat is and many of the Himalayan languages are still
\nunclassified.<\/p>\n

However, are for sure that we at least have 22
\nofficial languages identified and supported by 11
\nscripts.<\/p>\n

Just to give you a flavour of what the country is,
\n35 states and territories, a mix of usage of languages
\nas the official lack.<\/p>\n

If you see, you have Bangla used both in Assam and
\nBengal. And they now read the script that is used,
\nHindi is used in many states.<\/p>\n

So this was the easy part. If you had one language
\nsupporting many states, it was an easy part for us.<\/p>\n

The difficult part was if you look at the last, the
\nscripts that are there, to manage all these languages,
\nso that made it complex for us.<\/p>\n

Just to give you a flavour of the demand for
\nlanguage in our country, we have the young, they are
\ninterested in this technology. They are very keen on
\nusing technology for.<\/p>\n

Yes, the citizens who are now in the middle age or
\nbeyond are also finding it convenient to use this
\ntechnology for their purposes.<\/p>\n

There is a demand for many language in the country
\nand since I have very short time, I am going to just
\nskip through some of the slides and say that we have
\nthese challenges of standards, because you had multiple<\/p>\n

input and storage of the same string. Therefore, you
\ncould actually get the same string through two different
\nmethods and therefore, you had two different code points
\nfor the same string.<\/p>\n

Therefore, it was very important for us to see that
\nthese get normalised.<\/p>\n

In the case of the unicode, we have unicode version
\n3.2 for IDNs and 5.2 today.<\/p>\n

The 5.2 covers most of our character scripts and we
\nwould be happy if that is allowed for IDN
\nimplementation.<\/p>\n

Last but not the least, we have multiple languages
\nfrom the same code page.<\/p>\n

So the code page would be shared by at least 7 to 8
\nlanguages and therefore, it is very important for us to
\nUnited Kingdom I will identify the language character
\nset for each language.<\/p>\n

In addition, we have the drawbacks of not really
\nhaving taken on language and encoding protection in some
\ntime, so we are in the process.<\/p>\n

We are ready with dictionaries, spell checkers and
\nthese which are very important for supporting many
\nlanguages.<\/p>\n

The text to speech and the speech to text support is
\ncoming up very fast.<\/p>\n

We have demonstrated or almost 90 per cent accuracy
\nthere, but the OCRs the optical character recognition
\nsystems, are still not of the level that wore support
\na lot of Indian languages coming on board.<\/p>\n

Most important, as mentioned earlier, too,
\ntranslation tools are most important to us.<\/p>\n

So that we, amongst the same country, are able to
\ncommunicate between two different language, linguistic
\ngroups.<\/p>\n

I can skip these slides.<\/p>\n

The one important part is the trade marks are in
\nindik scripts, so we do not know how to handle issues of
\ndomain management.<\/p>\n

These are the important linguistic challenges that
\nI would like to bring forth. I already mentioned that
\none language written in more than one script and one
\nscript supports more than one language.<\/p>\n

We have variants not just within the same script,
\nbut across the scripts.<\/p>\n

If we include numerous written in our Indian
\nscripts, we would have an issue of scripts and the
\nnumerals getting mixed up to form strings which would
\nlook very similar to words, to characters made out of
\nthe variants there.<\/p>\n

Then we have both type of scripts. We have script
\nwritten left to right and we have languages where right
\nto left.<\/p>\n

So we have to manage them, too.<\/p>\n

There is a very common use of intermixing of scripts
\nto write in many languages.<\/p>\n

The most important, we have above and below. To
\nmanage above and below that URL that is available to us.
\nThat makes us very difficult to handle home graphic
\nissues of that font size.<\/p>\n

So we needed standards, we do have some. We manage
\nto use unicode page. We essentially needed script
\ntagging with languages and we needed fonts which are
\nuniform and is acceptable to all browsers.<\/p>\n

We needed interface tools, so we talked about fonts
\nand keyboards, we have developed those.<\/p>\n

And for registration, we have developed a back-end
\nregistration process, using.<\/p>\n

We have also identified the language character table
\nand the variant table.<\/p>\n

I do not know if I can — these are some of the
\npolicy issues that we have incorporated in our draft
\npolicy which is present as RFC for the community at
\nlarge to comment, so that we are able to finalise the
\npolicy for IDN implementation, both at the ccTLD and the
\nsecond level.<\/p>\n

This is what it would look like for Indian scripts.
\nThis is only one script that I have put forth here as an
\nexample.<\/p>\n

What we have done is to only taking variants, not
\npure consonants. Because if we had we would have
\ndebarred more than 80 per cent of domain names per
\nscript.<\/p>\n

Therefore, we had to agree that pure consonants,
\neven if they look very close to each other, are
\nidentifiable by the native speakers and therefore, we
\nwill not use them as variant, in the variant tables.<\/p>\n

This was an example for Hindi, which is in the
\nscript. What we have done is identified for Hindi from
\nthe table, the unicode table.<\/p>\n

These are the restriction rules, I can’t go through
\nthat now. It has very little — this is the ABN
\neffective that we have identified. For each of these
\nlanguages, we have brought out unique ABNF policy rules.
\nWe have unique language character tables and you teak
\nvariant tables.<\/p>\n

Yes, we have the floating keyboards available to our
\nregistrants and registrars.<\/p>\n

>>Izumi Aizu: I really need to ask you to wrap up.<\/p>\n

>>Tulika Pandey: I was just giving an example. We did also
\ndo a study on what the browsers respond to our Indian
\nscript content. Therefore, this was what we have
\nrealised is beyond IE6 internet explorer 6.0, we are
\nable to go through the I Indian pages.<\/p>\n

These are the last slide. We share Hindi with Fiji,
\nUrdu with Pakistan, Bangla are Bangladesh, Nepali with
\nNepal, Tamil with Singapore, Sri Lanka and Malaysia and
\nour intent is to normalise our language character tables
\nand variant tables as far as possible, so that we are
\nall on the same page and there are no issues in the
\nfuture gTLD requirements or the TLDs in that sense.<\/p>\n

India has recently submitted its request for seven
\nID in seven languages. We have 22, so we somehow have
\nchosen seven at present and it has been accepted by
\nICANN. They are in the process of confirming the
\nstrings first and then we will go further to IDN.<\/p>\n

Thank you.
\n17<\/p>\n

>>Izumi Aizu: Thank you very much.<\/p>\n

I myself fit a little bit unfair to give only five
\nminutes to the billion population and 22 official
\nlanguages, so I gave three extra minutes plus.<\/p>\n

Then we have another large country of China. Mr Mo,
\nare you ready?<\/p>\n

Then we have additional speaker in the meantime,
\nwhile you are setting the projection. Mr Kim Dowon from
\nKorea.<\/p>\n

>>Mo Rungang: I do not have a presentation, so I don’t need
\nthe screen.<\/p>\n

Thank you monitor Izumi and thanks Prof Tan for the
\nexcellent speech and Dr Hong as well.<\/p>\n

As everybody can see, IDN is very hot topic, it is
\nvery diversified and China has the bigger IDN internet
\nusers and we are about to see, as Chinese IDN become
\navailable.<\/p>\n

I think it has a huge impact on internet, the way
\ninternet grow, so I don’t have a presentation. I’m only
\ngoing to share some of thoughts of mine on how IDN has
\nchange our lives.<\/p>\n

I feel thankful for everyone here for being here
\ntoday and giving me this opportunity to talk about IDNs,
\nbut I’m feeling a little sorry for myself, because it’s
\nmy son’s birthday today and I’m supposed to be with him
\nin Boston.<\/p>\n

Anyway, back to our topic of IDNs and particularly
\nChinese IDNs. I want use example of Twitter. I believe
\neverybody in the room use Twitter more or less and for
\nthose people who are familiar or use Chinese languages,
\nthey will notice the difference of 140 characters. With
\nChinese languages, you can pretty much say anything you
\nwant to say with 140 characters. With that, my personal
\nexperience with using English language is not possible.<\/p>\n

So Chinese language is very rich, meaningful
\nlanguage, it is a beautiful language, so is Chinese
\nIDNs.<\/p>\n

As many people over here may already hear that China
\nhas over 404 million internet users today. It’s growing
\nevery day.<\/p>\n

So if you can imagine for all those people who are
\nnot able to use the internet because of the language
\nbarrier, now it’s their time, their time has come.<\/p>\n

If you imagine for millions and millions of Chinese
\ninternet users getting on line by being able to use
\nChinese IDN to access the internet, that’s going to
\ncreate a huge impact on the internet economy and a lot
\nof other things as well.<\/p>\n

So I’m a very enthusiastic IDN promoter. I only
\nknow IDN from fairly recently, but I think Chinese IDNs
\nhas a great potential.<\/p>\n

As many things has its good side as well as its bad
\nside and I think as everybody already see, IDNs becoming
\na very hot topic and a lot of things presented by
\nProf Xue and Prof Tan is actually reflected some hot
\nissues inch my conversation over here is pretty light,
\nso I don’t want to get into all that, but my personal
\nexperience is some of my thoughts about Chinese IDNs and
\nhow it is going to change our life is pretty mature, but
\nI still want to throw it out and share with you guys.<\/p>\n

One thing I could think of, because of the IDN
\nChinese IDN become available and it will create new
\nchallenges for the policy and governance from the
\nregional and international perspective.<\/p>\n

To make my speech short over here, I just briefly
\nmention another thought I have. It’s also premature.
\nIt might sound a little crazy, but I still want to say,
\nlike when the first plastic bag was invented, nobody had
\nthought of its going to become a huge problem for the
\nenvironment. Nowadays, everybody thinking living green,
\nsaving energy, but with IDNs, we are going to have
\nmillions and billions of new contents, because
\navailability of the new IDN.<\/p>\n

So with the technology evolving, if we cannot catch
\nup quickly enough with rapid growth of IDNs, we might
\nfacing a new problem of environmental problem.<\/p>\n

But this is not directly connected to IDNs. I think
\nit’s more like internet related for us to think about.<\/p>\n

That’s all I have for all of you. Again, thank you
\nvery much.<\/p>\n

>>Izumi Aizu: Thank you, Mr Mo, for your very concise and
\nvery interesting observation. Now I would like to give
\nthe floor to Mr Kim Dowon for the Korean experience.<\/p>\n

Then we move into the G space.<\/p>\n

>>Izumi Aizu: In the meantime, I have a feeling that we may
\nrun over. We started 20 minutes late, so we may end 15,
\n20 minutes later than scheduled before lunch, for your
\nappetite.<\/p>\n

>>Dowon Kim:<\/p>\n

While waiting, are there any people in the floor who
\nwant to make comments or questions? Just tentatively,
\ncould you raise your hands to see how many are there?<\/p>\n

Only one? Later, we’ll see.<\/p>\n

I encourage you to raise some comments, questions.
\nDon’t be bothered by the time constraints.<\/p>\n

If there are only a few to raise hands, I would
\ninvite or encourage or nominate some of the leadership
\npeople here.<\/p>\n

>>Dowon Kim: I’m Dowon Kim. It is .kr country code.<\/p>\n

I would like to talk about IDNTLD development in
\nKorea.<\/p>\n

Everybody hungry, so I quick start and finish
\nquickly.<\/p>\n

In 2009, we made IDN internationalised domain names
\nadvisory committee on January, but we need more meeting
\nto take opinions from the very different kinds of
\nsociety in Korea.<\/p>\n

So we organise the KINNF, Korea Internet Names and
\nNumbers Forum in November.<\/p>\n

But at the time, we should decide which character is
\nproper for IDNs, ccTLD in Korea, especially this
\ncharacter in Korean.<\/p>\n

So we made a survey and several public forums from
\nthe December 2009 and February 2010.<\/p>\n

In 2010, we decided Korean IDN ccTLD string is
\n.hangu.<\/p>\n

So we applied for IDNCCTL, the fast-track in May.<\/p>\n

Now we are waiting for ICANN’s approval.<\/p>\n

We have some issues before introducing Korean IDN
\nccTLD, like registration policy issue and circumstance
\nin Korean domain.<\/p>\n

Many Korean people may think, what is different from
\nhangu.kr domain and .hangu domain IDN ccTLD.<\/p>\n

We already use hangul.kr, but somebody complained.
\nI already have hangul.kr. But we spent more money to
\nhave another domain, so this is unfair.<\/p>\n

So we are discussing hangul.kr and .hangu IDN,
\nccTLD, is same domain space or not.<\/p>\n

We also discussing blocked and reserved names.<\/p>\n

The most important thing is our internet usage
\ncircumstance.<\/p>\n

As you can see that half of Korean people use
\ninternet explorer 6. As you know, Internet Explorer 6
\ncannot convert IDN to ASCII domain.<\/p>\n

That means IE6 cannot recognise character other than
\nASCII, so that is a serious problem with us.<\/p>\n

This is final chapter.<\/p>\n

So we should continue cooperate among the local
\ninternet community and finalise the registration policy
\ndiscussion, like reserve and blocked names, sunrise
\npolicy, registration fees, dispute resolution in KINNF,
\nKorea Internet Names and Numbers Forum.<\/p>\n

We require government approval.<\/p>\n

Also, we expect IE6Nomore campaign in the second
\nhalf of this year.<\/p>\n

These processes are finished, then we will begin
\nKorean IDN ccTLD registration next year.<\/p>\n

That’s all what I prepared.<\/p>\n

Thank you very much.<\/p>\n

>>Izumi Aizu: Thank you, Mr Kim, for your very interesting
\npresentation about the .hangu. That means the
\nabbreviation of your country name.<\/p>\n

>>Dowon Kim: Yes.<\/p>\n

>>Izumi Aizu: As well as the characters too, or is it
\ndifferent?<\/p>\n

>>Dowon Kim: We are Korean nation, that is a long one, that
\nis short one..<\/p>\n

>>Izumi Aizu: Last but not least, from the G space, but
\nDotAsia is sort of pioneering the domain name with the
\nregion name or geographic name on the one hand, and with
\nvery interesting many initiatives as we may know.
\nEdmon, what is your view on IDN.<\/p>\n

>>Edmon Chung: Thank you, Izumi.<\/p>\n

You asked a question earlier about who is ready to
\nuse IDNs, who is interested in registering IDNs.<\/p>\n

That’s a very valid question, I think, and that is
\na question I always asked my audience as well.<\/p>\n

But I think another important value of IDNs is if
\nyou ask the audience in Asia especially, what language
\nyou use when you search on a search engine, that’s
\na very important aspect of IDN, because beyond the
\nsocial values that I think tin wee and Xue Hong
\nmentioned, there is also economic and commercial values
\nand search engine optimisation is one of them and.<\/p>\n

Because almost all searches in China, Japan, Korea,
\nin the Arabic region is actually using their own native
\nlanguage, when people say that search engines will take
\nover domains, I take a different view, especially being
\ngTLDs, I guess, we take a very different view, because
\nIDNs will, in fact, become — IDNs would actually create
\na much higher perceived value in Asia, once people
\nrealise the importance of having domain names to support
\nsearch engine optimisation.<\/p>\n

So that’s one important aspect that I would like to
\nbring up.<\/p>\n

The other is an interesting thing that I start to
\nrecognise, is that there is a heightened respect for
\nintellectual property rights as domain names are being
\nperceived better and as IDNs are being introduced.<\/p>\n

Because people, small, medium sized companies from
\nChina, from India, suddenly realise that their name,
\ntheir brand name, is important and when people start
\nusing their name, especially in IDN, they feel the pain
\nand that actually helps heighten the respect for
\nintellectual property rights in the region, I think.<\/p>\n

These are some, I just want to start with some
\nimportant sort of IDNs in Asia.<\/p>\n

Just illustrate a point, really SEO, the search
\nengine optimisation is important, I already went through
\nin saying that some of the parts, I mean, in Japan, in
\nKorea, in China, people most of the time use Chinese,
\nJapanese, Korean and their local language search and
\nthis is going to make a different for IDNs.<\/p>\n

Again, businesses, they use their own names and this
\nis why I think IDN is important and is also important
\nfor gTLDs as well.<\/p>\n

Going to update on DotAsia, we are planning the
\nlaunch of IDNs in DotAsia in the latter part of this
\nyear.<\/p>\n

Going through to next year.<\/p>\n

Like our ASCII DotAsia launch, we will be going
\nthrough a multi-phase process through the sunrise and
\none of the interesting thing I think I was mentioned by
\nmy colleague next to me from Korea is that there is
\nobviously a concern for I already have a DotAsia domain
\nthat’s sort of reflects my identity. Now why do I want
\nan IDN as well? Why do I have to pay for an IDN as
\nwell?<\/p>\n

So we are providing considerations in the opening
\nperiod for current English or ASCII DotAsia domain users
\nand also we are committing to grandfathering
\nregistrations, especially for like Chinese.ASIA, into
\nChinese.Chinese or native language.native language Asia.<\/p>\n

In that particular language.<\/p>\n

So these are some of the policies that are being
\nconsidered.<\/p>\n

Another important consideration in our policy
\ndevelopment is that we are finding that IDN and ccTLDs
\nand gTLDs could be different, especially in the language
\npolicies.<\/p>\n

The reason being that take the example of Chinese
\nand Japanese as an example. In .JP, for example, it is
\nonly expected that the domain itself is going to be in
\nJapanese. In China, for example, .cn, it is expected
\nthat the Chinese is in Chinese. That the IDN is in
\nChinese.<\/p>\n

But the situation might be different.<\/p>\n

When you register a Chinese character or canjy
\ndomain in under.Asia, you are not sure where it is
\nsupposed to be Chinese or Japanese.<\/p>\n

The reason why it is significant is that in the
\nlanguage policy for Chinese, simplified Chinese and
\ntraditional Chinese are considered the same. If you use
\nthe Chinese language table, then, say, the example
\nthere, China.Asia in simplified Chinese and China.Asia
\nin traditional Chinese is considered the same. But if
\nyou use the Japanese language table, they are considered
\ndifferent.<\/p>\n

So what happens under .Asia, how do we implement,
\nhow do we combine these two situations, especially when,
\nlet’s say, China, these two characters, are being
\nregistered under the Japanese language table.<\/p>\n

This is some of the considerations that DotAsia is
\ngoing through for implementation of IDNs and gTLD area.
\nIt is analogous also to Arabic, so Chinese is not the
\nonly issue and Arabic also.<\/p>\n

We are going through the process of implementing and
\nwe also have the first showcase domain, which is Jacky<\/p>\n

Chan’s latest movie, utilising a Chinese.Asia domain.
\nWe are quite excited that it’s on buses and posters
\neverywhere. My last slide is just to say that every
\nDotAsia domain does contribute to internet development
\nin Asia, such as contributing to this forum, RIGF and
\nmany other forums.<\/p>\n

Thank you.<\/p>\n

>>Izumi Aizu: Thank you, Edmon.<\/p>\n

With the little start up project Tin Wee you started
\n17 years ago or something, now we are seeing a lot of
\nyour grandchildren.<\/p>\n

Before opening the floor to the question, I just,
\nwith privilege of moderator, would like to give one
\nquestion to all the panel members.<\/p>\n

Let’s in 10 years from now, where we have majority
\nof IP addresses migrating to IPV6 hopefully, do you
\nthink that your IDMTLDs in your CC space or DotAsia will
\nhave majority than the ASCII or not? It still remains
\nas a minority space? Which one do you foresee? Let’s
\nsay from Asia to Korea to India, Malaysia to China.<\/p>\n

>>Izumi Aizu: Just say “yes” or “no”. Does it go to
\nmajority or not?<\/p>\n

>>Edmon Chung: Can I answer little bit longer?<\/p>\n

>>Izumi Aizu: Yeah.<\/p>\n

>>Edmon Chung: This question I answered 10 years ago, 12
\nyears ago, in fact, is that I think the more important
\naspect is that I think 10 years if now, people will find
\nthat IDNs is nothing new and people will really think
\nthat it’s just part of the internet. They will take it
\nfor granted and not think it’s something other than
\nEnglish.<\/p>\n

>>Izumi Aizu: Thank you for your diplomatic answer. How
\nabout Korea.<\/p>\n

>>Dowon Kim: Korean people familiar with Korean character,
\nbut major language probably ASCII, I think so.<\/p>\n

>>Izumi Aizu: India with 22 language and 11 scripts.<\/p>\n

>>Tulika Pandey: The answer is a strong yes.<\/p>\n

>>Izumi Aizu: How about Malaysia? It is obvious question
\nor not?<\/p>\n

>>Shariya Haniz Zulkifli: If I knew that, I would be rich
\nand happy and famous, but, no, I think Malaysia’s
\nposition is a little bit unique, in the sense that I as
\nI mentioned we do use Roman alphabet, so I think it
\nmight probably be ASCII.<\/p>\n

>>Izumi Aizu: But you mention it is sort of the
\nintersection from Arabic and Chinese cultures.<\/p>\n

>>Shariya Haniz Zulkifli: True.<\/p>\n

>>Izumi Aizu: China, with 404 million users, in 10 years,
\nit could be a billion users.<\/p>\n

>>Mo Rungang: I think this is a very difficult question.<\/p>\n

If I’m a psychic, I will say Chinese, but honestly,
\nI think it has to do with a lot of other things, so it
\nis very hard to predict in 140 years, a lot of things
\ncan happen. Not just internet itself, it has to do with
\nthe governments and policies and as everybody knows,
\na lot of things going on, so it’s really hard to say.<\/p>\n

>>Izumi Aizu: Prof Xue, you also have the same?<\/p>\n

>>Xue Hong: China has a population of 1.3 billion and now
\nthere’s only 400 million on-line. So we have great
\npotential and as far as I know, the English penetration
\nin the whole population is less than 240 per cent. So
\nI assume in 10 years, if domain name is still relevant
\ntechnology and is mainstream application for internet
\napplication, I assume the Chinese characters will be the
\nmain domain name in Chinese Chinese market.<\/p>\n

>>Izumi Aizu: I think there could be some youngsters like
\nTin Wee 17 years ago, may come up with brilliant idea
\nfor domain name to go out of business.<\/p>\n

>>Tan Tin Wee: I’m sorry, I’m trying to do the psychic
\nthing as he mentioned, but I just cannot read Peter’s
\nmind, so maybe he would like to say something about
\nthis.<\/p>\n

>>Izumi Aizu: Thank you for your answer.<\/p>\n

The floor is open. Any questions, comments for the
\nprevious ones?<\/p>\n

>>: I’m Blogie Robillo from the Philippines.<\/p>\n

It’s rather unclear to me. Are the IDNTLDs specific
\nright now to ccTLDs or, I mean, is there someone or or
\nis ICANN going to decide that, OK, per country, there’s
\ngoing to be an IDN or is this like gTLDs where any group
\nthat’s interested can create an IDNTLD and then, for
\nexample, for me, I study Japanese, so I be interested in
\na Japanese language IDN, but I would not be interested
\nin .nihon or .nihongo.<\/p>\n

Then brand name domains also, if IDNs come out and
\nthen our brand names are going to be protected or is
\nthere going to be a grace period for, let’s say,
\ninternational brand name owner companies and who is
\ngoing to regulate that?<\/p>\n

>>Izumi Aizu: For the first question, there is a general
\nprocess of introducing gTLDs with IDN as well. But as
\nHong said, it is a fast-track for only the country code
\ntop level domains are now in place, followed by the gTLD
\nplace process later this year or next year, we would
\nlike to see this introduction.<\/p>\n

For any brand name thing, is there anybody who can
\nanswer?<\/p>\n

>>Edmon Chung: I think a couple of things. One, for the
\nnew gTLDs, I think that’s an important consideration in
\nthe whole process at ICANN as well, to protect some of
\nthe trade mark owners in terms of trade names that they
\nuse.<\/p>\n

For DotAsia, of course, when we first launched the
\nASCII domain and as now, we plan the IDN launch, we will
\nhave what we call the sunrise period, usually that’s the
\nindustry term for it, to provide some priority
\nregistration for brand owners.<\/p>\n

>>: My name Issac Mo from China.<\/p>\n

I just want to controversial to IDN, based on I’m
\ntrying to ask those experts on international domain
\nnames, you know, to what extent do you support IDN,
\nbesides commercial values and maybe cultural social, you
\nknow, values, of international domain names, for
\nexample, back to about 10 years ago, there was a Chinese
\ncompany called 3721, who provide Chinese domain names
\nresolution by providing browser plug in for users, so
\nusers can input Chinese domain names to support their
\naccess internet browser usages.<\/p>\n

But however, after about five years of collecting
\nmoney, processes, the company has been sold to Yahoo and
\nthen disappeared now totally.<\/p>\n

Right now, those Chinese domain name users, they
\nalmost all get back to English domain names for
\ndifferent international domains.<\/p>\n

So I’m also questioning that because of the other,
\nyou know, internet technologies developing themselves
\nlike search engine technologies, so most of the
\ncharacters or maybe the identifiers can be searched out
\nfrom the search engines, like in Google chrome, you can
\njust input Chinese companies name, then back to their
\ndomains, whatever it is.<\/p>\n

So the success of this, what kind of values do you
\nthink is beyond the redundancy of useability of end
\nusers? What additional comments.<\/p>\n

One of the Chinese engineering teams, they are
\nworking on Chinese version of HTML language, but it’s
\na joke, you know, they call themselves CHTML. Chinese
\nhow to make love —<\/p>\n

I just want to say that if you want to get back to
\nthose cultural steps, how much extent we should try to
\nlocalise the internet technologies to me to language or
\nback to Java script or whatever.<\/p>\n

So that’s the question to IDN experts.<\/p>\n

>>Izumi Aizu: Thank you. I’m tempted to turn the
\nmicrophone to our father of the IDN, the professor of
\nbiochemistry.<\/p>\n

>>Tan Tin Wee: I’m afraid no comments on the situation in
\nChina. I think 34721, but just illustrates to you that
\nif you can’t have a language you are familiar with, you
\ngo with the lowest hangs fruit and in this case, for
\nChinese people, Arabic numerals is something which they
\ncan easily remember, which accounts for the popularity
\nof 3721 back in those days.<\/p>\n

But regarding whether you want to carry out
\nlocalisation or not, as I said, I’m unqualified now to
\ncomment on that.<\/p>\n

>>Mo Rungang: I want to comment on the questions you raised
\nand maybe it’s my lack of understanding. I think the
\nmain part of the question of yours is the value you
\nprobably have doubts about the value of Chinese domain
\nnames.<\/p>\n

I think there is a misunderstanding about lot of
\npeople have, doesn’t have a good understanding of the
\nChinese domain names. I want to give you example to
\nsee, to help you to see the value of Chinese domain
\nnames.<\/p>\n

For a lot of Chinese people who doesn’t speak
\nEnglish or use English in their daily life, it’s very
\ndifficult for them to remember domain name. When
\nChinese domain name become available, for example,
\nI remember slides of presentation from a colleague of
\nmine, for example, say Mercedes Benz has a website
\ncalled Mercedes Benz.com. If I ask you to spell it
\ncorrectly now, I think it would be difficult for you.<\/p>\n

But if you put Mercedes in Chinese, it will be
\nremembered by everyone, so I hope you can see the value
\nof Chinese domain names by making example like that to
\nyou.<\/p>\n

I think all your questions will be summarised.
\nThat’s all I get from you, for that question. Maybe the
\nrest of the questions, you have, I think I am not able
\nto comments on those.<\/p>\n

Thank you.<\/p>\n

>>Edmon Chung: Just quickly, having been asked this
\nquestion for over 10 years, working on IDNs and working
\nat ICANN, there are two aspects. One, it is a matter of
\nworld view. There is a world view where everything is
\nuniversalised into ASCII or one language. This one
\nworld view. There is another world view where it is
\nmulticulturalism, where it is a multi-dimensional. It’s
\na diversity issue, having it itself is a statement
\nitself.<\/p>\n

Doesn’t matter whether, having the capability itself
\nis a matter.<\/p>\n

In terms of China, maybe Pinyin is quite popular,
\nbut if we put ourselves into the arabic or indic world,
\nthat might not be the same case.<\/p>\n

The second aspect is that 3721, the biggest problem
\nthere is that it’s not really standardised on the one
\nglobal root, one single global root and that goes on to
\nmy other over 10 yearses commitment at ICANN, to try to
\nmake this work, because we needed to work globally with
\n3721, it doesn’t resolve universally. At ICANN,
\nhopefully, it resolves universally and that will make
\na difference, because people will be able to access
\nChinese, Arabic, Russian domain names with a universal
\nsituation and I think it will change. Those who jump
\nthe gun in a way, sorry to use that phrase, but create
\nissues that we have to deal with and there is definitely
\na loss of some confidence in the consumers mind, but
\nI think we’ll make that up in time.<\/p>\n

>>Izumi Aizu: Any other comments, questions?<\/p>\n

>>: I used to be in localisation industry for many years.<\/p>\n

Atit Suriyakhun<\/p>\n

I just wonder, I just wonder, as domain name is part
\nof the universal resource low day for, did you see any
\nissues that have to be prevented or prepare something
\nthat — because about of using this IDN, because, for
\nexample, there’s an example of you have very similar
\nvisual representations of domain names and that’s OK.
\nI think that will be OK, if it’s only, because visually,
\nvery similar characters, when you turn into a bite, into
\ncomputer code, it is different. But once it got printed
\non paper, on that poster, you cannot really
\ndifferentiate that.<\/p>\n

This happens many times in, say, for example, if you
\ngo for book that have reference at the footnote or at
\nthe end of the books, the value of URL, universal
\nresource locater will be affected by this idea an when
\nit got transferred into something that is not
\nelectronic.<\/p>\n

Thanks.<\/p>\n

>>Izumi Aizu: Any comment from the panel?<\/p>\n

>>Edmon Chung: I didn’t quite get the gist of the question,
\nbut I think when you have it on print, that’s really
\na very important part of it, because that’s where the
\nvalue of IDNs come, because then it’s easier to
\nrecognise for people who are reading that book.
\nI assume that you would put a Chinese URL on a Chinese
\nbook rather than an Arabic URL on a Chinese book, so
\ngiven that, I think it’s easier to remember and after
\nreading the book, going to the computer, I can easily
\ntype in the URL and get to the page.<\/p>\n

I think the value is exemplified there, but I’m not
\nsure whether I’m answering the question correctly.<\/p>\n

>>Atit Suriyakhun: When you go across the languages, because
\nin many time, when you go to put a reference on paper,
\non books, many time it go across languages and I mean,
\nIDNs actually solve many language barriers, but at the
\nsame time, will it create some other language barrier as
\nwell?<\/p>\n

>>Edmon Chung: I get the question finally.<\/p>\n

I think the the way I see it, it is a world view
\nproblem. Today, if you quote a reference in Chinese
\nwhen you are writing in French, how do you quote it?
\nIt’s the — I guess the same question. If it’s Chinese
\ndomain name, then you have two choices. You can either
\nuse what is called in technical terms the Puny code,
\nwhich is an ASCII representation of it or you can use
\nthe native language which obviously is preferred, or you
\ncan provide both for your readers.<\/p>\n

So that’s sort of how I see it.<\/p>\n

>>Shariya Haniz Zulkifli: Just a little bit to add to this.
\nThis is something we raised within the Malaysian context
\nas well. Ultimately, it is a business decision, how you
\nwant people to access your information, so if the
\nwebsite is in Chinese, but you are reaching out to
\nperhaps an English speaking audience, I think you will
\nprobably not put the Chinese IDN as a reference point.
\nYou would probably register more than one.<\/p>\n

So I think organisations and businesses have to make
\nthis informed business decision on how to use IDNs and
\nmake it relevant for the target audience that you’re
\nlooking at.<\/p>\n

>>Izumi Aizu: So the ball is in the user’s side.<\/p>\n

>>Shariya Haniz Zulkifli: I think so.<\/p>\n

>>Blogie Robillo: Me again quickly. Has the issue of
\ncharacter sets been addressed, in Japanese, for example,
\nwe have several character sets, like UTF8 or shift JAS.
\nIf not, then will that be addressed or will that be
\na problem at all?<\/p>\n

>>Izumi Aizu: For the Japanese, it is not really a problem.
\nWe have some technical solution to accept different
\ncodes. It’s built into the most popular browsers and
\nthose other software.<\/p>\n

Any others? If not, I would like to close with some
\nof my remarks before thanking everybody.<\/p>\n

As predicted, the diversity or IDN in the diversity
\ncontext is very Asian and also, as Edmond said, it is
\na matter of world view whether you like the world highly
\ncomplex, complicated or simple, but in reality is, the
\nworld itself is fairly complex.<\/p>\n

How to deal with that.<\/p>\n

There are some solutions which may not cater
\neverything. But the more efficient. Others who might
\nnot be efficient, but it satisfies the various needs of
\nthe cultures and societies.<\/p>\n

The IDN, as we hear from the origin to the
\nimplementation to the 10 years from now, that it will
\ncontinue perhaps to be a very hard challenging topic.<\/p>\n

In Japan, we are trying to introduce some multiple open
\nselection process for the registry and also how to deal
\nwith the policy issues interesting and I learned
\na little bit from each countries effort.<\/p>\n

Perhaps combined, it will be a very good lesson for
\neach of you guys, because each society, cultures, have
\ndifferent context and approaches that no one can
\ndominate or any unified solution.<\/p>\n

We need to avoid fragmenttation with 1 billion users
\nin China, which may be majority of them are using only
\nChinese language, we may have difficulty in
\ncommunicating with these people from Japan or from
\nelsewhere, but internet is the global tool as Prof Xue
\nHong said, that we need some global legal framework or
\nif not, we need global monthly stakeholder forum, such
\nas IGF, for another 10 years.<\/p>\n

I really appreciate all of your effort to make this
\nmulti-stakeholder effort either be it think can context
\nof APRICOT or IGF or RIGF and we would like to see more
\nto come.<\/p>\n

With that, I would like to thank everyone.<\/p>\n

>>: Thank you. Now is the lunchtime. Lunch is served for
\nall participants. Please proceed to the left-hand side
\nfor the up will. Besides, please kindly fill in the
\nfeedback form in your welcome kit and return to the
\nregistration counter.<\/p>\n

We will be back at 2.15. Thank you.<\/p>\n","protected":false},"excerpt":{"rendered":"

Diversity: Challenges and Opportunities for Internationalized Domain Names ________________________________________________________________________ REAL TIME TRANSCRIPT: Diversity: Challenges and Opportunities for Internationalized Domain Names APrIGF 11:15-12:30, Wednesday 16 June 2010 Hong Kong DISCLAIMER: Due to the inherent difficulties in capturing a live speaker’s words, it is possible this realtime transcript may contain errors and mistranslations. An edited version of … <\/p>\n

Continue reading “APrIGF Roundtable \u2013 June 16th, 2010: Session 2”<\/span><\/a><\/p>\n","protected":false},"author":3,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":"","_links_to":"","_links_to_target":""},"class_list":["post-353","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/event.rigf.asia\/2010\/wp-json\/wp\/v2\/pages\/353","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/event.rigf.asia\/2010\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/event.rigf.asia\/2010\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/event.rigf.asia\/2010\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/event.rigf.asia\/2010\/wp-json\/wp\/v2\/comments?post=353"}],"version-history":[{"count":1,"href":"https:\/\/event.rigf.asia\/2010\/wp-json\/wp\/v2\/pages\/353\/revisions"}],"predecessor-version":[{"id":554,"href":"https:\/\/event.rigf.asia\/2010\/wp-json\/wp\/v2\/pages\/353\/revisions\/554"}],"wp:attachment":[{"href":"https:\/\/event.rigf.asia\/2010\/wp-json\/wp\/v2\/media?parent=353"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}