Kc normalization enough or not?
Lawrence Greenfield <leg+@andrew.cmu.edu> Thu, 21 March 2002 15:30 UTC
Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g2LFUhC14865 for ietf-sasl-bks; Thu, 21 Mar 2002 07:30:43 -0800 (PST)
Received: from lin2.andrew.cmu.edu (LIN2.ANDREW.CMU.EDU [128.2.6.35]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g2LFUf414853 for <ietf-sasl@imc.org>; Thu, 21 Mar 2002 07:30:41 -0800 (PST)
Received: from penguin.andrew.cmu.edu (PENGUIN.ANDREW.CMU.EDU [128.2.121.100]) by lin2.andrew.cmu.edu (8.12.3.Beta0/8.12.2.Beta3) with ESMTP id g2LFUf4F031365; Thu, 21 Mar 2002 10:30:42 -0500
Date: Thu, 21 Mar 2002 10:30:41 -0500
Message-Id: <200203211530.g2LFUf4F031365@lin2.andrew.cmu.edu>
From: Lawrence Greenfield <leg+@andrew.cmu.edu>
X-Mailer: BatIMail version 3.3
To: John Gardiner Myers <jgmyers@netscape.com>
Cc: ietf-sasl@imc.org
Subject: Kc normalization enough or not?
Mime-Version: 1.0 (generated by tm-edit 7.106)
Content-Type: text/plain; charset="US-ASCII"
Sender: owner-ietf-sasl@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sasl/mail-archive/>
List-ID: <ietf-sasl.imc.org>
List-Unsubscribe: <mailto:ietf-sasl-request@imc.org?body=unsubscribe>
If you take a look at the latest kerberos attempt at i18n, you'll see that they've defined a profile of stringprep with more than just Kc normalization. Should we follow their lead? Some of what they're doing (changing all spaces to the US-ASCII SP character) I think is harmful but maybe other things are useful. The krb draft is draft-ietf-krb-wg-utf8-profile-00. Larry
- Kc normalization enough or not? Lawrence Greenfield