Re: 8 bit characters in DNS names (and URNs?)

Keld J|rn Simonsen <keld@dkuug.dk> Thu, 07 March 1996 07:16 UTC

Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa08376; 7 Mar 96 2:16 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa08372; 7 Mar 96 2:16 EST
Received: from services.Bunyip.COM by CNRI.Reston.VA.US id aa02603; 7 Mar 96 2:16 EST
Received: (from daemon@localhost) by services.bunyip.com (8.6.10/8.6.9) id BAA11766 for uri-out; Thu, 7 Mar 1996 01:45:42 -0500
Received: from mocha.bunyip.com (mocha.Bunyip.Com [192.197.208.1]) by services.bunyip.com (8.6.10/8.6.9) with SMTP id BAA11753 for <uri@services.bunyip.com>; Thu, 7 Mar 1996 01:45:38 -0500
Received: from [193.88.44.89] by mocha.bunyip.com with SMTP (5.65a/IDA-1.4.2b/CC-Guru-2b) id AA23378 (mail destined for uri@services.bunyip.com); Thu, 7 Mar 96 01:45:33 -0500
Received: (from keld@localhost) by dkuug.dk (8.6.12/8.6.12) id HAA02413; Thu, 7 Mar 1996 07:43:47 +0100
Message-Id: <199603070643.HAA02413@dkuug.dk>
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Keld J|rn Simonsen <keld@dkuug.dk>
Date: Thu, 07 Mar 1996 07:43:45 +0100
In-Reply-To: Larry Masinter <masinter@parc.xerox.com> "Re: 8 bit characters in DNS names (and URNs?)" (Mar 7, 6:13)
X-Charset: ISO-8859-1
X-Char-Esc: 29
Mime-Version: 1.0
Content-Type: Text/Plain; Charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
Mnemonic-Intro: 29
X-Mailer: Mail User's Shell (7.2.2 4/12/91)
To: Larry Masinter <masinter@parc.xerox.com>
Subject: Re: 8 bit characters in DNS names (and URNs?)
Cc: martin@terena.nl, wg-i18n@terena.nl, uri@bunyip.com
X-Orig-Sender: owner-uri@bunyip.com
Precedence: bulk

Larry Masinter writes:

> While in ASCII you can define 'case independent match' by
> performing 'translate to upper case and then use string equality',
> this does not work for other character repertoires, e.g., JIS might
> have separate codes for single and double-wide codes yet want to treat
> them equivalent for matching.
> 
> While uppercase mapping is culturally sensitive, can we not make a
> culturally independent 'character matching' algorithm that is good
> enough for directory services. Perhaps it means treating accented and
> unaccented versions of French initial capitals equivalent, even though
> this equivalence is not determined by 'canonicalization'?
> 
ISO/IEC JTC1/SC22/WG20 is producing a sorting/comparison standard
that may be used for this purpose. It has a number of levels that
the comparison may be done at, for exmaple level 1 would equivalence
all "A"s and the level could also equivalence single and double-
width encodings (of the latin letters, mostly). The standard is
ISO 14651 now appearing as WD3 and going to CD stage in May 1996.

Keld