IETF Logo Mail Archive

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

"Santosh Chokhani" <chokhani@orionsec.com> Thu, 13 April 2006 16:34 UTC

Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FU4lj-0001ig-9z for pkix-archive@lists.ietf.org; Thu, 13 Apr 2006 12:34:07 -0400
Received: from balder-227.proper.com ([192.245.12.227]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FU4lh-0002cB-Ou for pkix-archive@lists.ietf.org; Thu, 13 Apr 2006 12:34:07 -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 k3DFi51k048910; Thu, 13 Apr 2006 08:44:05 -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 k3DFi5wm048909; Thu, 13 Apr 2006 08:44:05 -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 EXVS01.ex.dslextreme.net (exvs01.ex.dslextreme.net [66.51.199.51]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3DFi5KI048887 for <ietf-pkix@imc.org>; Thu, 13 Apr 2006 08:44:05 -0700 (MST) (envelope-from chokhani@orionsec.com)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Subject: RE: Last Call summary for draft-ietf-pkix-cert-utf8
Date: Thu, 13 Apr 2006 08:43:59 -0700
Message-ID: <82D5657AE1F54347A734BDD33637C8790241A90C@EXVS01.ex.dslextreme.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Last Call summary for draft-ietf-pkix-cert-utf8
Thread-Index: AcZfEN1FcpDaP1ASSpaEm0TDfaPbbgAADLXg
From: Santosh Chokhani <chokhani@orionsec.com>
To: Russ Housley <housley@vigilsec.com>, ietf-pkix@imc.org
Cc: iesg@ietf.org
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by balder-227.proper.com id k3DFi5KI048904
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.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64

Russ,

Looks good to me.

-----Original Message-----
From: owner-ietf-pkix@mail.imc.org [mailto:owner-ietf-pkix@mail.imc.org]
On Behalf Of Russ Housley
Sent: Thursday, April 13, 2006 10:33 AM
To: ietf-pkix@imc.org
Cc: iesg@ietf.org
Subject: RE: Last Call summary for draft-ietf-pkix-cert-utf8


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?

Russ


At 07:36 AM 4/13/2006, Santosh Chokhani wrote:
>When strings are mapped from internal representations to visual
>representations, sometimes two different strings will have
>the same visual representations.  This can happen due to similar
glyphs,
>multiple items being combined into a single glyph among other reasons.
>When
>this happens 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 these facts.

v2.23.0 | Report a Bug | By Email