RE: Last Call summary for draft-ietf-pkix-cert-utf8

"Kurt D. Zeilenga" <Kurt@OpenLDAP.org> Thu, 13 April 2006 16:51 UTC

Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FU52k-00016O-Q0 for pkix-archive@lists.ietf.org; Thu, 13 Apr 2006 12:51:42 -0400
Received: from balder-227.proper.com ([192.245.12.227]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FU52k-00033c-9o for pkix-archive@lists.ietf.org; Thu, 13 Apr 2006 12:51:42 -0400
Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3DG5sDn050440; Thu, 13 Apr 2006 09:05:54 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id k3DG5snb050439; Thu, 13 Apr 2006 09:05:54 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3DG5ri2050433 for <ietf-pkix@imc.org>; Thu, 13 Apr 2006 09:05:53 -0700 (MST) (envelope-from Kurt@OpenLDAP.org)
Received: from gypsy.OpenLDAP.org (24-205-218-53.dhcp.crcy.nv.charter.com [24.205.218.53] (may be forged)) (authenticated bits=0) by boole.openldap.org (8.13.3/8.13.3) with ESMTP id k3DG5oLh018427 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 13 Apr 2006 16:05:50 GMT (envelope-from Kurt@OpenLDAP.org)
Message-Id: <7.0.1.0.0.20060413090435.03a03908@OpenLDAP.org>
X-Mailer: QUALCOMM Windows Eudora Version 7.0.1.0
Date: Thu, 13 Apr 2006 09:05:26 -0700
To: Russ Housley <housley@vigilsec.com>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: RE: Last Call summary for draft-ietf-pkix-cert-utf8
Cc: ietf-pkix@imc.org, iesg@ietf.org
In-Reply-To: <7.0.0.16.2.20060413102956.059d9560@vigilsec.com>
References: <82D5657AE1F54347A734BDD33637C8790241A5B3@EXVS01.ex.dslextreme.net> <7.0.0.16.2.20060413102956.059d9560@vigilsec.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf-pkix@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-pkix/mail-archive/>
List-ID: <ietf-pkix.imc.org>
List-Unsubscribe: <mailto:ietf-pkix-request@imc.org?body=unsubscribe>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f

At 07:32 AM 4/13/2006, Russ Housley wrote:

>I suggest the following.  I think it adds the concept of "similar looking."
>
>   When strings are mapped from internal representations to visual representations,
>   sometimes two different strings will have the same or similar visual representations.
>   This can happen for many different reasons, including use of similar glyphs and
>   multiple items being combined into a single glyph.  As a result of this situation,
>   people doing visual comparisons between two different names may think they are
>   the same when in fact they are not.  Also, people may mistake one string for
>   another.  Issuers of certificates and relying parties both need to be aware of
>   this situation.
>
>This does not impose any untestable requirements.  Any concerns with this text?

This text adequately addresses my concern.  Thanks, Kurt