<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"\@SimSun";
panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#0F243E;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#0F243E">Jothan,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#0F243E"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#0F243E">.com/.net supports IDNA2008.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#0F243E"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#0F243E">I think you may be onto something wrt developers (i.e. implemeters) being fixed in IDNA2003 + TR46.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#0F243E"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#0F243E">For example, the domain name “faß.de” with U+00DF:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#0F243E">IDNA2003 maps it to “fass.de” (all ASCII)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#0F243E">IDNA2008 maps it to xn--fa-hia.de (Punycode encoded form of faß.de)
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#0F243E"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#0F243E">I just tested it in Chrome and “faß.de” takes me to “fass.de” (and then redirects to a landing page), on the other hand “xn--fa-hia.de” goes to a parked page.
If Chrome was supporting IDNA2008 all the way “faß.de” and “xn--fa-hia.de” should be equivalents, and they are not. IE does the same mapping from “faß.de” to “fass.de”. Interestingly, IE didn’t recognize the punycode-encoded form of the IDN.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#0F243E"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#0F243E">Dennis<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#0F243E"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Jothan Frakes [mailto:jothan@jothan.com]
<br>
<b>Sent:</b> Tuesday, December 01, 2015 6:54 PM<br>
<b>To:</b> Tan Tanaka, Dennis<br>
<b>Cc:</b> Jin Wang; ua-international@icann.org; ua-discuss; Andre Schappo<br>
<b>Subject:</b> Re: [UA-discuss] [UA-International] IDN-as-punycode-encoded-label in Baidu search engine results<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">@Andre I like hearing a Firefox win. We deal with U-Labels and A-Labels in the domain part of a URI<br>
<br>
@Dennis-<o:p></o:p></p>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
It is good to see the Punycode at least appearing within the results of the Baidu search.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">With respect to the A-Label displaying instead of the U-Label, there's something distinct to .com and a few of the other early innovator TLDs that supported 2003 which might be at play.<br>
<br>
Which IDNA is .COM / .NET supporting? I seem to recall Verisign really being a strong contributor in early times of IDN - but due to the early innovation, importance, and support Verisign put behind advancing IDN, I seem to recall it was IDNA2003. I could
see developers noticing the ways IDNA2008 might render a name like <a href="http://xn--fiqu8s.com">
xn--fiqu8s.com</a> restricted as a variant of <a href="http://xn--fiqs8s.com">xn--fiqs8s.com</a> where it was available in IDNA2003. With registrations existing that -might- be restricted cohabitating with those that are not, I could see those developers selecting
a perfectly reasonable solution being falling back to use of punycode rather than attempting to pick and choose whose domain is or is not valid. <br>
<br>
Just a hunch. I didn't speak with Baidu<br>
<br>
-Jothan <o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><br clear="all">
<o:p></o:p></p>
<div>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
Jothan Frakes<br>
Tel: +1.206-355-0230<o:p></o:p></p>
</div>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Thu, Nov 26, 2015 at 4:13 AM, Andre Schappo <<a href="mailto:A.Schappo@lboro.ac.uk" target="_blank">A.Schappo@lboro.ac.uk</a>> wrote:<o:p></o:p></p>
<p class="MsoNormal">Hi Jin<br>
<br>
Thank you very much for the complement, but I am not an expert in East Asian languages. I am , instead, a keen amateur :) I find the East Asian languages fascinating and beautiful.<br>
<br>
Thank you very much for the link. This is really good news. Prompted by your email I found a CNNIC article
<a href="http://cnnic.cn/gywm/xwzx/rdxw/2015/201511/t20151116_53029.htm" target="_blank">
http://cnnic.cn/gywm/xwzx/rdxw/2015/201511/t20151116_53029.htm</a><br>
<br>
Yesterday I had tested weibo idn links using Safari (OSX) and they failed. The CNNIC article states they should work. So, today, I tried with Firefox (OSX) instead and the chinese IDNs work in weibo with firefox :) This is such a huge step forward. I tested
with .<span lang="ZH-CN" style="font-family:SimSun">中国</span> .<span lang="ZH-CN" style="font-family:SimSun">网络</span> .<span lang="ZH-CN" style="font-family:SimSun">公司</span> IDNs. When I get time I will try with other browsers.<br>
<br>
So, why do they work with firefox and not safari. Here are my initial and brief findings.<br>
<br>
I had a quick look at the http headers and here is what appears to be happening — Weibo's
<a href="http://t.cn" target="_blank">t.cn</a> service is returning the unicode form and not the punycode form. The
<a href="http://t.cn" target="_blank">t.cn</a> service is probably further encoding (probably percent encoding, and there may be more than one level of encoding at play). I think a backend service like
<a href="http://t.cn" target="_blank">t.cn</a> should return the punycode form. Firefox copes with this but Safari fails.<br>
<br>
When I get time I will investigate further<br>
<br>
Those of you that have a Sina Weibo account - can you please test with other browsers and Operating Systems. Here are some test chinese IDNs<br>
<a href="http://xn--1lq90imwijke8n8a9u5b.xn--fiqs8s" target="_blank">http://<span lang="ZH-CN" style="font-family:SimSun">北京电影学院</span>.<span lang="ZH-CN" style="font-family:SimSun">中国</span></a><br>
<a href="http://xn--jvr02cd1l4kh.xn--io0a7i" target="_blank">http://<span lang="ZH-CN" style="font-family:SimSun">废品回收</span>.<span lang="ZH-CN" style="font-family:SimSun">网络</span></a><br>
<a href="http://xn--oct602bexdr40b.xn--55qx5d" target="_blank">http://<span lang="ZH-CN" style="font-family:SimSun">宿迁物流</span>.<span lang="ZH-CN" style="font-family:SimSun">公司</span></a><br>
<br>
André Schappo<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
On 26 Nov 2015, at 09:49, Jin Wang wrote:<br>
<br>
> Hi Andre,<br>
><br>
> From your personal blog and sina weibo I learnt you are an expert in Eastern Asian languages, so I recommend a Chinese news clip from CNNIC's Wechat platform. I personally think it is a great achievement and do hope more IDNs and new gtlds can join the effort
& share the achievement in near future.<br>
><br>
> Apology in advance for the ridiculously long url.<br>
><br>
> The topic is "Sina Weibo Now Fully Support Chinese IDN", it basically stated "Sina Weibo now giving equal treat on to 4 mainstream Chinese IDNs as ASCII tlds"<br>
> <a href="https://mp.weixin.qq.com/s?__biz=MjM5MzQ1ODQyMQ==&mid=400695189&idx=1&sn=700fffd846a532fbc750332702f4cb08&scene=2&srcid=1116dFUQTc6sB9oBsWxCtwc6&from=timeline&isappinstalled=0&key=ff7411024a07f3ebe7630197303ce39540fa79341032bd6201895e4003deb5480e1dae74dffb38e5da9211e324c07335&ascene=0&uin=OTI0NzMyMzgw&devicetype=iMac+MacBookPro12%2C1+OSX+OSX+10.10.5+build(14F27)&version=11020201&nettype=cmnet&pass_ticket=RrQ639TbIq%2FLcvSbltUj3ojz3mNDhBbWKujwHWQWK%2FZQndGgsSMXna9Mc7CcuEeR" target="_blank">
https://mp.weixin.qq.com/s?__biz=MjM5MzQ1ODQyMQ==&mid=400695189&idx=1&sn=700fffd846a532fbc750332702f4cb08&scene=2&srcid=1116dFUQTc6sB9oBsWxCtwc6&from=timeline&isappinstalled=0&key=ff7411024a07f3ebe7630197303ce39540fa79341032bd6201895e4003deb5480e1dae74dffb38e5da9211e324c07335&ascene=0&uin=OTI0NzMyMzgw&devicetype=iMac+MacBookPro12%2C1+OSX+OSX+10.10.5+build(14F27)&version=11020201&nettype=cmnet&pass_ticket=RrQ639TbIq%2FLcvSbltUj3ojz3mNDhBbWKujwHWQWK%2FZQndGgsSMXna9Mc7CcuEeR</a><br>
><br>
> Maybe you can try to play around with some IDN urls in Weibo and see how China's biggest social media platform is doing on UA right now. Looking forward to your feedback and please do contact me if any assistance is needed.<br>
><br>
> Best Regards,<br>
> Jin<br>
><br>
> On Thu, Nov 26, 2015 at 4:33 PM, Andre Schappo <<a href="mailto:A.Schappo@lboro.ac.uk">A.Schappo@lboro.ac.uk</a>> wrote:<br>
> Hi Jin<br>
><br>
> I am intrigued by your sentence "As for the Sina Weibo, I believe our beloved colleagues from CNNIC has just achieved some milestones with Sina and the rest of us from China ICANN Community would love to join them in the action."<br>
><br>
> So, please do tell us more about this as I am really curious :)<br>
><br>
> TIA<br>
><br>
> André Schappo<br>
><br>
> On 25 Nov 2015, at 09:18, Jin Wang wrote:<br>
><br>
> > Hi Andre,<br>
> ><br>
> > Thank you very much for the suggestion. Yes we are targeting all major social media platforms\search engines\input methods\browsers- they are helping more than 760 million internet users on a daily basis.<br>
> ><br>
> > We also want all the .brand registry operators which are mainly banks and telecommunication carriers. The good news is, as you have pointed out, most of the targeted stakeholders are new gtld registry operators for their own.<br>
> ><br>
> > As for the Sina Weibo, I believe our beloved colleagues from CNNIC has just achieved some milestones with Sina and the rest of us from China ICANN Community would love to join them in the action.<br>
> ><br>
> > I will keep working with my colleagues in China and also keep you posted on our progress.<br>
> ><br>
> > Best Regards,<br>
> > Jin<br>
> ><br>
> > On Wed, Nov 25, 2015 at 4:15 PM, Andre Schappo <<a href="mailto:A.Schappo@lboro.ac.uk">A.Schappo@lboro.ac.uk</a>> wrote:<br>
> > Hi Jin<br>
> ><br>
> > Good to know of UA activities in China.<br>
> ><br>
> > It would be good if you could include Sina Weibo <span lang="ZH-CN" style="font-family:SimSun">
新浪微博</span> in your outreach initiatives. I have been waiting years for Sina Weibo to correctly handle IDNs. I had more or less given up and have not tested IDNs on their system for a long long time. The situation for years has been that Sina could only handle
the punycode form of IDNs. Prompted by this thread I tested again and some progress has been made :)<br>
> ><br>
> > So I tested by posting on Sina Weibo with <a href="http://xn--6kr28kk1brxs.xn--fiqs8s" target="_blank">
http://xn--6kr28kk1brxs.xn--fiqs8s</a> and <a href="http://xn--6kr28kk1brxs.xn--fiqs8s" target="_blank">
http://<span lang="ZH-CN" style="font-family:SimSun">南昌大学</span>.<span lang="ZH-CN" style="font-family:SimSun">中国</span></a><br>
> ><br>
> > <a href="http://xn--6kr28kk1brxs.xn--fiqs8s" target="_blank">http://xn--6kr28kk1brxs.xn--fiqs8s</a> works as it always did — linkifies ok ...but shows punycode form in popup when one hovers over the link<br>
> ><br>
> > <a href="http://xn--6kr28kk1brxs.xn--fiqs8s" target="_blank">http://<span lang="ZH-CN" style="font-family:SimSun">南昌大学</span>.<span lang="ZH-CN" style="font-family:SimSun">中国</span></a> — linkifies ok (which it did not last time I tested) & shows unicode
form in popup when one hovers over the link …but does not work when one clicks on the link<br>
> ><br>
> > …and… still waiting for the new gtld .<span lang="ZH-CN" style="font-family:SimSun">微博</span> to be delegated to DNS Root<br>
> ><br>
> > André Schappo<br>
> > <a href="http://weibo.com/andreschappo" target="_blank">http://weibo.com/andreschappo</a><br>
> ><br>
> > On 24 Nov 2015, at 16:21, Jin Wang wrote:<br>
> ><br>
> > > Hi Dennis,<br>
> > ><br>
> > > 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.<br>
> > ><br>
> > > 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:<br>
> > ><br>
> > > Firstly identify the major stakeholders (policy makers, IDN tld registries, top registrars, top search application/service providers, internet research organisations),<br>
> > ><br>
> > > Secondly gather the demands from registries' side,<br>
> > ><br>
> > > 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,<br>
> > ><br>
> > > Last but not least, we should raise the awareness among the CIOs and CMOs in China through as many channels/methods as possible.<br>
> > ><br>
> > > 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.<br>
> > ><br>
> > > Best Regards,<br>
> > > Jin<br>
> > ><br>
> > > On Tue, Nov 24, 2015 at 11:19 PM, Tan Tanaka, Dennis <<a href="mailto:dtantanaka@verisign.com">dtantanaka@verisign.com</a>> wrote:<br>
> > > Hi Jin,<br>
> > ><br>
> > ><br>
> > ><br>
> > > 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—<a href="http://ebr05n.com" target="_blank">ebr05n.com</a>” instead of ”<a href="http://xn--ebr05n.com" target="_blank"><span lang="ZH-CN" style="font-family:SimSun">墨刀</span>.com</a>”.
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.<br>
> > ><br>
> > ><br>
> > ><br>
> > > 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?<br>
> > ><br>
> > ><br>
> > ><br>
> > > Thanks,<br>
> > ><br>
> > > Dennis<br>
> > ><br>
> > ><br>
> > ><br>
> > > From: Jin Wang [mailto:<a href="mailto:jin.wang@internetregistry.info">jin.wang@internetregistry.info</a>]<br>
> > > Sent: Tuesday, November 24, 2015 1:44 AM<br>
> > > To: Tan Tanaka, Dennis<br>
> > > Cc: ua-discuss; <a href="mailto:ua-international@icann.org">ua-international@icann.org</a>; yaojk; Brent London; Don Hollander; Mark Švančárek<br>
> > > Subject: Re: [UA-discuss] [UA-International] IDN-as-punycode-encoded-label in Baidu search engine results<br>
> > ><br>
> > ><br>
> > ><br>
> > > Hi Gentelmen,<br>
> > ><br>
> > ><br>
> > ><br>
> > > 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.<br>
> > ><br>
> > ><br>
> > ><br>
> > > 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.<br>
> > ><br>
> > ><br>
> > ><br>
> > > I can voluntarily embark on finding out a viable communication channel so that we can have a dialog mechanism in the future.<br>
> > ><br>
> > ><br>
> > ><br>
> > > Best Regards,<br>
> > ><br>
> > > Jin<br>
> > ><br>
> > ><br>
> > ><br>
> > ><br>
> > ><br>
> > ><br>
> > ><br>
> > > On Tue, Nov 24, 2015 at 1:40 PM, Jiankang Yao <<a href="mailto:yaojk@cnnic.cn">yaojk@cnnic.cn</a>> wrote:<br>
> > ><br>
> > ><br>
> > ><br>
> > > I can help to talk to baidu and forward your message to them.<br>
> > ><br>
> > ><br>
> > ><br>
> > > Jiankang Yao<br>
> > ><br>
> > ><br>
> > ><br>
> > > From: Tan Tanaka, Dennis<br>
> > ><br>
> > > Date: 2015-11-24 05:45<br>
> > ><br>
> > > To: <a href="mailto:UA-discuss@icann.org">UA-discuss@icann.org</a><br>
> > ><br>
> > > CC: <a href="mailto:ua-international@icann.org">ua-international@icann.org</a><br>
> > ><br>
> > > Subject: [UA-International] IDN-as-punycode-encoded-label in Baidu search engine results<br>
> > ><br>
> > > 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.
<a href="http://xn--ebr05n.com" target="_blank">xn--ebr05n.com</a>) .<br>
> > ><br>
> > ><br>
> > ><br>
> > > Google and Yandex appear to work as expected. Bing didn’t display the domain name in the results (first two pages).<br>
> > ><br>
> > ><br>
> > ><br>
> > > 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:
<a href="http://xn--ebr05.com" target="_blank">xn--ebr05.com</a>) and what the expected result should have been (IDN displayed as Chinese domain nam. Example:
<a href="http://xn--ebr05n.com" target="_blank"><span lang="ZH-CN" style="font-family:SimSun">墨刀</span>.com</a>).<br>
> > ><br>
> > ><br>
> > ><br>
> > ><br>
> > ><br>
> > > <image001.png><br>
> > ><br>
> > ><br>
> > ><br>
> > > <image002.gif><br>
> > ><br>
> > > Dennis Tan<br>
> > > Sr. Product Manager<br>
> > ><br>
> > > Naming Services<br>
> > ><br>
> > > <a href="mailto:DTanTanaka@Verisign.com">DTanTanaka@Verisign.com</a><br>
> > ><br>
> > ><br>
> > > m: <a href="tel:571-246-7303">571-246-7303</a> t: <a href="tel:703-948-4197">
703-948-4197</a><br>
> > > 12061 Bluemont Way, Reston, VA 20190<br>
> > ><br>
> > > VerisignInc.com<br>
> > ><br>
> > > <image003.gif><br>
> > ><br>
> > ><br>
> > ><br>
> > ><br>
> > ><br>
> > ><br>
> > ><br>
> > ><br>
> > ><br>
> > ><br>
> > > --<br>
> > ><br>
> > > <span lang="ZH-CN" style="font-family:SimSun">王瑨</span><br>
> > > <span lang="ZH-CN" style="font-family:SimSun">中国区总经理</span><br>
> > > Mr. Jin Wang<br>
> > ><br>
> > > China General Manager<br>
> > ><br>
> > > <span lang="ZH-CN" style="font-family:SimSun">域通联达</span><br>
> > ><br>
> > ><br>
> > ><br>
> > > <span lang="ZH-CN" style="font-family:SimSun">中文新顶级域名市场领航者</span><br>
> > > The Market-leading New Chinese Domains<br>
> > ><br>
> > > <span lang="ZH-CN" style="font-family:SimSun">北京</span> | <span lang="ZH-CN" style="font-family:SimSun">
香港</span> | <span lang="ZH-CN" style="font-family:SimSun">赫尔辛基</span> | <span lang="ZH-CN" style="font-family:SimSun">
纽约</span> | <span lang="ZH-CN" style="font-family:SimSun">奥斯汀</span> | <span lang="ZH-CN" style="font-family:SimSun">
奥斯陆</span><br>
> > > Beijing | Hong Kong | Helsinki | New York | Austin | Oslo<br>
> > ><br>
> > > <span lang="ZH-CN" style="font-family:SimSun">移动电话</span>: <a href="tel:%2B86%20159%200110%208743">
+86 159 0110 8743</a><br>
> > > <span lang="ZH-CN" style="font-family:SimSun">电子邮件</span>: <a href="mailto:jin.wang@internetregistry.info">
jin.wang@internetregistry.info</a><br>
> > ><br>
> > ><br>
> > ><br>
> > > --<br>
> > > <span lang="ZH-CN" style="font-family:SimSun">王瑨</span><br>
> > > <span lang="ZH-CN" style="font-family:SimSun">中国区总经理</span><br>
> > > Mr. Jin Wang<br>
> > > China General Manager<br>
> > > <span lang="ZH-CN" style="font-family:SimSun">域通联达</span><br>
> > ><br>
> > ><br>
> > > <span lang="ZH-CN" style="font-family:SimSun">中文新顶级域名市场领航者</span><br>
> > > The Market-leading New Chinese Domains<br>
> > ><br>
> > > <span lang="ZH-CN" style="font-family:SimSun">北京</span> | <span lang="ZH-CN" style="font-family:SimSun">
香港</span> | <span lang="ZH-CN" style="font-family:SimSun">赫尔辛基</span> | <span lang="ZH-CN" style="font-family:SimSun">
纽约</span> | <span lang="ZH-CN" style="font-family:SimSun">奥斯汀</span> | <span lang="ZH-CN" style="font-family:SimSun">
奥斯陆</span><br>
> > > Beijing | Hong Kong | Helsinki | New York | Austin | Oslo<br>
> > ><br>
> > > <span lang="ZH-CN" style="font-family:SimSun">移动电话</span>: <a href="tel:%2B86%20159%200110%208743">
+86 159 0110 8743</a><br>
> > > <span lang="ZH-CN" style="font-family:SimSun">电子邮件</span>: <a href="mailto:jin.wang@internetregistry.info">
jin.wang@internetregistry.info</a><br>
> ><br>
> ><br>
> ><br>
> ><br>
> ><br>
> ><br>
> > --<br>
> > <span lang="ZH-CN" style="font-family:SimSun">王瑨</span><br>
> > <span lang="ZH-CN" style="font-family:SimSun">中国区总经理</span><br>
> > Mr. Jin Wang<br>
> > China General Manager<br>
> > <span lang="ZH-CN" style="font-family:SimSun">域通联达</span><br>
> ><br>
> ><br>
> > <span lang="ZH-CN" style="font-family:SimSun">中文新顶级域名市场领航者</span><br>
> > The Market-leading New Chinese Domains<br>
> ><br>
> > <span lang="ZH-CN" style="font-family:SimSun">北京</span> | <span lang="ZH-CN" style="font-family:SimSun">
香港</span> | <span lang="ZH-CN" style="font-family:SimSun">赫尔辛基</span> | <span lang="ZH-CN" style="font-family:SimSun">
纽约</span> | <span lang="ZH-CN" style="font-family:SimSun">奥斯汀</span> | <span lang="ZH-CN" style="font-family:SimSun">
奥斯陆</span><br>
> > Beijing | Hong Kong | Helsinki | New York | Austin | Oslo<br>
> ><br>
> > <span lang="ZH-CN" style="font-family:SimSun">移动电话</span>: <a href="tel:%2B86%20159%200110%208743">
+86 159 0110 8743</a><br>
> > <span lang="ZH-CN" style="font-family:SimSun">电子邮件</span>: <a href="mailto:jin.wang@internetregistry.info">
jin.wang@internetregistry.info</a><br>
><br>
><br>
><br>
><br>
> --<br>
> <span lang="ZH-CN" style="font-family:SimSun">王瑨</span><br>
> <span lang="ZH-CN" style="font-family:SimSun">中国区总经理</span><br>
> Mr. Jin Wang<br>
> China General Manager<br>
> <span lang="ZH-CN" style="font-family:SimSun">域通联达</span><br>
><br>
><br>
> <span lang="ZH-CN" style="font-family:SimSun">中文新顶级域名市场领航者</span><br>
> The Market-leading New Chinese Domains<br>
><br>
> <span lang="ZH-CN" style="font-family:SimSun">北京</span> | <span lang="ZH-CN" style="font-family:SimSun">
香港</span> | <span lang="ZH-CN" style="font-family:SimSun">赫尔辛基</span> | <span lang="ZH-CN" style="font-family:SimSun">
纽约</span> | <span lang="ZH-CN" style="font-family:SimSun">奥斯汀</span> | <span lang="ZH-CN" style="font-family:SimSun">
奥斯陆</span><br>
> Beijing | Hong Kong | Helsinki | New York | Austin | Oslo<br>
><br>
> <span lang="ZH-CN" style="font-family:SimSun">移动电话</span>: <a href="tel:%2B86%20159%200110%208743">
+86 159 0110 8743</a><br>
> <span lang="ZH-CN" style="font-family:SimSun">电子邮件</span>: <a href="mailto:jin.wang@internetregistry.info">
jin.wang@internetregistry.info</a><o:p></o:p></p>
</div>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</body>
</html>