<<<
Chronological Index
>>> <<<
Thread Index
>>>
[ga] IDN-admin should be a recommendation, not mandatory.
FYI,
>Date: Wed, 26 Mar 2003 19:10:13 +0900 (JST)
>Message-Id: <200303261010.h2QAADu07959@indra.ism.ac.jp>
>To: idn-comments@icann.org
>Subject: IDN-admin should be a recommendation, not mandatory.
>From: maruyama@nic.ad.jp
>
>Dear Sir,
>
>This might be late, but I still want to say:
>
>I think points 2 to 5 should not be made mandatory. Only point 1
>should be mandatory, but all other points should be recommendations.
>
>In Taipei JET meeting, I heard that the IDN-admin is expected to be
>released as an "Informational RFC". I strongly against to a proposal
>that ICANN mandates something that are not techinical standards but
>only informational. Also I have to point out that IDN-admin is still
>in its draft stage. In additon, JET formally decided that they do not
>ensure effectivity of IDN-amdin to languages other CJK. Why ICANN
>wants to mandate such ambiguous things? I think such an approach is
>not consistent with the principle exactly stated in the March 13 ICANN
>document:
>
>: The deployment of IDNA within existing
>: top-level domain registries is fundamentally a registry
>: responsibility, and the registries will be in the best position to
>: make appropriate implementation decisions themselves, and should have
>: the freedom to make adjustments as experience dictates.
>
>I would like to ask the Board to take my point into account.
>
>Best resgards.
>
>----
>(Mr.) NaoMASA Maruyama
>Japan Network Information Center(JPNIC)
>maruyama@nic.ad.jp
--
This message was passed to you via the ga@dnso.org list.
Send mail to majordomo@dnso.org to unsubscribe
("unsubscribe ga" in the body of the message).
Archives at http://www.dnso.org/archives.html
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|