[UA-discuss] [UA-International] IDN-as-punycode-encoded-label in Baidu search engine results

Tue Nov 24 16:21:17 UTC 2015

Hi Dennis,

Sorry for the confusion caused, I did miss your point, and yes of course
you are definitely right about the a-label showing on the search result.

As for the plan for China UA task, actually there is an existing yet very
strong 'ICANN community' in China. we are working together to form a
combined effort in UA by:

Firstly identify the major stakeholders (policy makers, IDN tld registries,
top registrars, top search application/service providers, internet research
organisations),

Secondly gather the demands from registries' side,

Thirdly we need to interview the search engines and input methods companies
to analyse the potential technical obstacles-- with the interests of a
stakeholder group rather than one tld at a time,

Last but not least, we should raise the awareness among the CIOs and CMOs
in China through as many channels/methods as possible.

The current obstacles for this China group to join the UA discuss are their
working language (which is mainly Chinese) & the time difference.
Nonetheless we still want to make more contribution to ICANN UA by helping
the localization of any UA related document and sharing first-hand
feedbacks from Chinese 'netizens' and internet service providers.

Best Regards,
Jin

On Tue, Nov 24, 2015 at 11:19 PM, Tan Tanaka, Dennis <
dtantanaka at verisign.com> wrote:

> Hi Jin,
>
>
>
> Perhaps I was not clearly enough in my note. I was referring to the fifth
> search result on the picture. Note that the URL is “xn—ebr05n.com”
> instead of ”墨刀.com”. The point is that the a-label should not be
> displayed to the end user. The application should have identified the label
> as an IDN and as such transformed it to Unicode. That didn’t happen here.
>
>
>
> On your other note, if you can elaborate a plan on how to engage these
> companies in China, that would be extremely welcome. Could we discuss your
> high level plan in two weeks from today?
>
>
>
> Thanks,
>
> Dennis
>
>
>
> *From:* Jin Wang [mailto:jin.wang at internetregistry.info]
> *Sent:* Tuesday, November 24, 2015 1:44 AM
> *To:* Tan Tanaka, Dennis
> *Cc:* ua-discuss; ua-international at icann.org; yaojk; Brent London; Don
> Hollander; Mark Švančárek
> *Subject:* Re: [UA-discuss] [UA-International]
> IDN-as-punycode-encoded-label in Baidu search engine results
>
>
>
> Hi Gentelmen,
>
>
>
> I reckoned the term Dennis used is an IDN.com but all the BAIDU results
> just took the Chinese key words (the parts that were high-lighted in
> red)--- it barely has anything to do with domain name. It is really hard to
> come to the conclusion that BAIDU is supporting IDNs in their search engine.
>
>
>
> At present, Baidu is the leading search engine in China but there are
> still a handful companies providing similar services in China. Therefore,
> instead of having one or two experts talking to the companies one by one, I
> suggest we'd better make a combined effort to talk to a group of companies
> - search engines, mailbox service provider, input methods (for Chinese
> pinyin), and also some of the smartphone manufacturers. As most of them are
> competing locally rather than globally, it might works better to start
> within China, especially when some of the world's biggest player is in
> absence in China.
>
>
>
> I can voluntarily embark on finding out a viable communication channel so
> that we can have a dialog mechanism in the future.
>
>
>
> Best Regards,
>
> Jin
>
>
>
>
>
>
>
> On Tue, Nov 24, 2015 at 1:40 PM, Jiankang Yao <yaojk at cnnic.cn> wrote:
>
>
>
> I can help to talk to baidu and forward your message to them.
>
>
> ------------------------------
>
> Jiankang Yao
>
>
>
> *From:* Tan Tanaka, Dennis <dtantanaka at verisign.com>
>
> *Date:* 2015-11-24 05:45
>
> *To:* UA-discuss at icann.org
>
> *CC:* ua-international at icann.org
>
> *Subject:* [UA-International] IDN-as-punycode-encoded-label in Baidu
> search engine results
>
> Often times I hear that IDNs are not indexed by certain search engines.
> While I know this is not true, the example below doesn’t help my case
> either (at least not 100%). Here is an example where the IDN I’m looking
> for is showing up in the first 5 search results on Baidu (see picture
> below). However, the string is displayed as the punycode-encoded label
> instead of the corresponding Chinese IDN (i.e. xn--ebr05n.com) .
>
>
>
> Google and Yandex appear to work as expected. Bing didn’t display the
> domain name in the results (first two pages).
>
>
>
> Is there someone interested (and with the language skills) in taking the
> action item to reach out to Baidu? This might be in the form of opening a
> bug ticket to explain the problem (IDN is displayed as punycode-encoded
> label. Example: xn--ebr05.com) and what the expected result should have
> been (IDN displayed as Chinese domain nam. Example: 墨刀.com).
>
>
>
>
>
>
>
> [image: Verisign]
>
> *Dennis Tan *
> Sr. Product Manager
>
> Naming Services
>
> DTanTanaka at Verisign.com
>
>
> m: 571-246-7303 t: 703-948-4197
> 12061 Bluemont Way, Reston, VA 20190
>
> VerisignInc.com <http://www.verisigninc.com/>
>
> [image: Verisign™]
>
>
>
>
>
>
>
>
>
> --
>
> *王瑨*
>
> 中国区总经理
>
> *Mr. Jin Wang *
>
> China General Manager
>
> 域通联达
>
>
>
>
>
> 中文新顶级域名市场领航者
>
> *The Market-leading New Chinese Domains*
>
>
>
> 北京 | 香港 | 赫尔辛基 | 纽约 | 奥斯汀 | 奥斯陆
>
> Beijing | Hong Kong | Helsinki | New York | Austin | Oslo
>
>
>
> 移动电话: +86 159 0110 8743
>
> 电子邮件: jin.wang at internetregistry.info
>

-- 

*王瑨*

中国区总经理
*Mr. Jin Wang *
China General Manager

域通联达

中文新顶级域名市场领航者

*The Market-leading New Chinese Domains*

北京 | 香港 | 赫尔辛基 | 纽约 | 奥斯汀 | 奥斯陆

Beijing | Hong Kong | Helsinki | New York | Austin | Oslo

移动电话: +86 159 0110 8743

电子邮件: jin.wang at internetregistry.info
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/ua-discuss/attachments/20151125/7174c98c/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 43511 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/ua-discuss/attachments/20151125/7174c98c/image001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.gif
Type: image/gif
Size: 3105 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/ua-discuss/attachments/20151125/7174c98c/image003.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.gif
Type: image/gif
Size: 131 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/ua-discuss/attachments/20151125/7174c98c/image002.gif>