RE: [registrars] IDN Representative

["Tim Ruiz" <tim@godaddy.com>]

>I am confident that I will have the integrity to knowledge
>and experience I have gained over the last few years working
>with IDN to good use for the community.

> - transition strategy that takes into consideration current
> installed base

Edmon,

Your two comments above have me concerned, and seem to conflict. I don't
believe the current installed base of ad hoc IDN implementations should have
the consideration you imply. Please keep in mind that first an foremost you
represent registrars as a whole, not just those who have attempted their own
versions of an IDN implementation.

Best regards,
Tim Ruiz
Go Daddy Software, Inc.

-----Original Message-----
From: owner-registrars@dnso.org [mailto:owner-registrars@dnso.org]On
Behalf Of Edmon Chung
Sent: Tuesday, January 21, 2003 7:15 AM
To: registrars@dnso.org
Subject: [registrars] IDN Representative

Hi Everyone,

----- Original Message -----
From: "Michael D. Palage" <michael@palage.com>
> 1) Affirmation of IDN Representatives. Edmon from Neteka and Yann from
> Momentus were elected as the Registrar IDN Representative.

First of all, thank you for voting myself as a Registrar IDN Representative.
In response to Nikolaj's earlier comments, I would like to say that although
I am working in Canada right now, I grew up in Hongkong and does have an
Asian background that I can bring to the discussions.  Also, yes, Neteka is
a vendor of IDN products, but our solution is standards driven, and most
important of all, I am confident that I will have the integrity to knowledge
and experience I have gained over the last few years working with IDN to
good use for the community.

Also, as I will be voicing the concerns for registrars in the committee,
here are what I stand for for IDNs in the context of a registrar:

- open standard protocol
- transition strategy that takes into consideration current installed base
- fully functional multilingual domain names
- character equivalence mapping (Charprep) enabled for continued
user-friendliness
- registry responsibility to provide charprep information and support
- clear indication and specification of charprep support for registrars to
implement

I look forward to any feedback, comments or concerns anyone may have, and to
represent the constituency well.

Edmon