[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [idn] Proposal to re-prohibit U+3002



From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: [idn] Proposal to re-prohibit U+3002
Date: Mon, 29 Jan 2001 13:25:07 -0800

> U+3002 was prohibited in nameprep-00 because of its similarity to 
> U+002E, but it is allowed in nameprep-02. The nameprep design team 
> has tentatively agreed that we should revise nameprep to prohibit 
> U+3002, not because it looks like U+002E (in fact, in many fonts, 
> they look different), but because it is used as if it were U+002E in 
> input mechanisms. This would allow IME makers to safely map U+3002 to 
> U+002E *before* doing nameprep without worrying about preventing 
> users from accessing legitimate host name parts.

I think prohibiting U+3002 is essential.  Actually some Japanese vocal
groups using it as name, so that some people oppose or nervous
prohibiting it, but using it is harmful in technical reason.  Names
using U+3002 looks like domain name, but actually it is a single word,
then DNS queries for that name will cause TLD query to the root
servers.

I explained this problem at APAN/TransPAC/NLANR/Internet2 Techs
Workshop today.  The presentation material will be available soon from
the following URL.
http://www.ncne.nlanr.net/training/techs/2001/0128/mtgnotice.html

P.S.
Next version of mDNkit will provide such delimiter mapping as a part
of localization functionality.  mDNkit is distributed at JPNIC's web
page as opensource with BSD-like license.  It is now included in ISC
BIND's (BIND-8.2.3 / BIND-9.1.0) contrib area.

-- 
Yoshiro YONEYA <yone@po.ntts.co.jp>
           aka <yone@nic.ad.jp>